id
stringlengths 5
9
| technique
stringlengths 3
43
| subtechniqueid
stringlengths 3
60
⌀ | sentences
stringlengths 1
871
|
|---|---|---|---|
t1003 | os credential dumping | null | windows monitor for unexpected processes interacting with lsass |
t1003 | os credential dumping | null | 001 scripts also exist that contain credential dumping functionality such as powersploit invoke mimikatz module citation powersploit which may require additional logging features to be configured in the operating system to collect necessary information for analysis |
t1003 | os credential dumping | null | 1 and windows server 2012 r2 monitor windows logs for lsass |
t1003 | os credential dumping | null | adversaries may attempt to dump credentials to obtain account login and credential material normally in the form of a hash or a clear text password from the operating system and software |
t1003 | os credential dumping | null | also monitor for network protocols citation microsoft drsr dec 2017 citation microsoft nrpc dec 2017 and other replication requests citation microsoft samr from ips not associated with known domain controllers |
t1003 | os credential dumping | null | citation adsecurity dcsync sept 2015 linux to obtain the passwords and hashes stored in memory processes must open a maps file in the proc filesystem for the process being analyzed |
t1003 | os credential dumping | null | citation harmj0y dcsync sept 2015 |
t1003 | os credential dumping | null | citation medium detecting attempts to steal passwords from memory common credential dumpers such as mimikatzs0002 access the lsa subsystem service lsass process by opening the process locating the lsa secrets key and decrypting the sections in memory where credential details are stored |
t1003 | os credential dumping | null | citation microsoft drsr dec 2017 citation microsoft getchanges citation samba drsuapi note domain controllers may not log replication requests originating from the default domain controller account |
t1003 | os credential dumping | null | credential dumpers may also use methods for reflective process injectiont1055 to reduce potential indicators of malicious activity |
t1003 | os credential dumping | null | credentials can then be used to perform lateral movementta0008 and access restricted information |
t1003 | os credential dumping | null | detection of compromised valid accountst1078 in use by adversaries may help as well |
t1003 | os credential dumping | null | exe creation to verify that lsass started as a protected process |
t1003 | os credential dumping | null | hash dumpers open the security accounts manager sam on the local file system %systemroot%system32configsam or create a dump of the registry sam key to access stored account password hashes |
t1003 | os credential dumping | null | monitor domain controller logs for replication requests and other unscheduled activity possibly associated with dcsync |
t1003 | os credential dumping | null | monitor processes and command line arguments for program execution that may be indicative of credential dumping |
t1003 | os credential dumping | null | others will make an in memory copy of the same table before reading hashes |
t1003 | os credential dumping | null | process process creation process process access command command execution file file access windows registry windows registry key access active directory active directory object access network traffic network traffic flow network traffic network traffic content process os api execution |
t1003 | os credential dumping | null | remote access tools may contain built in features or incorporate existing tools like mimikatzs0002 |
t1003 | os credential dumping | null | some hash dumpers will open the local file system as a device and parse to the sam table to avoid file access defenses |
t1003 | os credential dumping | null | the auditd monitoring tool which ships stock in many linux distributions can be used to watch for hostile processes opening this file in the proc file system alerting on the pid process name and arguments of such programs |
t1003 | os credential dumping | null | this file is stored under the path proc<pid>maps where the <pid> directory is the unique pid of the program being interrogated for such authentication data |
t1003.004 | os credential dumping | null | apt 33 has used a variety of publicly available tools like lazagne to gather credentials. |
t1003.004 | os credential dumping | null | cosmicduke collects lsa secrets. |
t1003.004 | os credential dumping | null | crackmapexec can dump hashed passwords from lsa secrets for the targeted system. |
t1003.004 | os credential dumping | null | dragonfly 2.0 dropped and executed secretsdump to dump password hashes. |
t1003.004 | os credential dumping | null | gsecdump can dump lsa secrets. |
t1003.004 | os credential dumping | null | secretsdump and mimikatz modules within impacket can perform credential dumping to obtain account and password information. |
t1003.004 | os credential dumping | null | ke3chang has dumped credentials including by using gsecdump. |
t1003.004 | os credential dumping | null | lazagne can perform credential dumping from lsa secrets to obtain account and password information. |
t1003.004 | os credential dumping | null | leafminer used several tools for retrieving login and password information including lazagne. |
t1003.004 | os credential dumping | null | menupass has used a modified version of pentesting tools wmiexec.vbs and secretsdump.py to dump credentials. |
t1003.004 | os credential dumping | null | mimikatz performs credential dumping to obtain account and password information useful in gaining access to additional systems and enterprise network resources. it contains functionality to acquire information about credentials in many ways including from the lsa. |
t1003.004 | os credential dumping | null | muddy water has performed credential dumping with lazagne. |
t1003.004 | os credential dumping | null | oilrig has used credential dumping tools such as lazagne to steal credentials to accounts logged into the compromised system and to outlook web access. |
t1003.004 | os credential dumping | null | puppy can use lazagne for harvesting credentials. |
t1003.004 | os credential dumping | null | threat group-3390 actors have used gsecdump to dump credentials. they have also dumped credentials from domain controllers. |
t1003.006 | os credential dumping | dcsync | apt29 leveraged privileged accounts to replicate directory service data with domain controllers. |
t1003.006 | os credential dumping | dcsync | mimikatz performs credential dumping to obtain account and password information useful in gaining access to additional systems and enterprise network resources. it contains functionality to acquire information about credentials in many ways including from dcsync netsync. |
t1003.006 | os credential dumping | dcsync | operation wocao has used mimikatz dcsync to dump credentials from the memory of the targeted system. |
t1003.006 | os credential dumping | dcsync | unc 2452 leveraged privileged accounts to replicate directory service data with domain controllers. |
t1003.006 | os credential dumping | dcsync | the attacker discovered domain controllers dcs and submitted a replication request. this prompted the primary dc to replicate the credentials of other dcs back to the compromised domain administrator, using the directory replication service drs remote protocol. |
t1005 | data from local system | null | adversaries may do this using a command and scripting interpretert1059 such as cmds0106 which has functionality to interact with the file system to gather information |
t1005 | data from local system | null | adversaries may search local system sources such as file systems or local databases to find files of interest and sensitive data prior to exfiltration |
t1005 | data from local system | null | data may also be acquired through windows system management tools such as windows management instrumentationt1047 and powershellt1059 |
t1005 | data from local system | null | monitor processes and command line arguments for actions that could be taken to collect files from a system |
t1005 | data from local system | null | remote access tools with built in features may interact directly with the windows api to gather data |
t1005 | data from local system | null | script script execution file file access command command execution |
t1006 | direct volume access | null | 001 additional logging of powershell scripts is recommended |
t1006 | direct volume access | null | adversaries may directly access a volume to bypass file access controls and file system monitoring |
t1006 | direct volume access | null | citation github powersploit ninjacopy monitor processes and command line arguments for actions that could be taken to copy files from the logical drive and evade common file system protections |
t1006 | direct volume access | null | command command execution drive drive access |
t1006 | direct volume access | null | monitor handle opens on drive volumes that are made by processes to determine when they may directly access logical drives |
t1006 | direct volume access | null | since this technique may also be used through powershell |
t1006 | direct volume access | null | windows allows programs to have direct access to logical volumes |
t1007 | system service discovery | null | adversaries may try to get information about registered services |
t1007 | system service discovery | null | commands that may obtain information about services using operating system utilities are sc tasklist svc using tasklists0057 and net start using nets0039 but adversaries may also use other tools as well |
t1007 | system service discovery | 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 lateral movement based on the information obtained |
t1007 | system service discovery | null | information may also be acquired through windows system management tools such as windows management instrumentationt1047 and powershellt1059 |
t1007 | system service discovery | null | monitor processes and command line arguments for actions that could be taken to gather system information related to services |
t1007 | system service discovery | null | process process creation command command execution |
t1007 | system service discovery | null | remote access tools with built in features may interact directly with the windows api to gather information |
t1007 | system service discovery | null | system and network discovery techniques normally occur throughout an operation as an adversary learns the environment |
t1008 | fallback channels | null | a client sending significantly more data than it receives from a server |
t1008 | fallback channels | null | adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds |
t1008 | fallback channels | null | analyze network data for uncommon data flows e |
t1008 | fallback channels | null | analyze packet contents to detect communications that do not follow the expected protocol behavior for the port that is being used |
t1008 | fallback channels | null | citation university of birmingham c2 |
t1008 | fallback channels | null | network traffic network traffic flow network traffic network connection creation |
t1008 | fallback channels | null | processes utilizing the network that do not normally have network communication or have never been seen before are suspicious |
t1010 | application window discovery | null | adversaries may attempt to get a listing of open application windows |
t1010 | application window discovery | null | data and events should not be viewed in isolation but as part of a chain of behavior that could lead to other activities based on the information obtained |
t1010 | application window discovery | null | information may also be acquired through windows system management tools such as windows management instrumentationt1047 and powershellt1059 |
t1010 | application window discovery | null | monitor processes and command line arguments for actions that could be taken to gather system and network information |
t1010 | application window discovery | null | process process creation command command execution process os api execution |
t1010 | application window discovery | null | remote access tools with built in features may interact directly with the windows api to gather information |
t1010 | application window discovery | null | system and network discovery techniques normally occur throughout an operation as an adversary learns the environment |
t1010 | application window discovery | null | window listings could convey information about how the system is used or give context to information collected by a keylogger |
t1011 | exfiltration over other network medium | null | adversaries may attempt to exfiltrate data over a different network medium than the command and control channel |
t1011 | exfiltration over other network medium | null | if the command and control network is a wired internet connection the exfiltration may occur for example over a wifi connection modem cellular data connection bluetooth or another radio frequency rf channel |
t1011 | exfiltration over other network medium | null | monitor for and investigate changes to host adapter settings such as addition andor replication of communication interfaces |
t1011 | exfiltration over other network medium | null | monitor for processes utilizing the network that do not normally have network communication or have never been seen before |
t1011 | exfiltration over other network medium | null | network traffic network connection creation network traffic network traffic flow network traffic network traffic content file file access command command execution |
t1011 | exfiltration over other network medium | null | processes that normally require user driven events to access the network for example a web browser opening with a mouse click or key press but access the network without such may be malicious |
t1012 | query registry | null | adversaries may interact with the windows registry to gather information about the system configuration and installed software |
t1012 | query registry | null | command line invocation of utilities used to query the registry may be detected through process and command line monitoring |
t1012 | query registry | 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 lateral movement based on the information obtained |
t1012 | query registry | null | information may also be acquired through windows system management tools such as windows management instrumentationt1047 and powershellt1059 |
t1012 | query registry | null | interaction with the windows registry may come from the command line using utilities such as regs0075 or through running malware that may interact with the registry through an api |
t1012 | query registry | null | process process creation command command execution windows registry windows registry key access process os api execution |
t1012 | query registry | null | remote access tools with built in features may interact directly with the windows api to gather information |
t1012 | query registry | null | system and network discovery techniques normally occur throughout an operation as an adversary learns the environment |
t1012 | query registry | null | the registry contains a significant amount of information about the operating system configuration software and security |
t1014 | rootkit | null | adversaries may use rootkits to hide the presence of programs files network connections services drivers and other system components |
t1014 | rootkit | null | citation wikipedia rootkit |
t1014 | rootkit | null | drive drive modification firmware firmware modification |
t1014 | rootkit | null | monitor for the existence of unrecognized dlls devices services and changes to the mbr |
t1014 | rootkit | null | rootkits are programs that hide the existence of malware by interceptinghooking and modifying operating system api calls that supply system information |
t1014 | rootkit | null | some rootkit protections may be built into anti virus or operating system software |
t1014 | rootkit | null | there are dedicated rootkit detection tools that look for specific types of rootkit behavior |