text stringlengths 0 3.15k |
|---|
Technique ID: T1059 |
Name: Command and Scripting Interpreter |
Description: Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries. These interfaces and languages provide ways of interacting with computer systems and are a common feature across many different platforms. Most systems come with some built-in command-line interface and scripti... |
Tactics: Execution |
Platforms Affected: Azure AD, Google Workspace, IaaS, Linux, Network, Office 365, Windows, macOS |
Detection Strategies: Command-line and scripting activities can be captured through proper logging of process execution with command-line arguments. This information can be useful in gaining additional insight to adversaries' actions through how they use native processes or custom tools. Also monitor for loading of mod... |
More Information: https://attack.mitre.org/techniques/T1059 |
Technique ID: T1059.009 |
Name: Command and Scripting Interpreter: Cloud API |
Description: Adversaries may abuse cloud APIs to execute malicious commands. APIs available in cloud environments provide various functionalities and are a feature-rich method for programmatic access to nearly all aspects of a tenant. These APIs may be utilized through various methods such as command line interpreters ... |
Tactics: Execution |
Platforms Affected: Azure AD, Google Workspace, IaaS, Office 365, SaaS |
Detection Strategies: No detection description provided. |
More Information: https://attack.mitre.org/techniques/T1059/009 |
Technique ID: T1648 |
Name: Serverless Execution |
Description: Adversaries may abuse serverless computing, integration, and automation services to execute arbitrary code in cloud environments. Many cloud providers offer a variety of serverless resources, including compute engines, application integration services, and web servers. Adversaries may abuse these resources... |
Tactics: Execution |
Platforms Affected: IaaS, Office 365, SaaS |
Detection Strategies: No detection description provided. |
More Information: https://attack.mitre.org/techniques/T1648 |
Technique ID: T1204 |
Name: User Execution |
Description: An adversary may rely upon specific actions by a user in order to gain execution. Users may be subjected to social engineering to get them to execute malicious code by, for example, opening a malicious document file or link. These user actions will typically be observed as follow-on behavior from forms of ... |
Tactics: Execution |
Platforms Affected: Containers, IaaS, Linux, Windows, macOS |
Detection Strategies: Monitor the execution of and command-line arguments for applications that may be used by an adversary to gain Initial Access that require user interaction. This includes compression applications, such as those for zip files, that can be used to Deobfuscate/Decode Files or Information in payloads. ... |
More Information: https://attack.mitre.org/techniques/T1204 |
Technique ID: T1204.003 |
Name: User Execution: Malicious Image |
Description: Adversaries may rely on a user running a malicious image to facilitate execution. 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 backdoored. Backdoored images may be uploaded to a publi... |
Tactics: Execution |
Platforms Affected: Containers, IaaS |
Detection Strategies: Monitor the local image registry to make sure malicious images are not added. Track the deployment of new containers, especially from newly built images. Monitor the behavior of containers within the environment to detect anomalous behavior or malicious activity after users deploy from malicious i... |
More Information: https://attack.mitre.org/techniques/T1204/003 |
Technique ID: T1098 |
Name: Account Manipulation |
Description: Adversaries may manipulate accounts to maintain and/or elevate access to victim systems. Account manipulation may consist of any action that preserves or modifies adversary access to a compromised account, such as modifying credentials or permission groups. These actions could also include account activity... |
Tactics: Persistence, Privilege Escalation |
Platforms Affected: Azure AD, Containers, Google Workspace, IaaS, Linux, Network, Office 365, SaaS, Windows, macOS |
Detection Strategies: Collect events that correlate with changes to account objects and/or permissions on systems and the domain, such as event IDs 4738, 4728 and 4670. Monitor for modification of accounts in correlation with other suspicious activity. Changes may occur at unusual times or from unusual systems. Especia... |
More Information: https://attack.mitre.org/techniques/T1098 |
Technique ID: T1098.001 |
Name: Account Manipulation: Additional Cloud Credentials |
Description: Adversaries may add adversary-controlled credentials to a cloud account to maintain persistent access to victim accounts and instances within the environment. For example, adversaries may add credentials for Service Principals and Applications in addition to existing legitimate credentials in Azure AD. The... |
Tactics: Persistence, Privilege Escalation |
Platforms Affected: Azure AD, IaaS, SaaS |
Detection Strategies: Monitor Azure Activity Logs for Service Principal and Application modifications. Monitor for the usage of APIs that create or import SSH keys, particularly by unexpected users or accounts such as the root account. Monitor for use of credentials at unusual times or to unusual systems or services. T... |
More Information: https://attack.mitre.org/techniques/T1098/001 |
Technique ID: T1098.003 |
Name: Account Manipulation: Additional Cloud Roles |
Description: An adversary may add additional roles or permissions to an adversary-controlled cloud account to maintain persistent access to a tenant. For example, adversaries may update IAM policies in cloud-based environments or add a new global administrator in Office 365 environments. With sufficient permissions, a ... |
Tactics: Persistence, Privilege Escalation |
Platforms Affected: Azure AD, Google Workspace, IaaS, Office 365, SaaS |
Detection Strategies: Collect activity logs from IAM services and cloud administrator accounts to identify unusual activity in the 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/T1098/003 |
Technique ID: T1098.002 |
Name: Account Manipulation: Additional Email Delegate Permissions |
Description: Adversaries may grant additional permission levels to maintain persistent access to an adversary-controlled email account. For example, the Add-MailboxPermission PowerShell cmdlet, available in on-premises Exchange and in the cloud-based service Office 365, adds permissions to a mailbox. In Google Workspac... |
Tactics: Persistence, Privilege Escalation |
Platforms Affected: Google Workspace, Office 365, Windows |
Detection Strategies: Monitor for unusual Exchange and Office 365 email account permissions changes that may indicate excessively broad permissions being granted to compromised accounts. Enable the UpdateFolderPermissions action for all logon types. The mailbox audit log will forward folder permission modification even... |
More Information: https://attack.mitre.org/techniques/T1098/002 |
Technique ID: T1098.005 |
Name: Account Manipulation: Device Registration |
Description: Adversaries may register a device to an adversary-controlled account. Devices may be registered in a multifactor authentication (MFA) system, which handles authentication to the network, or in a device management system, which handles device access and compliance. MFA systems, such as Duo or Okta, allow us... |
Tactics: Persistence, Privilege Escalation |
Platforms Affected: Azure AD, SaaS, Windows |
Detection Strategies: No detection description provided. |
More Information: https://attack.mitre.org/techniques/T1098/005 |
Technique ID: T1098.004 |
Name: Account Manipulation: SSH Authorized Keys |
Description: Adversaries may modify the SSH authorizedkeys file in SSH specifies the SSH keys that can be used for logging into the user account for which the file is configured. This file is usually found in the user's home directory under <user-home>/.ssh/authorizedconfig. Adversaries may modify SSH authorizedk... |
Tactics: Persistence, Privilege Escalation |
Platforms Affected: IaaS, Linux, Network, macOS |
Detection Strategies: Use file integrity monitoring to detect changes made to the authorizedkeys file. In cloud environments, monitor instances for modification of metadata and configurations. Monitor for changes to and suspicious processes modifiying /etc/ssh/sshd_config. For network infrastructure devices, collect AA... |
More Information: https://attack.mitre.org/techniques/T1098/004 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.