text stringlengths 0 3.15k |
|---|
Technique ID: T1136 |
Name: Create Account |
Description: Adversaries may create an account to maintain access to victim systems. With a sufficient level of access, creating such accounts may be used to establish secondary credentialed access that do not require persistent remote access tools to be deployed on the system. Accounts may be created on the local syst... |
Tactics: Persistence |
Platforms Affected: Azure AD, Containers, Google Workspace, IaaS, Linux, Network, Office 365, SaaS, Windows, macOS |
Detection Strategies: Monitor for processes and command-line parameters associated with account creation, such as net user or useradd. Collect data on account creation within a network. Event ID 4720 is generated when a user account is created on a Windows system and domain controller. Perform regular audits of domain ... |
More Information: https://attack.mitre.org/techniques/T1136 |
Technique ID: T1136.003 |
Name: Create Account: Cloud Account |
Description: Adversaries may create a cloud account to maintain access to victim systems. With a sufficient level of access, such accounts may be used to establish secondary credentialed access that does not require persistent remote access tools to be deployed on the system. Adversaries may create accounts that only h... |
Tactics: Persistence |
Platforms Affected: Azure AD, Google Workspace, IaaS, Office 365, SaaS |
Detection Strategies: Collect usage logs from cloud user and administrator accounts to identify unusual activity in the creation of new accounts and assignment of roles to those accounts. Monitor for accounts assigned to admin roles that go over a certain threshold of known admins. |
More Information: https://attack.mitre.org/techniques/T1136/003 |
Technique ID: T1546 |
Name: Event Triggered Execution |
Description: Adversaries may establish persistence and/or elevate privileges using system mechanisms that trigger execution based on specific events. Various operating systems have means to monitor and subscribe to events such as logons or other user activity such as running specific applications/binaries. Cloud enviro... |
Tactics: Persistence, Privilege Escalation |
Platforms Affected: IaaS, Linux, Office 365, SaaS, Windows, macOS |
Detection Strategies: 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. Also look for changes that do not line up wi... |
More Information: https://attack.mitre.org/techniques/T1546 |
Technique ID: T1525 |
Name: Implant Internal Image |
Description: Adversaries may implant cloud or container images with malicious code to establish persistence after gaining access to an environment. Amazon Web Services (AWS) Amazon Machine Images (AMIs), Google Cloud Platform (GCP) Images, and Azure Images as well as popular container runtimes such as Docker can be imp... |
Tactics: Persistence |
Platforms Affected: Containers, IaaS |
Detection Strategies: Monitor interactions with images and containers by users to identify ones that are added or modified anomalously. In containerized environments, changes may be detectable by monitoring the Docker daemon logs or setting up and monitoring Kubernetes audit logs depending on registry configuration. |
More Information: https://attack.mitre.org/techniques/T1525 |
Technique ID: T1556 |
Name: Modify Authentication Process |
Description: Adversaries may modify authentication mechanisms and processes to access user credentials or enable otherwise unwarranted access to accounts. The authentication process is handled by mechanisms, such as the Local Security Authentication Server (LSASS) process and the Security Accounts Manager (SAM) on Wind... |
Tactics: Credential Access, Defense Evasion, Persistence |
Platforms Affected: Azure AD, Google Workspace, IaaS, Linux, Network, Office 365, SaaS, Windows, macOS |
Detection Strategies: Monitor for new, unfamiliar DLL files written to a domain controller and/or local computer. Monitor for changes to Registry entries for password filters (ex: HKEYMACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Notification Packages) and correlate then investigate the DLL files these files reference. ... |
More Information: https://attack.mitre.org/techniques/T1556 |
Technique ID: T1556.007 |
Name: Modify Authentication Process: Hybrid Identity |
Description: Adversaries may patch, modify, or otherwise backdoor cloud authentication processes that are tied to on-premises user identities in order to bypass typical authentication mechanisms, access credentials, and enable persistent access to accounts. Many organizations maintain hybrid user and device identities ... |
Tactics: Credential Access, Defense Evasion, Persistence |
Platforms Affected: Azure AD, Google Workspace, IaaS, Office 365, SaaS, Windows |
Detection Strategies: No detection description provided. |
More Information: https://attack.mitre.org/techniques/T1556/007 |
Technique ID: T1556.006 |
Name: Modify Authentication Process: Multi-Factor Authentication |
Description: Adversaries may disable or modify multi-factor authentication (MFA) mechanisms to enable persistent access to compromised accounts. Once adversaries have gained access to a network by either compromising an account lacking MFA or by employing an MFA bypass method such as Multi-Factor Authentication Request... |
Tactics: Credential Access, Defense Evasion, Persistence |
Platforms Affected: Azure AD, Google Workspace, IaaS, Linux, Office 365, SaaS, Windows, macOS |
Detection Strategies: No detection description provided. |
More Information: https://attack.mitre.org/techniques/T1556/006 |
Technique ID: T1137 |
Name: Office Application Startup |
Description: Adversaries may leverage Microsoft Office-based applications for persistence between startups. Microsoft Office is a fairly common application suite on Windows-based operating systems within an enterprise network. There are multiple mechanisms that can be used with Office for persistence when an Office-bas... |
Tactics: Persistence |
Platforms Affected: Office 365, Windows |
Detection Strategies: Collect process execution information including process IDs (PID) and parent process IDs (PPID) and look for abnormal chains of activity resulting from Office processes. Non-standard process execution trees may also indicate suspicious or malicious behavior. If winword.exe is the parent process fo... |
More Information: https://attack.mitre.org/techniques/T1137 |
Technique ID: T1137.006 |
Name: Office Application Startup: Add-ins |
Description: Adversaries may abuse Microsoft Office add-ins to obtain persistence on a compromised system. Office add-ins can be used to add functionality to Office programs. There are different types of add-ins that can be used by the various Office products; including Word/Excel add-in Libraries (WLL/XLL), VBA add-in... |
Tactics: Persistence |
Platforms Affected: Office 365, Windows |
Detection Strategies: Monitor and validate the Office trusted locations on the file system and audit the Registry entries relevant for enabling add-ins. Collect process execution information including process IDs (PID) and parent process IDs (PPID) and look for abnormal chains of activity resulting from Office processe... |
More Information: https://attack.mitre.org/techniques/T1137/006 |
Technique ID: T1137.001 |
Name: Office Application Startup: Office Template Macros |
Description: Adversaries may abuse Microsoft Office templates to obtain persistence on a compromised system. Microsoft Office contains templates that are part of common Office applications and are used to customize styles. The base templates within the application are used each time an application starts. Office Visual... |
Tactics: Persistence |
Platforms Affected: Office 365, Windows |
Detection Strategies: Many Office-related persistence mechanisms require changes to the Registry and for binaries, files, or scripts to be written to disk or existing files modified to include malicious scripts. Collect events related to Registry key creation and modification for keys that could be used for Office-base... |
More Information: https://attack.mitre.org/techniques/T1137/001 |
Technique ID: T1137.002 |
Name: Office Application Startup: Office Test |
Description: Adversaries may abuse the Microsoft Office "Office Test" Registry key to obtain persistence on a compromised system. An Office Test Registry location exists that allows a user to specify an arbitrary DLL that will be executed every time an Office application is started. This Registry key is thought to be u... |
Tactics: Persistence |
Platforms Affected: Office 365, Windows |
Detection Strategies: Monitor for the creation of the Office Test Registry key. Many Office-related persistence mechanisms require changes to the Registry and for binaries, files, or scripts to be written to disk or existing files modified to include malicious scripts. Collect events related to Registry key creation an... |
More Information: https://attack.mitre.org/techniques/T1137/002 |
Technique ID: T1137.003 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.