NSM ICT Security Principles (Norway)

Requirement

3.3.2: Establish and maintain expertise on the desired state of the organisation’s information systems

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

Establish and maintain expertise on the desired state of the organisation’s information systems to be able to detect changes or abnormalities that could indicate unauthorised actions. The desired state needs to be managed over time and should reflect any restructuring, reorganisation, acquisitions, mergers, staff redundancies and changes to the operational concept. Knowledge of the information systems should be good enough that it is possible to identify anomalies that represent a threat. This could include:
• Data flow in breach of permitted data flow as per principle 2.5 – Control data flow
• Data flow at abnormal times and which is not deemed normal traffic.
• Abnormal volumes of data flowing through the network.

Fulfill this requirement by completing the tasks below ->

This requirement is part of the framework:

NSM ICT Security Principles (Norway)

Other requirements of the framework

3.3.2: Establish and maintain expertise on the desired state of the organisation’s information systems

Best practices

How to implement:

3.3.2: Establish and maintain expertise on the desired state of the organisation’s information systems

This policy on

3.3.2: Establish and maintain expertise on the desired state of the organisation’s information systems

provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

Establish and maintain expertise on the desired state of the organisation’s information systems to be able to detect changes or abnormalities that could indicate unauthorised actions. The desired state needs to be managed over time and should reflect any restructuring, reorganisation, acquisitions, mergers, staff redundancies and changes to the operational concept. Knowledge of the information systems should be good enough that it is possible to identify anomalies that represent a threat. This could include:
• Data flow in breach of permitted data flow as per principle 2.5 – Control data flow
• Data flow at abnormal times and which is not deemed normal traffic.
• Abnormal volumes of data flowing through the network.

Read below what concrete actions you can take to improve this ->

Frameworks that include requirements for this topic:

No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to

3.3.2: Establish and maintain expertise on the desired state of the organisation’s information systems

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

No other tasks found.

Complete these tasks in Cyberday ISMS ->

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement

3.3.2: Establish and maintain expertise on the desired state of the organisation’s information systems

of the framework

NSM ICT Security Principles (Norway)

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Network usage log and process for detecting inappropriate network traffic

Critical

High

Normal

Low

Technical cyber security

Network security

Network usage log and process for detecting inappropriate network traffic

This task helps you comply with the following requirements

I11: Poikkeamien havainnointikyky ja toipuminen Katakri

12.4.1: Event logging ISO 27001

13.1.1: Network controls ISO 27001

PR.AC-3: Remote access management NIST

PR.AC-5: Network integrity NIST

Evaluation process and documentation of significant security-related changes

Critical

High

Normal

Low

Risk management and leadership

Risk management

Evaluation process and documentation of significant security-related changes

This task helps you comply with the following requirements

Članak 30.1.a: Politike analize rizika i sigurnosti informacijskih sustava NIS2 Croatia

7 §: Riskienhallinta Kyberturvallisuuslaki

5.2.1: Change management TISAX

30 § 3.1°: L'analyse des risques et à la sécurité des systèmes d'information NIS2 Belgium

2.10.1: Include security in the organisation’s change management process NSM ICT-SP

Determining the baseline for network and data system usage for monitoring purposes

Critical

High

Normal

Low

Technical cyber security

Security systems and logging

Determining the baseline for network and data system usage for monitoring purposes

This task helps you comply with the following requirements

8.16: Monitoring activities ISO 27001

I-11: MONITASOINEN SUOJAAMINEN – POIKKEAMIEN HAVAINNOINTIKYKY JA TOIPUMINEN Katakri 2020

Article 10: Detection DORA

DE.AE-1: A baseline of network operations and expected data flows for users and systems is established and managed.CyberFundamentals

3.3.1: Create a plan for analysing data from security monitoring NSM ICT-SP

Monitoring the use of the network and information systems to identify anomalies

Critical

High

Normal

Low

Technical cyber security

Security systems and logging

Monitoring the use of the network and information systems to identify anomalies

This task helps you comply with the following requirements

8.16: Monitoring activities ISO 27001

6.11: Alusta- ja verkkopalvelujen tietoturvallinen käyttö tietosuojan ja varautumisen kannalta Tietoturvasuunnitelma

I-11: MONITASOINEN SUOJAAMINEN – POIKKEAMIEN HAVAINNOINTIKYKY JA TOIPUMINEN Katakri 2020

5.2.3: Malware protection TISAX

DE.CM-1: The network is monitored to detect potential cybersecurity events.CyberFundamentals

Complete these tasks in Cyberday ISMS ->

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way‍

Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.

Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.

Do it once - we automatically apply it to all current and future frameworks.

Start free trial