+Business Continuity & Disaster Recovery (BC/DR) Plans
---+Recovery Time / Point Objectives (RTO / RPO)

Business Continuity & Disaster Recovery (BC/DR) Plans

Description

Mechanisms exist for process owners to establish and maintain formal Business Continuity & Disaster Recovery (BC/DR) plans to ensure information is detailed enough, accurate and representative of current operations in order to sustain and/or restore operations under adverse conditions.

Possible Solutions & Considerations

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

∙ Basic business continuity plan
∙ Regular data backup

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

∙ Business continuity plan
∙ Tested backup and restore procedures

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

∙ Formal BCP/DRP program
∙ Regular backup testing
∙ Alternate processing capability

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

∙ Enterprise BCP/DRP program
∙ DR site
∙ Annual exercises
∙ RTO/RPO targets

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

∙ Enterprise BC/DR platform (e.g., Zerto, Veeam Enterprise)
∙ Dedicated DR site
∙ Automated failover
∙ Annual DR exercises

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 develop BC/DR plans to recover business-critical TAASD.

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 for process owners to establish and maintain formal Business Continuity & Disaster Recovery (BC/DR) plans to ensure information is detailed enough, accurate and representative of current operations in order to sustain and/or restore operations under adverse conditions.

Level 4 Quantitatively Controlled

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. Ħarsa ġenerali

Recovery Time / Point Objectives (RTO / RPO)

Description

Mechanisms exist to facilitate recovery operations in accordance with Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs).

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)
∙ Recovery Time Objectives (RTOs)
∙ Recovery Point Objectives (RPOs)

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

∙ Continuity of Operations Plan (COOP)
∙ Business Continuity Plan (BCP)
∙ Disaster Recovery Plan (DRP)
∙ Recovery Time Objectives (RTOs)
∙ Recovery Point Objectives (RPOs)

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

∙ Continuity of Operations Plan (COOP)
∙ Business Continuity Plan (BCP)
∙ Disaster Recovery Plan (DRP)
∙ Recovery Time Objectives (RTOs)
∙ Recovery Point Objectives (RPOs)

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

∙ Continuity of Operations Plan (COOP)
∙ Business Continuity Plan (BCP)
∙ Disaster Recovery Plan (DRP)
∙ Recovery Time Objectives (RTOs)
∙ Recovery Point Objectives (RPOs)

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

∙ Continuity of Operations Plan (COOP)
∙ Business Continuity Plan (BCP)
∙ Disaster Recovery Plan (DRP)
∙ Recovery Time Objectives (RTOs)
∙ Recovery Point Objectives (RPOs)

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

SCR-CMM Level 2 criteria definitions are not available for this control:
▪ A reasonable person would conclude a well-defined and standardized process is required.
▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization.
▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).

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 recovery operations in accordance with Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs).

Level 4 Quantitatively Controlled

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.1 Referenzi

1.2 Rekwiżiti identifikati

1.3 Regolamenti relatati

2. Rekwiżiti identifikati

Rekwiżiti

3. Regolamenti relatati

Regolamenti
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 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 24 1

1.   Għall-fini tal-valutazzjoni tal-istat ta’ tħejjija għall-ġestjoni ta’ inċidenti relatati mal-ICT, tal-identifikazzjoni ta’ dgħufijiet, nuqqasijiet u lakuni fir-reżiljenza operazzjonali diġitali u tal-implimentazzjoni fil-pront ta’ miżuri korrettivi, l-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandhom, b’kont meħud tal-kriterji stabbiliti fl-Artikolu 4(2), jistabbilixxu, iżommu u jirrieżaminaw programm tajjeb u komprensiv ta’ ttestjar tar-reżiljenza operazzjonali diġitali bħala parti integrali mill-qafas tal-ġestjoni tar-riskju tal-ICT imsemmi fl-Artikolu 6.
EULAW Artikolu 24 2

2.   Il-programm tal-ittestjar tar-reżiljenza operazzjonali diġitali għandu jinkludi firxa ta’ valutazzjonijiet, testijiet, metodoloġiji, prattiki u għodod li għandhom jiġu applikati f’konformità mal-Artikoli 25 u 26.
EULAW Artikolu 24 3

3.   Meta jwettqu l-programm tal-ittestjar tar-reżiljenza operazzjonali diġitali msemmi fil-paragrafu 1 ta’ dan l-Artikolu, l-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandhom isegwu approċċ ibbażat fuq ir-riskju filwaqt li jqisu l-kriterji stabbiliti fl-Artikolu 4(2) b’kont dovut tax-xenarju li qed jevolvi tar-riskju tal-ICT, kwalunkwe riskju speċifiku li għalih l-entità finanzjarja kkonċernata hija jew tista’ tkun esposta, il-kritikalità tal-assi tal-informazzjoni u tas-servizzi pprovduti, kif ukoll kwalunkwe fattur ieħor li l-entità finanzjarja tqis xieraq.
EULAW Artikolu 24 4

4.   L-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandhom jiżguraw li t-testijiet jitwettqu minn partijiet indipendenti, kemm jekk ikunu interni kif ukoll jekk ikunu esterni. Meta t-testijiet jitwettqu internament, l-entitajiet finanzjarji għandhom jiddedikaw biżżejjed riżorsi u jiżguraw li l-kunflitti ta’ interess għal dawk li jittestjaw jiġu evitati matul il-fażijiet kollha tat-tfassil u tal-eżekuzzjoni tat-test.
EULAW Artikolu 24 5

5.   L-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandhom jistabbilixxu proċeduri u politiki biex jipprijoritizzaw, jikklassifikaw u jirrimedjaw il-kwistjonijiet kollha skoperti matul it-twettiq tat-testijiet u għandhom jistabbilixxu metodoloġiji ta’ validazzjoni interna biex jaċċertaw li d-dgħufijiet, in-nuqqasijiet jew il-lakuni kollha identifikati jiġu indirizzati bis-sħiħ.
EULAW Artikolu 24 6

6.   L-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandhom jiżguraw, mill-inqas darba fis-sena, li jitwettqu testijiet xierqa fuq is-sistemi u l-applikazzjonijiet kollha tal-ICT li jappoġġjaw funzjonijiet kritiċi jew importanti.
EULAW Artikolu 24 Komponenti tal-politika dwar il-kontinwità tal-operat tal-ICT
-
EULAW Artikolu 24 Komponenti tal-politika dwar il-kontinwità tal-operat tal-ICT
-
EULAW Artikolu 24 Komponenti tal-politika dwar il-kontinwità tal-operat tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 26 Pjanijiet ta’ rispons u ta’ rkupru tal-ICT
-
EULAW Artikolu 39 Komponenti tal-pjan ta’ kontinwità tal-operat tal-ICT
-
EULAW Artikolu 39 Komponenti tal-pjan ta’ kontinwità tal-operat tal-ICT
-
EULAW Artikolu 39 Komponenti tal-pjan ta’ kontinwità tal-operat tal-ICT
-
EULAW Artikolu 39 Komponenti tal-pjan ta’ kontinwità tal-operat tal-ICT
-
EULAW Artikolu 39 Komponenti tal-pjan ta’ kontinwità tal-operat tal-ICT
-

Kwistjonijiet marbuta

Links
is related to Annual
is related to relative Control Weighting = 06
is related to Process
is related to Recover
is related to SCRM Focus Tier 2 OPERATIONAL
is related to SCRM Focus Tier 3 TACTICAL
blocks Unauthorized Retention / Inability to Dispose of Data
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 Lack of oversight of internal controls
blocks Lack of oversight of third-party controls
blocks Incident Persistence / Recurrence
blocks Undetected / Delayed Detection of Adverse Activity
blocks Lack of a security-minded workforce
blocks Third-Party Cybersecurity Compromise / Exposure
blocks Third-Party Physical Security Disruption / Exposure
blocks Sub-Tier / Fourth-Party Supply Chain Exposure
blocks Third-Party Legal / Compliance Exposure
blocks Harm from Unauthorized / Unintended Product or Service Use
blocks Third-Party Dependency Failure
is related to Quarterly
is related to relative Control Weighting = 09
is related to Protect
is related to SCRM Focus Tier 1 STRATEGIC
blocks Business / Service Interruption
blocks Data Loss / Integrity Compromise
blocks Reduced Operational Productivity
blocks Revenue Loss
blocks Contractual Default / Termination
blocks Reputational Harm / Loss of Stakeholder Trust
blocks Regulatory / Legal / Contractual Financial Liability
blocks Failure to Achieve Strategic / Mission Objectives
blocks Loss of Authorization / Certification / License
blocks Inability to Demonstrate Due Diligence / Due Care
blocks Unreliable Assurance / Decision Information
blocks Delayed Containment / Increased Incident Impact
blocks Incident Response / Recovery Cost
blocks Recovery Failure / Unacceptable Recovery Delay
blocks Concentration / Single-Point 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 Malicious Cyber Activity
blocks Physical Crime
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Statutory / Regulatory / Contractual Change
blocks Data Quality Degradation / Data Poisoning
blocks Economic Shock / Market Disruption
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
is blocked by BCD-04 Business Continuity & Disaster Recovery (BC/DR) Plans – 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.