+Risk Management Program

Risk Management Program

Description

Mechanisms exist to facilitate the implementation of strategic, operational and tactical risk management controls that are aligned with:
(1) The organization's Enterprise Risk Management (ERM); and
(2) Industry-recognized cybersecurity risk management practices.

Possible Solutions & Considerations

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

∙ Risk Management Program (RMP)

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

∙ Risk Management Program (RMP)

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

∙ Risk Management Program (RMP)

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

∙ Risk Management Program (RMP)

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

∙ Risk Management Program (RMP)

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

Risk Management (RSK) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with RSK domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Risk 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 use an informal process to identify, assess, remediate and report on risk.
▪ Risk management processes (e.g., risk assessments) focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
▪ Data/process owners are expected to self-manage risks associated with their Technology Assets, Applications, Services and/or Data (TAASD), based on the organization's published policies and standards, including the identification, remediation and reporting of risks.

Level 2 Planned Tracked

Risk Management (RSK) 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 RSK domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with RSK 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 RSK domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Risk management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Risk management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ Risk management processes (e.g., risk assessments) and technologies focus on protecting High Value Assets (HVAs), including environments where sensitive/regulated data is stored, transmitted and processed.
▪ IT and/or cybersecurity personnel implement and maintain a form of Risk Management Program (RMP) that provides operational guidance on how risk is identified, assessed, remediated and reported.
▪ Data/process owners are expected to self-manage risks associated with their systems, applications, services and data, based on the organization's published policies and standards, including the identification, remediation and reporting of risks.
▪ Business process owners (BPOs) are made aware of cybersecurity and data protection risk(s).

Level 3 Well Defined

Risk Management (RSK) 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 RSK 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 RSK domain capabilities are well-documented and kept current by process owners.
▪ A risk management team, or similar function, is appropriately staffed and supported to implement and maintain RSK domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of risk management operations (e.g., risk management solution, GRC platform and TPRM tool).
▪ 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 RSK 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 strategic, operational and tactical risk management controls.

Level 4 Quantitatively Controlled

Risk Management (RSK) 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

1.1 Referenzi

1.2 Rekwiżiti identifikati

1.3 Regolamenti relatati

2. Rekwiżiti identifikati

Rekwiżiti

3. Regolamenti relatati

Regolamenti
EULAW Artikolu 8 Konformità mar-rekwiżiti
-
EULAW Artikolu 9 Sistema ta' ġestjoni tar-riskju
-
EULAW Artikolu 9 Sistema ta' ġestjoni tar-riskju
-
EULAW Artikolu 9 Sistema ta' ġestjoni tar-riskju
-
EULAW Artikolu 9 Sistema ta' ġestjoni tar-riskju
-
EULAW Artikolu 17 Sistema ta' ġestjoni tal-kwalità
-
EULAW Artikolu 1 Profil tar-riskju ġenerali u kumplessità

Artikolu 1

Profil tar-riskju ġenerali u kumplessità

Meta jiġu żviluppati u implimentati l-politiki, il-proċeduri, il-protokolli u l-għodod tas-sigurtà tal-ICT imsemmija fit-Titolu II u l-qafas issimplifikat tal-ġestjoni tar-riskju tal-ICT imsemmi fit-Titolu III, għandhom jitqiesu d-daqs u l-profil tar-riskju ġenerali tal-entità finanzjarja, u n-natura, l-iskala u l-elementi ta’ kumplessità akbar jew imnaqqsa tas-servizzi, tal-attivitajiet u tal-operazzjonijiet tagħha, inklużi l-elementi relatati ma’:

(a) 

kriptaġġ u kriptografija;

(b) 

sigurtà tal-operazzjonijiet tal-ICT;

(c) 

sigurtà tan-network;

(d) 

ġestjoni tal-proġetti tal-ICT u tat-tibdil tagħhom;

(e) 

l-impatt potenzjali tar-riskju tal-ICT fuq il-kunfidenzjalità, l-integrità u d-disponibbiltà tad-data, u tat-tfixkil fuq il-kontinwità u d-disponibbiltà tal-attivitajiet tal-entità finanzjarja.
EULAW Artikolu 2 Elementi ġenerali tal-politiki, proċeduri, protokolli u għodda ta’ sigurtà tal-ICT
-
EULAW Artikolu 3 Ġestjoni tar-riskju tal-ICT

Artikolu 3

Ġestjoni tar-riskju tal-ICT

L-entitajiet finanzjarji għandhom jiżviluppaw, jiddokumentaw u jimplimentaw politiki u proċeduri tal-ġestjoni tar-riskju tal-ICT li għandu jkun fihom dawn kollha li ġejjin:

(a) 

indikazzjoni tal-approvazzjoni tal-livell ta’ tolleranza tar-riskju għar-riskju tal-ICT stabbilit f’konformità mal-Artikolu 6(8), il-punt (b) tar-Regolament (UE) 2022/2554;

(b) 

proċedura u metodoloġija għat-twettiq tal-valutazzjoni tar-riskju tal-ICT, li tidentifika:

(i) 

il-vulnerabbiltajiet u t-theddid li jaffettwaw jew li jistgħu jaffettwaw il-funzjonijiet tan-negozju appoġġati, is-sistemi tal-ICT u l-assi tal-ICT li jappoġġaw dawk il-funzjonijiet;

(ii) 

l-indikaturi kwantitattivi jew kwalitattivi biex jitkejlu l-impatt u l-probabbiltà tal-vulnerabbiltajiet u t-theddid imsemmija fil-punt (i);

(c) 

il-proċedura biex jiġu identifikati, implimentati u ddokumentati miżuri għat-trattament tar-riskju tal-ICT għar-riskji tal-ICT identifikati u vvalutati, inkluża d-determinazzjoni tal-miżuri għat-trattament tar-riskju tal-ICT meħtieġa biex ir-riskju tal-ICT jinġieb fil-livell tat-tolleranza tar-riskju msemmi fil-punt (a);

(d) 

għar-riskji residwali tal-ICT li jkunu għadhom preżenti wara l-implimentazzjoni tal-miżuri tat-trattament tar-riskju tal-ICT imsemmija fil-punt (c):

(i) 

dispożizzjonijiet dwar l-identifikazzjoni ta’ dawk ir-riskji residwali tal-ICT;

(ii) 

l-assenjazzjoni tar-rwoli u tar-responsabbiltajiet fir-rigward ta’:

(1) 

l-aċċettazzjoni tar-riskji residwali tal-ICT li jaqbżu l-livell ta’ tolleranza tar-riskju tal-entità finanzjarja msemmi fil-punt (a);

(2) 

għall-proċess ta’ rieżami msemmi fil-punt (iv) ta’ dan il-punt (d);

(iii) 

l-iżvilupp ta’ inventarju tar-riskji residwali tal-ICT aċċettati, inkluża ġustifikazzjoni għall-aċċettazzjoni tagħhom;

(iv) 

dispożizzjonijiet dwar ir-rieżami tar-riskji residwali tal-ICT aċċettati mill-anqas darba fis-sena, inklużi:

(1) 

l-identifikazzjoni ta’ kwalunkwe tibdil fir-riskji residwali tal-ICT;

(2) 

il-valutazzjoni tal-miżuri ta’ mitigazzjoni disponibbli;

(3) 

il-valutazzjoni ta’ jekk ir-raġunijiet li jiġġustifikaw l-aċċettazzjoni tar-riskji residwali tal-ICT jkunux għadhom validi u applikabbli fid-data tar-rieżami;

(e) 

dispożizzjonijiet dwar il-monitoraġġ ta’:

(i) 

kwalunkwe tibdil fix-xenarju tar-riskju tal-ICT u tat-theddid ċibernetiku;

(ii) 

vulnerabbiltajiet u theddid interni u esterni:

(iii) 

ir-riskju tal-ICT tal-entità finanzjarja li jippermetti l-individwazzjoni fil-pront ta’ tibdiliet li jistgħu jaffettwaw il-profil tar-riskju tal-ICT tagħha;

(f) 

dispożizzjonijiet dwar proċess biex jiġi żgurat li jitqies kwalunkwe tibdil fl-istrateġija tan-negozju u fl-istrateġija tar-reżiljenza operazzjonali diġitali tal-entità finanzjarja.

Għall-finijiet tal-ewwel paragrafu, il-punt (c), il-proċedura msemmija f’dak il-punt għandha tiżgura:

(a) 

il-monitoraġġ tal-effettività tal-miżuri għat-trattament tar-riskju tal-ICT implimentati;

(b) 

il-valutazzjoni ta’ jekk intlaħqux il-livelli ta’ tolleranza tar-riskju stabbiliti tal-entità finanzjarja;

(c) 

il-valutazzjoni ta’ jekk l-entità finanzjarja tkunx ħadet azzjonijiet biex tikkoreġi jew ittejjeb dawk il-miżuri meta meħtieġ.
EULAW Artikolu 27 Format u kontenut tar-rapport dwar ir-rieżami tal-qafas tal-ġestjoni tar-riskju tal-ICT
-
EULAW Artikolu 28 Governanza u organizzazzjoni
-
EULAW Artikolu 31 Ġestjoni tar-riskju tal-ICT
-
EULAW Artikolu 6 Qafas tal-ġestjoni tar-riskju tal-ICT
-
EULAW Artikolu 11 Rispons u rkupru
-
EULAW Artikolu 32 Sigurtà tal-ipproċessar
-
EULAW Artikolu 21 Miżuri ta' ġestjoni tar-riskji taċ-ċibersigurtà
-
EULAW Artikolu 6 Qafas tal-ġestjoni tar-riskju tal-ICT
-
EULAW Artikolu 11 Rispons u rkupru
-
EULAW Artikolu 32 Sigurtà tal-ipproċessar
-
EULAW Artikolu 21 Miżuri ta' ġestjoni tar-riskji taċ-ċibersigurtà
-
EULAW Artikolu 6 1

1.   L-entitajiet finanzjarji għandu jkollhom qafas sod, komprensiv u ddokumentat sewwa għall-ġestjoni tar-riskju tal-ICT bħala parti mis-sistema globali tagħhom għall-ġestjoni tar-riskju, li jippermettilhom jindirizzaw ir-riskju tal-ICT malajr, b’mod effiċjenti u komprensiv, u jiżguraw livell għoli ta’ reżiljenza operazzjonali diġitali.
EULAW Artikolu 6 2

2.   Il-qafas għall-ġestjoni tar-riskju tal-ICT għandu jinkludi tal-anqas l-istrateġiji, il-politiki, il-proċeduri, il-protokolli tal-ICT u l-għodod li huma meħtieġa biex b’mod debitu u adegwat jiġu protetti l-assi kollha ta’ informazzjoni u l-assi kollha tal-ICT, fosthom is-software tal-kompjuters, il-hardware u s-servers, kif ukoll biex jiġu protetti l-komponenti fiżiċi u l-infrastrutturi rilevanti kollha, bħall-bini, iċ-ċentri tad-data u ż-żoni kklassifikati bħala sensittivi, sabiex jiġi żgurat li l-assi kollha ta’ informazzjoni u l-assi kollha tal-ICT ikunu protetti b’mod adegwat mir-riskji inkluż il-ħsara u l-aċċess jew l-użu mhux awtorizzat.
EULAW Artikolu 6 3

3.   F’konformità mal-qafas tagħhom għall-ġestjoni tar-riskju tal-ICT, l-entitajiet finanzjarji għandhom jimminimizzaw l-impatt tar-riskju tal-ICT billi jużaw strateġiji, politiki, proċeduri, protokolli tal-ICT u għodod xierqa. Huma għandhom jipprovdu informazzjoni kompleta u aġġornata dwar ir-riskju tal-ICT u dwar il-qafas tal-ġestjoni tar-riskju tal-ICT tagħhom lill-awtoritajiet kompetenti fuq talba tagħhom.
EULAW Artikolu 6 4

4.   L-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandhom jassenjaw ir-responsabbiltà għall-ġestjoni u s-sorveljanza ta’ riskju tal-ICT lil funzjoni ta’ kontroll u jiżguraw livell xieraq ta’ indipendenza ta’ tali funzjoni ta’ kontroll sabiex jevitaw kunflitti ta’ interess. L-entitajiet finanzjarji għandhom jiżguraw segregazzjoni u indipendenza xierqa tal-funzjonijiet tal-ġestjoni tar-riskju tal-ICT, tal-funzjonijiet ta’ kontroll u tal-funzjonijiet tal-awditjar intern, skont it-tliet linji tal-mudell ta’ difiża, jew mudell intern ta’ kontroll u tal-ġestjoni tar-riskji.
EULAW Artikolu 6 5

5.   Il-qafas tal-ġestjoni tar-riskju tal-ICT għandu jiġi ddokumentat u rieżaminat mill-inqas darba fis-sena, jew perjodikament fil-każ tal-mikrointrapriżi, kif ukoll mal-okkorrenza ta’ inċidenti kbar relatati mal-ICT, u wara struzzjonijiet superviżorji jew konklużjonijiet derivati mill-ittestjar tar-reżiljenza operazzjonali diġitali jew il-proċessi tal-awditjar rilevanti. Huwa għandu jittejjeb kontinwament abbażi tal-lezzjonijiet meħuda mill-implimentazzjoni u l-monitoraġġ. Rapport dwar ir-rieżami tal-qafas tal-ġestjoni tar-riskju tal-ICT għandu jiġi ppreżentat lill-awtorità kompetenti fuq talba tagħha.
EULAW Artikolu 6 6

6.   Il-qafas tal-ġestjoni tar-riskju tal-ICT tal-entitajiet finanzjarji, għajr il-mikrointrapriżi, għandu jkun soġġett għal awditu intern minn awdituri fuq bażi regolari skont il-pjan ta’ awditu tal-entitajiet finanzjarji. Dawk l-awdituri għandu jkollhom biżżejjed għarfien, ħiliet u għarfien espert fir-riskju tal-ICT, kif ukoll indipendenza xierqa. Il-frekwenza u l-enfasi tal-awditi tal-ICT għandhom ikunu proporzjonati mar-riskju tal-ICT tal-entità finanzjarja.
EULAW Artikolu 6 7

7.   Abbażi tal-konklużjonijiet tar-rieżami intern tal-awditu, l-entitajiet finanzjarji għandhom jistabbilixxu proċess formali ta’ segwitu, inkluż regoli għall-verifika u r-rimedju f’waqthom tas-sejbiet kruċjali tal-awditu tal-ICT.
EULAW Artikolu 6 8

8.   Il-qafas tal-ġestjoni tar-riskju tal-ICT għandu jinkludi strateġija ta’ reżiljenza operazzjonali diġitali li turi kif għandu jiġi implimentat il-qafas. Għal dak l-għan, l-istrateġija ta’ reżiljenza operazzjonali diġitali għandha tinkludi l-metodi biex jiġi indirizzat ir-riskju tal-ICT u biex jintlaħqu l-objettivi speċifiċi tal-ICT, billi:

(a)

tispjega kif il-qafas tal-ġestjoni tar-riskju tal-ICT jappoġġja l-istrateġija u l-objettivi tan-negozju tal-entità finanzjarja;

(b)

tistabbilixxi l-livell ta’ tolleranza tar-riskju għar-riskju tal-ICT, f’konformità mal-predispożizzjoni għar-riskju tal-entità finanzjarja, u tiġi analizzata t-tolleranza tal-impatt għal tfixkil fl-ICT;

(c)

tistabbilixxi l-objettivi ċari għas-sigurtà tal-informazzjoni, inkluż indikaturi ewlenin tal-prestazzjoni u metriċi tar-riskju ewlenin;

(d)

tispjega l-arkitettura ta’ referenza tal-ICT u kwalunkwe bidla meħtieġa biex jintlaħqu objettivi speċifiċi tan-negozju;

(e)

tiddeskrivi l-mekkaniżmi differenti implimentati biex jindividwaw inċidenti relatati mal-ICT, jipprevjenu l-impatt tagħhom u jipprovdu protezzjoni minnu;

(f)

turi l-evidenza għas-sitwazzjoni attwali tar-reżiljenza operazzjonali diġitali abbażi tal-għadd ta’ inċidenti kbar marbuta mal-ICT irrappurtati u l-effikaċja tal-miżuri preventivi;

(g)

timplimenta l-ittestjar tar-reżiljenza operazzjonali diġitali, f’konformità mal-Kapitolu IV ta’ dan ir-Regolament;

(h)

tiddeskrivi strateġija ta’ komunikazzjoni f’każ ta’ inċidenti marbuta mal-ICT li d-divulgazzjoni tagħhom hija meħtieġa f’konformità mal-Artikolu 14.
EULAW Artikolu 6 9

9.   L-entitajiet finazjarji jistgħu, fil-kuntest tal-istrateġija ta’ reżiljenza operazzjonali diġitali msemmija fil-paragrafu 8, jiddefinixxu strateġija olistika tal-ICT b’diversi bejjiegħa, fil-livell ta’ grupp jew entità, waqt li juru d-dipendenzi ewlenin fuq fornituri terzi ta’ servizzi tal-ICT u jispjegaw ir-raġunament wara l-akkwist imħallat ta’ fornituri terzi ta’ servizzi tal-ICT.
EULAW Artikolu 6 10

10.   L-entitajiet finanzjarji jistgħu, f’konformità mal-liġi settorjali tal-Unjoni u dik nazzjonali, jesternalizzaw il-kompiti tal-verifika tal-konformità mar-rekwiżiti tal-ġestjoni tar-riskju tal-ICT lil impriżi intragrupp jew esterni. Fil-każ ta’ tali esternalizzazzjoni, l-entità finanzjarja tibqa’ terfa’ r-responsabbiltà aħħarija għall-verifika tal-konformità mar-rekwiżiti tal-ġestjoni tar-riskju 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.

Kwistjonijiet marbuta

Links
is related to Annual
is related to relative Control Weighting = 09
is related to Process
is related to Identify
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 of Accountability / Attribution
blocks Excessive or Unauthorized Privilege
blocks Unauthorized Privilege Elevation
blocks Unauthorized Access
blocks Loss, Theft or Damage of Assets
blocks Unauthorized Modification / Loss of System Integrity
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 Exposure from Unaddressed Vulnerabilities
blocks System / Service Compromise
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 Harm from Illegal, Abusive or Unsafe Content / Conduct
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 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 relative Control Weighting = 10
is related to Govern
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 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 Dysfunctional Management Practices
blocks Human Error
blocks Statutory / Regulatory / Contractual Change
blocks Data Quality Degradation / Data Poisoning
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Economic Shock / Market Disruption
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks OIS-04.01B
blocks OIS-07.01B
blocks OIS-08.03B
blocks OIS-08.01AC
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 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 Dysfunctional Management Practices
blocks Human Error
blocks Statutory / Regulatory / Contractual Change
blocks Data Quality Degradation / Data Poisoning
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Economic Shock / Market Disruption
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks OIS-04.01B
blocks OIS-07.01B
blocks OIS-08.03B
blocks OIS-08.01AC
is blocked by RSK-02 Risk Management Program – Assessment Procedure
blocks PM-09 Risk Management Strategy
blocks PM-29 Risk Management Program Leadership Roles
blocks RA-01 Policy and Procedures
blocks RA-01 [L] Policy and Procedures
blocks RA-01 [M] Policy and Procedures
blocks RA-01 [H] Policy and Procedures
blocks PM-09 [P] Risk Management Strategy
blocks RA-01 [P] Policy and Procedures
blocks 03.11.01 Risk Assessment
blocks 03.17.01 Supply Chain Risk Management Plan
blocks 03.17.03 Supply Chain Requirements and Processes
blocks GV GOVERN
blocks GV.RM Risk Management Strategy
blocks GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders
blocks GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk management processes
blocks GV.RM-04 Strategic direction that describes appropriate risk response options is established and communicated
blocks GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated
blocks GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually …
blocks GV.OV-02 The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks
blocks GV.OV-03 Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed
blocks GV.SC Cybersecurity Supply Chain Risk Management
blocks GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational …
blocks GV.SC-03 Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes
blocks GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of …
blocks GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored …
blocks ID IDENTIFY
blocks ID.RA Risk Assessment
blocks ID.IM Improvement
blocks PR PROTECT
blocks PR.IR Technology Infrastructure Resilience
  • 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.