+Continuous Monitoring

Continuous Monitoring

Description

Mechanisms exist to facilitate the implementation of enterprise-wide monitoring controls.

Possible Solutions & Considerations

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

∙ Centralized event logging
∙ Managed Security Services Provider (MSSP)
∙ Cloud-native SIEM (e.g., Microsoft Sentinel free tier, Elastic SIEM free)

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

∙ Centralized event logging
∙ Managed Security Services Provider (MSSP)
∙ Cloud SIEM (e.g., Microsoft Sentinel, Elastic SIEM, Sumo Logic)

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

∙ Centralized event logging
∙ Security Incident Event Management (SIEM) (e.g., Splunk, Microsoft Sentinel, IBM QRadar)
∙ Managed Security Services Provider (MSSP)
∙ Security Operations Center (SOC)

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

∙ Centralized event logging
∙ Security Incident Event Management (SIEM) (e.g., Splunk, Microsoft Sentinel, IBM QRadar)
∙ Managed Security Services Provider (MSSP)
∙ Security Operations Center (SOC) with 24/7 coverage

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

∙ Enterprise SIEM platform (e.g., Splunk Enterprise Security, IBM QRadar, Microsoft Sentinel)
∙ 24/7 Security Operations Center (SOC)
∙ Security Orchestration, Automation & Response (SOAR)
∙ Threat intelligence integration
∙ Managed Detection & Response (MDR) or in-house SOC

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

Continuous Monitoring (MON) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with MON domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Event monitoring-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Monitoring is primarily reactive in nature, focused on identifying incidents that occurred.
▪ Event log reviews primarily rely on manual processes to identify anomalous behaviors.
▪ Generating event logs and the review of those event logs is narrowly-focused to business-critical Technology Assets, Applications, Services and/or Data (TAASD).

Level 2 Planned Tracked

Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with MON 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 MON domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Continuous monitoring-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Continuous monitoring may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.

Level 3 Well Defined

Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Cybersecurity personnel use a structured process via Standardized Operating Procedures (SOP) to review and analyze logs.
▪ A Security Operations Center (SOC) team, or similar function, is appropriately staffed and supported to implement and maintain MON domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of continuous monitoring operations (e.g., Security Incident Event Manager (SIEM)).
▪ 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 MON 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).
▪ Secure Baseline Configurations (SBC) enforce security event logging to contain sufficient information to establish necessary details of activity and allow for forensics analysis.
▪ An implemented and operational capability exists to facilitate the implementation of enterprise-wide monitoring controls.

Level 4 Quantitatively Controlled

Continuous Monitoring (MON) 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 12 Registros
-
EULAW Artículo 12 Registros
-
EULAW Artículo 23 Detección de actividades anómalas y criterios para detectar y responder a incidentes relacionados con las TIC
-
EULAW Artículo 23 Detección de actividades anómalas y criterios para detectar y responder a incidentes relacionados con las TIC
-
EULAW Artículo 23 Detección de actividades anómalas y criterios para detectar y responder a incidentes relacionados con las TIC
-
EULAW Artículo 34 Seguridad de las operaciones de TIC

Artículo 34

Seguridad de las operaciones de TIC

Dentro de sus sistemas, protocolos y herramientas, y con respecto a todos los activos de TIC, las entidades financieras a que se refiere el artículo 16, apartado 1, del Reglamento (UE) 2022/2554:

a) 

harán un seguimiento del ciclo de vida de todos los activos de TIC y lo gestionarán;

b) 

harán un seguimiento, en su caso, de si los activos de TIC cuentan con el soporte de proveedores terceros de servicios de TIC;

c) 

determinarán los requisitos de capacidad de sus activos de TIC y las medidas para mantener y mejorar la disponibilidad y eficiencia de los sistemas de TIC y prevenir la escasez de capacidad de TIC antes de que se materialice;

d) 

llevarán a cabo exploraciones y evaluaciones automatizadas de vulnerabilidad de los activos de TIC, acordes con la clasificación de tales activos contemplada en el artículo 30, apartado 1, y con el perfil de riesgo general de cada activo de TIC, e implementarán parches para hacer frente a las vulnerabilidades detectadas;

e) 

gestionarán los riesgos relacionados con los activos de TIC obsoletos, sin soporte o heredados;

f) 

registrarán los acontecimientos relacionados con el control del acceso lógico y físico, las operaciones de TIC, incluidas las actividades de sistema y de tráfico de red, y la gestión de cambios en las TIC;

g) 

determinarán y aplicarán medidas para el seguimiento y el análisis de la información sobre actividades y comportamientos anómalos respecto de operaciones de TIC esenciales o importantes;

h) 

aplicarán medidas para el seguimiento de la información pertinente y actualizada sobre las ciberamenazas;

i) 

aplicarán medidas para la detección de posibles fugas de información, códigos maliciosos y otras amenazas para la seguridad, así como vulnerabilidades en el software y el hardware conocidas públicamente, y comprobarán las nuevas actualizaciones de seguridad correspondientes.

A efectos de la letra f), las entidades financieras adaptarán el grado de detalle de los registros a la finalidad y al uso del activo de TIC que los genere.
EULAW Artículo 34 Seguridad de las operaciones de TIC

Artículo 34

Seguridad de las operaciones de TIC

Dentro de sus sistemas, protocolos y herramientas, y con respecto a todos los activos de TIC, las entidades financieras a que se refiere el artículo 16, apartado 1, del Reglamento (UE) 2022/2554:

a) 

harán un seguimiento del ciclo de vida de todos los activos de TIC y lo gestionarán;

b) 

harán un seguimiento, en su caso, de si los activos de TIC cuentan con el soporte de proveedores terceros de servicios de TIC;

c) 

determinarán los requisitos de capacidad de sus activos de TIC y las medidas para mantener y mejorar la disponibilidad y eficiencia de los sistemas de TIC y prevenir la escasez de capacidad de TIC antes de que se materialice;

d) 

llevarán a cabo exploraciones y evaluaciones automatizadas de vulnerabilidad de los activos de TIC, acordes con la clasificación de tales activos contemplada en el artículo 30, apartado 1, y con el perfil de riesgo general de cada activo de TIC, e implementarán parches para hacer frente a las vulnerabilidades detectadas;

e) 

gestionarán los riesgos relacionados con los activos de TIC obsoletos, sin soporte o heredados;

f) 

registrarán los acontecimientos relacionados con el control del acceso lógico y físico, las operaciones de TIC, incluidas las actividades de sistema y de tráfico de red, y la gestión de cambios en las TIC;

g) 

determinarán y aplicarán medidas para el seguimiento y el análisis de la información sobre actividades y comportamientos anómalos respecto de operaciones de TIC esenciales o importantes;

h) 

aplicarán medidas para el seguimiento de la información pertinente y actualizada sobre las ciberamenazas;

i) 

aplicarán medidas para la detección de posibles fugas de información, códigos maliciosos y otras amenazas para la seguridad, así como vulnerabilidades en el software y el hardware conocidas públicamente, y comprobarán las nuevas actualizaciones de seguridad correspondientes.

A efectos de la letra f), las entidades financieras adaptarán el grado de detalle de los registros a la finalidad y al uso del activo de TIC que los genere.
EULAW Artículo 10 Detección
-
EULAW Artículo 10 3

3.   Las entidades financieras dedicarán recursos y capacidades suficientes al seguimiento de la actividad de los usuarios y la aparición de anomalías en las TIC y de incidentes relacionados con las TIC, en particular de ciberataques.

Incidencias vinculadas

Vínculos
is related to Annual
is related to relative Control Weighting = 10
is related to Technology
is related to Detect
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 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 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 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
is related to Govern
blocks Data Obfuscation
blocks Junk Data
blocks Steganography
blocks Protocol or Service Impersonation
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 Data from Local System
blocks Fallback Channels
blocks Exfiltration Over Other Network Medium
blocks Exfiltration Over Bluetooth
blocks Traffic Duplication
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 Direct Cloud VM Connections
blocks Data from Removable Media
blocks Obfuscated Files or Information
blocks Software Packing
blocks Dynamic API Resolution
blocks Stripped Payloads
blocks Embedded Payloads
blocks Command Obfuscation
blocks Fileless Storage
blocks LNK Icon Smuggling
blocks Scheduled Transfer
blocks Data Transfer Size Limits
blocks Masquerading
blocks Invalid Code Signature
blocks Rename Legitimate Utilities
blocks Match Legitimate Resource Name or Location
blocks Double File Extension
blocks Masquerade File Type
blocks Masquerade Account Name
blocks Boot or Logon Initialization Scripts
blocks Login Hook
blocks Network Logon Script
blocks RC Scripts
blocks Startup Items
blocks Network Sniffing
blocks Exfiltration Over C2 Channel
blocks Network Service Discovery
blocks Windows Management Instrumentation
blocks Exfiltration Over Alternative Protocol
blocks Exfiltration Over Symmetric Encrypted Non-C2 Protocol
blocks Exfiltration Over Asymmetric Encrypted Non-C2 Protocol
blocks Exfiltration Over Unencrypted Non-C2 Protocol
blocks Exfiltration Over Physical Medium
blocks Exfiltration over USB
blocks Scheduled Task/Job
blocks At
blocks Cron
blocks Scheduled Task
blocks Systemd Timers
blocks Process Injection
blocks Dynamic-link Library Injection
blocks Portable Executable Injection
blocks Thread Execution Hijacking
blocks Asynchronous Procedure Call
blocks Thread Local Storage
blocks Ptrace System Calls
blocks Proc Memory
blocks Extra Window Memory Injection
blocks Process Hollowing
blocks Process Doppelgänging
blocks VDSO Hijacking
blocks GUI Input Capture
blocks Command and Scripting Interpreter
blocks PowerShell
blocks AppleScript
blocks Windows Command Shell
blocks Unix Shell
blocks Visual Basic
blocks Python
blocks JavaScript
blocks Network Device CLI
blocks Cloud API
blocks AutoHotKey & AutoIT
blocks Lua
blocks Exploitation for Privilege Escalation
blocks Indicator Removal
blocks Clear Command History
blocks Clear Network Connection History and Configurations
blocks Clear Mailbox Data
blocks Clear Persistence
blocks Relocate Malware
blocks Application Layer Protocol
blocks Web Protocols
blocks File Transfer Protocols
blocks Mail Protocols
blocks DNS
blocks Publish/Subscribe Protocols
blocks Software Deployment Tools
blocks Valid Accounts
blocks Default Accounts
blocks Domain Accounts
blocks Local Accounts
blocks Cloud Accounts
blocks Taint Shared Content
blocks Account Discovery
blocks Local Account
blocks Domain Account
blocks Proxy
blocks Internal Proxy
blocks External Proxy
blocks Replication Through Removable Media
blocks Communication Through Removable Media
blocks Non-Application Layer Protocol
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 Web Service
blocks Dead Drop Resolver
blocks Bidirectional Communication
blocks One-Way Communication
blocks Multi-Stage Channels
blocks Ingress Tool Transfer
blocks Native API
blocks Brute Force
blocks Password Guessing
blocks Password Cracking
blocks Password Spraying
blocks Credential Stuffing
blocks Multi-Factor Authentication Interception
blocks Email Collection
blocks Local Email Collection
blocks Remote Email Collection
blocks Email Forwarding Rule
blocks Automated Collection
blocks Trusted Developer Utilities Proxy Execution
blocks MSBuild
blocks ClickOnce
blocks Shared Modules
blocks Data Encoding
blocks Standard Encoding
blocks Non-Standard Encoding
blocks External Remote Services
blocks Network Share Discovery
blocks Create Account
blocks Local Account
blocks Domain Account
blocks Cloud Account
blocks Office Application Startup
blocks Office Template Macros
blocks Software Extensions
blocks Browser Session Hijacking
blocks Forced Authentication
blocks Drive-by Compromise
blocks Exploit Public-Facing Application
blocks Supply Chain Compromise
blocks Compromise Software Dependencies and Development Tools
blocks BITS Jobs
blocks Password Policy Discovery
blocks Exploitation for Client Execution
blocks User Execution
blocks Malicious Link
blocks Malicious File
blocks Malicious Image
blocks Traffic Signaling
blocks Port Knocking
blocks Socket Filters
blocks Exploitation of Remote Services
blocks Exploitation for Stealth
blocks Exploitation for Credential Access
blocks Data from Information Repositories
blocks Confluence
blocks Sharepoint
blocks Customer Relationship Management Software
blocks Messaging Applications
blocks System Script Proxy Execution
blocks PubPrn
blocks System Binary Proxy Execution
blocks Compiled HTML File
blocks Control Panel
blocks CMSTP
blocks InstallUtil
blocks Mshta
blocks Odbcconf
blocks Regsvcs/Regasm
blocks Regsvr32
blocks Rundll32
blocks Verclsid
blocks Mavinject
blocks MMC
blocks Electron Applications
blocks Remote Access Tools
blocks XSL Script Processing
blocks Template Injection
blocks File and Directory Permissions Modification
blocks Windows Permissions
blocks Linux and Mac Permissions
blocks Domain or Tenant Policy Modification
blocks Data Destruction
blocks Data Encrypted for Impact
blocks Service Stop
blocks Inhibit System Recovery
blocks Defacement
blocks Internal Defacement
blocks External Defacement
blocks Endpoint Denial of Service
blocks OS Exhaustion Flood
blocks Service Exhaustion Flood
blocks Application Exhaustion Flood
blocks Application or System Exploitation
blocks Server Software Component
blocks Transport Agent
blocks Web Shell
blocks IIS Components
blocks Terminal Services DLL
blocks Implant Internal Image
blocks Steal Application Access Token
blocks Data from Cloud Storage
blocks Transfer Data to Cloud Account
blocks Steal Web Session Cookie
blocks ROMMONkit
blocks TFTP Boot
blocks Create or Modify System Process
blocks Systemd Service
blocks Screensaver
blocks Windows Management Instrumentation Event Subscription
blocks Unix Shell Configuration Modification
blocks LC_LOAD_DYLIB Addition
blocks Accessibility Features
blocks PowerShell Profile
blocks Emond
blocks Installer Packages
blocks Authentication Package
blocks Time Providers
blocks Winlogon Helper DLL
blocks Security Support Provider
blocks Kernel Modules and Extensions
blocks Re-opened Applications
blocks LSASS Driver
blocks Shortcut Modification
blocks Print Processors
blocks XDG Autostart Entries
blocks Abuse Elevation Control Mechanism
blocks Setuid and Setgid
blocks Bypass User Account Control
blocks Sudo and Sudo Caching
blocks Elevated Execution with Prompt
blocks TCC Manipulation
blocks Application Access Token
blocks Pass the Ticket
blocks Unsecured Credentials
blocks Credentials In Files
blocks Credentials in Registry
blocks Shell History
blocks Private Keys
blocks Cloud Instance Metadata API
blocks Group Policy Preferences
blocks Chat Messages
blocks Subvert Trust Controls
blocks Gatekeeper Bypass
blocks SIP and Trust Provider Hijacking
blocks Install Root Certificate
blocks Mark-of-the-Web Bypass
blocks Credentials from Password Stores
blocks Keychain
blocks Securityd Memory
blocks Windows Credential Manager
blocks Password Managers
blocks Modify Authentication Process
blocks Domain Controller Authentication
blocks Password Filter DLL
blocks Pluggable Authentication Modules
blocks Network Device Authentication
blocks Network Provider DLL
blocks Conditional Access Policies
blocks Adversary-in-the-Middle
blocks Name Resolution Poisoning and SMB Relay
blocks ARP Cache Poisoning
blocks DHCP Spoofing
blocks Evil Twin
blocks Steal or Forge Kerberos Tickets
blocks Silver Ticket
blocks Kerberoasting
blocks AS-REP Roasting
blocks Ccache Files
blocks Inter-Process Communication
blocks Dynamic Data Exchange
blocks XPC Services
blocks Archive Collected Data
blocks Archive via Utility
blocks Disk Wipe
blocks Disk Content Wipe
blocks Disk Structure Wipe
blocks Remote Service Session Hijacking
blocks SSH Hijacking
blocks RDP Hijacking
blocks Hidden Users
blocks NTFS File Attributes
blocks Run Virtual Instance
blocks VBA Stomping
blocks Email Hiding Rules
blocks Resource Forking
blocks Process Argument Spoofing
blocks Data Manipulation
blocks Stored Data Manipulation
blocks Transmitted Data Manipulation
blocks Runtime Data Manipulation
blocks Phishing
blocks Spearphishing Attachment
blocks Spearphishing Link
blocks Spearphishing via Service
blocks Exfiltration Over Web Service
blocks Dynamic Resolution
blocks Domain Generation Algorithms
blocks System Services
blocks Service Execution
blocks Lateral Tool Transfer
blocks Non-Standard Port
blocks Protocol Tunneling
blocks Encrypted Channel
blocks Symmetric Cryptography
blocks Asymmetric Cryptography
blocks Hijack Execution Flow
blocks DLL
blocks Dylib Hijacking
blocks Executable Installer File Permissions Weakness
blocks Path Interception by PATH Environment Variable
blocks Path Interception by Search Order Hijacking
blocks Path Interception by Unquoted Path
blocks Services File Permissions Weakness
blocks KernelCallbackTable
blocks AppDomainManager
blocks Modify Cloud Compute Infrastructure
blocks Create Snapshot
blocks Create Cloud Instance
blocks Delete Cloud Instance
blocks Phishing for Information
blocks Spearphishing Service
blocks Spearphishing Attachment
blocks Spearphishing Link
blocks Network Boundary Bridging
blocks Network Address Translation Traversal
blocks Modify System Image
blocks Patch System Image
blocks Downgrade System Image
blocks Data from Configuration Repository
blocks SNMP (MIB Dump)
blocks Network Device Configuration Dump
blocks Deploy Container
blocks Escape to Host
blocks Build Image on Host
blocks Container and Resource Discovery
blocks Debugger Evasion
blocks Plist File Modification
blocks Serverless Execution
blocks Cloud Administration Command
blocks Power Settings
blocks Loss of Accountability / Attribution
blocks Unauthorized Privilege Elevation
blocks Identity Compromise / Impersonation
blocks Fraud / Theft / Direct Financial Loss
blocks Inability to Demonstrate Due Diligence / Due Care
blocks Unreliable Assurance / Decision Information
blocks AI Output / Decision Integrity Failure
blocks AI Data Confidentiality / Integrity / Provenance Loss
blocks Unauthorized / Harmful Autonomous Action
blocks Unintended or Unsafe Technology Behavior
blocks OT Safety / Process Availability Failure
blocks Loss of Confidentiality
blocks Loss of Data Integrity
blocks Loss of Data / Service Availability
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 Utility Service Disruption
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Data Quality Degradation / Data Poisoning
blocks Artificial Intelligence & Autonomous Technologies (AAT) System Failure or Unintended Behavior
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks Infrastructure Failure / Degradation
blocks Adversarial Artificial Intelligence (AI) Attack
blocks Operational Technology (OT) / Industrial Control System (ICS) Attack
blocks OIS-04.03B
blocks OIS-04.01AC
blocks AM-01.01AC
blocks AM-09.03AC
blocks OPS-07.01B
blocks OPS-10.01B
blocks OPS-17.01B
blocks OPS-30.01B
blocks OPS-32.01AC
blocks OPS-34.02B
blocks PSS-01.02B
blocks PSS-12.02AC
is blocked by MON-02 Continuous Monitoring – Assessment Procedure
blocks AU-01 Policy and Procedures
blocks PM-31 Continuous Monitoring Strategy
blocks SI-04 System Monitoring
blocks AU-01 [L] Policy and Procedures
blocks SI-04 [L] System Monitoring
blocks AU-01 [M] Policy and Procedures
blocks SI-04 [M] System Monitoring
blocks AU-01 [H] Policy and Procedures
blocks SI-04 [H] System Monitoring
blocks AU-01 [P] Policy and Procedures
blocks PM-31 [P] Continuous Monitoring Strategy
blocks 03.03.01 Event Logging
blocks 03.12.03 Continuous Monitoring
blocks 03.14.06 System Monitoring
blocks PR.PS-04 Log records are generated and made available for continuous monitoring
blocks DE.CM-01 Networks and network services are monitored to find potentially adverse events
blocks DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
blocks DE.CM-06 External service provider activities and services are monitored to find potentially adverse events
blocks DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events
blocks DE.AE Adverse Event Analysis