+Business Continuity & Disaster Recovery Policy

Business Continuity & Disaster Recovery Policy

Description

Mechanisms exist to establish a formal, documented Business Continuity and Disaster Recovery (BC/DR) policy that:
(1) Conveys executive management's intent;
(2) Provides organizational direction and expected behaviors;
(3) Is reviewed at least annually; and
(4) Is updated, as necessary, to adapt to evolving risks, threats and other changes that affect the organization.

Possible Solutions & Considerations

Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2

∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ Executive-approved written policy with documented annual review

Small Business (10-49 staff) / BLS Firm Size Classes 3-4

∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ Executive-approved written policy with documented annual review
∙ Policy acknowledgement tracking (e.g., HR onboarding records)

Medium Business (50-249 staff) / BLS Firm Size Classes 5-6

∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.) for policy lifecycle management
∙ Documented annual policy review with version control

Large Business (250-999 staff) / BLS Firm Size Classes 7-8

∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.) for policy lifecycle management
∙ Policy governance committee with formal annual review and approval workflow
∙ Automated policy attestation and acknowledgement tracking

Enterprise (> 1,000 staff) / BLS Firm Size Class 9

∙ Steering committee
∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ Enterprise GRC platform (e.g., Cyturus, Archer, MetricStream, ServiceNow IRM) for policy lifecycle management
∙ Automated policy attestation, exception tracking and change history
∙ Annual executive approval and board-level reporting

SCR-CMM

Level 0 Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 Performed Informally

SCR-CMM Level 1 criteria definitions are not available for this control:
▪ A reasonable person would conclude this control requires a structured process.
▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 Planned Tracked

Business Continuity & Disaster Recovery (BCD) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Policies and standards associated with BCD domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with BCD domain capabilities are documented and maintained by process owners.
▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with BCD domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Business Continuity / Disaster Recovery (BC/DR)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ BC/DR may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.

Level 3 Well Defined

Business Continuity & Disaster Recovery (BCD) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Policies and standards associated with BCD domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Standardized Operating Procedures (SOP) associated with BCD domain capabilities are well-documented and kept current by process owners.
▪ A Business Continuity & Disaster Recovery (BC/DR) team, or similar function, is appropriately staffed and supported to implement and maintain BCD domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of BC/DR operations (e.g., BC/DR planning software, Disaster Recovery as a Service (DRaaS), Orchestration and Automation Tools).
▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with BCD domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls).

Level 4 Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions:
▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control.
▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

Level 5 Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions:
▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control.
▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies.
▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

1. Ħarsa ġenerali

Titlu Standard

1.1 Referenzi

1.2 Rekwiżiti identifikati

1.3 Regolamenti relatati

2. Rekwiżiti identifikati

Rekwiżiti
Sors Rekwiżit

3. Regolamenti relatati

Regolamenti
Sors Regolamentazzjoni
EULAW Artikolu 11 1

1.   Bħala parti mill-qafas tal-ġestjoni tar-riskju tal-ICT imsemmi fl-Artikolu 6(1) u abbażi tar-rekwiżiti ta’ identifikazzjoni li jinsabu fl-Artikolu 8, l-entitajiet finanzjarji għandhom jistabbilixxu politika komprensiva tal-kontinwità tal-operat tal-ICT, li tista’ tiġi adottata bħala politika speċifika dedikata, li tifforma parti integrali mill-politika globali tal-kontinwità tal-operat tal-entità finanzjarja.

EULAW Artikolu 11 2

2.   L-entitajiet finanzjarji għandhom jimplimentaw il-politika tal-kontinwità tal-operat tal-ICT permezz ta’ arranġamenti, pjanijiet, proċeduri u mekkaniżmi ddedikati, xierqa u ddokumentati bil-għan li:

(a)

jiżguraw il-kontinwità tal-funzjonijiet kritiċi jew importanti tal-entità finanzjarja;

(b)

jirrispondu malajr, b’mod xieraq u effettiv għall-inċidenti kollha relatati mal-ICT, u jirriżolvuhom, b’mod li jillimita l-ħsara u jagħti prijorità lit-tkomplija tal-attivitajiet u tal-azzjonijiet ta’ rkupru;

(c)

jattivaw, mingħajr dewmien, pjanijiet iddedikati li jippermettu miżuri ta’ trażżin, proċessi u teknoloġiji adatti għal kull tip ta’ inċident relatat mal-ICT u jipprevjenu aktar ħsara, kif ukoll proċeduri ta’ rispons u rkupru mfassla apposta stabbiliti f’konformità mal-Artikolu 12;

(d)

jagħtu stima preliminari tal-impatti, il-ħsarat u t-telf;

(e)

jistipulaw azzjonijiet ta’ komunikazzjoni u ta’ ġestjoni ta’ kriżijiet li jiżguraw li l-informazzjoni aġġornata tintbagħat lill-persunal intern u lill-partijiet ikkonċernati esterni rilevanti kollha f’konformità mal-Artikolu 14, u jirrapportaw lill-awtoritajiet kompetenti f’konformità mal-Artikolu 19.

EULAW Artikolu 11 3

3.   Bħala parti mill-qafas ta’ ġestjoni tar-riskju tal-ICT imsemmi fl-Artikolu 6(1), l-entitajiet finanzjarji għandhom jimplimentaw pjanijiet ta’ rispons u rkupru għall-ICT assoċjati, li fil-każ ta’ entitajiet finanzjarji għajr il-mikrointrapriżi, għandhom ikunu soġġetti għal rieżamijiet ta’ awditjar intern.

EULAW Artikolu 11 4

4.   L-entitajiet finanzjarji għandhom jistabbilixxu, iżommu u jittestjaw perjodikament il-pjanijiet xierqa tal-kontinwità tal-operat tal-ICT, b’mod partikolari fir-rigward ta’ funzjonijiet kritiċi jew importanti esternalizzati jew ikkuntrattati permezz ta’ arranġamenti ma’ fornituri terzi ta’ servizzi tal-ICT.

EULAW Artikolu 11 5

5.   Bħala parti mill-politika ġenerali tal-kontinwità tal-operat, l-entitajiet finanzjarji għandhom iwettqu valutazzjoni tal-impatt fuq in-negozju (BIA) tal-esponiment tagħhom għal tqallib serju fl-operat. Skont il-BIA, l-entitajiet finanzjarji għandhom jivvalutaw l-impatt potenzjali ta’ tqallib serju fl-operat permezz ta’ kriterji kwantitattivi u kwalitattivi, bl-użu ta’ data interna u esterna u analiżi tax-xenarji, kif xieraq. Il-BIA għandha tikkunsidra l-kritikalità tal-funzjonijiet tan-negozju identifikati u mmappjati, il-proċessi ta’ appoġġ, id-dipendenzi ta’ partijiet terzi u l-assi tal-informazzjoni, u l-interdipendenzi tagħhom. L-entitajiet finanzjarji għandhom jiżguraw li l-assi tal-ICT u s-servizzi tal-ICT jitfasslu u jintużaw f’allinjament sħiħ mal-BIA, b’mod partikolari sabiex jiżguraw kif xieraq ir-ridondanza tal-komponenti kritiċi kollha.

EULAW Artikolu 11 6

6.   Bħala parti mill-ġestjoni komprensiva tar-riskju tal-ICT tagħhom, l-entitajiet finanzjarji għandhom:

(a)

jittestjaw il-pjanijiet ta’ kontinwità tal-operat tal-ICT u l-pjanijiet ta’ rispons u rkupru għall-ICT fir-rigward tas-sistemi tal-ICT li jappoġġjaw il-funzjonijiet kollha mill-anqas darba f’sena, kif ukoll fil-każ ta’ kwalunkwe bidla sostantiva fis-sistemi tal-ICT li jappoġġjaw funzjonijiet kritiċi jew importanti;

(b)

jittestjaw il-pjanijiet ta’ komunikazzjoni tal-kriżijiet stabbiliti f’konformità mal-Artikolu 14.

Għall-finijiet tal-ewwel subparagrafu, il-punt (a), l-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandhom jinkludu fil-pjanijiet tal-ittestjar xenarji ta’ ċiberattakki u l-qlib minn infrastruttura primarja tal-ICT għall-oħra u l-kapaċità żejda, il-backups u l-faċilitajiet żejda meħtieġa biex jiġu ssodisfati l-obbligi stabbiliti fl-Artikolu 12.

L-entitajiet finanzjarji għandhom jirrevedu regolarment il-politika tagħhom tal-kontinwità tal-operat tal-ICT u l-pjanijiet tagħhom ta’ rispons u rkupru għall-ICT, filwaqt li jqisu r-riżultati tat-testijiet imwettqa f’konformità mal-ewwel subparagrafu u mar-rakkomandazzjonijiet li jirriżultaw minn kontrolli tal-awditjar jew rieżamijiet superviżorji.

EULAW Artikolu 11 7

7.   L-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandu jkollhom funzjoni ta’ ġestjoni tal-kriżijiet, li, f’każ ta’ attivazzjoni tal-pjanijiet tagħhom ta’ kontinwità tal-operat tal-ICT jew tal-pjanijiet tagħhom ta’ rispons u rkupru għall-ICT, għandha, fost oħrajn, tistabbilixxi proċeduri ċari għall-ġestjoni tal-komunikazzjonijiet interni u esterni għall-kriżijiet f’konformità mal-Artikolu 14.

EULAW Artikolu 11 8

8.   L-entitajiet finanzjarji għandhom iżommu rekords aċċessibbli fil-pront tal-attivitajiet qabel u waqt każijiet ta’ tfixkil meta jiġu attivati l-pjanijiet tagħhom ta’ kontinwità tal-operat tal-ICT u l-pjanijiet tagħhom ta’ rispons u ta’ rkupru għall-ICT.

EULAW Artikolu 11 9

9.   Id-depożitorji ċentrali tat-titoli għandhom jipprovdu lill-awtoritajiet kompetenti bil-kopji tar-riżultati tat-testijiet tal-kontinwità tal-operat tal-ICT, jew ta’ eżerċizzji simili.

EULAW Artikolu 11 10

10.   L-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandhom jirrapportaw lill-awtoritajiet kompetenti, fuq talba tagħhom, stima annwali aggregata tal-kostijiet u tat-telf ikkawżati minn inċidenti kbar relatati mal-ICT.

EULAW Artikolu 11 11

11.   F’konformità mal-Artikolu 16 tar-Regolamenti (UE) Nru 1093/2010, (UE) Nru 1094/2010 u (UE) Nru 1095/2010, l-ASE, permezz tal-Kumitat Konġunt, għandhom, sas-17 ta’ Lulju 2024 jiżviluppaw linji gwida komuni dwar l-istima tal-kostijiet u tat-telf annwali msemmija fil-paragrafu 10.

EULAW Artikolu 12 1

1.   Sabiex jiġi żgurat ir-restawr tas-sistemi tal-ICT u tad-data bl-iqsar perjodu ta’ qtugħ, tfixkil u telf limitati, bħala parti mill-qafas tagħhom ta’ ġestjoni tar-riskju tal-ICT, l-entitajiet finanzjarji għandhom jiżviluppaw u jiddokumentaw:

(a)

politiki u proċeduri ta’ backup li jispeċifikaw l-ambitu tad-data li tkun soġġetta għall-backup u l-frekwenza minima tal-backup, abbażi tal-kritikalità tal-informazzjoni jew il-livell ta’ kunfidenzjalità tad-data;

(b)

proċeduri u metodi ta’ restawr u rkupru.

EULAW Artikolu 32 Sigurtà tal-ipproċessar
-
EULAW Artikolu 21 Miżuri ta' ġestjoni tar-riskji taċ-ċibersigurtà
-
EULAW Artikolu 24 Komponenti tal-politika dwar il-kontinwità tal-operat tal-ICT
-
EULAW Artikolu 5 Governanza u organizzazzjoni
-
EULAW Artikolu 11 Rispons u rkupru
-
EULAW Artikolu 16 Qafas simplifikat tal-ġestjoni tar-riskju tal-ICT
-
EULAW Artikolu 5 2

2.   Il-korp maniġerjali tal-entità finanzjarja għandu jiddefinixxi, japprova, jissorvelja u jkun responsabbli għall-implimentazzjoni tal-arranġamenti kollha relatati mal-qafas ta’ ġestjoni tar-riskju tal-ICT imsemmi fl-Artikolu 6(1).

Għall-finijiet tal-ewwel subparagrafu, il-korp maniġerjali għandu:

(a)

jerfa’ r-responsabbiltà aħħarija għall-ġestjoni tar-riskji tal-ICT tal-entità finanzjarja;

(b)

jistabbilixxi politiki li għandhom l-għan li jiżguraw iż-żamma ta’ standards għolja ta’ disponibbiltà, awtentiċità, integrità u kunfidenzjalità tad-data;

(c)

jistabbilixxi rwoli u responsabbiltajiet ċari għall-funzjonijiet kollha marbuta mal-ICT u jistabbilixxi arranġamenti xierqa ta’ governanza sabiex jiżgura l-komunikazzjoni, il-kooperazzjoni u l-koordinazzjoni effettivi u f’waqthom fost dawk il-funzjonijiet;

(d)

jerfa’ r-responsabbiltà globali għall-istabbiliment u l-approvazzjoni tal-istrateġija ta’ reżiljenza operazzjonali diġitali kif imsemmija fl-Artikolu 6(8), inkluż id-determinazzjoni tal-livell xieraq ta’ tolleranza għar-riskju tal-ICT tal-entità finanzjarja, kif imsemmi fl-Artikolu 6(8), il-punt (b);

(e)

japprova, jissorvelja u jirrieżamina perjodikament l-implimentazzjoni tal-politika ta’ kontinwità ta’ negozju tal-ICT tal-entità finanzjarja u tal-pjanijiet ta’ rispons u ta’ rkupru għall-ICT, imsemmija, rispettivament, fl-Artikolu 11(1) u (3), li jistgħu jiġu adottati bħala politika speċifika ddedikata li tifforma parti integrali mill-politika globali ta’ kontinwità ta’ negozju tal-entità finanzjarja u mill-pjan ta’ rispons u ta’ rkupru;

(f)

japprova u jirrieżamina perjodikament il-pjanijiet tal-entità finanzjarja tal-awditu intern tal-ICT, l-awditi tal-ICT u l-modifiki materjali għalihom;

(g)

jalloka u jirrevedi perjodikament il-baġit xieraq biex jissodisfa l-ħtiġijiet ta’ reżiljenza operazzjonali diġitali tal-entità finanzjarja fir-rigward tat-tipi kollha ta’ riżorsi, inkluż programmi rilevanti ta’ sensibilizzazzjoni dwar is-sigurtà tal-ICT u taħriġ fir-reżiljenza operazzjonali diġitali kif imsemmi fl-Artikolu 13(6), u ħiliet fl-ICT għall-persunal kollu;

(h)

japprova u jirrieżamina perjodikament il-politika tal-entità finanzjarja dwar l-arranġamenti rigward l-użu tas-servizzi tal-ICT ipprovduti minn fornituri terzi ta’ servizzi tal-ICT;

(i)

jistabbilixxi, fil-livell korporattiv, kanali ta’ rapportar li permezz tagħhom jiġi infurmat kif xieraq dwar dan li ġej:

(i)

l-arranġamenti konklużi ma’ fornituri terzi ta’ servizzi tal-ICT dwar l-użu ta’ servizzi tal-ICT,

(ii)

kwalunkwe bidla materjali rilevanti ppjanata fir-rigward tal-fornituri terzi ta’ servizzi tal-ICT,

(iii)

l-impatt potenzjali ta’ tali bidliet fuq il-funzjonijiet kritiċi jew importanti soġġetti għal dawk l-arranġamenti, inkluż sommarju tal-analiżi tar-riskju li tivvaluta l-impatt ta’ dawk il-bidliet, u l-inċidenti marbuta mal-ICT, tal-anqas dawk kbar, u l-impatt tagħhom, kif ukoll il-miżuri ta’ rispons, irkupru u rimedju.

EULAW Artikolu 16 1

1.   L-Artikoli 5 sa 15 ta’ dan ir-Regolament ma għandhomx japplikaw għal ditti tal-investiment żgħar u mhux interkonnessi, istituzzjonijiet ta’ pagament eżentati skont id-Direttiva (UE) 2015/2366; istituzzjonijiet eżentati skont id-Direttiva 2013/36/UE li fir-rigward tagħhom l-Istati Membri ddeċidew li ma japplikawx l-opzjoni msemmija fl-Artikolu 2(4) ta’ dan ir-Regolament; istituzzjonijiet tal-flus elettroniċi eżentati skont id-Direttiva 2009/110/KE; u istituzzjonijiet żgħar għall-provvista ta’ rtirar okkupazzjonali.

Mingħajr preġudizzju għall-ewwel subparagrafu, l-entitajiet elenkati fl-ewwel subparagrafu għandhom:

(a)

jistabbilixxu u jżommu qafas għall-ġestjoni tar-riskju tal-ICT li jkun sod u ddokumentat li jiddeskrivi fid-dettall il-mekkaniżmi u l-miżuri mmirati lejn ġestjoni rapida, effiċjenti u komprensiva tar-riskju tal-ICT, inkluż għall-protezzjoni ta’ komponenti u infrastrutturi fiżiċi rilevanti;

(b)

jimmonitorjaw b’mod kontinwu s-sigurtà u l-funzjonament tas-sistemi kollha tal-ICT;

(c)

jimminimizzaw l-impatt tar-riskju tal-ICT billi jużaw sistemi, protokolli u għodod tal-ICT li jkunu sodi, reżiljenti u aġġornati u li jkunu xierqa biex jappoġġjaw it-twettiq tal-attivitajiet tagħhom u l-forniment tas-servizzi u jipproteġu b’mod adegwat id-disponibbiltà, l-awtentiċità, l-integrità u l-kunfidenzjalità tad-data fin-netwerk u fis-sistemi tal-informazzjoni;

(d)

jippermettu li s-sorsi ta’ riskju tal-ICT u anomaliji fin-netwerk u fis-sistemi tal-informazzjoni jiġu identifikati u individwati fil-pront u li l-inċidenti relatati mal-ICT jiġu mmaniġġati malajr;

(e)

jidentifikaw dipendenzi ewlenin fuq fornituri terzi ta’ servizzi tal-ICT;

(f)

jiżguraw il-kontinwità ta’ funzjonijiet kritiċi jew importanti, permezz ta’ pjanijiet ta’ kontinwità tal-operat u miżuri ta’ rispons u ta’ rkupru, li jinkludu, mill-inqas, miżuri ta’ backup u restawr;

(g)

jittestjaw, fuq bażi regolari, il-pjanijiet u l-miżuri msemmija fil-punt (f), kif ukoll l-effettività tal-kontrolli implimentati f’konformità mal-punti (a) u (c);

(h)

jimplimentaw, kif xieraq, konklużjonijiet operazzjonali rilevanti li jirriżultaw mit-testijiet imsemmija fil-punt (g) u mill-analiżi ta’ wara l-inċident fil-proċess ta’ valutazzjoni tar-riskju tal-ICT u jiżviluppaw, skont il-ħtiġijiet u l-profil tar-riskju tal-ICT, programmi ta’ sensibilizzazzjoni dwar is-sigurtà tal-ICT u taħriġ dwar ir-reżiljenza operazzjonali diġitali għall-persunal u għall-maniġment.

Kwistjonijiet marbuta

Links
Tip ta’ link Kwistjoni
is related to Annual
is related to relative Control Weighting = 10
is related to Process
is related to Govern
is related to SCRM Focus Tier 1 STRATEGIC
is related to SCRM Focus Tier 2 OPERATIONAL
is related to SCRM Focus Tier 3 TACTICAL
blocks Loss, Theft or Damage of Assets
blocks Unauthorized Modification / Loss of System Integrity
blocks Unauthorized Retention / Inability to Dispose of Data
blocks Business / Service Interruption
blocks Data Loss / Integrity Compromise
blocks Reduced Operational Productivity
blocks System / Data Compromise (Technical Vector)
blocks System / Data Compromise (Non-Technical Vector)
blocks Revenue Loss
blocks Contractual Default / Termination
blocks Loss of Competitive Advantage
blocks Reputational Harm / Loss of Stakeholder Trust
blocks Regulatory / Legal / Contractual Financial Liability
blocks Failure to Support Business / Mission Objectives
blocks Unaddressed Security / Compliance Exposure
blocks Unperformed / Unowned Control Responsibilities
blocks Uncontrolled Internal Security / Privacy Exposure
blocks Uncontrolled Third-Party Security / Privacy Exposure
blocks Loss of Investigative / Evidentiary Capability
blocks Delayed Containment / Increased Incident Impact
blocks Incident Persistence / Recurrence
blocks Incident Response / Recovery Cost
blocks Undetected / Delayed Detection of Adverse Activity
blocks Data Destruction
blocks Data Encrypted for Impact
blocks Inhibit System Recovery
blocks Defacement
blocks Internal Defacement
blocks External Defacement
blocks Disk Wipe
blocks Disk Content Wipe
blocks Disk Structure Wipe
blocks Loss of Authorization / Certification / License
blocks Lack of oversight of internal controls
blocks Inability to Demonstrate Due Diligence / Due Care
blocks Unreliable Assurance / Decision Information
blocks Recovery Failure / Unacceptable Recovery Delay
blocks Drought & Water Shortage
blocks Earthquakes
blocks Fire & Wildfires
blocks Floods
blocks Hurricanes & Tropical Storms
blocks Landslides & Debris Flow
blocks Pandemic (Disease) Outbreaks
blocks Severe Weather
blocks Space Weather
blocks Thunderstorms & Lightning
blocks Tornadoes
blocks Tsunamis
blocks Volcanoes
blocks Winter Storms & Extreme Cold
blocks Malicious Cyber Activity
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Statutory / Regulatory / Contractual Change
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks BCM-01.02B
is blocked by BCD-01 Business Continuity & Disaster Recovery Policy – Assessment Procedure
  • Secure Controls Framework -

    The Secure Controls Framework® (SCF)

    "The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.

    The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.

    Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.

    The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/ 

    Terms & Conditions

    The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.