Techniques › T1480
T1480 Execution Guardrails
stealth — ESXi, Linux, macOS, Windows · attack.mitre.org · JSON
1
MITRE detection strategy
4
analytics
0
Sigma rules tagged attack.t1480
0
KEV CVEs mapped here
<p>Adversaries may use execution guardrails to constrain execution or actions based on adversary supplied and environment specific conditions that are expected to be present on the target. Guardrails ensure that a payload only executes against an intended target and reduces collateral damage from an adversary’s campaign. Values an adversary can provide about a target system or environment to use as guardrails may include specific network share names, attached physical devices, files, joined Active Directory (AD) domains, and local/external IP addresses.</p><p>Guardrails can be used to prevent exposure of capabilities in environments that are not intended to be compromised or operated within. This use of guardrails is distinct from typical Virtualization/Sandbox Evasion. While use of Virtualization/Sandbox Evasion may involve checking for known sandbox values and continuing with execution only if there is no match, the use of guardrails will involve checking for an expected target-specific value and only continuing with execution if there is such a match.</p><p>Adversaries may identify and block certain user-agents to evade defenses and narrow the scope of their attack to victims and platforms on which it will be most effective. A user-agent self-identifies data such as a user's software application, operating system, vendor, and version. Adversaries may check user-agents for operating system identification and then only serve malware for the exploitable software while ignoring all other operating systems.</p>
KEV CVEs mapped to this technique · CTID Mappings Explorer
None. No KEV entry in the public mapping names this technique. Given that 74.7% of KEV has no mapping at all, this says more about the mapping than about the technique.
Detection strategy · ATT&CK Enterprise v19.2
- DET0562 Multi-Platform Execution Guardrails Environmental Validation Detection Strategy v1.0
AN1551 WindowsWindows environmental validation behavioral chain: (1) Rapid system discovery reconnaissance through WMI queries, registry enumeration, and network share discovery, (2) Environment-specific artifact collection (hostname, domain, IP addresses, installed software, hardware identifiers), (3) Cryptographic operations or conditional logic based on collected environmental values, (4) Selective payload execution contingent on environmental validation results, (5) Temporal correlation between discovery activities and subsequent execution or network communicationTunable:
DiscoveryTimeWindowDiscoveryActivityThresholdCryptographicLibraryWhitelistWMIQueryComplexityThresholdEnvironmentalArtifactListExecutionDelayBaselineAN1552 LinuxLinux environmental validation behavioral chain: (1) Intensive system enumeration through command execution (uname, hostname, ifconfig, lsblk, mount), (2) File system reconnaissance targeting specific paths, network configurations, and installed packages, (3) Process and user enumeration to validate target environment characteristics, (4) Conditional script execution or binary activation based on environmental criteria, (5) Network connectivity validation and external IP address resolution for geolocation verificationauditd:PROCTITLEcommand-line execution patterns for system discovery utilities (uname, hostname, ifconfig, netstat, lsof, ps, mount)→ DC0064 Command Executionlinux:syslogauthentication and authorization events during environmental validation phase→ DC0002 User Account AuthenticationTunable:SystemDiscoveryCommandListReconnaissanceBurstThresholdEnvironmentalCheckPatternsNetworkDiscoveryBaselineConditionalExecutionIndicatorsAN1553 macOSmacOS environmental validation behavioral chain: (1) System profiling through system_profiler, sysctl, and hardware discovery commands, (2) Network interface and configuration enumeration for geolocation and network environment validation, (3) Application installation and version discovery for software environment fingerprinting, (4) Security feature detection (SIP, Gatekeeper, XProtect status), (5) Conditional payload execution based on macOS-specific environmental criteria and System Integrity Protection bypass validationmacos:unifiedlogprocess execution events for system discovery utilities (system_profiler, sysctl, networksetup, ioreg) with parameter analysis→ DC0032 Process Creationfs:fileeventsFile system access events with kFSEventStreamEventFlagItemRemoved, kFSEventStreamEventFlagItemRenamed flags for environmental artifact collection (/System/Library, /usr/sbin, plist files)→ DC0055 File AccessTunable:MacOSDiscoveryToolsSecurityFeatureEnumerationHardwareFingerprintBaselineSIPBypassIndicatorsAN1554 ESXiESXi hypervisor environmental validation behavioral chain: (1) Virtual machine inventory and configuration enumeration through vim-cmd and esxcli commands, (2) Host hardware and network configuration discovery for hypervisor environment validation, (3) Datastore and storage configuration reconnaissance, (4) vCenter connectivity and cluster membership validation, (5) Selective malware deployment based on virtualization infrastructure characteristics and target VM validationesxi:shellshell command execution for system discovery (vim-cmd, esxcli, vmware-cmd) targeting VM inventory and host configuration→ DC0064 Command Executionesxi:hostdhost daemon events related to VM operations and configuration queries during reconnaissance→ DC0032 Process CreationTunable:ESXiDiscoveryCommandsVMInventoryEnumerationThresholdHypervisorEnvironmentBaselineDatastoreAccessPatterns
Sigma rules · SigmaHQ da9bb07d64, tag attack.t1480
No Sigma rule carries this tag. MITRE publishes a detection strategy above, so the behaviour is specified; what is missing is public detection content.