instruction stringlengths 16 110 | output stringlengths 0 4.13k |
|---|---|
Define the MITRE ATT&CK technique T1055.011. | Adversaries may inject malicious code into process via Extra Window Memory (EWM) in order to evade process-based defenses as well as possibly elevate privileges. EWM injection is a method of executing arbitrary code in the address space of a separate live process. Before creating a window, graphical Windows-based proce... |
List key detection ideas for MITRE ATT&CK technique T1055.011. | Monitor for API calls related to enumerating and manipulating EWM such as GetWindowLong and SetWindowLong . Malware associated with this technique have also used SendNotifyMessage to trigger the associated window procedure and eventual malicious injection. |
Which ATT&CK tactic(s) does technique T1055.011 belong to? | defense-evasion, privilege-escalation |
List mitigations for MITRE ATT&CK technique T1055.011. | M1040 – Behavior Prevention on Endpoint |
Define the MITRE ATT&CK technique T1053.005. | Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The [schtasks](https://attack.mitre.org/software/S0111) utility can be run directly on the command line, or the Task Schedule... |
List key detection ideas for MITRE ATT&CK technique T1053.005. | Monitor process execution from the svchost.exe in Windows 10 and the Windows Task Scheduler taskeng.exe for older versions of Windows. If scheduled tasks are not used for persistence, then the adversary is likely to remove the task when the action is complete. Monitor Windows Task Scheduler stores in %systemroot%\Syste... |
Which ATT&CK tactic(s) does technique T1053.005 belong to? | execution, persistence, privilege-escalation |
List mitigations for MITRE ATT&CK technique T1053.005. | M1026 – Privileged Account Management; M1018 – User Account Management; M1047 – Audit; M1028 – Operating System Configuration |
Define the MITRE ATT&CK technique T1205.002. | Adversaries may attach filters to a network socket to monitor then activate backdoors used for persistence or command and control. With elevated permissions, adversaries can use features such as the `libpcap` library to open sockets and install filters to allow or disallow certain types of data to come through the sock... |
List key detection ideas for MITRE ATT&CK technique T1205.002. | Identify running processes with raw sockets. Ensure processes listed have a need for an open raw socket and are in accordance with enterprise policy. |
Which ATT&CK tactic(s) does technique T1205.002 belong to? | command-and-control, defense-evasion, persistence |
List mitigations for MITRE ATT&CK technique T1205.002. | M1037 – Filter Network Traffic |
Define the MITRE ATT&CK technique T1560.001. | Adversaries may use utilities to compress and/or encrypt collected data prior to exfiltration. Many utilities include functionalities to compress, encrypt, or otherwise package data into a format that is easier/more secure to transport. Adversaries may abuse various utilities to compress or encrypt data before exfiltra... |
List key detection ideas for MITRE ATT&CK technique T1560.001. | Common utilities that may be present on the system or brought in by an adversary may be detectable through process monitoring and monitoring for command-line arguments for known archival utilities. This may yield a significant number of benign events, depending on how systems in the environment are typically used. Cons... |
Which ATT&CK tactic(s) does technique T1560.001 belong to? | collection |
List mitigations for MITRE ATT&CK technique T1560.001. | M1047 – Audit |
Define the MITRE ATT&CK technique T1021.005. | Adversaries may use [Valid Accounts](https://attack.mitre.org/techniques/T1078) to remotely control machines using Virtual Network Computing (VNC). VNC is a platform-independent desktop sharing system that uses the RFB (“remote framebuffer”) protocol to enable users to remotely control another computer’s display by rel... |
List key detection ideas for MITRE ATT&CK technique T1021.005. | Use of VNC may be legitimate depending on the environment and how it’s used. Other factors, such as access patterns and activity that occurs after a remote login, may indicate suspicious or malicious behavior using VNC. On macOS systems log show --predicate 'process = "screensharingd" and eventMessage contains "Authent... |
Which ATT&CK tactic(s) does technique T1021.005 belong to? | lateral-movement |
List mitigations for MITRE ATT&CK technique T1021.005. | M1042 – Disable or Remove Feature or Program; M1037 – Filter Network Traffic; M1047 – Audit; M1033 – Limit Software Installation |
Define the MITRE ATT&CK technique T1047. | Adversaries may abuse Windows Management Instrumentation (WMI) to execute malicious commands and payloads. WMI is designed for programmers and is the infrastructure for management data and operations on Windows systems. WMI is an administration feature that provides a uniform environment to access Windows system compon... |
List key detection ideas for MITRE ATT&CK technique T1047. | Monitor network traffic for WMI connections; the use of WMI in environments that do not typically use WMI may be suspect. Perform process monitoring to capture command-line arguments of "wmic" and detect commands that are used to perform remote behavior. |
Which ATT&CK tactic(s) does technique T1047 belong to? | execution |
List mitigations for MITRE ATT&CK technique T1047. | M1026 – Privileged Account Management; M1040 – Behavior Prevention on Endpoint; M1018 – User Account Management; M1038 – Execution Prevention |
Define the MITRE ATT&CK technique T1113. | Adversaries may attempt to take screen captures of the desktop to gather information over the course of an operation. Screen capturing functionality may be included as a feature of a remote access tool used in post-compromise operations. Taking a screenshot is also typically possible through native utilities or API cal... |
List key detection ideas for MITRE ATT&CK technique T1113. | Monitoring for screen capture behavior will depend on the method used to obtain data from the operating system and write output files. Detection methods could include collecting information from unusual processes using API calls used to obtain image data, and monitoring for image files written to disk. The sensor data ... |
Which ATT&CK tactic(s) does technique T1113 belong to? | collection |
Define the MITRE ATT&CK technique T1027.011. | Adversaries may store data in "fileless" formats to conceal malicious activity from defenses. Fileless storage can be broadly defined as any format other than a file. Common examples of non-volatile fileless storage in Windows systems include the Windows Registry, event logs, or WMI repository. In Linux systems, shared... |
Which ATT&CK tactic(s) does technique T1027.011 belong to? | defense-evasion |
List mitigations for MITRE ATT&CK technique T1027.011. | M1047 – Audit |
Define the MITRE ATT&CK technique T1037. | Adversaries may use scripts automatically executed at boot or logon initialization to establish persistence. Initialization scripts can be used to perform administrative functions, which may often execute other programs or send information to an internal logging server. These scripts can vary based on operating system ... |
List key detection ideas for MITRE ATT&CK technique T1037. | Monitor logon scripts for unusual access by abnormal users or at abnormal times. Look for files added or modified by unusual accounts outside of normal administration duties. Monitor running process for actions that could be indicative of abnormal programs or executables running upon logon. |
Which ATT&CK tactic(s) does technique T1037 belong to? | persistence, privilege-escalation |
List mitigations for MITRE ATT&CK technique T1037. | M1024 – Restrict Registry Permissions; M1022 – Restrict File and Directory Permissions |
Define the MITRE ATT&CK technique T1557. | Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.mitre.org/techniques/T1040), [Transmitted Data Manipulation](https://attack.mitre.org/techniques/T1565/002), or ... |
List key detection ideas for MITRE ATT&CK technique T1557. | Monitor network traffic for anomalies associated with known AiTM behavior. Consider monitoring for modifications to system configuration files involved in shaping network traffic flow. |
Which ATT&CK tactic(s) does technique T1557 belong to? | collection, credential-access |
List mitigations for MITRE ATT&CK technique T1557. | M1037 – Filter Network Traffic; M1041 – Encrypt Sensitive Information; M1035 – Limit Access to Resource Over Network; M1042 – Disable or Remove Feature or Program; M1017 – User Training; M1031 – Network Intrusion Prevention; M1030 – Network Segmentation |
Define the MITRE ATT&CK technique T1033. | Adversaries may attempt to identify the primary user, currently logged in user, set of users that commonly uses a system, or whether a user is actively using the system. They may do this, for example, by retrieving account usernames or by using [OS Credential Dumping](https://attack.mitre.org/techniques/T1003). The inf... |
List key detection ideas for MITRE ATT&CK technique T1033. | `System and network discovery techniques normally occur throughout an operation as an adversary learns the environment. 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. Monitor processes and command-line argument... |
Which ATT&CK tactic(s) does technique T1033 belong to? | discovery |
Define the MITRE ATT&CK technique T1583. | Adversaries may buy, lease, rent, or obtain infrastructure that can be used during targeting. A wide variety of infrastructure exists for hosting and orchestrating adversary operations. Infrastructure solutions include physical or cloud servers, domains, and third-party web services. Some infrastructure providers offer... |
List key detection ideas for MITRE ATT&CK technique T1583. | Consider use of services that may aid in tracking of newly acquired infrastructure, such as WHOIS databases for domain registration information. Once adversaries have provisioned infrastructure (ex: a server for use in command and control), internet scans may help proactively discover adversary acquired infrastructure.... |
Which ATT&CK tactic(s) does technique T1583 belong to? | resource-development |
List mitigations for MITRE ATT&CK technique T1583. | M1056 – Pre-compromise |
Define the MITRE ATT&CK technique T1218.011. | Adversaries may abuse rundll32.exe to proxy execution of malicious code. Using rundll32.exe, vice executing directly (i.e. [Shared Modules](https://attack.mitre.org/techniques/T1129)), may avoid triggering security tools that may not monitor execution of the rundll32.exe process because of allowlists or false positives... |
List key detection ideas for MITRE ATT&CK technique T1218.011. | Use process monitoring to monitor the execution and arguments of rundll32.exe. Compare recent invocations of rundll32.exe with prior history of known good arguments and loaded DLLs to determine anomalous and potentially adversarial activity. Command arguments used with the rundll32.exe invocation may also be useful in ... |
Which ATT&CK tactic(s) does technique T1218.011 belong to? | defense-evasion |
List mitigations for MITRE ATT&CK technique T1218.011. | M1050 – Exploit Protection |
Define the MITRE ATT&CK technique T1613. | Adversaries may attempt to discover containers and other resources that are available within a containers environment. Other resources may include images, deployments, pods, nodes, and other information such as the status of a cluster. These resources can be viewed within web applications such as the Kubernetes dashboa... |
List key detection ideas for MITRE ATT&CK technique T1613. | Establish centralized logging for the activity of container and Kubernetes cluster components. This can be done by deploying logging agents on Kubernetes nodes and retrieving logs from sidecar proxies for application pods to detect malicious activity at the cluster level. Monitor logs for actions that could be taken to... |
Which ATT&CK tactic(s) does technique T1613 belong to? | discovery |
List mitigations for MITRE ATT&CK technique T1613. | M1030 – Network Segmentation; M1035 – Limit Access to Resource Over Network; M1018 – User Account Management |
Define the MITRE ATT&CK technique T1583.007. | Adversaries may purchase and configure serverless cloud infrastructure, such as Cloudflare Workers, AWS Lambda functions, or Google Apps Scripts, that can be used during targeting. By utilizing serverless infrastructure, adversaries can make it more difficult to attribute infrastructure used during operations back to t... |
Which ATT&CK tactic(s) does technique T1583.007 belong to? | resource-development |
List mitigations for MITRE ATT&CK technique T1583.007. | M1056 – Pre-compromise |
Define the MITRE ATT&CK technique T1132.001. | Adversaries may encode data with a standard data encoding system to make the content of command and control traffic more difficult to detect. Command and control (C2) information can be encoded using a standard data encoding system that adheres to existing protocol specifications. Common data encoding schemes include A... |
List key detection ideas for MITRE ATT&CK technique T1132.001. | Analyze network data for uncommon data flows (e.g., a client sending significantly more data than it receives from a server). Processes utilizing the network that do not normally have network communication or have never been seen before are suspicious. Analyze packet contents to detect communications that do not follow... |
Which ATT&CK tactic(s) does technique T1132.001 belong to? | command-and-control |
List mitigations for MITRE ATT&CK technique T1132.001. | M1031 – Network Intrusion Prevention |
Define the MITRE ATT&CK technique T1027.009. | Adversaries may embed payloads within other files to conceal malicious content from defenses. Otherwise seemingly benign files (such as scripts and executables) may be abused to carry and obfuscate malicious payloads and content. In some cases, embedded payloads may also enable adversaries to [Subvert Trust Controls](h... |
Which ATT&CK tactic(s) does technique T1027.009 belong to? | defense-evasion |
List mitigations for MITRE ATT&CK technique T1027.009. | M1049 – Antivirus/Antimalware; M1040 – Behavior Prevention on Endpoint |
Define the MITRE ATT&CK technique T1556.003. | Adversaries may modify pluggable authentication modules (PAM) to access user credentials or enable otherwise unwarranted access to accounts. PAM is a modular system of configuration files, libraries, and executable files which guide authentication for many services. The most common authentication module is pam_unix.so,... |
List key detection ideas for MITRE ATT&CK technique T1556.003. | Monitor PAM configuration and module paths (ex: /etc/pam.d/) for changes. Use system-integrity tools such as AIDE and monitoring tools such as auditd to monitor PAM files. Look for suspicious account behavior across systems that share accounts, either user, admin, or service accounts. Examples: one account logged into ... |
Which ATT&CK tactic(s) does technique T1556.003 belong to? | credential-access, defense-evasion, persistence |
List mitigations for MITRE ATT&CK technique T1556.003. | M1032 – Multi-factor Authentication; M1026 – Privileged Account Management |
Define the MITRE ATT&CK technique T1578.004. | An adversary may revert changes made to a cloud instance after they have performed malicious activities in attempt to evade detection and remove evidence of their presence. In highly virtualized environments, such as cloud-based infrastructure, this may be accomplished by restoring virtual machine (VM) or data storage ... |
List key detection ideas for MITRE ATT&CK technique T1578.004. | Establish centralized logging of instance activity, which can be used to monitor and review system events even after reverting to a snapshot, rolling back changes, or changing persistence/type of storage. Monitor specifically for events related to snapshots and rollbacks and VM configuration changes, that are occurring... |
Which ATT&CK tactic(s) does technique T1578.004 belong to? | defense-evasion |
Define the MITRE ATT&CK technique T1592. | Adversaries may gather information about the victim's hosts that can be used during targeting. Information about hosts may include a variety of details, including administrative data (ex: name, assigned IP, functionality, etc.) as well as specifics regarding its configuration (ex: operating system, language, etc.). Adv... |
List key detection ideas for MITRE ATT&CK technique T1592. | Internet scanners may be used to look for patterns associated with malicious content designed to collect host information from visitors. Much of this activity may have a very high occurrence and associated false positive rate, as well as potentially taking place outside the visibility of the target organization, making... |
Which ATT&CK tactic(s) does technique T1592 belong to? | reconnaissance |
List mitigations for MITRE ATT&CK technique T1592. | M1056 – Pre-compromise |
Define the MITRE ATT&CK technique T1596.003. | Adversaries may search public digital certificate data for information about victims that can be used during targeting. Digital certificates are issued by a certificate authority (CA) in order to cryptographically verify the origin of signed content. These certificates, such as those used for encrypted web traffic (HTT... |
List key detection ideas for MITRE ATT&CK technique T1596.003. | Much of this activity may have a very high occurrence and associated false positive rate, as well as potentially taking place outside the visibility of the target organization, making detection difficult for defenders. Detection efforts may be focused on related stages of the adversary lifecycle, such as during Initial... |
Which ATT&CK tactic(s) does technique T1596.003 belong to? | reconnaissance |
List mitigations for MITRE ATT&CK technique T1596.003. | M1056 – Pre-compromise |
Define the MITRE ATT&CK technique T1056.001. | Adversaries may log user keystrokes to intercept credentials as the user types them. Keylogging is likely to be used to acquire credentials for new access opportunities when [OS Credential Dumping](https://attack.mitre.org/techniques/T1003) efforts are not effective, and may require an adversary to intercept keystrokes... |
List key detection ideas for MITRE ATT&CK technique T1056.001. | Keyloggers may take many forms, possibly involving modification to the Registry and installation of a driver, setting a hook, or polling to intercept keystrokes. Commonly used API calls include `SetWindowsHook`, `GetKeyState`, and `GetAsyncKeyState`. Monitor the Registry and file system for such changes, monitor driver... |
Which ATT&CK tactic(s) does technique T1056.001 belong to? | collection, credential-access |
Define the MITRE ATT&CK technique T1564.012. | Adversaries may attempt to hide their file-based artifacts by writing them to specific folders or file names excluded from antivirus (AV) scanning and other defensive capabilities. AV and other file-based scanners often include exclusions to optimize performance as well as ease installation and legitimate use of applic... |
Which ATT&CK tactic(s) does technique T1564.012 belong to? | defense-evasion |
List mitigations for MITRE ATT&CK technique T1564.012. | M1049 – Antivirus/Antimalware; M1013 – Application Developer Guidance |
Define the MITRE ATT&CK technique T1222.002. | Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files. File and directory permissions are commonly managed by ACLs configured by the file or directory owner, or users with the appropriate permissions. File and directory ACL implementations vary b... |
List key detection ideas for MITRE ATT&CK technique T1222.002. | Monitor and investigate attempts to modify ACLs and file/directory ownership. Many of the commands used to modify ACLs and file/directory ownership are built-in system utilities and may generate a high false positive alert rate, so compare against baseline knowledge for how systems are typically used and correlate modi... |
Which ATT&CK tactic(s) does technique T1222.002 belong to? | defense-evasion |
List mitigations for MITRE ATT&CK technique T1222.002. | M1022 – Restrict File and Directory Permissions; M1026 – Privileged Account Management |
Define the MITRE ATT&CK technique T1110.001. | Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts. Without knowledge of the password for an account, an adversary may opt to systematically guess the password using a repetitive or iterative mechanism. An adversary may guess ... |
List key detection ideas for MITRE ATT&CK technique T1110.001. | Monitor authentication logs for system and application login failures of [Valid Accounts](https://attack.mitre.org/techniques/T1078). If authentication failures are high, then there may be a brute force attempt to gain access to a system using legitimate credentials. |
Which ATT&CK tactic(s) does technique T1110.001 belong to? | credential-access |
List mitigations for MITRE ATT&CK technique T1110.001. | M1051 – Update Software; M1032 – Multi-factor Authentication; M1027 – Password Policies; M1036 – Account Use Policies |
Define the MITRE ATT&CK technique T1216.001. | Adversaries may use PubPrn to proxy execution of malicious remote files. PubPrn.vbs is a [Visual Basic](https://attack.mitre.org/techniques/T1059/005) script that publishes a printer to Active Directory Domain Services. The script may be signed by Microsoft and is commonly executed through the [Windows Command Shell](h... |
List key detection ideas for MITRE ATT&CK technique T1216.001. | Monitor script processes, such as `cscript`, and command-line parameters for scripts like PubPrn.vbs that may be used to proxy execution of malicious files. |
Which ATT&CK tactic(s) does technique T1216.001 belong to? | defense-evasion |
List mitigations for MITRE ATT&CK technique T1216.001. | M1038 – Execution Prevention; M1040 – Behavior Prevention on Endpoint |
Define the MITRE ATT&CK technique T1597.002. | Adversaries may purchase technical information about victims that can be used during targeting. Information about victims may be available for purchase within reputable private sources and databases, such as paid subscriptions to feeds of scan databases or other data aggregation services. Adversaries may also purchase ... |
List key detection ideas for MITRE ATT&CK technique T1597.002. | Much of this activity may have a very high occurrence and associated false positive rate, as well as potentially taking place outside the visibility of the target organization, making detection difficult for defenders. Detection efforts may be focused on related stages of the adversary lifecycle, such as during Initial... |
Which ATT&CK tactic(s) does technique T1597.002 belong to? | reconnaissance |
List mitigations for MITRE ATT&CK technique T1597.002. | M1056 – Pre-compromise |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 3