Norm for informasjonssikkerhet og personvern i helse- og omsorgssektoren (Norge)

Requirement

5.8.1: Avvikshåndtering

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

Uønskede hendelser (for eksempel brudd på rutiner, personvernet, informasjonssikkerheten eller nettverk- og informasjonssystemer) skal behandles som avvik. Avvik skal behandles for å gjenopprette normal tilstand, fjerne årsaken til avviket og hindre gjentagelse.

Virksomheten skal ha rutiner for å oppdage og håndtere avvik. Avviksbehandlingen skal være dokumentert.

Virksomheten skal samle inn fakta om hendelsesforløpet for etablering av korrigerende tiltak. Effekten av korrigerende tiltak skal vurderes og eventuelle andre tiltak settes i verk ved behov.

Ved alvorlige eller gjentatte avvik skal det gjennomføres ny risikovurdering.

Avviksmeldinger som inneholder personopplysninger eller informasjon med betydning for informasjonssikkerheten, skal sikres.

I Normen omtales rapportering av avvik på personvern og informasjonssikkerhet til Datatilsynet, Statens helsetilsyn og Nasjonal sikkerhetsmyndighet.

See how Cyberday guides you to fulfill this requirement:

Start free trial

This requirement is part of the framework:

Norm for informasjonssikkerhet og personvern i helse- og omsorgssektoren (Norge)

Other requirements of the framework

5.8.1: Avvikshåndtering

Best practices

How to implement:

5.8.1: Avvikshåndtering

This policy on

5.8.1: Avvikshåndtering

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.

Uønskede hendelser (for eksempel brudd på rutiner, personvernet, informasjonssikkerheten eller nettverk- og informasjonssystemer) skal behandles som avvik. Avvik skal behandles for å gjenopprette normal tilstand, fjerne årsaken til avviket og hindre gjentagelse.

Virksomheten skal ha rutiner for å oppdage og håndtere avvik. Avviksbehandlingen skal være dokumentert.

Virksomheten skal samle inn fakta om hendelsesforløpet for etablering av korrigerende tiltak. Effekten av korrigerende tiltak skal vurderes og eventuelle andre tiltak settes i verk ved behov.

Ved alvorlige eller gjentatte avvik skal det gjennomføres ny risikovurdering.

Avviksmeldinger som inneholder personopplysninger eller informasjon med betydning for informasjonssikkerheten, skal sikres.

I Normen omtales rapportering av avvik på personvern og informasjonssikkerhet til Datatilsynet, Statens helsetilsyn og Nasjonal sikkerhetsmyndighet.

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

5.8.1: Avvikshåndtering

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

5.8.1: Avvikshåndtering

of the framework

Norm for informasjonssikkerhet og personvern i helse- og omsorgssektoren (Norge)

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Risk assessment review after major incidents

Critical

High

Normal

Low

Risk management and leadership

Risk management

Risk assessment review after major incidents

5.8.1: Avvikshåndtering Norm for informasjonssikkerhet

Reporting personal data breaches to authorities / data subjects

Critical

High

Normal

Low

Incident management

Data breach management

Reporting personal data breaches to authorities / data subjects

33. Notification of a personal data breach to the supervisory authority GDPR

34. Communication of a personal data breach to the data subject GDPR

6.1.3: Contact with authorities ISO 27001

16.1.5: Response to information security incidents ISO 27001

RS.CO-2: Incident reporting NIST

Personnel guidelines for reporting security incidents

Critical

High

Normal

Low

Incident management

Incident management and response

Personnel guidelines for reporting security incidents

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

2.2(1): Ansvar for den behandlingsansvarlige Norm for informasjonssikkerhet

9.9a §: Poikkeamien havainnointi Kyberturvallisuuslaki

1.6.1: Reporting of security events TISAX

1.3.2: Classification of information assets TISAX

Process for checking integrity of data after an incident

Critical

High

Normal

Low

Risk management and leadership

Continuity management

Process for checking integrity of data after an incident

Article 12: Backup policies and procedures, restoration and recovery procedures and methods DORA

RC.RP-05: Integrity of restored assets is verified, systems and services NIST 2.0

13.1.d: Recovering from incidents CER

§ 14.4: Återhämta sig från incidenter NIS2 Åland

5.8.1: Avvikshåndtering Norm for informasjonssikkerhet

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

Treatment process and documentation of identified non-conformities

Critical

High

Normal

Low

Risk management and leadership

Risk management

Treatment process and documentation of identified non-conformities

1.5.1: Assessment of policies and requirements TISAX

30 § 6°: Non-conformités et mesures correctives NIS2 Belgium

I-11: DEFENCE-IN-DEPTH - INCIDENT DETECTION AND RECOVERY Katakri 2020

45.(3): Neatbilstības un koriģējošās darbības NIS2 Latvia

Art 24.4: Non conformità e azioni correttive NIS2 Italy

Regular periodic analysis and learning of incidents

Critical

High

Normal

Low

Incident management

Incident management and response

Regular periodic analysis and learning of 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.1: Identify experiences and lessons learnt from incidents NSM ICT-SP

Follow-up analysis for security incidents

Critical

High

Normal

Low

Incident management

Incident management and response

Follow-up analysis for security incidents

16.1.6: Learning from information security incidents ISO 27001

6.4: Menettelytavat virhe- ja ongelmatilanteissa Omavalvontasuunnitelma

ID.RA-4: Impacts on business NIST

DE.DP-5: Detection processes improvment NIST

RS.AN-2: The impact of the incident NIST

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