+Identity & Access Management (IAM)

Identity & Access Management (IAM)

Description

Mechanisms exist to facilitate the implementation of Identification and Access Management (IAM) controls.

Possible Solutions & Considerations

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

∙ Strong password policy
∙ MFA for key accounts

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

∙ Password manager
∙ MFA on all accounts
∙ Identity policy

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

∙ Identity & Access Management (IAM) program

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

∙ Identity & Access Management (IAM) program

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

∙ Identity & Access Management (IAM) program

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

Identification & Authentication (IAC) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with IAC domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Identity & Access Management (IAM)-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ IAM controls are primarily administrative in nature (e.g., policies & standards) to manage accounts and permissions.
▪ IT and/or cybersecurity personnel identify and implement IAM cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements.
▪ Active Directory (AD), or a similar technologies, are used to centrally manage identities and permissions, but asset/process owners are authorized to operate a decentralized access control program for their specific Technology Assets, Applications, Services and/or Data (TAASD).

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.
▪ IAM restricts the assignment of privileged accounts to entity-defined personnel and/or roles (privilege assignment requires management approval).

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 facilitate the implementation of identification and access management controls.

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. Resumen

1.1 Referencias

1.2 Requisitos identificados

1.3 Regulaciones relacionadas

2. Requisitos identificados

Requisitos

3. Regulaciones relacionadas

Regulaciones
EULAW Artículo 20 Gestión de la identidad
-
EULAW Artículo 20 Gestión de la identidad
-
EULAW Artículo 21 Control de acceso

Artículo 21

Control de acceso

Dentro de su control de los derechos de gestión de accesos, las entidades financieras elaborarán, documentarán y aplicarán una política que incluya todos los aspectos siguientes:

a) 

la asignación de derechos de acceso a los activos de TIC sobre la base de los principios de «necesidad de conocer», «necesidad de uso» y «mínimo privilegio», también para el acceso a distancia y de emergencia;

b) 

la separación de funciones con el fin de impedir el acceso injustificado a datos esenciales o la asignación de combinaciones de derechos de acceso que puedan utilizarse para eludir los controles;

c) 

una disposición sobre responsabilidad de los usuarios que limite en la medida de lo posible el uso de cuentas de usuario genéricas y compartidas y garantice que, en todo momento, los usuarios sean identificables cuando realicen acciones en los sistemas de TIC;

d) 

una disposición sobre las restricciones de acceso a los activos de TIC que establezca controles y herramientas para impedir el acceso no autorizado;

e) 

procedimientos de gestión de cuentas para la concesión, modificación o revocación de derechos de acceso en relación con las cuentas de usuario y las cuentas genéricas, incluidas las cuentas de administrador genéricas, que incluyan disposiciones sobre todos los aspectos siguientes:

i) 

asignación de funciones y responsabilidades para la concesión, revisión y revocación de los derechos de acceso,

ii) 

asignación de acceso privilegiado, de emergencia y de administrador sobre la base del principio de «necesidad de uso» o con carácter ad hoc para todos los sistemas de TIC,

iii) 

retirada de los derechos de acceso sin demora indebida al término de la relación laboral o cuando el acceso ya no sea necesario,

iv) 

actualización de los derechos de acceso cuando se requiera introducir cambios y al menos una vez al año para todos los sistemas de TIC que no sustenten funciones esenciales o importantes y al menos cada seis meses para los sistemas de TIC que sustenten funciones esenciales o importantes;

f) 

métodos de autenticación, incluidos todos los aspectos siguientes:

i) 

el uso de métodos de autenticación que sean acordes con la clasificación establecida de conformidad con el artículo 8, apartado 1, del Reglamento (UE) 2022/2554 y con el perfil de riesgo general de los activos de TIC, y que tengan en cuenta las prácticas punteras,

ii) 

el uso de métodos de autenticación sólidos de conformidad con las prácticas y técnicas punteras para el acceso a distancia a la red de la entidad financiera, el acceso privilegiado y el acceso a los activos de TIC que sustenten funciones esenciales o importantes o a los activos de TIC que sean de acceso público;

g) 

medidas de control del acceso físico que incluyan lo siguiente:

i) 

la identificación y el registro de las personas físicas autorizadas a acceder a los locales, los centros de datos y las zonas sensibles designadas determinadas por la entidad financiera en los que se encuentren los activos de TIC y de información,

ii) 

la concesión de derechos de acceso físico a los activos de TIC esenciales únicamente a las personas autorizadas, de conformidad con los principios de «necesidad de conocer» y «mínimo privilegio» y con carácter ad hoc,

iii) 

el seguimiento del acceso físico a los locales, los centros de datos y las zonas sensibles designadas determinadas por la entidad financiera en los que se encuentren los activos de TIC, los activos de información o ambos,

iv) 

la revisión de los derechos de acceso físico para garantizar la rápida revocación de los derechos que no sean necesarios.

A efectos de la letra e), inciso i), las entidades financieras establecerán el período de conservación teniendo en cuenta los objetivos empresariales y de seguridad de la información, los motivos por los que se consigna el hecho de que se trate en los registros y los resultados de la evaluación del riesgo relacionado con las TIC.

A efectos de la letra e), inciso ii), las entidades financieras utilizarán, en la medida de lo posible, cuentas específicas para la realización de tareas administrativas en los sistemas de TIC. Cuando sea factible y adecuado, las entidades financieras implementarán soluciones automatizadas para la gestión del acceso privilegiado.

A efectos de la letra g), inciso i), la identificación y el registro serán acordes con la importancia de los locales, los centros de datos y las zonas sensibles designadas y con el carácter esencial de las operaciones que se realicen en ellos o los sistemas de TIC que se encuentren en ellos.

A efectos de la letra g), inciso iii), el seguimiento será acorde con la clasificación establecida de conformidad con el artículo 8, apartado 1, del Reglamento (UE) 2022/2554 y con el carácter esencial de la zona a la que se acceda.
EULAW Artículo 33 Control de acceso

Artículo 33

Control de acceso

Las entidades financieras a que se refiere el artículo 16, apartado 1, del Reglamento (UE) 2022/2554 elaborarán, documentarán y aplicarán procedimientos para controlar el acceso lógico y físico, velarán por su cumplimiento, los someterán a seguimiento y los revisarán periódicamente. Dichos procedimientos incluirán los siguientes elementos de control del acceso lógico y físico:

a) 

derechos de acceso a los activos de información, los activos de TIC y las funciones que sustentan, así como a los emplazamientos esenciales de actividad de la entidad financiera, gestionados sobre la base de los principios de «necesidad de conocer», «necesidad de uso» y «mínimo privilegio», también para el acceso a distancia y de emergencia;

b) 

responsabilidad de los usuarios, en virtud de la cual se garantice la identificación de los usuarios en las acciones realizadas en los sistemas de TIC;

c) 

procedimientos de gestión de cuentas para la concesión, modificación o revocación de derechos de acceso en relación con las cuentas de usuario y cuentas genéricas, incluidas las cuentas de administrador genéricas;

d) 

métodos de autenticación acordes con la clasificación a que se refiere el artículo 30, apartado 1, y con el perfil de riesgo general de los activos de TIC, y basados en las prácticas punteras;

e) 

revisión periódica de los derechos de acceso y retirada de esos derechos cuando ya no sean necesarios.

A efectos de la letra c), la entidad financiera asignará, para todos los activos de TIC, acceso privilegiado, de emergencia y de administrador sobre la base del principio de «necesidad de uso» o con carácter ad hoc, y lo registrará de conformidad con el artículo 34, apartado 1, letra f).

A efectos de la letra d), las entidades financieras utilizarán métodos de autenticación fuerte basados en las prácticas punteras para el acceso a distancia a sus redes, el acceso privilegiado y el acceso a los activos de TIC que sustenten funciones esenciales o importantes que sean de acceso público.
EULAW Artículo 9 Protección y prevención
-
EULAW Artículo 21 Medidas para la gestión de riesgos de ciberseguridad
-
EULAW Artículo 9 Protección y prevención
-
EULAW Artículo 21 Medidas para la gestión de riesgos de ciberseguridad
-
EULAW Artículo 9 4

4.   Como parte del marco de gestión del riesgo relacionado con las TIC a que se refiere el artículo 6, apartado 1, las entidades financieras deberán:

a)

elaborar y documentar una política de seguridad de la información que defina normas para proteger la confidencialidad, disponibilidad, integridad o autenticidad de los datos, activos de información y activos de TIC, incluidos los de sus clientes, en su caso;

b)

siguiendo un enfoque basado en el riesgo, establecer una estructura de gestión sólida de redes e infraestructuras utilizando técnicas, métodos y protocolos adecuados que puedan incluir la aplicación de mecanismos automatizados para aislar los activos de información afectados en caso de ciberataques;

c)

aplicar políticas que limiten el acceso físico o lógico a los activos de información y activos de TIC a lo que sea necesario únicamente para funciones y actividades legítimas y aprobadas, y establecer a tal fin un conjunto de políticas, procedimientos y controles que se centren en los derechos de acceso y garanticen una buena administración de estos;

d)

aplicar políticas y protocolos para mecanismos de autenticación fuerte, basados en estándares pertinentes y sistemas de control específicos, y medidas de protección de las claves criptográficas mediante las que se cifran los datos en función de los resultados de los procesos aprobados de clasificación de datos y evaluación de riesgos relacionados con las TIC;

e)

aplicar políticas, procedimientos y controles documentados para la gestión de los cambios en las TIC, incluidos los cambios en el software, el hardware, los componentes de firmware, los sistemas o los parámetros de seguridad, que se basen en un enfoque de evaluación de riesgos y formen parte integrante del proceso general de gestión de cambios de la entidad financiera, a fin de garantizar que todos los cambios en los sistemas de TIC se registren, sometan a prueba, evalúen, aprueben, apliquen y verifiquen de forma controlada;

f)

contar con políticas documentadas adecuadas y globales para los parches y actualizaciones.

A efectos del párrafo primero, letra b), las entidades financieras diseñarán la infraestructura de conexión a la red de manera que permita su ruptura o segmentación instantánea con el fin de minimizar y prevenir el contagio, especialmente en los procesos financieros interconectados.

A efectos del párrafo primero, letra e), el proceso de gestión de cambios en las TIC será aprobado por los niveles directivos adecuados y dispondrá de protocolos específicos.

Incidencias vinculadas

Vínculos
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 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 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 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 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
blocks OS Credential Dumping
blocks LSASS Memory
blocks Security Account Manager
blocks NTDS
blocks LSA Secrets
blocks Cached Domain Credentials
blocks DCSync
blocks Proc Filesystem
blocks /etc/passwd and /etc/shadow
blocks Remote Services
blocks Remote Desktop Protocol
blocks SMB/Windows Admin Shares
blocks Distributed Component Object Model
blocks SSH
blocks VNC
blocks Windows Remote Management
blocks Cloud Services
blocks Direct Cloud VM Connections
blocks Double File Extension
blocks Masquerade Account Name
blocks Network Sniffing
blocks Windows Management Instrumentation
blocks Scheduled Task/Job
blocks At
blocks Cron
blocks Scheduled Task
blocks Systemd Timers
blocks Container Orchestration Job
blocks Process Injection
blocks Ptrace System Calls
blocks Web Portal Capture
blocks Command and Scripting Interpreter
blocks PowerShell
blocks Network Device CLI
blocks Cloud API
blocks Software Deployment Tools
blocks Valid Accounts
blocks Domain Accounts
blocks Local Accounts
blocks Cloud Accounts
blocks Cloud Account
blocks Account Manipulation
blocks Additional Cloud Credentials
blocks Additional Email Delegate Permissions
blocks Additional Cloud Roles
blocks SSH Authorized Keys
blocks Additional Local or Domain Groups
blocks Brute Force
blocks Password Guessing
blocks Password Cracking
blocks Password Spraying
blocks Credential Stuffing
blocks Multi-Factor Authentication Interception
blocks Email Collection
blocks Remote Email Collection
blocks External Remote Services
blocks Access Token Manipulation
blocks Token Impersonation/Theft
blocks Create Process with Token
blocks Make and Impersonate Token
blocks Create Account
blocks Local Account
blocks Domain Account
blocks Cloud Account
blocks Browser Session Hijacking
blocks Exploit Public-Facing Application
blocks BITS Jobs
blocks Exploitation of Remote Services
blocks Exploitation for Credential Access
blocks Data from Information Repositories
blocks Confluence
blocks Sharepoint
blocks Code Repositories
blocks Customer Relationship Management Software
blocks Messaging Applications
blocks System Binary Proxy Execution
blocks Msiexec
blocks File and Directory Permissions Modification
blocks Windows Permissions
blocks Linux and Mac Permissions
blocks Domain or Tenant Policy Modification
blocks Service Stop
blocks Firmware Corruption
blocks Server Software Component
blocks Transport Agent
blocks IIS Components
blocks Implant Internal Image
blocks Steal Application Access Token
blocks Data from Cloud Storage
blocks Transfer Data to Cloud Account
blocks Cloud Service Dashboard
blocks Steal Web Session Cookie
blocks Pre-OS Boot
blocks System Firmware
blocks Bootkit
blocks TFTP Boot
blocks Create or Modify System Process
blocks Launch Agent
blocks Systemd Service
blocks Windows Service
blocks Launch Daemon
blocks Container Service
blocks Windows Management Instrumentation Event Subscription
blocks Winlogon Helper DLL
blocks Kernel Modules and Extensions
blocks Shortcut Modification
blocks Print Processors
blocks XDG Autostart Entries
blocks Abuse Elevation Control Mechanism
blocks Bypass User Account Control
blocks Sudo and Sudo Caching
blocks Use Alternate Authentication Material
blocks Application Access Token
blocks Pass the Hash
blocks Pass the Ticket
blocks Unsecured Credentials
blocks Credentials In Files
blocks Credentials in Registry
blocks Private Keys
blocks Group Policy Preferences
blocks Container API
blocks Password Managers
blocks Modify Authentication Process
blocks Domain Controller Authentication
blocks Pluggable Authentication Modules
blocks Network Device Authentication
blocks Multi-Factor Authentication
blocks Hybrid Identity
blocks Conditional Access Policies
blocks Steal or Forge Kerberos Tickets
blocks Golden Ticket
blocks Silver Ticket
blocks Kerberoasting
blocks AS-REP Roasting
blocks Ccache Files
blocks Inter-Process Communication
blocks Component Object Model
blocks Remote Service Session Hijacking
blocks SSH Hijacking
blocks RDP Hijacking
blocks System Services
blocks Launchctl
blocks Service Execution
blocks Hijack Execution Flow
blocks Executable Installer File Permissions Weakness
blocks Services File Permissions Weakness
blocks COR_PROFILER
blocks Modify Cloud Compute Infrastructure
blocks Create Snapshot
blocks Create Cloud Instance
blocks Delete Cloud Instance
blocks Cloud Infrastructure Discovery
blocks Network Boundary Bridging
blocks Network Address Translation Traversal
blocks Modify System Image
blocks Patch System Image
blocks Downgrade System Image
blocks Deploy Container
blocks Escape to Host
blocks Container and Resource Discovery
blocks Cloud Storage Object Discovery
blocks Multi-Factor Authentication Request Generation
blocks Serverless Execution
blocks Steal or Forge Authentication Certificates
blocks Cloud Administration Command
is related to relative Control Weighting = 10
is related to Govern
blocks Identity Compromise / Impersonation
blocks Intellectual Property / Trade Secret Loss
blocks Fraud / Theft / Direct Financial Loss
blocks Loss of Confidentiality
blocks Loss of Data Integrity
blocks Loss of Data / Service Availability
blocks Loss of Authenticity / Provenance
blocks Privacy Harm / Unauthorized Processing
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 Data Quality Degradation / Data Poisoning
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Product Defect / Design Failure
blocks Supplier Financial Distress / Insolvency
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks Infrastructure Failure / Degradation
blocks Cryptographic Compromise / Cryptanalytic Capability Advancement
blocks OPS-34.02B
blocks IAM-01.01B
blocks IAM-01.02B
blocks PI-01.02AC
blocks PSS-12.01AC
blocks Identity Compromise / Impersonation
blocks Intellectual Property / Trade Secret Loss
blocks Fraud / Theft / Direct Financial Loss
blocks Loss of Confidentiality
blocks Loss of Data Integrity
blocks Loss of Data / Service Availability
blocks Loss of Authenticity / Provenance
blocks Privacy Harm / Unauthorized Processing
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 Data Quality Degradation / Data Poisoning
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Product Defect / Design Failure
blocks Supplier Financial Distress / Insolvency
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks Infrastructure Failure / Degradation
blocks Cryptographic Compromise / Cryptanalytic Capability Advancement
blocks OPS-34.02B
blocks IAM-01.01B
blocks IAM-01.02B
blocks PI-01.02AC
blocks PSS-12.01AC
is blocked by IAC-02 Identity & Access Management (IAM) – Assessment Procedure
blocks AC-01 Policy and Procedures
blocks IA-01 Policy and Procedures
blocks AC-01 [L] Policy and Procedures
blocks IA-01 [L] Policy and Procedures
blocks AC-01 [M] Policy and Procedures
blocks IA-01 [M] Policy and Procedures
blocks AC-01 [H] Policy and Procedures
blocks IA-01 [H] Policy and Procedures
blocks AC-01 [P] Policy and Procedures
blocks 03.01.01 Account Management
blocks 03.01.18 Access Control for Mobile Devices
blocks 03.05.01 User Identification and Authentication
blocks 03.05.05 Identifier Management
blocks 03.05.12 Authenticator Management
blocks PR.AA Identity Management, Authentication, and Access Control
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.