+Behavior Prevention on Endpoint

Behavior Prevention on Endpoint

Behavior Prevention on Endpoint refers to the use of technologies and strategies to detect and block potentially malicious activities by analyzing the behavior of processes, files, API calls, and other endpoint events. Rather than relying solely on known signatures, this approach leverages heuristics, machine learning, and real-time monitoring to identify anomalous patterns indicative of an attack. This mitigation can be implemented through the following measures: Suspicious Process Behavior: - Implementation: Use Endpoint Detection and Response (EDR) tools to monitor and block processes exhibiting unusual behavior, such as privilege escalation attempts. - Use Case: An attacker uses a known vulnerability to spawn a privileged process from a user-level application. The endpoint tool detects the abnormal parent-child process relationship and blocks the action. Unauthorized File Access: - Implementation: Leverage Data Loss Prevention (DLP) or endpoint tools to block processes attempting to access sensitive files without proper authorization. - Use Case: A process tries to read or modify a sensitive file located in a restricted directory, such as /etc/shadow on Linux or the SAM registry hive on Windows. The endpoint tool identifies this anomalous behavior and prevents it. Abnormal API Calls: - Implementation: Implement runtime analysis tools to monitor API calls and block those associated with malicious activities. - Use Case: A process dynamically injects itself into another process to hijack its execution. The endpoint detects the abnormal use of APIs like `OpenProcess` and `WriteProcessMemory` and terminates the offending process. Exploit Prevention: - Implementation: Use behavioral exploit prevention tools to detect and block exploits attempting to gain unauthorized access. - Use Case: A buffer overflow exploit is launched against a vulnerable application. The endpoint detects the anomalous memory write operation and halts the process.

1. Overview

1.1 References

1.2 Identified Requirements

1.3 Related Regulations

2. Identified Requirements

Requirements

3. Related Regulations

Regulations

Linked Issues

Issuelinks
is related to Mitigations
blocks Masquerade File Type
blocks Windows Service
blocks Portable Executable Injection
blocks Asynchronous Procedure Call
blocks Polymorphic Code
blocks Add-ins
blocks Proc Memory
blocks Command Obfuscation
blocks Process Hollowing
blocks Windows Management Instrumentation
blocks JavaScript
blocks User Execution
blocks Create or Modify System Process
blocks Dynamic Data Exchange
blocks Hijack Execution Flow
blocks Service Execution
blocks VDSO Hijacking
blocks Process Doppelgänging
blocks PubPrn
blocks Masquerading
blocks Thread Execution Hijacking
blocks Outlook Home Page
blocks Office Application Startup
blocks Replication Through Removable Media
blocks OS Credential Dumping
blocks Office Template Macros
blocks Office Test
blocks KernelCallbackTable
blocks Visual Basic
blocks Extra Window Memory Injection
blocks Extended Attributes
blocks LNK Icon Smuggling
blocks Data Encrypted for Impact
blocks Outlook Rules
blocks Malicious File
blocks Ptrace System Calls
blocks Native API
blocks Process Injection
blocks System Services
blocks Direct Volume Access
blocks Inter-Process Communication
blocks Obfuscated Files or Information
blocks Embedded Payloads
blocks Outlook Forms
blocks Windows Management Instrumentation Event Subscription
blocks LSASS Memory
blocks Command and Scripting Interpreter
blocks Thread Local Storage
blocks Encrypted/Encoded File
blocks Dynamic-link Library Injection
blocks ListPlanting
  • MITREATTACK -

    © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. https://attack.mitre.org/

    Terms of Use

    LICENSE

    The MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use ATT&CK® for research, development, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

    "© 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation."

    DISCLAIMERS

    MITRE does not claim ATT&CK enumerates all possibilities for the types of actions and behaviors documented as part of its adversary model and framework of techniques. Using the information contained within ATT&CK to address or cover full categories of techniques will not guarantee full defensive coverage as there may be undisclosed techniques or variations on existing techniques not documented by ATT&CK.

    ALL DOCUMENTS AND THE INFORMATION CONTAINED THEREIN ARE PROVIDED ON AN "AS IS" BASIS AND THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE MITRE CORPORATION, ITS BOARD OF TRUSTEES, OFFICERS, AGENTS, AND EMPLOYEES, DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

    See our FAQ for more information on how to use and represent the ATT&CK name.
Impressum German English