Skip to content

Execution & Shell Command Spawning (TA0002) — Detection Coverage Assessment

Density:
Evaluation DimensionObserved Telemetry / AttributeEpistemic Status
Tactical IdentifierTA0002Canonical Tactic Node
Tactic DesignationExecution & Shell Command SpawningTactical Dimension
Referential FrameworkMITRE ATT&CKTaxonomy Anchor
Coverage Index Score88/100Posture Quantification
Defensive Maturity TierADVANCEDOperational Readiness
Monitored Techniques Ratio12 / 14 techniquesCoverage Completeness
Analytical Confidence96%Multi-Sensor Attestation
Primary Evidence SourcesSRC-MANDIANT-GOOGLE, SRC-CERT-FRMulti-Source Grounding

Monitored Techniques & Primary Detection Engines

Section titled “Monitored Techniques & Primary Detection Engines”

The following core techniques within this tactic are systematically monitored by Hermes detection sensors:

Technique IDTechnique NameCoverage LevelPrimary Detection Engine
T1059.004Unix ShellHIGHSigma (Linux auditd)
T1059.001PowerShellHIGHMicrosoft Sentinel / Sysmon
T1203Exploitation for Client ExecutionHIGHYARA / Sigma

Identified operational gaps where adversary tradecraft can evade current sensor placements:

  1. Blind Spot 1: Fileless memory-only shellcode executions bypassing fork/exec syscall auditing.

Prescriptive Detection Engineering Priorities

Section titled “Prescriptive Detection Engineering Priorities”

Hermes recommends the following prioritized implementation roadmaps to close defense gaps:

  1. Priority Action 1: Configure eBPF runtime process tracking across container worker nodes.