Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
NCM ICT Security Principles is a framework for ICT security published and maintained by the Norwegian National Security Authority (NSM). The security principles advice businesses and organisations on how to protect their information systems from unauthorized access, damage or misuse.
NCM ICT Security Principles is a framework for ICT security published and maintained by the Norwegian National Security Authority (NSM). The security principles advise businesses and organisations on how to protect their information systems from unauthorized access, damage or misuse.
The principles focus on technological and organisational measures. Measures concerning physical security and the human perspective are generally not covered. The measures apply to both unintentional and intentional acts, although the main focus is on intentional acts.
In this framework there are 21 security principles with a total of 118 security measures, distributed across four categories: i) identify, ii) protect and maintain, iii) detect and iv) respond and recover.
Below you'll find all of the requirements of this framework. In Cyberday, we map all requirement to global tasks, making multi-compliance management easy. Do it once, and see the progress across all frameworks!
Co-ordinate and communicate with internal and external stakeholders while managing the incident. This could be the organisations system management team, the executive management, in-house departments and other organisation’s that may be affected by the incident. Organisations should also adopt a media strategy for incidents that may be of interest to the media and wider public.
Perform necessary activities after the incident. The severity of the incident and the organisation’s expertise and capacity will determine which activities are required and whether they should be conducted by internal or external personnel. It could involve:
• Investigation to determine the root cause of the incident, including:
o Type of malware
o Threat actor
o Attack vector
o Tools
o How the sequence of events unfolded, and how the threat actor behaved.
• Preparing a summary that the management can understand and act on.
• Communication with relevant parties, including sector-specific computer emergency response teams
and/or NSM NCSC.
Identify experiences and lessons learnt from incidents, both things that worked and things that could be improved.
Review identified compromised security measures to prevent a similar incident from occurring. Determine whether the established measures are adequate for the organisation’s risk tolerance.
Assess the effectiveness of processes, procedures, reporting formats and organisational structures related to incident response. Review regularly, also after an incident, and update based on any lessons learnt.
Communicate and share findings with relevant stakeholders, and use actual stories from the incident response to train and raise awareness amongst staff.
Explore our comprehensive resources and improve your security with the themes of this framework.
Discover specific ways our platform streamlines your ISO 27001 compliance process, from automated controls to audit preparation.
Explore use caseTake our comprehensive assessment to identify gaps in your current implementation and get personalized recommendations.
Start assessmentDive deeper with our articles, case studies, and expert insights on framework implementation.
Read articleGet a concise overview of all requirements, controls, and implementation steps in our quick guide.
Get the guideSee how the overlap and differences with any other framework to optimize your compliance strategy.
Compare frameworkParticipate in expert-led sessions covering implementation strategies, common pitfalls, and best practices for compliance.
Register for webinarParticipate in expert-led sessions covering implementation strategies, common pitfalls, and best practices for compliance.
Register for webinarUnderstand the basics of cyber security frameworks with our comprehensive guide.
Read the articleWhen building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.
Sets the overall compliance standard or regulation your organization needs to follow.
Break down the framework into specific obligations that must be met.
Concrete actions and activities your team carries out to satisfy each requirement.
Documented rules and practices that are created and maintained as a result of completing tasks.