Lov om digital sikkerhet (Norge)

Requirement

§ 6.1: Sikkerhetsstyringssystem

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

En tilbyder av en samfunnsviktig tjeneste skal etablere og vedlikeholde et styringssystem for sikkerhet som omfatter digital sikkerhet. Styringssystemet skal dokumenteres og inngå som del av den overordnede virksomhetsstyringen. Roller og ansvar for digital sikkerhet skal defineres, utpekes og dokumenteres. Sikkerhetsstyringssystemet skal baseres på anerkjente standarder og bidra til å

a. forebygge hendelser

b. avdekke hendelser

c. håndtere hendelser

d. korrigere og gjenopprette sikkerheten i nettverk og informasjonssystemer ved hendelser

e. kontinuerlig styre og følge opp at formålene i bokstavene a til d oppnås.

Alle aktiviteter som er nødvendige for å etablere og opprettholde et forsvarlig sikkerhetsnivå skal inngå i sikkerhetsstyringssystemet. Aktivitetene skal dokumenteres og gjøres kjent for personell med tjenstlig behov.

See how Cyberday guides you to fulfill this requirement:

Start free trial

This requirement is part of the framework:

Lov om digital sikkerhet (Norge)

Other requirements of the framework

§ 6.1: Sikkerhetsstyringssystem

No items found.

Best practices

How to implement:

§ 6.1: Sikkerhetsstyringssystem

This policy on

§ 6.1: Sikkerhetsstyringssystem

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.

En tilbyder av en samfunnsviktig tjeneste skal etablere og vedlikeholde et styringssystem for sikkerhet som omfatter digital sikkerhet. Styringssystemet skal dokumenteres og inngå som del av den overordnede virksomhetsstyringen. Roller og ansvar for digital sikkerhet skal defineres, utpekes og dokumenteres. Sikkerhetsstyringssystemet skal baseres på anerkjente standarder og bidra til å

a. forebygge hendelser

b. avdekke hendelser

c. håndtere hendelser

d. korrigere og gjenopprette sikkerheten i nettverk og informasjonssystemer ved hendelser

e. kontinuerlig styre og følge opp at formålene i bokstavene a til d oppnås.

Alle aktiviteter som er nødvendige for å etablere og opprettholde et forsvarlig sikkerhetsnivå skal inngå i sikkerhetsstyringssystemet. Aktivitetene skal dokumenteres og gjøres kjent for personell med tjenstlig behov.

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

§ 6.1: Sikkerhetsstyringssystem

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

§ 6.1: Sikkerhetsstyringssystem

of the framework

Lov om digital sikkerhet (Norge)

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Designation of an incident management team

Critical

High

Normal

Low

Incident management

Incident management and response

Designation of an incident management team

Članak 30.1.b: Postupanje s incidentima, uključujući njihovo praćenje, evidentiranje i prijavljivanje NIS2 Croatia

9.9b §: Poikkeamien käsittely Kyberturvallisuuslaki

1.6.2: Management of reported events TISAX

30 § 3.2° (incidents): La gestion des incidents NIS2 Belgium

4.1.1: Establish plans for incident management NSM ICT-SP

Treatment process and documentation of occurred security incidents

Critical

High

Normal

Low

Incident management

Incident management and response

Treatment process and documentation of occurred security incidents

Članak 30.1.b: Postupanje s incidentima, uključujući njihovo praćenje, evidentiranje i prijavljivanje NIS2 Croatia

9.9b §: Poikkeamien käsittely Kyberturvallisuuslaki

1.6.2: Management of reported events TISAX

30 § 3.2° (incidents): La gestion des incidents NIS2 Belgium

4.4.2: Review identified compromised security measures NSM ICT-SP

ISMS description and maintenance

Critical

High

Normal

Low

Risk management and leadership

Cyber security management

ISMS description and maintenance

2.1: Tietoturvallisuusvastuiden määrittely TiHL tietoturvavaatimukset

2.3: Tietoturvallisuus tiedonhallintamallissa TiHL tietoturvavaatimukset

1.2.1: Scope of Information Security management TISAX

PR.AT-5: Physical security and cybersecurity personnel understand their roles and responsibilities.CyberFundamentals

Article 21: Ensuring the network is free from interference, damage or unauthorized access CSL (China)

Review of information security management system best practices

Critical

High

Normal

Low

Risk management and leadership

Cyber security management

Review of information security management system best practices

§ 6.1: Sikkerhetsstyringssystem NIS2 NO

47.37: OWASP pagrįsti žiniatinklio saugumo standartai NIS2 Guide Lithuania

Creating and maintaining incident response plans

Critical

High

Normal

Low

Incident management

Incident management and response

Creating and maintaining incident response plans

4.1.1: Establish plans for incident management NSM ICT-SP

ID.IM-04: Incident response and cybersecurity plans NIST 2.0

PR.IR-03: Meeting resilience requirements NIST 2.0

RS.MA-01: Incident response plan execution NIST 2.0

RC.RP-01: Recovery plan NIST 2.0

Developing and executing a recovery plan

Critical

High

Normal

Low

Incident management

Incident management and response

Developing and executing a recovery plan

4.3.4: Launch recovery plan during or after the incident NSM ICT-SP

Article 39: Components of the ICT business continuity plan DORA simplified RMF

13.1.d: Recovering from incidents CER

§ 13.2: Hendelseshåndtering og -respons NIS2 NO

§ 6.1: Sikkerhetsstyringssystem NIS2 NO

Defining security roles and responsibilities

Critical

High

Normal

Low

Risk management and leadership

Cyber security management

Defining security roles and responsibilities

T02: Turvallisuustyön tehtävien ja vastuiden määrittäminen Katakri

24. Responsibility of the controller GDPR

6.1.1: Information security roles and responsibilities ISO 27001

ID.AM-6: Cybersecurity roles and responsibilities NIST

ID.GV-2: Cybersecurity role coordination NIST

Incident management resourcing and monitoring

Critical

High

Normal

Low

Risk management and leadership

Cyber security management

Incident management resourcing and monitoring

24. Responsibility of the controller GDPR

7.2.1: Management responsibilities ISO 27001

16.1.1: Responsibilities and procedures ISO 27001

5.24: Information security incident management planning and preparation ISO 27001

Article 17: ICT-related incident management process DORA

Documentation of other stakeholders

Critical

High

Normal

Low

Partner management

Agreements and monitoring

Documentation of other stakeholders

Članak 30.1.d: Sigurnost lanca opskrbe NIS2 Croatia

9.4 §: Toimitusketjun hallinta ja valvonta Kyberturvallisuuslaki

1.3.3: Use of approved external IT services TISAX

30 § 3.4°: La sécurité de la chaîne d'approvisionnement NIS2 Belgium

ID.SC-1: Cyber supply chain risk management processes are identified, established, assessed, managed, and agreed to by organizational stakeholders.CyberFundamentals

Developing an incident response plan for critical information systems

Critical

High

Normal

Low

Risk management and leadership

Continuity management

Developing an incident response plan for critical information systems

RS.RP: Response Planning NIST

RS.RP-1: Incident response plan NIST

HAL-17: Tietojärjestelmien toiminnallinen käytettävyys ja vikasietoisuus Julkri

VAR-09: Tietojärjestelmien toipumissuunnitelmat Julkri

CC7.4: Responding to identified security incidents SOC 2

Incident containing measures

Critical

High

Normal

Low

Incident management

Incident management and response

Incident containing measures

RS.MI-1: Incident containment NIST

Article 17: ICT-related incident management process DORA

RS.MI-1: Incidents are contained.CyberFundamentals

4.3.2: Determine whether the incident is under control and take the necessary reactive measures NSM ICT-SP

RS.MI-01: Incident containment NIST 2.0

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