+Identification & Authentication for Devices
---+Device Attestation
---+Device Authorization Enforcement

Identification & Authentication for Devices

Description

Mechanisms exist to uniquely identify and centrally Authenticate, Authorize and Audit (AAA) devices before establishing a connection using bidirectional authentication that is cryptographically- based and replay resistant.

Possible Solutions & Considerations

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

∙ Microsoft Active Directory (https://microsoft.com)
∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

∙ Microsoft Active Directory (https://microsoft.com)
∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

∙ Microsoft Active Directory (https://microsoft.com)
∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

∙ Microsoft Active Directory (https://microsoft.com)
∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

∙ Microsoft Active Directory (https://microsoft.com)
∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

Identification & Authentication (IAC) 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 IAC domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with IAC 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 IAC domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Identity & Access Management (IAM)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines) to enforce Logical Access Control (LAC).
▪ IAM may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel to implement Role Based Access Control (RBAC) practices for the management of user, group and system accounts, including privileged accounts.
▪ A directory services technology is used to centrally manage identities and permissions with RBAC. Due to technical or business limitations, asset/process owners are empowered to operate a decentralized access control program for their specific Technology Assets, Applications and/or Services (TAAS) that cannot be integrated into directory services.
▪ Configuration management and IAM functions collaborate to ensure Secure Baseline Configurations (SBC) enforce “least privileges” on TAAS.

Level 3 Well Defined

Identification & Authentication (IAC) 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 IAC 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 IAC domain capabilities are well-documented and kept current by process owners.
▪ An Identity & Access Management (IAM) team, or similar function, is appropriately staffed and supported to implement and maintain IAC domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of IAM operations (e.g., directory services, Authenticate, Authorize and Audit (AAA) solution).
▪ 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 IAC 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 uniquely identify and centrally Authenticate, Authorize and Audit (AAA) devices before establishing a connection using bidirectional authentication that is cryptographically- based and replay resistant.

Level 4 Quantitatively Controlled

Identification & Authentication (IAC) 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. Yleiskatsaus

Device Attestation

Description

Mechanisms exist to ensure device identification and authentication is accurate by centrally-managing the joining of systems to the domain as part of the initial asset configuration management process.

Possible Solutions & Considerations

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

∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

∙ Microsoft Entra (https://microsoft.com)
∙ AWS IAM (https://aws.amazon.com)

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

Identification & Authentication (IAC) 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 IAC domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with IAC 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 IAC domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Identity & Access Management (IAM)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines) to enforce Logical Access Control (LAC).
▪ IAM may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel to implement Role Based Access Control (RBAC) practices for the management of user, group and system accounts, including privileged accounts.
▪ A directory services technology is used to centrally manage identities and permissions with RBAC. Due to technical or business limitations, asset/process owners are empowered to operate a decentralized access control program for their specific Technology Assets, Applications and/or Services (TAAS) that cannot be integrated into directory services.
▪ Configuration management and IAM functions collaborate to ensure Secure Baseline Configurations (SBC) enforce “least privileges” on TAAS.

Level 3 Well Defined

Identification & Authentication (IAC) 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 IAC 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 IAC domain capabilities are well-documented and kept current by process owners.
▪ An Identity & Access Management (IAM) team, or similar function, is appropriately staffed and supported to implement and maintain IAC domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of IAM operations (e.g., directory services, Authenticate, Authorize and Audit (AAA) solution).
▪ 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 IAC 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 ensure device identification and authentication is accurate by centrally-managing the joining of systems to the domain as part of the initial asset configuration management process.

Level 4 Quantitatively Controlled

Identification & Authentication (IAC) 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

Identification & Authentication (IAC) 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.
▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes.
▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.
Device Authorization Enforcement

Description

Mechanisms exist to enforce cryptographic communications keys to prevent one key from being used to access multiple devices.

Possible Solutions & Considerations

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

∙ Policy requiring device authorization before network access

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

∙ Device authorization policy
∙ Require known devices for network access

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

∙ Device authorization enforcement
∙ Certificate-based device auth or MDM enrollment

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

∙ NAC solution for device authorization (e.g., Cisco ISE, Aruba ClearPass)

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

∙ Enterprise NAC platform (e.g., Cisco ISE, Aruba ClearPass, Forescout)
∙ Certificate-based device authentication
∙ Zero-trust device posture checking

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

Identification & Authentication (IAC) 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 IAC 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 IAC domain capabilities are well-documented and kept current by process owners.
▪ An Identity & Access Management (IAM) team, or similar function, is appropriately staffed and supported to implement and maintain IAC domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of IAM operations (e.g., directory services, Authenticate, Authorize and Audit (AAA) solution).
▪ 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 IAC 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 enforce cryptographic communications keys to prevent one key from being used to access multiple devices.

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 Viittaukset

1.2 Tunnistetut vaatimukset

1.3 Liittyvät säädökset

2. Tunnistetut vaatimukset

Vaatimukset

3. Liittyvät säädökset

Säädökset
EULAW 13 artikla Verkkoturvallisuuden hallinta

13 artikla

Verkkoturvallisuuden hallinta

Finanssiyhteisöjen on osana suojatoimia, joilla varmistetaan verkkojen turvallisuus tunkeutumista ja tietojen väärinkäyttöä vastaan, laadittava, dokumentoitava ja otettava käyttöön verkkoturvallisuuden hallintaa koskevat toimintaperiaatteet, menettelyt, protokollat ja välineet, mukaan lukien kaikki seuraavat:

a) 

TVT-järjestelmien ja -verkkojen eriyttäminen ja segmentointi ottaen huomioon

i) 

niiden toimintojen kriittisyyden ja merkityksen, joita kyseisillä TVT-järjestelmillä ja -verkoilla tuetaan;

ii) 

asetuksen (EU) 2022/2554 8 artiklan 1 kohdan mukaisesti laaditun luokittelun;

iii) 

kyseisiä TVT-järjestelmiä ja -verkkoja käyttävän TVT-omaisuuden kokonaisriskiprofiilin;

b) 

kaikkien finanssiyhteisön verkkoyhteyksien ja datavirtojen dokumentointi;

c) 

erillisen ja tarkoitukseen varatun verkon käyttö TVT-omaisuuden hallinnointia varten;

d) 

verkkoon pääsyn valvontatoimenpiteiden määrittäminen ja toteuttaminen, jotta estetään ja havaitaan luvattomien laitteiden tai järjestelmien tai sellaisten päätepisteiden kautta tapahtuvat yhteydet finanssiyhteisön verkkoon, jotka eivät täytä finanssiyhteisön turvallisuusvaatimuksia;

e) 

yritysverkkojen, julkisten verkkojen, kotimaisten verkkojen, kolmansien osapuolten verkkojen ja langattomien verkkojen kautta kulkevien verkkoyhteyksien salaaminen käytettyjä viestintäprotokollia varten ottaen huomioon hyväksytyn tietoluokittelun tulokset, TVT-riskinarvioinnin tulokset ja 6 artiklan 2 kohdassa tarkoitettu verkkoyhteyksien salaus;

f) 

verkkojen suunnittelu finanssiyhteisön vahvistamien TVT-turvallisuusvaatimusten mukaisesti ottaen huomioon johtavat käytännöt, joilla varmistetaan verkon luottamuksellisuus, eheys ja käytettävyys;

g) 

sisäisten verkkojen sekä internetin ja muiden ulkoisten yhteyksien välisen verkkoliikenteen suojaaminen;

h) 

tehtävien ja vastuiden sekä vaiheiden määrittäminen palomuuria koskevien sääntöjen ja yhteyssuodattimien määrittelyä, täytäntöönpanoa, hyväksymistä, muuttamista ja tarkistamista varten;

i) 

verkkoarkkitehtuurin ja verkon turvallisuussuunnittelun tarkastelu kerran vuodessa, tai mikroyritysten osalta säännöllisesti, mahdollisten haavoittuvuuksien tunnistamiseksi;

j) 

toimenpiteet, joilla aliverkot, verkon osat ja verkkolaitteet voidaan tarvittaessa tilapäisesti eristää;

k) 

kaikkien verkon osien turvallisen perustason konfiguraation käyttöönotto sekä verkon ja verkkolaitteiden suojaaminen myyjän ohjeiden, soveltuvin osin asetuksen (EU) N:o 1025/2012 2 artiklan 1 alakohdassa määriteltyjen standardien sekä johtavien käytäntöjen mukaisesti;

l) 

menettelyt, joilla rajoitetaan järjestelmä- ja etäistuntoja sekä lukitaan ja lopetetaan järjestelmä- ja etäistunnot tietyn ajanjakson jälkeen;

m) 

verkkopalvelusopimusten osalta:

i) 

kaikkien verkkopalvelujen TVT- ja tietoturvatoimenpiteiden, palvelutasojen ja hallintaa koskevien vaatimusten yksilöinti ja määrittely;

ii) 

sen määrittäminen, tarjoaako kyseiset palvelut konsernin sisäinen TVT-palveluntarjoaja vai TVT-palveluntarjoajana oleva kolmas osapuoli.

Sovellettaessa h alakohtaa finanssiyhteisöjen on tarkasteltava palomuuria koskevia sääntöjä ja yhteyssuodattimia säännöllisesti asetuksen (EU) 2022/2554 8 artiklan 1 kohdan mukaisesti vahvistetun luokittelun ja asianomaisten TVT-järjestelmien yleisen riskiprofiilin mukaisesti. Kriittisiä tai tärkeitä toimintoja tukevien TVT-järjestelmien osalta finanssiyhteisöjen on tarkistettava olemassa olevien palomuuria koskevien sääntöjen ja yhteyssuodattimien riittävyys vähintään kuuden kuukauden välein.

Linkitetyt tehtävät

Linkit
is related to Annual
is related to relative Control Weighting = 09
is related to Technology
is related to Protect
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 Data from Cloud Storage
blocks Transfer Data to Cloud Account
blocks Unsecured Credentials
blocks Cloud Instance Metadata API
blocks Data from Configuration Repository
blocks SNMP (MIB Dump)
blocks Network Device Configuration Dump
blocks Multi-Factor Authentication Request Generation
blocks Loss of Accountability / Attribution
blocks Excessive or Unauthorized Privilege
blocks Unauthorized Privilege Elevation
blocks Unauthorized Access
blocks Identity Compromise / Impersonation
blocks Unauthorized Modification / Loss of System Integrity
blocks System / Data Compromise (Technical Vector)
blocks System / Data Compromise (Non-Technical Vector)
blocks System / Service Compromise
blocks Undetected / Delayed Detection of Adverse Activity
blocks OT Safety / Process Availability Failure
blocks Loss of Confidentiality
blocks Loss of Data Integrity
blocks Loss of Authenticity / Provenance
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 Utility Service Disruption
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Counterfeit / Non-Conforming Products
blocks Product Defect / Design Failure
blocks Infrastructure Failure / Degradation
blocks Harvest Now / Decrypt Later (HNDL)
blocks Cryptographic Compromise / Cryptanalytic Capability Advancement
blocks AM-09.01AC
blocks AM-09.02AC
blocks IAM-07.03AC
blocks IAM-08.01B
is blocked by IAC-34 Identification & Authentication for Devices – Assessment Procedure
blocks IA-03 Device Identification and Authentication
blocks IA-03(01) Cryptographic Bidirectional Authentication
blocks IA-03(04) Device Attestation
blocks IA-03 [M] Device Identification and Authentication
blocks IA-03 [H] Device Identification and Authentication
blocks 03.01.18 Access Control for Mobile Devices
blocks 03.05.02 Device Identification and Authentication
blocks PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
blocks PR.AA-03 Users, services, and hardware are authenticated
blocks PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of …
  • 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.