+Business Continuity Management System (BCMS)
---+Defined Operational Resilience Requirements

Business Continuity Management System (BCMS)

Description

Mechanisms exist to operate a Business Continuity Management System (BCMS) to achieve resilient Technology Assets, Applications, Services and/or Data (TAASD) during:
(1) Routine operations; and
(2) Adverse conditions.

Possible Solutions & Considerations

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

∙ Continuity of Operations Plan (COOP)
∙ Business Continuity Plan (BCP)
∙ Disaster Recovery Plan (DRP)
∙ Business Impact Analysis (BIA)
∙ Criticality assessments

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

∙ Continuity of Operations Plan (COOP)
∙ Business Continuity Plan (BCP)
∙ Disaster Recovery Plan (DRP)
∙ Business Impact Analysis (BIA)
∙ Criticality assessments

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

∙ Continuity of Operations Plan (COOP)
∙ Business Continuity Plan (BCP)
∙ Disaster Recovery Plan (DRP)
∙ Business Impact Analysis (BIA)
∙ Criticality assessments

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

∙ Continuity of Operations Plan (COOP)
∙ Business Continuity Plan (BCP)
∙ Disaster Recovery Plan (DRP)
∙ Business Impact Analysis (BIA)
∙ Criticality assessments

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

∙ Continuity of Operations Plan (COOP)
∙ Business Continuity Plan (BCP)
∙ Disaster Recovery Plan (DRP)
∙ Business Impact Analysis (BIA)
∙ Criticality assessments

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

Business Continuity & Disaster Recovery (BCD) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with BCD domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Contingency management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Limited technologies exist to support near real-time network infrastructure failover (e.g., redundant ISPs and redundant power).
▪ IT and/or cybersecurity personnel develop limited Disaster Recovery Plans (DRP) to recover business-critical Technology Assets, Applications and/or Services (TAAS) and services.

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.
▪ Business stakeholders and process owners identify business-critical TAASD and External Service Providers (ESPs).
▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to identify single points of failure from a TAASD perspective.
▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to develop BC/DR plans to recover business-critical TAASD.
▪ Data/process owners conduct a Business Impact Analysis (BIA) at least annually, or after any major technology or process change, to identify TAASD that are critical to the business, as well as single points of failure.
▪ Business stakeholders and process owners designate alternative decision-makers if primary decision-makers are unavailable.

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).
▪ An implemented and operational capability exists to facilitate the implementation of contingency planning controls to help ensure resilient Technology Assets, Applications and/or Services (TAAS) (e.g., Continuity of Operations Plan (COOP) or BC/DR playbooks).

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.
Business Continuity & Disaster Recovery (BCD) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational.
▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

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. Forbhreathnú

Defined Operational Resilience Requirements

Description

Mechanisms exist to define operational resilience requirements for Technology Assets, Applications, Services and/or Data (TAASD) to operate in a controlled and acceptable manner during:
(1) Routine operations; and
(2) Adverse conditions.

Possible Solutions & Considerations

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

∙ Business Impact Analysis (BIA)
∙ Documented RTO/RPO for critical systems

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

∙ Business Impact Analysis (BIA)
∙ Documented RTO/RPO/MTD for critical systems
∙ Business Continuity Plan (BCP)

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

∙ Business Impact Analysis (BIA)
∙ Continuity of Operations Plan (COOP)
∙ Documented resilience requirements per system in the CMDB

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

∙ Business Impact Analysis (BIA)
∙ Continuity of Operations Plan (COOP)
∙ BC/DR platform (e.g., Fusion Risk Management, Castellan)
∙ Resilience requirements traced to architecture and backup design

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

∙ Enterprise operational resilience program (e.g., aligned with ISO 22301 and DORA)
∙ BC/DR platform (e.g., Fusion Risk Management, ServiceNow BCM)
∙ Resilience requirements traced to architecture, backup and failover design
∙ Annual requirements recertification

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

Business Continuity & Disaster Recovery (BCD) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with BCD domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Contingency management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ IT and/or cybersecurity personnel develop limited Disaster Recovery Plans (DRP) to recover business-critical Technology Assets, Applications and/or Services (TAAS) and services.
▪ Recovery Time Objectives (RTOs) and/or Recovery Point Objectives (RPOs) are not formally planned for or resourced to meet.

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.1 Tagairtí

1.2 Ceanglais aitheanta

1.3 Rialacháin ghaolmhara

2. Ceanglais aitheanta

Ceanglais

3. Rialacháin ghaolmhara

Rialacháin
EULAW Airteagal 8 4

4.   Sainaithneoidh eintitis airgeadais gach sócmhainn faisnéise agus gach sócmhainn TFC, lena n-áirítear na cinn ar shuíomhanna cianda, acmhainní gréasáin agus an trealamh crua-earraí, agus déanfaidh siad mapáil ar na cinn a meastar gur trealamh criticiúil iad. Déanfaidh siad mapáil ar chumraíocht na sócmhainní faisnéise agus sócmhainní TFC agus ar na naisc agus na hidirspleáchais idir na sócmhainní faisnéise agus sócmhainní TFC éagsúla.
EULAW Airteagal 24 Comhpháirteanna an bheartais um leanúnachas gnó TFC
EULAW Airteagal 24 Comhpháirteanna an bheartais um leanúnachas gnó TFC
EULAW Airteagal 24 Comhpháirteanna an bheartais um leanúnachas gnó TFC
EULAW Airteagal 24 Comhpháirteanna an bheartais um leanúnachas gnó TFC
EULAW Airteagal 24 Comhpháirteanna an bheartais um leanúnachas gnó TFC
EULAW Airteagal 24 Comhpháirteanna an bheartais um leanúnachas gnó TFC
EULAW Airteagal 24 Comhpháirteanna an bheartais um leanúnachas gnó TFC
EULAW Airteagal 24 Comhpháirteanna an bheartais um leanúnachas gnó TFC
EULAW Airteagal 28 Rialachas agus eagrú
EULAW Airteagal 28 Rialachas agus eagrú
EULAW Airteagal 39 Comhpháirteanna an phlean leanúnachais gnó TFC
EULAW Airteagal 11 Freagairt agus athshlánú
-
EULAW Airteagal 12 Beartais agus nósanna imeachta cúltaca, nósanna imeachta agus modhanna athbhunaithe agus athshlánaithe
-
EULAW Airteagal 32 Slándáil na próiseála
-
EULAW Airteagal 21 Bearta bainistíochta riosca cibearshlándála
-
EULAW Airteagal 11 1

1.   Mar chuid de chreat bainistíochta riosca TFC dá dtagraítear in Airteagal 6(1) agus bunaithe ar na ceanglais sainaitheantais a leagtar amach in Airteagal 8, cuirfidh eintitis airgeadais beartas cuimsitheach leanúnachais gnó TFC i bhfeidhm, a d’fhéadfaí a ghlacadh mar bheartas tiomnaithe sonrach mar chuid lárnach de bheartas foriomlán leanúnachais gnó é.
EULAW Airteagal 11 2

2.   Cuirfidh eintitis airgeadais an beartas leanúnachais gnó TFC chun feidhme trí shocruithe, pleananna, nósanna imeachta agus sásraí tiomnaithe, iomchuí agus doiciméadaithe, a bhfuil mar aidhm leo:

(a)

leanúnachas fheidhmeanna criticiúla nó tábhachtacha an eintitis airgeadais a áirithiú;

(b)

freagairt ar gach teagmhas a bhaineann le TFC, agus iad a réiteach, go tapa, go hiomchuí agus go héifeachtach, ar bhealach ina gcuirtear teorainn leis an dochar agus lena dtugtar tús áite d’atosú na ngníomhaíochtaí agus na mbeart athshlánaithe;

(c)

pleananna tiomnaithe a ghníomhachtú, gan mhoill, lena gcumasaítear bearta, próisis agus teicneolaíochtaí srianta atá in oiriúint do gach cineál teagmhais a bhaineann le TFC agus dochar eile a chosc, chomh maith le nósanna imeachta saincheaptha freagartha agus athshlánaithe a bhunaítear i gcomhréir le hAirteagal 12;

(d)

tionchair, dochar agus caillteanais tosaigh a mheas;

(e)

gníomhaíochtaí cumarsáide agus bainistíochta géarchéime a leagan amach lena n-áirithítear go seoltar faisnéis cothrom le dáta chuig gach ball foirne inmheánach ábhartha agus gach geallsealbhóir seachtrach ábhartha i gcomhréir le hAirteagal 14, agus tuairisciú do na húdaráis inniúla i gcomhréir le hAirteagal 19.
EULAW Airteagal 11 3

3.   Mar chuid de chreat bainistíochta riosca TFC dá dtagraítear in Airteagal 6(1), cuirfidh eintitis airgeadais pleananna TFC freagartha agus athshlánaithe gaolmhara chun feidhme a chuirfear, i gcás eintitis airgeadais nach micrifhiontair iad, faoi réir athbhreithnithe iniúchta inmheánaigh neamhspleách.
EULAW Airteagal 11 4

4.   Déanfaidh eintitis airgeadais pleananna leanúnachais gnó TFC iomchuí a chur i bhfeidhm, a choinneáil ar bun, agus a thástáil go tréimhsiúil, go háirithe maidir le feidhmeanna criticiúla nó tábhachtacha arna seachfhoinsiú nó arna gcur amach ar conradh trí shocruithe le soláthraithe seirbhísí TFC tríú páirtí.
EULAW Airteagal 11 5

5.   Mar chuid den bheartas foriomlán leanúnachais gnó, déanfaidh eintitis airgeadais anailís ar thionchar gnó a neamhchosaintí ar mhórbhristeacha gnó. Faoin anailís ar thionchar gnó, measúnóidh eintitis airgeadais an tionchar a d’fhéadfadh a bheith ag mórbhristeacha gnó trí bhíthin critéir chainníochtúla agus cháilíochtúla, agus úsáid á baint as sonraí inmheánacha agus seachtracha agus anailís ar chásanna, de réir mar is iomchuí. Measfar san anailís ar thionchar gnó criticiúlacht na bhfeidhmeanna sainaitheanta agus mapáilte gnó, na bpróiseas tacaíochta, na spleáchas tríú páirtí agus na sócmhainní faisnéise, agus a n-idirspleáchais. Áiritheoidh eintitis airgeadais go ndéanfar sócmhainní TFC agus seirbhísí TFC a cheapadh agus a úsáid i gcomhréir iomlán leis an anailís ar thionchar gnó, go háirithe maidir le hiomarcaíocht na gcomhpháirteanna criticiúla uile a áirithiú ar bhealach leordhóthanach.
EULAW Airteagal 11 6

6.   Mar chuid dá mbainistíocht chuimsitheach riosca TFC, déanfaidh eintitis airgeadais na nithe seo a leanas:

(a)

pleananna leanúnachais gnó TFC agus pleananna freagartha agus athshlánaithe TFC a thástáil i ndáil le córais TFC lena dtacaítear leis na feidhmeanna uile ar bhonn bliantúil ar a laghad, agus i gcás aon mhórathruithe ar chórais TFC lena dtacaítear le feidhmeanna criticiúla nó tábhachtacha;

(b)

tástáil ar na pleananna cumarsáide géarchéime a bhunaítear i gcomhréir le hAirteagal 14.

Chun críocha na chéad fhomhíre, pointe (a), áireoidh eintitis airgeadais, nach micrifhiontair iad, sna pleananna tástála faoi chásanna cibirionsaithe agus lascaistrithe idir príomhbhonneagar TFC agus an acmhainneacht iomarcach, cúltacaí agus saoráidí iomarcacha is gá chun na hoibleagáidí a leagtar amach in Airteagal 12 a chomhlíonadh.

Athbhreithneoidh eintitis airgeadais a mbeartas leanúnachais gnó TFC agus a bpleananna freagartha agus athshlánaithe TFC go tráthrialta agus torthaí na dtástálacha, arna ndéanamh i gcomhréir leis an gcéad fhomhír agus le moltaí a eascraíonn as seiceálacha iniúchta nó athbhreithnithe maoirseachta, á gcur san áireamh.
EULAW Airteagal 11 7

7.   Beidh, feidhm bhainistíochta géarchéime ag eintitis airgeadais, nach micrifhiontair iad, ina leagfar amach, i gcás ina ngníomhachtófar a bpleananna leanúnachais gnó TFC nó a bpleananna freagartha agus athshlánaithe TFC, inter alia, nósanna imeachta soiléire chun cumarsáid inmheánach agus sheachtrach i gcás géarchéime a bhainistiú i gcomhréir le hAirteagal 14.
EULAW Airteagal 11 8

8.   Coimeádfaidh eintitis airgeadais taifid sho-inrochtana ar ghníomhaíochtaí roimh imeachtaí bristeacha agus lena linn nuair a ghníomhachtófar a bpleananna leanúnachais gnó TFC nó a bpleananna freagartha agus athshlánaithe TFC.
EULAW Airteagal 11 9

9.   Cuirfidh taisclanna lárnacha urrús cóipeanna de thorthaí na dtástálacha ar leanúnachas gnó TFC, nó de thorthaí cleachtaí eile den sórt sin, ar fáil do na húdaráis inniúla.
EULAW Airteagal 11 10

10.   Tuairisceoidh eintitis airgeadais, nach micrifhiontair iad, d’údaráis inniúla, arna iarraidh sin dóibh, meastachán ar chostais agus caillteanais chomhiomlánaithe bhliantúla de dheasca mórtheagmhais a bhaineann le TFC.
EULAW Airteagal 11 11

11.   I gcomhréir le hAirteagal 16 de Rialacháin (AE) Uimh. 1093/2010, (AE) Uimh. 1094/2010 agus (AE) Uimh. 1095/2010, ceapfaidh ÚMEnna, tríd an gComhchoiste, faoin 17 Iúil 2024 treoirlínte comhchoiteanna maidir le meastachán ar na costais agus na caillteanais chomhiomlánaithe bhliantúla dá dtagraítear i mír 10.
EULAW Airteagal 12 1

1.   Chun a áirithiú go n-athbhunófar córais agus sonraí TFC agus aga neamhfhónaimh íosta, briseadh agus caillteanas teoranta i gceist leo, mar chuid dá gcreat bainistíochta riosca TFC, déanfaidh eintitis airgeadais an méid seo a leanas a fhorbairt agus a dhoiciméadú:

(a)

beartais agus nósanna imeachta cúltaca lena sonrófar raon feidhme na sonraí is ábhar don chúltaca agus íosmhinicíocht an chúltaca, bunaithe ar chriticiúlacht na faisnéise nó leibhéal rúndachta na sonraí;

(b)

nósanna imeachta agus modhanna athbhunaithe agus athshlánaithe.

Saincheisteanna nasctha

Naisc
is related to Annual
is related to relative Control Weighting = 09
is related to Process
is related to Recover
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
is related to relative Control Weighting = 10
is related to Govern
is related to SCRM Focus Tier 1 STRATEGIC
is related to SCRM Focus Tier 2 OPERATIONAL
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 Failure to Achieve Strategic / Mission Objectives
blocks Inability to Demonstrate Due Diligence / Due Care
blocks Unreliable Assurance / Decision Information
blocks Recovery Failure / Unacceptable Recovery Delay
blocks Concentration / Single-Point Dependency Failure
blocks Third-Party Dependency Failure
blocks Loss of Data / Service Availability
blocks Loss of Critical Knowledge / Capability
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 Civil or Political Unrest
blocks Malicious Cyber Activity
blocks Hazardous Materials Emergencies
blocks Nuclear, Biological and Chemical (NBC) Weapons
blocks Physical Crime
blocks Terrorism & Armed Attacks
blocks Utility Service Disruption
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Statutory / Regulatory / Contractual Change
blocks Economic Shock / Market Disruption
blocks Supplier Financial Distress / Insolvency
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks Infrastructure Failure / Degradation
blocks PS-01.04B
blocks PS-02.02B
blocks OPS-21.01B
blocks SSO-06.02B
blocks BCM-01.01B
blocks BCM-01.02B
blocks BCM-03.01B
is blocked by BCD-02 Business Continuity Management System (BCMS) – Assessment Procedure
blocks CP-01 Policy and Procedures
blocks CP-02 Contingency Plan
blocks CP-10 System Recovery and Reconstitution
blocks IR-04(03) Continuity of Operations
blocks PM-08 Critical Infrastructure Plan
blocks CP-01 [L] Policy and Procedures
blocks CP-02 [L] Contingency Plan
blocks CP-10 [L] System Recovery and Reconstitution
blocks CP-01 [M] Policy and Procedures
blocks CP-02 [M] Contingency Plan
blocks CP-10 [M] System Recovery and Reconstitution
blocks CP-01 [H] Policy and Procedures
blocks CP-02 [H] Contingency Plan
blocks CP-10 [H] System Recovery and Reconstitution
blocks PM-08 [P] Critical Infrastructure Plan
blocks GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities
blocks ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
blocks PR.IR-02 The organization's technology assets are protected from environmental threats
blocks PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
blocks RS.MA-05 The criteria for initiating incident recovery are applied
blocks RC RECOVER
blocks RC.RP Incident Recovery Plan Execution
blocks RC.RP-02 Recovery actions are selected, scoped, prioritized, and performed
blocks RC.RP-04 Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms
  • 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.