ATT&CK index / stage 12 of 15

Collection

Gathering what they came for, usually staged before it leaves.

Techniques
4117 parent
With mitigations
2895 listed
Detection strategies
41from ATT&CK analytics

If this is live right now

Stop reading the matrix and work the playbook. The reference below is for afterwards, when you are deciding what to change.

The techniques

open one for mitigations and detection
T1005Data from Local System1 on this site1 mitigationAdversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration. Adversaries may do this using a Command and Scripting Interpreter, such as cmd as well as a Network Device CLI, which have functionality to interact with the file system to gather information.

Platforms: ESXi, Linux, macOS, Network Devices, Windows

What reduces it

  • M1057 Data Loss Prevention. Data loss prevention can restrict access to sensitive data and detect sensitive data that is unencrypted.

How to see it

  • Detection of Local Data Collection Prior to Exfiltration

    • Adversaries collecting local files via PowerShell, WMI, or direct file API calls often include recursive file listings, targeted file reads, and temporary file staging.
    • Adversaries using bash scripts or tools to recursively enumerate user home directories, config files, or SSH keys.
    • Adversary use of bash/zsh or AppleScript to locate files and exfil targets like user keychains or documents.
    • Collection of device configuration via CLI commands (e.g., `show running-config`, `copy flash`, `more`), often followed by TFTP/SCP transfers.

Everything on this site for T1005 →T1005 on attack.mitre.org

T1025Data from Removable Media1 mitigationAdversaries may search connected removable media on computers they have compromised to find files of interest. Sensitive data can be collected from any removable media (optical disk drive, USB memory, etc.) connected to the compromised system prior to Exfiltration. Interactive command shells may be in use, and common functionality within cmd may be used to gather information. Some adversaries may also use Automated Collection on removable media.

Platforms: Linux, macOS, Windows

What reduces it

  • M1057 Data Loss Prevention. Data loss prevention can restrict access to sensitive data and detect sensitive data that is unencrypted.

How to see it

  • Detection of Data Access and Collection from Removable Media

    • Adversary mounts a USB device and begins enumerating, copying, or compressing files using scripting engines, cmd, or remote access tools.
    • Adversary mounts external drive to /media or /mnt then accesses or copies targeted data via shell, cp, or tar.
    • Adversary attaches USB drive and accesses sensitive files using Finder, cp, or bash scripts.

The T1025 page →T1025 on attack.mitre.org

T1039Data from Network Shared DriveAdversaries may search network shares on computers they have compromised to find files of interest. Sensitive data can be collected from remote systems via shared network drives (host shared directory, network file server, etc.) that are accessible from the current system prior to Exfiltration. Interactive command shells may be in use, and common functionality within cmd may be used to gather information.

Platforms: Linux, macOS, Windows

How to see it

  • Detection Strategy for Data from Network Shared Drive

    • Monitoring of file access to network shares (e.g., C$, Admin$) followed by unusual read or copy operations by processes not typically associated with such activity (e.g., PowerShell, certutil).
    • Unusual access or copying of files from mounted network drives (e.g., NFS, CIFS/SMB) by user shells or scripts followed by large data transfer.
    • Detection of file access from mounted SMB shares followed by copy or exfil commands from Terminal or script interpreter processes.

The T1039 page →T1039 on attack.mitre.org

T1056Input Capture4 sub-techniquesAdversaries may use methods of capturing user input to obtain credentials or collect information. During normal system usage, users often provide credentials to various different locations, such as login pages/portals or system dialog boxes. Input capture mechanisms may be transparent to the user (e.g. Credential API Hooking) or rely on deceiving the user into providing input into what they believe to be a genuine service (e.g. Web Portal Capture).

Platforms: Linux, macOS, Network Devices, Windows

How to see it

  • Behavioral Detection of Input Capture Across Platforms

    • Monitors for abnormal process behavior and API calls like SetWindowsHookEx, GetAsyncKeyState, or device input polling commonly used for keystroke logging.
    • Detects use of tools/scripts accessing input devices like /dev/input/* or evdev via suspicious processes lacking GUI context.
    • Monitors for TCC-bypassing or unauthorized access to input services like IOHIDSystem or Quartz Event Services used in keylogging or screen monitoring.
    • Detects web-based credential phishing by analyzing traffic to suspicious URLs that mimic login portals and POST credential content.

Sub-techniques

  • T1056.001 Keylogging. 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 efforts are not effective, and may require an adversary to intercept keystrokes on a system for a substantial period of time before credentials can be successfully captured.
  • T1056.002 GUI Input Capture. Adversaries may mimic common operating system GUI components to prompt users for credentials with a seemingly legitimate prompt. When programs are executed that need additional privileges than are present in the current user context, it is common for the operating system to prompt the user for proper credentials to authorize the elevated privileges for the task (ex: Bypass User Account Control).
  • T1056.003 Web Portal Capture. Adversaries may install code on externally facing portals, such as a VPN login page, to capture and transmit credentials of users who attempt to log into the service. For example, a compromised login page may log provided user credentials before logging the user in to the service.
  • T1056.004 Credential API Hooking. Adversaries may hook into Windows application programming interface (API) functions and Linux system functions to collect user credentials. Malicious hooking mechanisms may capture API or function calls that include parameters that reveal user authentication credentials. Unlike Keylogging, this technique focuses specifically on API functions that include parameters that reveal user credentials.

The T1056 page →T1056 on attack.mitre.org

T1074Data Staged1 on this site2 sub-techniquesAdversaries may stage collected data in a central location or directory prior to Exfiltration. Data may be kept in separate files or combined into one file through techniques such as Archive Collected Data. Interactive command shells may be used, and common functionality within cmd and bash may be used to copy data into a staging location.

Platforms: ESXi, IaaS, Linux, macOS, Windows

How to see it

  • Detection of Data Staging Prior to Exfiltration

    • Detects staging of sensitive files into temporary or public directories, compression with 7zip/WinRAR, or batch copy prior to exfiltration.
    • Detects script or user activity copying files to a central temp or /mnt directory followed by archive/compression utilities.
    • Detects files collected into user temp or shared directories followed by compression with ditto, zip, or custom scripts.
    • Detects virtual disk expansion or file copy operations to cloud buckets or mounted volumes from isolated instances.

Sub-techniques

  • T1074.001 Local Data Staging. Adversaries may stage collected data in a central location or directory on the local system prior to Exfiltration. Data may be kept in separate files or combined into one file through techniques such as Archive Collected Data. Interactive command shells may be used, and common functionality within cmd and bash may be used to copy data into a staging location.
  • T1074.002 Remote Data Staging. Adversaries may stage data collected from multiple systems in a central location or directory on one system prior to Exfiltration. Data may be kept in separate files or combined into one file through techniques such as Archive Collected Data. Interactive command shells may be used, and common functionality within cmd and bash may be used to copy data into a staging location.

Everything on this site for T1074 →T1074 on attack.mitre.org

T1113Screen CaptureAdversaries 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 calls, such as `CopyFromScreen`, `xwd`, or `screencapture`.

Platforms: Linux, macOS, Windows

How to see it

  • Detect Screen Capture via Commands and API Calls

    • Unusual use of screen capture APIs (e.g., CopyFromScreen) or command-line tools to write image files to disk.
    • Invocation of built-in commands like screencapture or use of undocumented APIs from suspicious parent processes.
    • Use of tools like xwd or import to generate screenshots, especially under non-GUI parent processes.

The T1113 page →T1113 on attack.mitre.org

T1114Email Collection9 on this site4 mitigations3 sub-techniquesAdversaries may target user email to collect sensitive information. Emails may contain sensitive data, including trade secrets or personal information, that can prove valuable to adversaries. Emails may also contain details of ongoing incident response operations, which may allow adversaries to adjust their techniques in order to maintain persistence or evade defenses. Adversaries can collect or forward email from mail servers or clients.

Platforms: Windows, macOS, Linux, Office Suite

What reduces it

  • M1060 Out-of-Band Communications Channel. Use secure out-of-band authentication methods to verify the authenticity of critical actions initiated via email, such as password resets, financial transactions, or access requests. For highly sensitive information, utilize out-of-band communication channels instead of relying solely on email to prevent adversaries from collecting data through compromised email accounts.
  • M1032 Multi-factor Authentication. Use of multi-factor authentication for public-facing webmail servers is a recommended best practice to minimize the usefulness of usernames and passwords to adversaries.
  • M1047 Audit. Enterprise email solutions have monitoring mechanisms that may include the ability to audit auto-forwarding rules on a regular basis. In an Exchange environment, Administrators can use Get-InboxRule to discover and remove potentially malicious auto-forwarding rules.
  • M1041 Encrypt Sensitive Information. Use of encryption provides an added layer of security to sensitive information sent over email. Encryption using public key cryptography requires the adversary to obtain the private certificate along with an encryption key to decrypt messages.

How to see it

  • Email Collection via Local Email Access and Auto-Forwarding Behavior

    • Correlates creation of email forwarding rules or header anomalies (e.g., X-MS-Exchange-Organization-AutoForwarded) with suspicious process execution, file access of.pst/.ost files, and network connections to external SMTP servers.
    • Detects file access to mbox/maildir files in conjunction with curl/wget/postfix execution, or anomalous shell scripts harvesting user mail directories.
    • Monitors Mail.app database or maildir file access, automation via AppleScript, and abnormal mail rule creation using scripting or UI automation frameworks.
    • Correlates unusual auto-forwarding rule creation via Exchange Web Services or Outlook rules engine, presence of X-MS-Exchange-Organization-AutoForwarded headers, and logon session anomalies from abnormal IPs.

Sub-techniques

  • T1114.001 Local Email Collection. Adversaries may target user email on local systems to collect sensitive information. Files containing email data can be acquired from a user’s local system, such as Outlook storage or cache files. Outlook stores data locally in offline data files with an extension of.ost. Outlook 2010 and later supports.ost file sizes up to 50GB, while earlier versions of Outlook support up to 20GB.
  • T1114.002 Remote Email Collection · 2 on this site. Adversaries may target an Exchange server, Office 365, or Google Workspace to collect sensitive information. Adversaries may leverage a user's credentials and interact directly with the Exchange server to acquire information from within a network. Adversaries may also access externally facing Exchange services, Office 365, or Google Workspace to access email using credentials or access tokens.
  • T1114.003 Email Forwarding Rule · 6 on this site. Adversaries may setup email forwarding rules to collect sensitive information. Adversaries may abuse email forwarding rules to monitor the activities of a victim, steal information, and further gain intelligence on the victim or the victim’s organization to use as part of further exploits or operations.

Everything on this site for T1114 →T1114 on attack.mitre.org

T1115Clipboard DataAdversaries may collect data stored in the clipboard from users copying information within or between applications. For example, on Windows adversaries can access clipboard data by using `clip.exe` or `Get-Clipboard`. Additionally, adversaries may monitor then replace users’ clipboard with their data (e.g., Transmitted Data Manipulation). macOS and Linux also have commands, such as `pbpaste`, to grab clipboard contents.

Platforms: Linux, macOS, Windows

How to see it

  • Clipboard Data Access with Anomalous Context

    • Detection of clipboard access via OS utilities (e.g., clip.exe, Get-Clipboard) by non-interactive or abnormal parent processes, potentially chained with staging or exfiltration commands.
    • Detection of pbpaste/pbcopy clipboard access by processes without terminal sessions or linked to launch agents, potentially staged for collection.
    • Detection of xclip or xsel access to clipboard buffers outside of user terminal context, especially when chained to staging (gzip, base64) or network exfiltration (curl, scp).

The T1115 page →T1115 on attack.mitre.org

T1119Automated Collection2 mitigationsOnce established within a system or network, an adversary may use automated techniques for collecting internal data. Methods for performing this technique could include use of a Command and Scripting Interpreter to search for and copy information fitting set criteria such as file type, location, or name at specific time intervals.

Platforms: IaaS, Linux, macOS, Office Suite, SaaS, Windows

What reduces it

  • M1029 Remote Data Storage. Encryption and off-system storage of sensitive information may be one way to mitigate collection of files, but may not stop an adversary from acquiring the information if an intrusion persists over a long period of time and the adversary is able to discover and access the data through other means.
  • M1041 Encrypt Sensitive Information. Encryption and off-system storage of sensitive information may be one way to mitigate collection of files, but may not stop an adversary from acquiring the information if an intrusion persists over a long period of time and the adversary is able to discover and access the data through other means.

How to see it

  • Automated File and API Collection Detection Across Platforms

    • Automated execution of native utilities and scripts to discover, enumerate, and exfiltrate files and clipboard content. Focus is on detecting repeated file access, scripting engine use, and use of command-line utilities commonly leveraged by collection scripts.
    • Repeated or automated access to user document directories or clipboard using shell scripts or utilities like xclip/pbpaste. Detectable via auditd syscall logs or osquery file events.
    • Use of pbpaste, AppleScript, or third-party automation frameworks (e.g., Automator) to collect clipboard or file content in bursts. Observable via unified logs.
    • Suspicious sign-ins to Graph API or sensitive resources using non-browser scripting agents (e.g., Python, PowerShell), often for programmatic access to mailbox or OneDrive content.

The T1119 page →T1119 on attack.mitre.org

T1123Audio CaptureAn adversary can leverage a computer's peripheral devices (e.g., microphones and webcams) or applications (e.g., voice and video call services) to capture audio recordings for the purpose of listening into sensitive conversations to gather information. Malware or scripts may be used to interact with the devices through an available API provided by the operating system or an application to capture audio.

Platforms: Linux, macOS, Windows

How to see it

  • Behavioral Detection Strategy for T1123 Audio Capture Across Windows, Linux, macOS

    • Unusual or unauthorized processes accessing microphone APIs (e.g., winmm.dll, avrt.dll) followed by audio file writes to user-accessible or temp directories.
    • Processes accessing ALSA/PulseAudio devices or executing audio capture binaries like 'arecord', followed by file creation or suspicious child process spawning.
    • Processes invoking AVFoundation or CoreAudio frameworks, accessing input devices via TCC logs or Unified Logs, followed by writing AIFF/WAV/MP3 files to disk.

The T1123 page →T1123 on attack.mitre.org

T1125Video CaptureAn adversary can leverage a computer's peripheral devices (e.g., integrated cameras or webcams) or applications (e.g., video call services) to capture video recordings for the purpose of gathering information. Images may also be captured from devices or applications, potentially in specified intervals, in lieu of video files.

Platforms: Linux, macOS, Windows

How to see it

  • Behavior-chain, platform-aware detection strategy for T1125 Video Capture

    • A non-standard process (or script-hosted process) loads camera/video-capture libraries (e.g., avicap32.dll, mf.dll, ksproxy.ax), opens the Camera Frame Server/device, writes video/image artifacts (e.g.,.mp4/.avi/.yuv) to unusual locations, and optionally initiates outbound transfer shortly after.
    • A process opens/reads /dev/video* (V4L2), performs ioctl/read loops, writes large/continuous video artifacts to disk, and/or quickly establishes outbound connections for exfiltration.
    • A non-whitelisted process receives TCC camera entitlement (kTCCServiceCamera), opens AppleCamera/AVFoundation device handles, writes.mov/.mp4 artifacts to unusual locations, and/or beacons/exfiltrates soon after.

The T1125 page →T1125 on attack.mitre.org

T1185Browser Session Hijacking2 mitigationsAdversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques. A specific example is when an adversary injects software into a browser that allows them to inherit cookies, HTTP sessions, and SSL client certificates of a user then use the browser as a way to pivot into an authenticated...

Platforms: Windows

What reduces it

  • M1017 User Training. Close all browser sessions regularly and when they are no longer needed.
  • M1018 User Account Management. Since browser pivoting requires a high integrity process to launch from, restricting user permissions and addressing Privilege Escalation and Bypass User Account Control opportunities can limit the exposure to this technique.

How to see it

  • Detect browser session hijacking via privilege, handle access, and remote thread into browsers

    • Adversary gains high integrity or special privileges (e.g., SeDebugPrivilege), locates a running browser process, opens it with write/inject rights, and modifies it (e.g., CreateRemoteThread / DLL load) to inherit cookies/tokens or establish a browser pivot.

The T1185 page →T1185 on attack.mitre.org

T1213Data from Information Repositories2 on this site6 mitigations6 sub-techniquesAdversaries may leverage information repositories to mine valuable information. Information repositories are tools that allow for storage of information, typically to facilitate collaboration or information sharing between users, and can store a wide variety of data that may aid adversaries in further objectives, such as Credential Access, Lateral Movement, or Defense Evasion, or direct access to the target information.

Platforms: Linux, Windows, macOS, SaaS, IaaS, Office Suite

What reduces it

  • M1017 User Training. Develop and publish policies that define acceptable information to be stored in repositories.
  • M1060 Out-of-Band Communications Channel. Create plans for leveraging a secure out-of-band communications channel, rather than existing in-network chat applications, in case of a security incident.
  • M1018 User Account Management. Enforce the principle of least-privilege. Consider implementing access control mechanisms that include both authentication and authorization.
  • M1032 Multi-factor Authentication. Use two or more pieces of evidence to authenticate to a system; such as username and password in addition to a token from a physical smart card or token generator.
  • M1054 Software Configuration. Consider implementing data retention policies to automate periodically archiving and/or deleting data that is no longer needed.
  • M1047 Audit. Consider periodic review of accounts and privileges for critical and sensitive repositories. Ensure that repositories such as cloud-hosted databases are not unintentionally exposed to the public, and that security groups assigned to them permit only necessary and authorized hosts.

How to see it

  • Abuse of Information Repositories for Data Collection

    • Programmatic or excessive access to file shares, SharePoint, or database repositories by users not typically interacting with them. This includes abnormal access by privileged accounts, enumeration of large numbers of files, or downloads of sensitive content in bursts.
    • Command-line tools (e.g., curl, rsync, wget, or custom Python scripts) used to scrape documentation systems or internal REST APIs. Unusual access patterns to knowledge base folders or shared team drives.
    • Abuse of SaaS platforms such as Confluence, GitHub, SharePoint Online, or Slack to access excessive internal documentation or export source code/data. Includes use of tokens or browser automation from unapproved IPs.
    • Access of mounted cloud shares or document repositories via browser, terminal, or Finder by users not typically interacting with those resources. Includes script-based enumeration or mass download.

Sub-techniques

  • T1213.001 Confluence. Adversaries may leverage Confluence repositories to mine valuable information. Often found in development environments alongside Atlassian JIRA, Confluence is generally used to store development-related documentation, however, in general may contain more diverse categories of useful information, such as: * Policies, procedures, and standards * Physical / logical network diagrams * System architecture diagrams * Technical system documentation * Testing /...
  • T1213.002 Sharepoint. Adversaries may leverage the SharePoint repository as a source to mine valuable information. SharePoint will often contain useful information for an adversary to learn about the structure and functionality of the internal network and systems.
  • T1213.003 Code Repositories. Adversaries may leverage code repositories to collect valuable information. Code repositories are tools/services that store source code and automate software builds. They may be hosted internally or privately on third party sites such as Github, GitLab, SourceForge, and BitBucket. Users typically interact with code repositories through a web application or command-line utilities such as git.
  • T1213.004 Customer Relationship Management Software. Adversaries may leverage Customer Relationship Management (CRM) software to mine valuable information. CRM software is used to assist organizations in tracking and managing customer interactions, as well as storing customer data. Once adversaries gain access to a victim organization, they may mine CRM software for customer data.
  • T1213.005 Messaging Applications. Adversaries may leverage chat and messaging applications, such as Microsoft Teams, Google Chat, and Slack, to mine valuable information. The following is a brief list of example information that may hold potential value to an adversary and may also be found on messaging applications: * Testing / development credentials (i.e., Chat Messages) * Source code snippets * Links to network shares and other internal resources * Proprietary data * Discussions about...
  • T1213.006 Databases. Adversaries may leverage databases to mine valuable information. These databases may be hosted on-premises or in the cloud (both in platform-as-a-service and software-as-a-service environments). Examples of databases from which information may be collected include MySQL, PostgreSQL, MongoDB, Amazon Relational Database Service, Azure SQL Database, Google Firebase, and Snowflake.

Everything on this site for T1213 →T1213 on attack.mitre.org

T1530Data from Cloud Storage2 on this site6 mitigationsAdversaries may access data from cloud storage. Many IaaS providers offer solutions for online data object storage such as Amazon S3, Azure Storage, and Google Cloud Storage. Similarly, SaaS enterprise platforms such as Office 365 and Google Workspace provide cloud-based document storage to users through services such as OneDrive and Google Drive, while SaaS application providers such as Slack, Confluence, Salesforce, and Dropbox may provide cloud storage...

Platforms: IaaS, Office Suite, SaaS

What reduces it

  • M1037 Filter Network Traffic. Cloud service providers support IP-based restrictions when accessing cloud resources. Consider using IP allowlisting along with user account management to ensure that data access is restricted not only to valid users but only from expected IP ranges to mitigate the use of stolen credentials to access data.
  • M1018 User Account Management. Configure user permissions groups and roles for access to cloud storage. Implement strict Identity and Access Management (IAM) controls to prevent access to storage solutions except for the applications, users, and services that require access.
  • M1022 Restrict File and Directory Permissions. Use access control lists on storage systems and objects.
  • M1032 Multi-factor Authentication. Consider using multi-factor authentication to restrict access to resources and cloud storage APIs.
  • M1047 Audit. Frequently check permissions on cloud storage to ensure proper permissions are set to deny open or unprivileged access to resources.
  • M1041 Encrypt Sensitive Information. Encrypt data stored at rest in cloud storage. Managed encryption keys can be rotated by most providers. At a minimum, ensure an incident response plan to storage breach includes rotating the keys and test for impact on client applications.

How to see it

  • Multi-Platform Cloud Storage Exfiltration Behavior Chain

    • Spike in object access from new IAM user or role followed by data exfiltration to external IPs
    • OAuth token granted to external app followed by download of high-volume files in OneDrive/Google Drive
    • Internal user account accesses shared links outside org followed by mass file download

Everything on this site for T1530 →T1530 on attack.mitre.org

T1557Adversary-in-the-Middle4 on this site6 mitigations4 sub-techniquesAdversaries 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, Transmitted Data Manipulation, or replay attacks (Exploitation for Credential Access). By abusing features of common networking protocols that can determine the flow of network traffic (e.g.

Platforms: Linux, macOS, Network Devices, Windows

What reduces it

  • M1031 Network Intrusion Prevention. Network intrusion detection and prevention systems that can identify traffic patterns indicative of AiTM activity can be used to mitigate activity at the network level.
  • M1035 Limit Access to Resource Over Network. Limit access to network infrastructure and resources that can be used to reshape traffic or otherwise produce AiTM conditions.
  • M1037 Filter Network Traffic. Use network appliances and host-based security software to block network traffic that is not necessary within the environment, such as legacy protocols that may be leveraged for AiTM conditions.
  • M1017 User Training. Train users to be suspicious about certificate errors. Adversaries may use their own certificates in an attempt to intercept HTTPS traffic. Certificate errors may arise when the application’s certificate does not match the one expected by the host.
  • M1030 Network Segmentation. Network segmentation can be used to isolate infrastructure components that do not require broad network access. This may mitigate, or at least alleviate, the scope of AiTM activity.
  • M1042 Disable or Remove Feature or Program. Disable legacy network protocols that may be used to intercept network traffic if applicable, especially those that are not needed within an environment.

How to see it

  • Detect Adversary-in-the-Middle via Network and Configuration Anomalies

    • Detects suspicious DNS/ARP poisoning attempts, unauthorized modifications to registry/network configuration, or abnormal TLS downgrade activity. Correlates changes in system configuration with subsequent unusual network flows or authentication events.
    • Detects unauthorized edits to /etc/hosts, /etc/resolv.conf, or suspicious ARP broadcasts. Correlates file modifications with subsequent unexpected network sessions or service creation.
    • Detects unauthorized edits to system configuration profiles, unexpected certificate trust changes, or abnormal ARP/DNS patterns indicative of interception.
    • Detects unauthorized firmware or configuration changes enabling adversary-in-the-middle positioning (e.g., route injection, DNS spoofing, SSL downgrade). Behavioral analytics focus on sudden changes to routing tables or image file integrity failures.

Sub-techniques

  • T1557.001 Name Resolution Poisoning and SMB Relay. By responding to LLMNR/NBT-NS/mDNS network traffic, adversaries may spoof an authoritative source for name resolution to force communication with an adversary controlled system. This activity may be used to collect or relay authentication materials. Link-Local Multicast Name Resolution (LLMNR) and NetBIOS Name Service (NBT-NS) are Microsoft Windows components that serve as alternate methods of host identification.
  • T1557.002 ARP Cache Poisoning. Adversaries may poison Address Resolution Protocol (ARP) caches to position themselves between the communication of two or more networked devices. This activity may be used to enable follow-on behaviors such as Network Sniffing or Transmitted Data Manipulation. The ARP protocol is used to resolve IPv4 addresses to link layer addresses, such as a media access control (MAC) address.
  • T1557.003 DHCP Spoofing. Adversaries may redirect network traffic to adversary-owned systems by spoofing Dynamic Host Configuration Protocol (DHCP) traffic and acting as a malicious DHCP server on the victim network. By achieving the adversary-in-the-middle (AiTM) position, adversaries may collect network communications, including passed credentials, especially those sent over insecure, unencrypted protocols.
  • T1557.004 Evil Twin. Adversaries may host seemingly genuine Wi-Fi access points to deceive users into connecting to malicious networks as a way of supporting follow-on behaviors such as Network Sniffing, Transmitted Data Manipulation, or Input Capture. By using a Service Set Identifier (SSID) of a legitimate Wi-Fi network, fraudulent Wi-Fi access points may trick devices or users into connecting to malicious Wi-Fi networks.

Everything on this site for T1557 →T1557 on attack.mitre.org

T1560Archive Collected Data2 on this site1 mitigation3 sub-techniquesAn adversary may compress and/or encrypt data that is collected prior to exfiltration. Compressing the data can help to obfuscate the collected data and minimize the amount of data sent over the network. Encryption can be used to hide information that is being exfiltrated from detection or make exfiltration less conspicuous upon inspection by a defender.

Platforms: Linux, macOS, Windows

What reduces it

  • M1047 Audit. System scans can be performed to identify unauthorized archival utilities.

How to see it

  • Detect Archiving and Encryption of Collected Data (T1560)

    • Detects adversarial archiving of files prior to exfiltration by correlating execution of compression/encryption utilities (e.g., makecab.exe, rar.exe, 7z.exe, powershell Compress-Archive) with subsequent creation of large compressed or encrypted files.
    • Detects adversarial archiving activity through invocation of utilities like tar, gzip, bzip2, or openssl used in non-administrative or unusual contexts. Correlates command execution patterns with file creation of compressed/encrypted outputs in staging directories (e.g., /tmp, /var/tmp).
    • Detects use of macOS-native archiving or encryption tools (zip, ditto, hdiutil) for staging collected data. Identifies unexpected invocation of archive utilities by Office apps, browsers, or background daemons. Correlates file creation of.zip/.dmg containers with process lineage anomalies.

Sub-techniques

  • T1560.001 Archive via Utility · 2 on this site. 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 exfiltration. Some third party utilities may be preinstalled, such as `tar` on Linux and macOS or `zip` on Windows systems.
  • T1560.002 Archive via Library. An adversary may compress or encrypt data that is collected prior to exfiltration using 3rd party libraries. Many libraries exist that can archive data, including Python rarfile, libzip, and zlib. Most libraries include functionality to encrypt and/or compress data. Some archival libraries are preinstalled on systems, such as bzip2 on macOS and Linux, and zip on Windows. Note that the libraries are different from the utilities.
  • T1560.003 Archive via Custom Method. An adversary may compress or encrypt data that is collected prior to exfiltration using a custom method. Adversaries may choose to use custom archival methods, such as encryption with XOR or stream ciphers implemented with no external library or utility references. Custom implementations of well-known compression algorithms have also been used.

Everything on this site for T1560 →T1560 on attack.mitre.org

T1602Data from Configuration Repository6 mitigations2 sub-techniquesAdversaries may collect data related to managed devices from configuration repositories. Configuration repositories are used by management systems in order to configure, manage, and control data on remote systems. Configuration repositories may also facilitate remote access and administration of devices. Adversaries may target these repositories in order to collect large quantities of sensitive system administration data.

Platforms: Network Devices

What reduces it

  • M1031 Network Intrusion Prevention. Configure intrusion prevention devices to detect SNMP queries and commands from unauthorized sources.
  • M1037 Filter Network Traffic. Apply extended ACLs to block unauthorized protocols outside the trusted network.
  • M1030 Network Segmentation. Segregate SNMP traffic on a separate management network.
  • M1054 Software Configuration. Allowlist MIB objects and implement SNMP views.
  • M1051 Update Software. Keep system images and software updated and migrate to SNMPv3.
  • M1041 Encrypt Sensitive Information. Configure SNMPv3 to use the highest level of security (authPriv) available.

How to see it

  • Detection Strategy for Data from Configuration Repository on Network Devices

    • Defenders may observe adversary attempts to extract configuration data from management repositories by monitoring for anomalous SNMP queries, API calls, or protocol requests (e.g., NETCONF, RESTCONF) that enumerate system configuration.

Sub-techniques

  • T1602.001 SNMP (MIB Dump). Adversaries may target the Management Information Base (MIB) to collect and/or mine valuable information in a network managed using Simple Network Management Protocol (SNMP). The MIB is a configuration repository that stores variable information accessible via SNMP in the form of object identifiers (OID).
  • T1602.002 Network Device Configuration Dump. Adversaries may access network configuration files to collect sensitive data about the device and the network. The network configuration is a file containing parameters that determine the operation of the device. The device typically stores an in-memory copy of the configuration while operating, and a separate configuration on non-volatile storage to load after device reset.

The T1602 page →T1602 on attack.mitre.org

Technique descriptions, mitigations and detection analytics on this page are reproduced from MITRE ATT&CK, ATT&CK version 19.2, retrieved 2026-09-12. ATT&CK is a registered trademark of The MITRE Corporation and is used here under its terms of use. The playbooks, and the sentence describing what this stage means for a responder, are ours.