MSBFS 2020:7 (Sverige)

Requirement

§ 4.22: Katastrofåterställning och redundans

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

Myndigheten ska, för att säkerställa tillgänglighet till information och informationssystem vid incidenter och avvikelser,

ha interna regler för återställning av produktionsmiljön i sin helhet och för enskilda informationssystem,
öva återställning av informationssystem som är centrala för myndighetens förmåga att utföra sitt uppdrag, och
placera centrala servrar och central nätverksutrustning som skapar redundant funktion i olika särskilda it-utrymmen.

Fulfill this requirement by completing the tasks below ->

This requirement is part of the framework:

MSBFS 2020:7 (Sverige)

Other requirements of the framework

§ 4.22: Katastrofåterställning och redundans

Best practices

How to implement:

§ 4.22: Katastrofåterställning och redundans

This policy on

§ 4.22: Katastrofåterställning och redundans

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.

Myndigheten ska, för att säkerställa tillgänglighet till information och informationssystem vid incidenter och avvikelser,

ha interna regler för återställning av produktionsmiljön i sin helhet och för enskilda informationssystem,
öva återställning av informationssystem som är centrala för myndighetens förmåga att utföra sitt uppdrag, och
placera centrala servrar och central nätverksutrustning som skapar redundant funktion i olika särskilda it-utrymmen.

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

§ 4.22: Katastrofåterställning och redundans

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

§ 4.22: Katastrofåterställning och redundans

of the framework

MSBFS 2020:7 (Sverige)

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Creating and documenting continuity plans

Critical

High

Normal

Low

Risk management and leadership

Continuity management

Creating and documenting continuity plans

This task helps you comply with the following requirements

Članak 30.1.c: Kontinuitet poslovanja NIS2 Croatia

2.7: Varautuminen häiriötilanteisiin TiHL tietoturvavaatimukset

9.10 §: Varmuuskopiointi ja jatkuvuuden hallinta Kyberturvallisuuslaki

5.2.8: IT service continuity planning TISAX

1.6.3: Crisis preparedness TISAX

Regular testing, evaluation, and recovery instructions for backups

Critical

High

Normal

Low

Technical cyber security

Backups

Regular testing, evaluation, and recovery instructions for backups

This task helps you comply with the following requirements

12.1.1: Documented operating procedures ISO 27001

12.3.1: Information backup ISO 27001

PR.IP-4: Backups NIST

TEK-20: Varmuuskopiointi Julkri

8.13: Information backup ISO 27001

Documenting and delegating ownership of own backup processes

Critical

High

Normal

Low

Technical cyber security

Backups

Documenting and delegating ownership of own backup processes

This task helps you comply with the following requirements

12.3: Backup ISO 27001

12.3.1: Information backup ISO 27001

I24: Varmuuskopiointi Katakri

PR.IP-4: Backups NIST

TEK-20: Varmuuskopiointi Julkri

Resilient design of the public warning system

Critical

High

Normal

Low

Risk management and leadership

Continuity management

Resilient design of the public warning system

This task helps you comply with the following requirements

13.4: Sikring af udsendelse af offentlige advarsler NIS2 Denmark

§ 4.22: Katastrofåterställning och redundans MSBFS 2020:7

Developing and executing a recovery plan

Critical

High

Normal

Low

Incident management

Incident management and response

Developing and executing a recovery plan

This task helps you comply with the following requirements

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

Determining responsibilities for backing up important information assets

Critical

High

Normal

Low

Technical cyber security

Backups

Determining responsibilities for backing up important information assets

This task helps you comply with the following requirements

12.3.1: Information backup ISO 27001

I24: Varmuuskopiointi Katakri

PR.IP-4: Backups NIST

TEK-20: Varmuuskopiointi Julkri

8.13: Information backup ISO 27001

Regular testing and review of continuity plans

Critical

High

Normal

Low

Risk management and leadership

Continuity management

Regular testing and review of continuity plans

This task helps you comply with the following requirements

17.1.3: Verify, review and evaluate information security continuity ISO 27001

ID.SC-5: Response and recovery NIST

PR.IP-10: Response and recovery plan tests NIST

RS.IM-2: Response strategies update NIST

RC.IM-2: Recovery strategies NIST

Addressing disasters in continuity planning

Critical

High

Normal

Low

Risk management and leadership

Continuity management

Addressing disasters in continuity planning

This task helps you comply with the following requirements

PR.IP-9: Response and recovery plans NIST

Article 11: Response and recovery DORA

1.6.3: Crisis preparedness TISAX

PR.IP-9: Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed.CyberFundamentals

RC.RP-1: Recovery plan is executed during or after a cybersecurity incident.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

This task helps you comply with the following requirements

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

Availability of data systems and procedures to protect their availability

Critical

High

Normal

Low

System management

Data system management

Availability of data systems and procedures to protect their availability

This task helps you comply with the following requirements

TEK-22: Tietojärjestelmien saatavuus Julkri

TEK-22.1: Tietojärjestelmien saatavuus - saatavuutta suojaavat menettelyt Julkri

31: Toipumissuunnitelmat kriittisille järjestelmille Digiturvan kokonaiskuvapalvelu

Article 7: ICT systems, protocols and tools DORA

Article 9a: Protection DORA

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