Endpoint Cybersecurity GmbH is proud to sponsor the volleyball team of 12-16 years old from TV Langenargen.
Endpoint Cybersecurity’s CEO, Sorin Mustaca proudly taking a photo together with the team.
We wrote here https://www.sorinmustaca.com/how-to-nis2-eu-directive/ that the 3rd step in implementing the requirements of the directive is to establish a cybersecurity framework.
If you haven’t read what a cybersecurity framework means, then you should read article: https://www.sorinmustaca.com/demystifying-cybersecurity-terms-policy-standard-procedure-controls-framework/ .
Establishing a cybersecurity framework is critically important for organizations of all sizes and types because it is the basis on which you build your cybersecurity. The cybersecurity framework is the basis of the ISMS, which represents the plan of your cybersecurity strategy.
In case you still wonder if you need a cybersecurity framework, here are several key reasons why it is essential:
Protection against Cyber Threats
Cyber threats are constantly evolving and becoming more sophisticated. A cybersecurity framework provides a structured approach to identifying and mitigating these threats, reducing the risk of data breaches, cyberattacks, and other security incidents.
Risk Management
Cybersecurity frameworks help organizations assess their cybersecurity risks and prioritize their efforts to address the most critical vulnerabilities. This risk-based approach ensures that resources are allocated where they are needed most.
Compliance and Legal Requirements
Many industries and regions have specific cybersecurity regulations and legal requirements that organizations must adhere to. A cybersecurity framework provides a roadmap for meeting these compliance obligations, reducing the risk of fines and legal repercussions.
Business Continuity
Cybersecurity incidents can disrupt business operations, leading to downtime, financial losses, and damage to reputation. A well-structured cybersecurity framework helps organizations prepare for and respond to incidents, minimizing their impact and ensuring business continuity.
Protection of Sensitive Data
Organizations store vast amounts of sensitive and confidential data, including customer information, financial records, and intellectual property. A cybersecurity framework helps safeguard this data from unauthorized access or theft.
Preservation of Reputation
A security breach can seriously damage an organization’s reputation and erode customer trust. Implementing a cybersecurity framework demonstrates a commitment to security, which can enhance the organization’s reputation and instill confidence among customers, partners, and stakeholders.
Cost Savings
Proactively addressing cybersecurity through a framework can ultimately save an organization money. Preventing security incidents is more cost-effective than dealing with the aftermath of a breach, which can involve significant financial and legal expenses.
Consistency and Standardization
Cybersecurity frameworks promote consistency and standardization of security practices across an organization. This is especially important in larger enterprises with multiple locations, business units, or teams, ensuring that security measures are applied uniformly.
Continuous Improvement
Cyber threats and technology evolve rapidly. A cybersecurity framework emphasizes the importance of ongoing monitoring, assessment, and improvement, helping organizations stay ahead of emerging threats and vulnerabilities.
Competitive Advantage
Having a robust cybersecurity framework can be a competitive advantage. It can differentiate an organization in the eyes of customers, partners, and investors who prioritize security when choosing business partners.
Choosing a cybersecurity framework is a tedious process and potentially long. If you want to succeed, then you need to plan for it. In order to create a project plan, follow these milestones:
Assess Organizational Needs and Objectives
Begin by understanding your organization’s specific cybersecurity needs, objectives, and goals. Consider the industry you operate in, the types of data you handle, and your organization’s size and complexity.
Identify Relevant Regulations and Standards
Determine which cybersecurity regulations, standards, and compliance requirements are applicable to your organization. These may include GDPR, HIPAA, ISO 27001, NIST, CIS Controls, TISAX, ISO 21434 and industry-specific regulations.
Conduct a Risk Assessment
Perform a comprehensive risk assessment to identify potential cybersecurity threats, vulnerabilities, and the potential impact of security incidents. This assessment will help you prioritize security measures.
Define Your Scope
Clearly define the scope of your cybersecurity efforts. Consider which systems, data, and assets are in scope for protection and compliance efforts. Document this scope in detail.
Research Existing Frameworks
Investigate existing cybersecurity frameworks and standards that align with your organization’s needs and objectives. Consider well-established frameworks like NIST Cybersecurity Framework, ISO 27001, CIS Controls, and others.
Have a look here to view a comparison. Consider country-specific frameworks like the recommendations or requirements from your country’s information security agency.
Evaluate Framework Alignment
Evaluate how closely each candidate framework aligns with your organization’s requirements, risk assessment findings, and compliance obligations. Consider factors like ease of implementation and ongoing maintenance.
Customization vs. Adoption
Decide whether to adopt an existing framework as-is or customize it to fit your organization’s specific needs. Customization may be necessary to address unique risks or industry-specific requirements.
Engage Stakeholders
Involve key stakeholders, including senior leadership, IT teams, compliance experts, and legal advisors, in the decision-making process. Ensure their input and buy-in throughout the framework selection or development process.
Develop Framework Documentation
If you choose to customize or create a framework, develop comprehensive documentation that outlines the framework’s policies, procedures, controls, and guidelines. This documentation serves as a roadmap for the implementation of the ISMS.
Implement and Test
Begin implementing the selected or customized framework within your organization. Test its effectiveness in addressing cybersecurity risks and compliance requirements.
Training and Awareness
Train employees and raise awareness about the cybersecurity framework, its policies, and best practices. Ensure that everyone in the organization understands their role in maintaining security.
Continuous Monitoring and Improvement
Establish ongoing monitoring and assessment processes to ensure the framework’s effectiveness. Regularly review and update the framework to adapt to evolving threats and technology.
There are some things to keep in mind when implementing the project plan for choosing the cybersecurity framework. The project can easily go out of scope because of the security landscape continuously changing.
Please review regularly these considerations and make sure you go through the list before taking any big decisions.
Alignment with Objectives: Ensure that the chosen framework aligns with your organization’s cybersecurity objectives, risk profile, and compliance requirements.
Applicability: Consider the framework’s applicability to your industry and specific business needs.
Resource Requirements: Assess the resources (financial, human, and technological) required for framework implementation and maintenance.
Scalability: Determine whether the framework can scale with your organization’s growth and evolving cybersecurity needs.
Integration: Ensure that the framework can integrate with existing security technologies and processes within your organization.
Cost vs. Benefit: Evaluate the cost-effectiveness of implementing and maintaining the framework relative to the expected security benefits and risk reduction.
Accessibility of Expertise: Consider the availability of expertise and training resources related to the chosen framework.
Audit and Certification: If compliance or certification is a goal, verify that the framework is recognized and accepted by relevant certification bodies or authorities.
Legal and Privacy Considerations: Ensure that the framework supports compliance with relevant data protection and privacy laws.
Flexibility: Assess the framework’s flexibility to adapt to changing threat landscapes and emerging technologies.
Conclusions
Having a robust cybersecurity framework can be a competitive advantage. It can differentiate an organization in the eyes of customers, partners, and investors who prioritize security when choosing business partners.
Remember that selecting or creating a cybersecurity framework is not a one-size-fits-all process. It should be a thoughtful and strategic decision that aligns with your organization’s unique needs and circumstances.
Establishing a cybersecurity framework is essential to protect an organization’s digital assets, manage risks effectively, comply with legal requirements, and maintain the trust of stakeholders.
The post NIS2: 3.Establish a cybersecurity framework first appeared on Sorin Mustaca on Cybersecurity.
We wrote here https://www.sorinmustaca.com/how-to-nis2-eu-directive/ that the 3rd step in implementing the requirements of the directive is to establish a cybersecurity framework.
If you haven’t read what a cybersecurity framework means, then you should read article: https://www.sorinmustaca.com/demystifying-cybersecurity-terms-policy-standard-procedure-controls-framework/ .
An ISMS is typically based on the ISO 27001 standard, which provides a framework for establishing, implementing, maintaining, and continually improving information security within an organization.
Establishing a cybersecurity framework is usually achieved together with, or while implementing an Information Security Management System (ISMS) based on a standard like ISO 27001. So, before going to the NIS2 Step 3, I must explain why is it important to have a “good” ISMS.
This article will guide you through the steps to create a solid foundation for the ISMS which uses a cybersecurity framework.
Here are the steps you must follow to implement your ISMS:
Get Top Management Support
Before you start, synchronize with the top management in order to define company’s goals in this regard. Usually it should be clear, since the company strives to receive a certification like ISO 27001, ISO 16949, TISAX, CSMS, etc..
Then secure the commitment and support of senior management by helping them understand the necessary resources and efforts.
In all standards that require an ISMS it is imperative to have the commitment of the management because their feedback and support are required in several places along the way.
Scope Definition
Define the scope of your ISMS: determine which assets, processes, and locations will be covered by the ISMS.
This will help in setting boundaries for your security efforts. Some certifications require an assessment per location and scope, so this needs to be developed properly and in accordance with company’s goals.
Risk Assessment
Create policies that help identify and assess information security risks.
This involves:
How to identifying assets: List all the information assets your organization handles, such as data, hardware, software, and personnel, intellectual property.
How to identify threats and vulnerabilities: Determine potential risks and vulnerabilities that could impact your assets.
How to assess risks: Analyze the likelihood and potential impact of these risks.
How to calculate risk levels: Prioritize risks based on their severity.
Risk Treatment
Develop a policy for risk treatment plan:
How to implement controls: Select and implement security controls and measures to mitigate identified risks.
Document policies and procedures that enforce the creation of security controls.
Allocate responsibilities: Assign roles and responsibilities for managing and monitoring security measures.
Set risk acceptance criteria: Determine which risks can be accepted, mitigated, or transferred.
Establish the ISMS Framework
Establish the ISMS framework based on ISO 27001:
Define information security objectives.
Develop an information security policy.
Create a risk assessment methodology.
Define criteria for risk acceptance.
Develop and implement security controls.
Implementation
Execute the ISMS based on the established framework:
Train employees: Provide information security training to all staff members.
Implement security controls: Put in place the technical, administrative, and physical controls identified in your risk treatment plan.
Monitor and review: Continuously monitor the effectiveness of your controls and review your risk assessment.
Measurement and Evaluation
Regularly measure and evaluate the performance of your ISMS to ensure that it remains effective and aligned with your objectives.
Conduct internal audits.
Perform security testing (e.g., penetration testing, vulnerability scanning).
Analyze security incident data.
Management Review
Conduct regular management reviews to assess the ISMS’s performance and effectiveness.
Ensure that the ISMS is aligned with the organization’s strategic goals.
Make improvements based on review findings.
Continual Improvement
Use the results of audits, reviews, and incidents to continually improve the ISMS.
Update policies and procedures as needed.
Enhance security controls based on new threats and vulnerabilities.
Maintain employee awareness and training.
Certification (Optional):
If your organization desires ISO 27001 or any other certification, engage an accredited certification body to perform an external audit and certification assessment.
Be careful because several certification require a pre-certification or pre-assessment performed either with in-house auditors (internal) or external auditors.
Documentation
Maintain detailed documentation of all ISMS activities, including policies, procedures, risk assessments, and audit reports.
Maintain a log of all changes in time, because this demonstrates continual improvement and usage.
Training and Awareness
Continuously educate and raise awareness among employees regarding information security policies and best practices.
Incident Response and Recovery
Develop an incident response plan to address security incidents promptly and effectively.
Remember, and make sure that your management remembers as well, that implementing and maintaining an ISMS is an ongoing process. Even if certifications are renewed only after 3 years (usually) it is important that in these 3 years the ISMS is lived.
Regularly update your risk assessments and adapt your security controls to evolving threats and business needs. Continuous improvement is key to the success of your ISMS.
The post How to implement an Information Security Management System (ISMS) first appeared on Sorin Mustaca on Cybersecurity.
We wrote here https://www.sorinmustaca.com/how-to-nis2-eu-directive/ that the first step in implementing NIS2 requirements is to perform a gap analysis.
The most critical part when performing a gap analysis is to define upfront against which standard or security framework are you comparing the existing situation.
It is usual when performing a gap analysis of security maturity to compare against ISO 27000 standard, the ISO 27001 in particular.
Performing a gap analysis on the security stance of a company following ISO 27001 involves comparing its current security measures and practices against the requirements specified in the ISO 27001 standard.
This analysis helps identify areas where the company’s security posture aligns with the standard (compliance) and areas where there are gaps or deficiencies (non-compliance). Here’s a technical breakdown of the process:
Familiarize with ISO 27001
Understand the ISO 27001 standard and its security requirements. This includes studying the Annex A controls, which represent a comprehensive set of security best practices.
Define the Scope
Determine the scope of the analysis, starting with which areas of the organization’s security management system (SMS) will be assessed, such as specific departments, processes, assets, or locations.
Then focus on which parts of the company’s operations will be assessed. This could include networks, systems, applications, physical security, personnel, and other relevant components.
Keep in mind that usually the goal of the company is not reaching ISO 27001 compliance but to see their maturity level and see how prepared they are cybersecurity events and incidents.
This means that the parallel to ISO 27001 controls (see below) should not be extremely strict, unless the goal really is achieving the ISO 27001 certification.
Conduct Interviews and Gather Information
Collaborate with key stakeholders, security personnel, and IT staff to collect relevant documentation.
Relevant documentation is anything related to the company’s security practices, policies, procedures, risk assessments, and controls.
This includes also security manuals, configuration details, system logs, incident reports, risk assessments, and other related documents.
Create a Gap Analysis Checklist
Develop a detailed checklist that maps the ISO 27001 controls to the company’s existing security controls and practices. The checklist should include relevant information for each control, such as descriptions, implementation status, supporting evidence, and any gaps or deviations. Always keep in mind what was decided in “2. Define the scope”, because this will give you the depth of the analysis.
Assess Current Security Controls for Non-Compliance
For each control in the checklist, assess whether the company has implemented the control as specified by ISO 27001. Evaluate the effectiveness of the existing controls in meeting the standard’s requirements. Identify gaps and areas where the company’s security measures do not meet the standard’s expectations. These gaps may include missing controls, insufficient implementation, inadequate documentation, or deviations from best practices.
Prioritize and Rate the Gaps
Classify the identified gaps based on their severity and potential impact on security. Assign a risk rating to each gap to help prioritize remediation efforts.
Propose Remediation Measures
For each identified gap, suggest specific remediation measures to address the deficiencies. These measures should align with ISO 27001 requirements and aim to improve the company’s security posture.
Create an Action Plan
Create a detailed action plan that outlines the steps to be taken to address each identified gap. This plan should include timelines, responsibilities, and resources required for implementation.
Reassess and Update
Periodically repeat the gap analysis process to assess the company’s security stance and ensure continuous improvement. Regularly review and update the action plan based on new threats, changes in the organization’s structure, or updates to the ISO 27001 standard.Develop an
Monitor and Review Progress
Once the action plan is underway, monitor the progress of each remediation effort and periodically review the improvements made. Track the status of the gaps and ensure that the company is moving towards full compliance with ISO 27001.
References:
https://www.sorinmustaca.com/how-to-nis2-eu-directive/
ISO 27001: www.iso.org/standard/27001
https://www.sorinmustaca.com/executive-summary-nis2-directive-for-the-eu-members/
The NIS2 Directive is a European Union legislative text on cybersecurity that supersedes the first NIS (Network and Information Security) Directive, adopted in July 2016.
While the first NIS (Network and Information Security) Directive increased the Member States’ cybersecurity capabilities, its implementation proved difficult, resulting in fragmentation at different levels across the internal market. To respond to the growing threats posed with digitalisation and the surge in cyber-attacks, the Commission has submitted a proposal to replace the NIS Directive and thereby strengthen the security requirements, address the security of supply chains, streamline reporting obligations, and introduce more stringent supervisory measures and stricter enforcement requirements, including harmonised sanctions across the EU.
NIS2 strengthens security requirements in the EU by expanding the NIS scope to more sectors and entities, taking into account
the security of supply chains,
streamlining reporting obligations,
introducing monitoring measures,
introducing more stringent enforcement requirements,
adding the concept of “management bodies” accountability within companies, and
harmonizing and tightening sanctions in all Member States.
To achieve the above mentioned goals, NIS2 requires member states to take a number of measures that forces them to work together:
Establish or improve information sharing between member states and a common incident response plan that coordinates with other member state plans
Establish a national Computer Emergency Response Team
Strengthen cooperation between public and private sector entities
In a nutshell, companies can stay compliant with the NIS2 Directive by
establishing an effective monitoring system that can detect intrusions, detect suspicious activities, and alert the authorities when necessary
developing comprehensive plans that detail how they will respond to an attack and what steps they will take to recover from it.
The official website of the EU for the NIS2 Directive has prepared an FAQ with many good questions and answers.
However, what the website is not saying (for good reasons) is how should companies start to prepare for implementing the directive.
In order to successfully start implementing the requirements, the following steps should be implemented in this order. We will publish articles about pretty much each of these topics.
Assess your company’s current cybersecurity practices, policies, and infrastructure against the requirements of the NIS2 directive.
Identify any gaps or areas that need improvement to comply with the directive.
Appoint an individual or a team responsible for overseeing the implementation of the NIS2 directive within your company. This could be a dedicated cybersecurity team or an existing department with relevant expertise.
Develop or update your company’s cybersecurity framework to align with the NIS2 directive. This framework should include policies, procedures, and technical controls to protect your network and information systems effectively.
Conduct a comprehensive risk assessment of your company’s network and information systems. Identify potential threats, vulnerabilities, and risks that may impact the availability, integrity, and confidentiality of critical systems and data. This assessment will help you prioritize security measures and allocate appropriate resources. Risk management and assessments are an ongoing process. Once one risk assessment is carried out, it is important to schedule regular updates to ensure all steps are maintained.
Based on the risk assessment findings, implement appropriate security measures to mitigate identified risks. This may include network segmentation, access controls, intrusion detection systems, incident response procedures, encryption, employee training, and regular security updates, among others.
Develop an incident response plan and establish procedures for detecting, responding to, and recovering from cybersecurity incidents. Ensure the assigned employees are trained on how to recognize and report security breaches promptly. Business continuity is a very complex topic, which must be planned with a lot of time in advance and it requires extra resources (both human and financial).
Implement mechanisms to continuously monitor and assess your network and information systems for potential threats. Regularly review and update your cybersecurity measures to adapt to emerging risks and changes in the threat landscape.
Keep comprehensive documentation of your cybersecurity measures, risk assessments, incident response activities, and any other relevant information. This documentation will serve as evidence of compliance and may be required for regulatory audits or investigations. A good record might save your company legal and regulatory repercussions in case of a major incident (cyber related or not).
Stay informed about any reporting or notification obligations outlined in the NIS2 directive. Establish communication channels with the relevant regulatory authorities and comply with any reporting requirements or inquiries they may have. NIS2 strives to improve EU-wide communication and sharing of cyber events in order to better prepare answers and reactions. Communication has never been more important than now.
10. Define KPIs for cybersecurity and measures taken based on them
In order to measure the effectiveness of the cybersecurity, you need to define metrics that allow identifying and quantifying changes. Example of metrics are number of incidents, types of incidents, how many trainings have been made, how many people were trained, how many pentests were made and how many issues were identified, and many more.
Next:
We will address the first topic: Perform a gap analysis.
The NIS 2 Directive is a set of cybersecurity guidelines and requirements established by the European Union (EU) . It replaces and repeals the NIS Directive (Directive 2016/1148/EC) . The full name of the directive is “Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive)” .
The NIS 2 Directive aims to improve cybersecurity risk management and introduce reporting obligations across sectors such as energy, transport, health, and digital infrastructure . It provides legal measures to boost the overall level of cybersecurity in the EU .
The directive covers a larger share of the economy and society by including more sectors, which means that more entities are obliged to take measures to increase their level of cybersecurity .
The management bodies of essential and important entities must approve the cybersecurity risk-management measures taken by those entities, oversee its implementation, and can be held liable for infringements .
The NIS 2 Directive significantly expands the sectors and type of critical entities falling under its scope.
As a ground rule, companies from certain areas that meet these conditions are affected:
Essential Entities (EE):
at least 250 employees and
50 Mil € revenue
Important Entities (IE):
at least 50 employees and
10 Mil € revenue
NIS 2 covers areas such as
Essential Entities:
energy (electricity, district heating and cooling, oil, gas and hydrogen);
transport (air, rail, water and road); banking;
financial market infrastructures;
health including manufacture of pharmaceutical products including vaccines;
drinking water;
waste water;
digital infrastructure (internet exchange points; DNS service providers;
TLD name registries; cloud computing service providers;
data centre service providers;
content delivery networks;
trust service providers;
providers of public electronic communications networks and publicly available electronic communications services);
ICT service management (managed service providers and managed security service providers), public administration and space.
Important Entities:
postal and courier services;
waste management;
chemicals;
food;
manufacturing of medical devices, computers and electronics, machinery and equipment, motor vehicles, trailers and semi-trailers and other transport equipment;
digital providers (online market places, online search engines, and social networking service platforms) and research organisations.
Note:
An entity may still be considered “essential” or “important” even if it does not meet the size criteria, in specific cases such as when it is the sole provider of a critical service for societal or economic activity in a Member State.
The Member States have until October 17, 2024, to adopt and publish the measures necessary to comply with the NIS 2 Directive. They shall apply those measures from October 18, 2024 .
The benefits of the NIS 2 directive include creating the necessary cyber crisis management structure (CyCLONe), increasing the level of harmonization regarding security requirements and reporting obligations, encouraging Members States to introduce new areas of interest such as supply chain, vulnerability management, core internet, and cyber hygiene in their national cybersecurity strategies, bringing novel ideas such as peer reviews for enhancing collaboration and knowledge sharing amongst Member States .
In order to comply with the NIS 2 directive, entities will need to take measures to increase their level of cybersecurity. This may include following training for members of management bodies of essential and important entities as well as offering similar training to their employees on a regular basis .
The NIS 2 Directive replaces the previous Network and Information Security (NIS) Directive, which was the first piece of EU-wide legislation on cybersecurity. Its specific aim was to achieve a high common level of cybersecurity across the Member States .
While the NIS Directive increased the Member States’ cybersecurity capabilities, its implementation proved difficult, resulting in fragmentation at different levels across the internal market. To respond to the growing threats posed by digitalization and the surge in cyber-attacks, the Commission submitted a proposal to replace the NIS Directive and thereby strengthen security requirements, address security of supply chains, streamline reporting obligations, and introduce more stringent supervisory measures and stricter enforcement requirements, including harmonized sanctions across the EU .
The proposed expansion of the scope covered by NIS 2, by effectively obliging more entities and sectors to take measures, would assist in increasing the level of cybersecurity in Europe in the longer term . The NIS 2 Directive establishes very strict sanctions for breaches of its obligations. In contrast to the previous NIS Directive, which merely required Member States to set forth effective, proportionate and dissuasive penalties for non-compliance, the NIS 2 Directive introduces a much stricter regime .
NIS 2 will introduce a fining regime for non-compliance. The potential maximum fines for non-compliance could reach either
(i) €10 million or 2% of global annual turnover for “essential” entities or
(ii) €7 million or 1.4% of global annual turnover for “important” entities .
Who is affected?DeadlinesHow does the NIS 2 Directive differ from the previous directive?ConsequencesNext
The NIS 2 Directive is a set of cybersecurity guidelines and requirements established by the European Union (EU) . It replaces and repeals the NIS Directive (Directive 2016/1148/EC) . The full name of the directive is “Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive)” .
The NIS 2 Directive aims to improve cybersecurity risk management and introduce reporting obligations across sectors such as energy, transport, health, and digital infrastructure . It provides legal measures to boost the overall level of cybersecurity in the EU .
The directive covers a larger share of the economy and society by including more sectors, which means that more entities are obliged to take measures to increase their level of cybersecurity .
The management bodies of essential and important entities must approve the cybersecurity risk-management measures taken by those entities, oversee its implementation, and can be held liable for infringements .
The NIS 2 Directive significantly expands the sectors and type of critical entities falling under its scope.
As a ground rule, companies from certain areas that meet these conditions are affected:
Essential Entities (EE):
at least 250 employees and
50 Mil € revenue
Important Entities (IE):
at least 50 employees and
10 Mil € revenue
NIS 2 covers areas such as
Essential Entities:
energy (electricity, district heating and cooling, oil, gas and hydrogen);
transport (air, rail, water and road); banking;
financial market infrastructures;
health including manufacture of pharmaceutical products including vaccines;
drinking water;
waste water;
digital infrastructure (internet exchange points; DNS service providers;
TLD name registries; cloud computing service providers;
data centre service providers;
content delivery networks;
trust service providers;
providers of public electronic communications networks and publicly available electronic communications services);
ICT service management (managed service providers and managed security service providers), public administration and space.
Important Entities:
postal and courier services;
waste management;
chemicals;
food;
manufacturing of medical devices, computers and electronics, machinery and equipment, motor vehicles, trailers and semi-trailers and other transport equipment;
digital providers (online market places, online search engines, and social networking service platforms) and research organisations.
Note:
An entity may still be considered “essential” or “important” even if it does not meet the size criteria, in specific cases such as when it is the sole provider of a critical service for societal or economic activity in a Member State.
The Member States have until October 17, 2024, to adopt and publish the measures necessary to comply with the NIS 2 Directive. They shall apply those measures from October 18, 2024 .
The benefits of the NIS 2 directive include creating the necessary cyber crisis management structure (CyCLONe), increasing the level of harmonization regarding security requirements and reporting obligations, encouraging Members States to introduce new areas of interest such as supply chain, vulnerability management, core internet, and cyber hygiene in their national cybersecurity strategies, bringing novel ideas such as peer reviews for enhancing collaboration and knowledge sharing amongst Member States .
In order to comply with the NIS 2 directive, entities will need to take measures to increase their level of cybersecurity. This may include following training for members of management bodies of essential and important entities as well as offering similar training to their employees on a regular basis .
The NIS 2 Directive replaces the previous Network and Information Security (NIS) Directive, which was the first piece of EU-wide legislation on cybersecurity. Its specific aim was to achieve a high common level of cybersecurity across the Member States .
While the NIS Directive increased the Member States’ cybersecurity capabilities, its implementation proved difficult, resulting in fragmentation at different levels across the internal market. To respond to the growing threats posed by digitalization and the surge in cyber-attacks, the Commission submitted a proposal to replace the NIS Directive and thereby strengthen security requirements, address security of supply chains, streamline reporting obligations, and introduce more stringent supervisory measures and stricter enforcement requirements, including harmonized sanctions across the EU .
The proposed expansion of the scope covered by NIS 2, by effectively obliging more entities and sectors to take measures, would assist in increasing the level of cybersecurity in Europe in the longer term . The NIS 2 Directive establishes very strict sanctions for breaches of its obligations. In contrast to the previous NIS Directive, which merely required Member States to set forth effective, proportionate and dissuasive penalties for non-compliance, the NIS 2 Directive introduces a much stricter regime .
NIS 2 will introduce a fining regime for non-compliance. The potential maximum fines for non-compliance could reach either
(i) €10 million or 2% of global annual turnover for “essential” entities or
(ii) €7 million or 1.4% of global annual turnover for “important” entities .
Who is affected?DeadlinesHow does the NIS 2 Directive differ from the previous directive?ConsequencesNext
The NIS 2 Directive is a set of cybersecurity guidelines and requirements established by the European Union (EU) . It replaces and repeals the NIS Directive (Directive 2016/1148/EC) . The full name of the directive is “Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive)” .
The NIS 2 Directive aims to improve cybersecurity risk management and introduce reporting obligations across sectors such as energy, transport, health, and digital infrastructure . It provides legal measures to boost the overall level of cybersecurity in the EU .
The directive covers a larger share of the economy and society by including more sectors, which means that more entities are obliged to take measures to increase their level of cybersecurity .
The management bodies of essential and important entities must approve the cybersecurity risk-management measures taken by those entities, oversee its implementation, and can be held liable for infringements .
The NIS 2 Directive significantly expands the sectors and type of critical entities falling under its scope.
As a ground rule, companies from certain areas that meet these conditions are affected:
Essential Entities (EE):
at least 250 employees and
50 Mil € revenue
Important Entities (IE):
at least 50 employees and
10 Mil € revenue
NIS 2 covers areas such as
Essential Entities:
energy (electricity, district heating and cooling, oil, gas and hydrogen);
transport (air, rail, water and road); banking;
financial market infrastructures;
health including manufacture of pharmaceutical products including vaccines;
drinking water;
waste water;
digital infrastructure (internet exchange points; DNS service providers;
TLD name registries; cloud computing service providers;
data centre service providers;
content delivery networks;
trust service providers;
providers of public electronic communications networks and publicly available electronic communications services);
ICT service management (managed service providers and managed security service providers), public administration and space.
Important Entities:
postal and courier services;
waste management;
chemicals;
food;
manufacturing of medical devices, computers and electronics, machinery and equipment, motor vehicles, trailers and semi-trailers and other transport equipment;
digital providers (online market places, online search engines, and social networking service platforms) and research organisations.
Note:
An entity may still be considered “essential” or “important” even if it does not meet the size criteria, in specific cases such as when it is the sole provider of a critical service for societal or economic activity in a Member State.
The Member States have until October 17, 2024, to adopt and publish the measures necessary to comply with the NIS 2 Directive. They shall apply those measures from October 18, 2024 .
The benefits of the NIS 2 directive include creating the necessary cyber crisis management structure (CyCLONe), increasing the level of harmonization regarding security requirements and reporting obligations, encouraging Members States to introduce new areas of interest such as supply chain, vulnerability management, core internet, and cyber hygiene in their national cybersecurity strategies, bringing novel ideas such as peer reviews for enhancing collaboration and knowledge sharing amongst Member States .
In order to comply with the NIS 2 directive, entities will need to take measures to increase their level of cybersecurity. This may include following training for members of management bodies of essential and important entities as well as offering similar training to their employees on a regular basis .
The NIS 2 Directive replaces the previous Network and Information Security (NIS) Directive, which was the first piece of EU-wide legislation on cybersecurity. Its specific aim was to achieve a high common level of cybersecurity across the Member States .
While the NIS Directive increased the Member States’ cybersecurity capabilities, its implementation proved difficult, resulting in fragmentation at different levels across the internal market. To respond to the growing threats posed by digitalization and the surge in cyber-attacks, the Commission submitted a proposal to replace the NIS Directive and thereby strengthen security requirements, address security of supply chains, streamline reporting obligations, and introduce more stringent supervisory measures and stricter enforcement requirements, including harmonized sanctions across the EU .
The proposed expansion of the scope covered by NIS 2, by effectively obliging more entities and sectors to take measures, would assist in increasing the level of cybersecurity in Europe in the longer term . The NIS 2 Directive establishes very strict sanctions for breaches of its obligations. In contrast to the previous NIS Directive, which merely required Member States to set forth effective, proportionate and dissuasive penalties for non-compliance, the NIS 2 Directive introduces a much stricter regime .
NIS 2 will introduce a fining regime for non-compliance. The potential maximum fines for non-compliance could reach either
(i) €10 million or 2% of global annual turnover for “essential” entities or
(ii) €7 million or 1.4% of global annual turnover for “important” entities .
Who is affected?DeadlinesHow does the NIS 2 Directive differ from the previous directive?ConsequencesNext
The NIS 2 Directive is a set of cybersecurity guidelines and requirements established by the European Union (EU) . It replaces and repeals the NIS Directive (Directive 2016/1148/EC) . The full name of the directive is “Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive)” .
The NIS 2 Directive aims to improve cybersecurity risk management and introduce reporting obligations across sectors such as energy, transport, health, and digital infrastructure . It provides legal measures to boost the overall level of cybersecurity in the EU .
The directive covers a larger share of the economy and society by including more sectors, which means that more entities are obliged to take measures to increase their level of cybersecurity .
The management bodies of essential and important entities must approve the cybersecurity risk-management measures taken by those entities, oversee its implementation, and can be held liable for infringements .
The NIS 2 Directive significantly expands the sectors and type of critical entities falling under its scope.
As a ground rule, companies from certain areas that meet these conditions are affected:
Essential Entities (EE):
at least 250 employees and
50 Mil € revenue
Important Entities (IE):
at least 50 employees and
10 Mil € revenue
NIS 2 covers areas such as
Essential Entities:
energy (electricity, district heating and cooling, oil, gas and hydrogen);
transport (air, rail, water and road); banking;
financial market infrastructures;
health including manufacture of pharmaceutical products including vaccines;
drinking water;
waste water;
digital infrastructure (internet exchange points; DNS service providers;
TLD name registries; cloud computing service providers;
data centre service providers;
content delivery networks;
trust service providers;
providers of public electronic communications networks and publicly available electronic communications services);
ICT service management (managed service providers and managed security service providers), public administration and space.
Important Entities:
postal and courier services;
waste management;
chemicals;
food;
manufacturing of medical devices, computers and electronics, machinery and equipment, motor vehicles, trailers and semi-trailers and other transport equipment;
digital providers (online market places, online search engines, and social networking service platforms) and research organisations.
Note:
An entity may still be considered “essential” or “important” even if it does not meet the size criteria, in specific cases such as when it is the sole provider of a critical service for societal or economic activity in a Member State.
The Member States have until October 17, 2024, to adopt and publish the measures necessary to comply with the NIS 2 Directive. They shall apply those measures from October 18, 2024 .
The benefits of the NIS 2 directive include creating the necessary cyber crisis management structure (CyCLONe), increasing the level of harmonization regarding security requirements and reporting obligations, encouraging Members States to introduce new areas of interest such as supply chain, vulnerability management, core internet, and cyber hygiene in their national cybersecurity strategies, bringing novel ideas such as peer reviews for enhancing collaboration and knowledge sharing amongst Member States .
In order to comply with the NIS 2 directive, entities will need to take measures to increase their level of cybersecurity. This may include following training for members of management bodies of essential and important entities as well as offering similar training to their employees on a regular basis .
The NIS 2 Directive replaces the previous Network and Information Security (NIS) Directive, which was the first piece of EU-wide legislation on cybersecurity. Its specific aim was to achieve a high common level of cybersecurity across the Member States .
While the NIS Directive increased the Member States’ cybersecurity capabilities, its implementation proved difficult, resulting in fragmentation at different levels across the internal market. To respond to the growing threats posed by digitalization and the surge in cyber-attacks, the Commission submitted a proposal to replace the NIS Directive and thereby strengthen security requirements, address security of supply chains, streamline reporting obligations, and introduce more stringent supervisory measures and stricter enforcement requirements, including harmonized sanctions across the EU .
The proposed expansion of the scope covered by NIS 2, by effectively obliging more entities and sectors to take measures, would assist in increasing the level of cybersecurity in Europe in the longer term . The NIS 2 Directive establishes very strict sanctions for breaches of its obligations. In contrast to the previous NIS Directive, which merely required Member States to set forth effective, proportionate and dissuasive penalties for non-compliance, the NIS 2 Directive introduces a much stricter regime .
NIS 2 will introduce a fining regime for non-compliance. The potential maximum fines for non-compliance could reach either
(i) €10 million or 2% of global annual turnover for “essential” entities or
(ii) €7 million or 1.4% of global annual turnover for “important” entities .
Who is affected?DeadlinesHow does the NIS 2 Directive differ from the previous directive?ConsequencesNext
The NIS 2 Directive is a set of cybersecurity guidelines and requirements established by the European Union (EU) . It replaces and repeals the NIS Directive (Directive 2016/1148/EC) . The full name of the directive is “Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive)” .
The NIS 2 Directive aims to improve cybersecurity risk management and introduce reporting obligations across sectors such as energy, transport, health, and digital infrastructure . It provides legal measures to boost the overall level of cybersecurity in the EU .
The directive covers a larger share of the economy and society by including more sectors, which means that more entities are obliged to take measures to increase their level of cybersecurity .
The management bodies of essential and important entities must approve the cybersecurity risk-management measures taken by those entities, oversee its implementation, and can be held liable for infringements .
The NIS 2 Directive significantly expands the sectors and type of critical entities falling under its scope.
As a ground rule, companies from certain areas that meet these conditions are affected:
Essential Entities (EE):
at least 250 employees and
50 Mil € revenue
Important Entities (IE):
at least 50 employees and
10 Mil € revenue
NIS 2 covers areas such as
Essential Entities:
energy (electricity, district heating and cooling, oil, gas and hydrogen);
transport (air, rail, water and road); banking;
financial market infrastructures;
health including manufacture of pharmaceutical products including vaccines;
drinking water;
waste water;
digital infrastructure (internet exchange points; DNS service providers;
TLD name registries; cloud computing service providers;
data centre service providers;
content delivery networks;
trust service providers;
providers of public electronic communications networks and publicly available electronic communications services);
ICT service management (managed service providers and managed security service providers), public administration and space.
Important Entities:
postal and courier services;
waste management;
chemicals;
food;
manufacturing of medical devices, computers and electronics, machinery and equipment, motor vehicles, trailers and semi-trailers and other transport equipment;
digital providers (online market places, online search engines, and social networking service platforms) and research organisations.
Note:
An entity may still be considered “essential” or “important” even if it does not meet the size criteria, in specific cases such as when it is the sole provider of a critical service for societal or economic activity in a Member State.
The Member States have until October 17, 2024, to adopt and publish the measures necessary to comply with the NIS 2 Directive. They shall apply those measures from October 18, 2024 .
The benefits of the NIS 2 directive include creating the necessary cyber crisis management structure (CyCLONe), increasing the level of harmonization regarding security requirements and reporting obligations, encouraging Members States to introduce new areas of interest such as supply chain, vulnerability management, core internet, and cyber hygiene in their national cybersecurity strategies, bringing novel ideas such as peer reviews for enhancing collaboration and knowledge sharing amongst Member States .
In order to comply with the NIS 2 directive, entities will need to take measures to increase their level of cybersecurity. This may include following training for members of management bodies of essential and important entities as well as offering similar training to their employees on a regular basis .
The NIS 2 Directive replaces the previous Network and Information Security (NIS) Directive, which was the first piece of EU-wide legislation on cybersecurity. Its specific aim was to achieve a high common level of cybersecurity across the Member States .
While the NIS Directive increased the Member States’ cybersecurity capabilities, its implementation proved difficult, resulting in fragmentation at different levels across the internal market. To respond to the growing threats posed by digitalization and the surge in cyber-attacks, the Commission submitted a proposal to replace the NIS Directive and thereby strengthen security requirements, address security of supply chains, streamline reporting obligations, and introduce more stringent supervisory measures and stricter enforcement requirements, including harmonized sanctions across the EU .
The proposed expansion of the scope covered by NIS 2, by effectively obliging more entities and sectors to take measures, would assist in increasing the level of cybersecurity in Europe in the longer term . The NIS 2 Directive establishes very strict sanctions for breaches of its obligations. In contrast to the previous NIS Directive, which merely required Member States to set forth effective, proportionate and dissuasive penalties for non-compliance, the NIS 2 Directive introduces a much stricter regime .
NIS 2 will introduce a fining regime for non-compliance. The potential maximum fines for non-compliance could reach either
(i) €10 million or 2% of global annual turnover for “essential” entities or
(ii) €7 million or 1.4% of global annual turnover for “important” entities .
