id
stringlengths 5
9
| technique
stringlengths 3
43
| subtechniqueid
stringlengths 3
60
⌀ | sentences
stringlengths 1
871
|
|---|---|---|---|
t1542
|
pre os boot
| null |
disk check forensic utilities and data from device drivers i
|
t1542
|
pre os boot
| null |
during the booting process of a computer firmware and various startup services are loaded before the operating system
|
t1542
|
pre os boot
| null |
log changes to boot records bios and efi which can be performed by api calls and compare against known good behavior and patching
|
t1542
|
pre os boot
| null |
perform integrity checking on pre os boot mechanisms that can be manipulated for malicious purposes
|
t1542
|
pre os boot
| null |
processes and api calls may reveal anomalies that warrant deeper investigation
|
t1542
|
pre os boot
| null |
take snapshots of boot records and firmware and compare against known good images
|
t1543
|
create or modify system process
| null |
including by comparing results against a trusted system baseline
|
t1543
|
create or modify system process
| null |
adversaries may create or modify system level processes to repeatedly execute malicious payloads as part of persistence
|
t1543
|
create or modify system process
| null |
command line invocation of tools capable of modifying services may be unusual depending on how systems are typically used in a particular environment
|
t1543
|
create or modify system process
| null |
data and events should not be viewed in isolation but as part of a chain of behavior that could lead to other activities such as network connections made for command and control learning details about the environment through discovery and lateral movement
|
t1543
|
create or modify system process
| null |
look for abnormal process call trees from known services and for execution of other commands that could relate to discovery or other adversary techniques
|
t1543
|
create or modify system process
| null |
monitor for changes to files associated with system level processes
|
t1543
|
create or modify system process
| null |
monitor for changes to system processes that do not correlate with known software patch cycles etc
|
t1543
|
create or modify system process
| null |
new benign system processes may be created during installation of new software
|
t1543
|
create or modify system process
| null |
service service creation service service modification process process creation process os api execution command command execution windows registry windows registry key creation windows registry windows registry key modification file file creation file file modification
|
t1543
|
create or modify system process
| null |
when operating systems boot up they can start processes that perform background system functions
|
t1546
|
event triggered execution
| null |
adversaries may establish persistence andor elevate privileges using system mechanisms that trigger execution based on specific events
|
t1546
|
event triggered execution
| null |
also look for abnormal process call trees for execution of other commands that could relate to discovery actions or other techniques
|
t1546
|
event triggered execution
| null |
also look for changes that do not line up with updates patches or other planned administrative activity
|
t1546
|
event triggered execution
| null |
data and events should not be viewed in isolation but as part of a chain of behavior that could lead to other activities such as making network connections for command and control learning details about the environment through discovery and conducting lateral movement
|
t1546
|
event triggered execution
| null |
look for abnormal process behavior that may be due to a process loading a malicious dll
|
t1546
|
event triggered execution
| null |
monitor dll loads by processes specifically looking for dlls that are not recognized or not normally loaded into a process
|
t1546
|
event triggered execution
| null |
monitor for processes apisystem calls and other common ways of manipulating these event repositories
|
t1546
|
event triggered execution
| null |
monitoring for additions or modifications of mechanisms that could be used to trigger event based execution especially the addition of abnormal commands such as execution of unknown programs opening network sockets or reaching out across the network
|
t1546
|
event triggered execution
| null |
process process creation windows registry windows registry key modification command command execution file file creation file file modification wmi wmi creation file file metadata module module load
|
t1546
|
event triggered execution
| null |
these mechanisms may vary by os but are typically stored in central repositories that store configuration information such as the windows registry common information model cim andor specific named files the last of which can be hashed and compared to known good values
|
t1546
|
event triggered execution
| null |
tools such as sysinternals autoruns can be used to detect changes to execution triggers that could be attempts at persistence
|
t1546
|
event triggered execution
| null |
various operating systems have means to monitor and subscribe to events such as logons or other user activity such as running specific applicationsbinaries
|
t1547
|
boot or logon auto start execution
| null |
adversaries may configure system settings to automatically execute a program during system boot or logon to maintain persistence or gain higher level privileges on compromised systems
|
t1547
|
boot or logon auto start execution
| null |
citation technet autoruns changes to some auto start configuration settings may happen under normal conditions when legitimate software is installed
|
t1547
|
boot or logon auto start execution
| null |
file file creation windows registry windows registry key creation windows registry windows registry key modification file file modification command command execution process process creation module module load kernel kernel module load driver driver load process os api execution
|
t1547
|
boot or logon auto start execution
| null |
look for abnormal process behavior that may be due to a process loading a malicious dll
|
t1547
|
boot or logon auto start execution
| null |
look for changes that are not correlated with known updates patches or other planned administrative activity
|
t1547
|
boot or logon auto start execution
| null |
monitor dll loads by processes specifically looking for dlls that are not recognized or not normally loaded into a process
|
t1547
|
boot or logon auto start execution
| null |
monitor for abnormal usage of utilities and command line parameters involved in kernel modification or driver installation
|
t1547
|
boot or logon auto start execution
| null |
monitor for additions or modifications of mechanisms that could be used to trigger auto start execution such as relevant additions to the registry
|
t1547
|
boot or logon auto start execution
| null |
operating systems may have mechanisms for automatically running a program on system boot or account logon
|
t1547
|
boot or logon auto start execution
| null |
suspicious program execution as auto start programs may show up as outlier processes that have not been seen before when compared against historical data
|
t1547
|
boot or logon auto start execution
| null |
to increase confidence of malicious activity data and events should not be viewed in isolation but as part of a chain of behavior that could lead to other activities such as network connections made for command and control learning details about the environment through discovery and lateral movement
|
t1547
|
boot or logon auto start execution
| null |
tools such as sysinternals autoruns may also be used to detect system auto start configuration changes that could be attempts at persistence
|
t1548
|
abuse elevation control mechanism
| null |
001 which indicate attempts to gain access to higher privileged processes
|
t1548
|
abuse elevation control mechanism
| null |
adversaries may circumvent mechanisms designed to control elevate privileges to gain higher level permissions
|
t1548
|
abuse elevation control mechanism
| null |
also look for any process api calls for behavior that may be indicative of process injectiont1055 and unusual loaded dlls through dll search order hijackingt1574
|
t1548
|
abuse elevation control mechanism
| null |
analysts should monitor registry settings for unauthorized changes
|
t1548
|
abuse elevation control mechanism
| null |
consider monitoring for usrlibexecsecurity_authtrampoline executions which may indicate that authorizationexecutewithprivileges is being executed
|
t1548
|
abuse elevation control mechanism
| null |
efforts should likely be placed on mitigation and collecting enough information on process launches and actions that could be performed before and after a uac bypass is performed
|
t1548
|
abuse elevation control mechanism
| null |
mac os system logs may also indicate when authorizationexecutewithprivileges is being called
|
t1548
|
abuse elevation control mechanism
| null |
monitor the file system for files that have the setuid or setgid bits set
|
t1548
|
abuse elevation control mechanism
| null |
monitoring os api callbacks for the execution can also be a way to detect this behavior but requires specialized security tooling
|
t1548
|
abuse elevation control mechanism
| null |
most modern systems contain native elevation control mechanisms that are intended to limit privileges that a user can perform on a machine
|
t1548
|
abuse elevation control mechanism
| null |
on linux auditd can alert every time a users actual id and effective id are different this is what happens when you sudo
|
t1548
|
abuse elevation control mechanism
| null |
process process metadata process process creation windows registry windows registry key modification command command execution file file metadata file file modification process os api execution
|
t1548
|
abuse elevation control mechanism
| null |
some uac bypass methods rely on modifying specific user accessible registry settings
|
t1548
|
abuse elevation control mechanism
| null |
there are many ways to perform uac bypasses when a user is in the local administrator group on a system so it may be difficult to target detection on all variations
|
t1548
|
abuse elevation control mechanism
| null |
this technique is abusing normal functionality in mac os and linux systems but sudo has the ability to log all input and output based on the log_input and log_output directives in the etcsudoers file
|
t1550
|
use alternate authentication material
| null |
a user has an active login session but has not entered the building or does not have vpn access
|
t1550
|
use alternate authentication material
| null |
activity may be from interactive login sessions or process ownership from accounts being used to execute binaries on a remote system as a particular account
|
t1550
|
use alternate authentication material
| null |
adversaries may use alternate authentication material such as password hashes kerberos tickets and application access tokens in order to move laterally within an environment and bypass normal system access controls
|
t1550
|
use alternate authentication material
| null |
authentication processes generally require a valid identity e
|
t1550
|
use alternate authentication material
| null |
citation technet audit policy look for suspicious account behavior across systems that share accounts either user admin or service accounts
|
t1550
|
use alternate authentication material
| null |
configure robust consistent account activity audit policies across the enterprise and with externally accessible services
|
t1550
|
use alternate authentication material
| null |
correlate other security systems with login information e
|
t1550
|
use alternate authentication material
| null |
examples one account logged into multiple systems simultaneously; multiple accounts logged into the same machine simultaneously; accounts logged in at odd times or outside of business hours
|
t1550
|
use alternate authentication material
| null |
logon session logon session creation web credential web credential usage application log application log content user account user account authentication active directory active directory credential request
|
t1550.001
|
use alternate authentication material
|
applicationTechniqueaccessTechniquetoken
|
apt28 has used several malicious applications that abused oauth access tokens to gain access to target email accounts including gmail and yahoo mail.
|
t1550.001
|
use alternate authentication material
|
applicationTechniqueaccessTechniquetoken
|
adversaries may use alternate authentication material, such as password hashes, kerberos tickets, and application access tokens, in order to move laterally within an environment and bypass normal system access controls.
|
t1550.001
|
use alternate authentication material
|
applicationTechniqueaccessTechniquetoken
|
with an oauth access token an adversary can use the user-granted rest api to perform functions such as email searching and contact enumeration.
|
t1550.001
|
use alternate authentication material
|
applicationTechniqueaccessTechniquetoken
|
obtaining a token which grants access to a victims primary email, the adversary may be able to extend access to all other services which the target subscribes by triggering forgotten password routines.
|
t1550.001
|
use alternate authentication material
|
applicationTechniqueaccessTechniquetoken
|
oauth is one commonly implemented framework that issues tokens to users for access to software-as-a-service.
|
t1552
|
unsecured credentials
| null |
additionally monitor processes for applications that can be used to query the registry such as regs0075 and collect command parameters that may indicate credentials are being searched
|
t1552
|
unsecured credentials
| null |
adversaries may search compromised systems to find and obtain insecurely stored credentials
|
t1552
|
unsecured credentials
| null |
bash_history
|
t1552
|
unsecured credentials
| null |
bash_history is read can help alert to suspicious activity
|
t1552
|
unsecured credentials
| null |
command command execution file file access process process creation user account user account authentication windows registry windows registry key access
|
t1552
|
unsecured credentials
| null |
correlate activity with related suspicious behavior that may indicate an active intrusion to reduce false positives
|
t1552
|
unsecured credentials
| null |
monitor for suspicious file access activity specifically indications that a process is reading multiple files in a short amount of time andor using command line arguments indicative of searching for credential material ex regex patterns
|
t1552
|
unsecured credentials
| null |
monitor the command line arguments of executing processes for suspicious words or regular expressions that may indicate searching for a password for example password pwd login secure or credentials
|
t1552
|
unsecured credentials
| null |
monitoring when the users
|
t1552
|
unsecured credentials
| null |
see valid accountst1078 for more information
|
t1552
|
unsecured credentials
| null |
these credentials can be stored andor misplaced in many locations on a system including plaintext files e
|
t1552
|
unsecured credentials
| null |
these may be indicators of automatedscripted credential access behavior
|
t1552
|
unsecured credentials
| null |
while detecting adversaries accessing credentials may be difficult without knowing they exist in the environment it may be possible to detect adversary use of credentials they have obtained
|
t1552
|
unsecured credentials
| null |
while users do typically rely on their history of commands they often access this history through other utilities like history instead of commands like cat ~
|
t1553
|
subvert trust controls
| null |
adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs
|
t1553
|
subvert trust controls
| null |
autoruns will hide entries signed by microsoft or windows by default so ensure hide microsoft entries and hide windows entries are both deselected
|
t1553
|
subvert trust controls
| null |
built in system utilities may generate high false positive alerts so compare against baseline knowledge for how systems are typically used and correlate modification events with other indications of malicious activity where possible
|
t1553
|
subvert trust controls
| null |
citation spectorops code signing dec 2017 analyze autoruns data for oddities and anomalies specifically malicious files attempting persistent execution by hiding within auto starting locations
|
t1553
|
subvert trust controls
| null |
citation spectorops subverting trust sept 2017 monitor and investigate attempts to modify extended file attributes with utilities such as xattr
|
t1553
|
subvert trust controls
| null |
citation spectorops subverting trust sept 2017 a systems root certificates are unlikely to change frequently
|
t1553
|
subvert trust controls
| null |
collect and analyze signing certificate metadata on software that executes within the environment to look for unusual certificate characteristics and outliers
|
t1553
|
subvert trust controls
| null |
monitor new certificates installed on a system that could be due to malicious activity
|
t1553
|
subvert trust controls
| null |
operating systems and security products may contain mechanisms to identify programs or websites as possessing some level of trust
|
t1553
|
subvert trust controls
| null |
periodically baseline registered sips and trust providers registry entries and files on disk specifically looking for new modified or non microsoft entries
|
t1553
|
subvert trust controls
| null |
windows registry windows registry key creation windows registry windows registry key modification process process creation command command execution file file metadata file file modification module module load
|
t1553.006
|
subvert trust controls
|
codeTechniquesigning Technique policy Technique modification
|
apt 39 has used malware to turn off the requiresigned feature which ensures only signed dlls can be run on windows.
|
t1553.006
|
subvert trust controls
|
codeTechniquesigning Technique policy Technique modification
|
blackenergy has enabled the testsigning boot configuration option to facilitate loading of a driver component.
|
t1553.006
|
subvert trust controls
|
codeTechniquesigning Technique policy Technique modification
|
hikit has attempted to disable driver signing verification by tampering with several registry keys prior to the loading of a rootkit driver component.
|
t1553.006
|
subvert trust controls
|
codeTechniquesigning Technique policy Technique modification
|
turla has modified variables in kernel memory to turn off driver signature enforcement after exploiting vulnerabilities that obtained kernel mode privileges.
|
t1553.006
|
subvert trust controls
|
codeTechniquesigning Technique policy Technique modification
|
especter patches windows kernel function sep initialize codeintegrity directly in memory to disable driver signature enforcement dse.
|
t1554
|
compromise client software binary
| null |
adversaries may modify client software binaries to establish persistent access to systems
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.