NIS2 Directive
NIS2 Directive
Companies are under pressure to comply with NIS2. You can help.
NIS2 brings significant change to the European Union (EU) cybersecurity landscape by imposing stricter requirements on a wider range of organizations.
With ConnectSecure, you can help your clients navigate and comply with this complex framework.
Our all-in-one platform for vulnerability management and compliance supports NIS2’s risk management and mitigation criteria, while simplifying the entire compliance process. With features such as vulnerability assessments, automated remediation, continuous monitoring, and compliance benchmarking, you can position your MSP as an industry leader in security and compliance.
5 major components of NIS2 compliance
Covered Entities
NIS2 applies to organizations providing “essential or important services.”
Essential entities are large organizations that operate across 11 critical sectors, including:
- Energy
- Transport
- Banking
- Financial Market Infrastructure
- Health
- Drinking Water
- Waste Water
- Digital Infrastructure
- ICT Service Management (B2B)
- Public Administration
- Space
Important entities are medium-sized organizations that operate in seven areas of high criticality, including:
- Postal and Courier Services
- Waste Management
- Manufacture, Production and Distribution of Chemicals
- Production, Processing and Distribution of Food
- Manufacturing
- Digital Providers
- Research
Large companies are those with at least 250 employees, an annual turnover of at least €50 million, or an annual balance sheet of at least €43 million, whereas medium companies are those with at least 50 employees, an annual turnover of at least €10 million, or a €10 million balance sheet.
Risk Management
Article 21 of the framework specifies cybersecurity risk management measures that Member States are expected to build on based on the criticality and size of covered entities. The 10 broad measures include:
- Risk Management: Policies on risk analysis and information system security.
- Incident Response: Procedures for handling and reporting cybersecurity incidents.
- Continuity Planning: Business continuity measures, including backup management, disaster recovery, and crisis management.
- Supply Chain: Security measures for relationships between entities and their direct suppliers or service providers.
- System Security: Practices for secure acquisition, development, and maintenance of network and information systems, including vulnerability handling and disclosure.
- Effectiveness Assessment: Policies and procedures to evaluate the impact of cybersecurity risk-management measures.
- Training: Implementation of basic cyber hygiene practices and cybersecurity training programs.
- Encryption: Policies and procedures regarding the use of cryptography and, where appropriate, encryption techniques.
- Access Control: Human resources security measures, access control policies, and asset management strategies.
- Authentication: Deployment of multifactor or continuous authentication solutions, secured communications systems, and emergency communication tools within the entity, as appropriate.
Leadership Responsibilities
Management bodies, including senior management and executive leadership, must participate in the development, implementation, and management of their organization’s cybersecurity initiatives and programs. They’re also required to undergo risk management and cybersecurity training, and it’s recommended that employees undergo the same training. Should a cybersecurity incident occur due to gross negligence of management, they can be held criminally liable.
Supply Chain Security
NIS2 broadly mandates organizations to strengthen supply chain security. Organizations should assess and understand the risks associated with suppliers and vendors, implement appropriate security measures based on those risks, and regularly monitor and respond to ongoing supplier risk. Organizations may be considered non-compliant should they conduct business with high-risk third parties in the supply chain, meaning that organizations who fall outside the original scope of NIS2 may still be required to comply.
Incident Reporting
Covered entities must report incidents with the potential to cause severe operational disruptions or financial loss to the covered entity or other entities. Three incident reports must be submitted to the national computer security response incident response team (CSIRT):
- Initial report: Submitted within 24 hours of becoming aware of an incident and outlining the type of incident and its expected impact.
- Follow-up report: Submitted within 72 hours of becoming aware of an incident and including an assessment of the incident as well as details of its severity and impact.
- Comprehensive report: Submitted within one month of the incident and including details of remediation efforts and what initiatives have been implemented to mitigate risk in the future.
Vulnerability Assessment: Identify vulnerabilities and exposures across operating systems, networks, and applications by scanning for over 240,000 known risks from our in-depth database.
Automated Scanning & Remediation: Proactively monitor ongoing risk and set up automated remediation tools to ensure gaps are identified and closed immediately.
EPSS Scoring: Build an evidence-based risk management and remediation strategy with the Exploit Predication Scoring System (EPSS), that helps you categorize and prioritize vulnerabilities.
Policy Creation & Evaluation: Fulfill the policy requirements of Article 21 with GPO policy downloads and policy evaluation tools that measure your alignment.
External Scanning: Get an external view of your client’s network perimeter with advanced Attack Surface Management and mapping tools.
Access Control Management: Define user access controls for sensitive data and resources, enforce multi-factor authentication, and receive instant notifications of anomalies to prevent unauthorized access.
Compliance Benchmarking: Use comparative analysis tools to measure and improve your NIS2 compliance performance against globally recognized standards.
Audit-readiness: Prove compliance to NIS2 assessors with easy access to white labeled reports, multi-level reports, role-specific reports and customization options.
The business case for NIS2 compliance
NIS2 compliance is sure to be challenging for resource-constrained organizations, but MSPs are uniquely positioned to handle both the security components and the regulatory requirements of the framework. By guiding your clients through all aspects of the process, you help them achieve regulatory compliance, boost their revenue, and reduce financial risk.