Execution & Shell Command Spawning (TA0002) — Detection Coverage Assessment
Defensive Scorecard & Telemetry Metrics
Section titled “Defensive Scorecard & Telemetry Metrics”| Evaluation Dimension | Observed Telemetry / Attribute | Epistemic Status |
|---|---|---|
| Tactical Identifier | TA0002 | Canonical Tactic Node |
| Tactic Designation | Execution & Shell Command Spawning | Tactical Dimension |
| Referential Framework | MITRE ATT&CK | Taxonomy Anchor |
| Coverage Index Score | 88/100 | Posture Quantification |
| Defensive Maturity Tier | ADVANCED | Operational Readiness |
| Monitored Techniques Ratio | 12 / 14 techniques | Coverage Completeness |
| Analytical Confidence | 96% | Multi-Sensor Attestation |
| Primary Evidence Sources | SRC-MANDIANT-GOOGLE, SRC-CERT-FR | Multi-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 ID | Technique Name | Coverage Level | Primary Detection Engine |
|---|---|---|---|
T1059.004 | Unix Shell | HIGH | Sigma (Linux auditd) |
T1059.001 | PowerShell | HIGH | Microsoft Sentinel / Sysmon |
T1203 | Exploitation for Client Execution | HIGH | YARA / Sigma |
Architectural Telemetry Blind Spots
Section titled “Architectural Telemetry Blind Spots”Identified operational gaps where adversary tradecraft can evade current sensor placements:
- 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:
- Priority Action 1: Configure eBPF runtime process tracking across container worker nodes.