+Malicious Code Protection (Antimalware)
---+Always On Antimalware Protection
---+Heuristic / Nonsignature-Based Malware Detection

Malicious Code Protection (Antimalware)

Description

Mechanisms exist to utilize antimalware, or similar technologies, to detect and eradicate malicious code.

Possible Solutions & Considerations

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

∙ Antimalware software

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

∙ Antimalware software

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

∙ Antimalware software

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

∙ Antimalware software

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

∙ Antimalware software

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

Endpoint Security (END) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with END domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Endpoint security management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Anti-malware technologies are decentralized but are deployed on all technology assets that can run anti-malware software.

Level 2 Planned Tracked

Endpoint Security (END) 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 END domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with END 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 END domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Endpoint security-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Endpoint security management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ Anti-malware technologies are centralized, deployed on all technology assets that can run anti-malware software.
▪ Anti-malware technologies are configured to generate event logs that can be centrally-reviewed (e.g., forwarded to a SIEM).
▪ Anti-malware detection tools are configured to provide real-time protection (e.g., always on).
▪ Anti-malware detection tools are configured to automatically update.

Level 3 Well Defined

Endpoint Security (END) 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 END 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 END domain capabilities are well-documented and kept current by process owners.
▪ An endpoint technology management team, or similar function, is appropriately staffed and supported to implement and maintain END domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of endpoint security operations (e.g., unified endpoint management 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 END 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 utilize antimalware technologies to detect and eradicate malicious code.

Level 4 Quantitatively Controlled

Endpoint Security (END) 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

Always On Antimalware Protection

Description

Mechanisms exist to ensure unless specifically authorized by management on a case-by-case basis for a limited time period that anti-malware technologies:
(1) Are continuously running in real-time; and
(2) Cannot be disabled or altered by non-privileged users.

Possible Solutions & Considerations

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

∙ Antimalware software

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

∙ Antimalware software

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

∙ Antimalware software

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

∙ Antimalware software

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

∙ Antimalware software

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

Endpoint Security (END) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with END domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Endpoint security management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.

Level 2 Planned Tracked

Endpoint Security (END) 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 END domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with END 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 END domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Endpoint security-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Endpoint security management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ Anti-malware technologies are centralized, deployed on all technology assets that can run anti-malware software.
▪ Anti-malware technologies are configured to generate event logs that can be centrally-reviewed (e.g., forwarded to a SIEM).
▪ Anti-malware detection tools are configured to provide real-time protection (e.g., always on).

Level 3 Well Defined

Endpoint Security (END) 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 END 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 END domain capabilities are well-documented and kept current by process owners.
▪ An endpoint technology management team, or similar function, is appropriately staffed and supported to implement and maintain END domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of endpoint security operations (e.g., unified endpoint management 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 END 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 that anti-malware technologies are continuously running in real-time and cannot be disabled or altered by non-privileged users, unless specifically authorized by management on a case-by-case basis for a limited time period.

Level 4 Quantitatively Controlled

Endpoint Security (END) 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.
Heuristic / Nonsignature-Based Malware Detection

Description

Mechanisms exist to utilize heuristic / nonsignature-based antimalware detection capabilities.

Possible Solutions & Considerations

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

∙ Antimalware software

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

∙ Antimalware software

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

∙ Antimalware software

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

∙ Antimalware software

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

∙ Antimalware software

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

Endpoint Security (END) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with END domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Endpoint security management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.

Level 2 Planned Tracked

Endpoint Security (END) 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 END domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with END 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 END domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Endpoint security-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Endpoint security management 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

Endpoint Security (END) 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 END 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 END domain capabilities are well-documented and kept current by process owners.
▪ An endpoint technology management team, or similar function, is appropriately staffed and supported to implement and maintain END domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of endpoint security operations (e.g., unified endpoint management 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 END 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 utilize heuristic / nonsignature-based antimalware detection capabilities.

Level 4 Quantitatively Controlled

Endpoint Security (END) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational.
▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions:
▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control.
▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies.
▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

1.1 Referencias

1.2 Requisitos identificados

1.3 Regulaciones relacionadas

2. Requisitos identificados

Requisitos

3. Regulaciones relacionadas

Regulaciones
EULAW Artículo 11 Seguridad de los datos y sistemas
-
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.

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 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 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 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
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 Bluetooth
blocks Distributed Component Object Model
blocks VNC
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 LNK Icon Smuggling
blocks Encrypted/Encoded File
blocks Polymorphic Code
blocks Scheduled Transfer
blocks Data Transfer Size Limits
blocks Masquerading
blocks Rename Legitimate Utilities
blocks Match Legitimate Resource Name or Location
blocks Masquerade File Type
blocks Boot or Logon Initialization Scripts
blocks Login Hook
blocks Network Logon Script
blocks RC Scripts
blocks Startup Items
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 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 ListPlanting
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 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 Software Deployment Tools
blocks Taint Shared Content
blocks Proxy
blocks Internal Proxy
blocks External Proxy
blocks Replication Through Removable Media
blocks Communication Through Removable Media
blocks Non-Application Layer Protocol
blocks SSH Authorized Keys
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 Multi-Factor Authentication Interception
blocks Shared Modules
blocks Data Encoding
blocks Standard Encoding
blocks Non-Standard Encoding
blocks Office Application Startup
blocks Office Template Macros
blocks Software Extensions
blocks Browser Session Hijacking
blocks Drive-by Compromise
blocks Exploit Public-Facing Application
blocks Supply Chain Compromise
blocks Password Policy Discovery
blocks Exploitation for Client Execution
blocks User Execution
blocks Malicious Link
blocks Malicious File
blocks Malicious Image
blocks Exploitation of Remote Services
blocks Exploitation for Stealth
blocks Exploitation for Credential Access
blocks System Binary Proxy Execution
blocks Compiled HTML File
blocks Control Panel
blocks CMSTP
blocks InstallUtil
blocks Mshta
blocks Odbcconf
blocks Regsvcs/Regasm
blocks Verclsid
blocks Mavinject
blocks MMC
blocks Electron Applications
blocks Remote Access Tools
blocks Template Injection
blocks Data Destruction
blocks Data Encrypted for Impact
blocks Inhibit System Recovery
blocks Defacement
blocks Internal Defacement
blocks External Defacement
blocks IIS Components
blocks Implant Internal Image
blocks Steal Web Session Cookie
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 PowerShell Profile
blocks Emond
blocks Installer Packages
blocks Authentication Package
blocks Security Support Provider
blocks Kernel Modules and Extensions
blocks Re-opened Applications
blocks LSASS Driver
blocks Shortcut Modification
blocks XDG Autostart Entries
blocks Abuse Elevation Control Mechanism
blocks Elevated Execution with Prompt
blocks TCC Manipulation
blocks SIP and Trust Provider Hijacking
blocks Compromise Host Software Binary
blocks Adversary-in-the-Middle
blocks Name Resolution Poisoning and SMB Relay
blocks ARP Cache Poisoning
blocks DHCP Spoofing
blocks Steal or Forge Kerberos Tickets
blocks Silver Ticket
blocks Kerberoasting
blocks AS-REP Roasting
blocks Inter-Process Communication
blocks Component Object Model
blocks Dynamic Data Exchange
blocks Archive Collected Data
blocks Archive via Utility
blocks Disk Wipe
blocks Disk Content Wipe
blocks Disk Structure Wipe
blocks NTFS File Attributes
blocks Email Hiding Rules
blocks Resource Forking
blocks File/Path Exclusions
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 Path Interception by PATH Environment Variable
blocks Path Interception by Search Order Hijacking
blocks Path Interception by Unquoted Path
blocks KernelCallbackTable
blocks AppDomainManager
blocks Phishing for Information
blocks Spearphishing Service
blocks Spearphishing Attachment
blocks Spearphishing Link
blocks Data from Configuration Repository
blocks SNMP (MIB Dump)
blocks Network Device Configuration Dump
blocks Escape to Host
blocks Debugger Evasion
blocks Identity Compromise / Impersonation
blocks Fraud / Theft / Direct Financial Loss
blocks Undetected / Delayed Detection of Adverse Activity
blocks Loss of Confidentiality
blocks Loss of Data Integrity
blocks Loss of Data / Service Availability
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 Fraud, Corruption and/or Intentional Criminal Conduct
blocks Product Defect / Design Failure
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks Infrastructure Failure / Degradation
blocks Adversarial Artificial Intelligence (AI) Attack
blocks AM-05.01B
blocks AM-12.01B
blocks OPS-04.01B
blocks OPS-05.01B
blocks OPS-05.03B
blocks OPS-05.01AC
blocks OPS-34.02B
blocks PSS-01.02B
is blocked by END-04 Malicious Code Protection (Antimalware) – Assessment Procedure
blocks SI-03 Malicious Code Protection
blocks SI-03 [L] Malicious Code Protection
blocks SI-03 [M] Malicious Code Protection
blocks SI-03 [H] Malicious Code Protection
blocks 03.14.02 Malicious Code Protection
blocks DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events