5.4.5: Styrig og håndtering av tekniske sårbarheter

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

Styring og håndtering av tekniske sårbarheter skal følge rutinene for endringsstyring. Virksomheten skal ha rutine for å skaffe seg informasjon om tekniske sårbarheter i nettverk- og informasjonssystemer, utstyr og programvare.

Utgangspunktet for styring og håndtering er oversikt over:

  • IKT-utstyr
  • programvare: programvaren, leverandør, versjonsnumre, hvilken versjon som er installert hvor, og hvem som har ansvaret for programvaren

Det skal etableres rutiner og operative tiltak som ivaretar:

  • ansvaret for overvåkning, risikovurdering, korrigering og koordinering
  • ansvaret for sikkerhetsovervåkning av nettverk- og informasjonssystemer for å avdekke hendelser
  • hvordan virksomheten skal reagere og varsle om sårbarheter
  • prioritering og etablering av tidslinje for korrigering
  • at alle korrigeringer bør testes før de implementeres

See how Cyberday guides you to fulfill this requirement:

Other requirements of the framework

59060
5.4.5: Styrig og håndtering av tekniske sårbarheter
Best practices
How to implement:
5.4.5: Styrig og håndtering av tekniske sårbarheter
This policy on
5.4.5: Styrig og håndtering av tekniske sårbarheter
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.

Styring og håndtering av tekniske sårbarheter skal følge rutinene for endringsstyring. Virksomheten skal ha rutine for å skaffe seg informasjon om tekniske sårbarheter i nettverk- og informasjonssystemer, utstyr og programvare.

Utgangspunktet for styring og håndtering er oversikt over:

  • IKT-utstyr
  • programvare: programvaren, leverandør, versjonsnumre, hvilken versjon som er installert hvor, og hvem som har ansvaret for programvaren

Det skal etableres rutiner og operative tiltak som ivaretar:

  • ansvaret for overvåkning, risikovurdering, korrigering og koordinering
  • ansvaret for sikkerhetsovervåkning av nettverk- og informasjonssystemer for å avdekke hendelser
  • hvordan virksomheten skal reagere og varsle om sårbarheter
  • prioritering og etablering av tidslinje for korrigering
  • at alle korrigeringer bør testes før de implementeres

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.4.5: Styrig og håndtering av tekniske sårbarheter
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

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.4.5: Styrig og håndtering av tekniske sårbarheter
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
Process for managing technical vulnerabilities
Critical
High
Normal
Low
59
requirements
Development and cloud
Technical vulnerability management

Process for managing technical vulnerabilities

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Regular vulnerability scanning
Critical
High
Normal
Low
54
requirements
Development and cloud
Technical vulnerability management

Regular vulnerability scanning

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Initial treatment of identified technical vulnerabilities
Critical
High
Normal
Low
28
requirements
Development and cloud
Technical vulnerability management

Initial treatment of identified technical vulnerabilities

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Selecting and tracking data sources for vulnerability information
Critical
High
Normal
Low
18
requirements
Development and cloud
Technical vulnerability management

Selecting and tracking data sources for vulnerability information

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Maintenance and updates of security systems that detect vulnerabilities
Critical
High
Normal
Low
7
requirements
System management
Update and patch management

Maintenance and updates of security systems that detect vulnerabilities

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Defining metrics related to vulnerability management
Critical
High
Normal
Low
9
requirements
Development and cloud
Technical vulnerability management

Defining metrics related to vulnerability management

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Regular monitoring of the vulnerability management process
Critical
High
Normal
Low
28
requirements
Development and cloud
Technical vulnerability management

Regular monitoring of the vulnerability management process

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Monitoring the use of the network and information systems to identify anomalies
Critical
High
Normal
Low
53
requirements
Technical cyber security
Security systems and logging

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

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

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.