Initial Access & Perimeter Exploitation (TA0001) — Detection Coverage Assessment
Defensive Scorecard & Telemetry Metrics
Section titled “Defensive Scorecard & Telemetry Metrics”| Evaluation Dimension | Observed Telemetry / Attribute | Epistemic Status |
|---|---|---|
| Tactical Identifier | TA0001 | Canonical Tactic Node |
| Tactic Designation | Initial Access & Perimeter Exploitation | Tactical Dimension |
| Referential Framework | MITRE ATT&CK | Taxonomy Anchor |
| Coverage Index Score | 92/100 | Posture Quantification |
| Defensive Maturity Tier | ADVANCED | Operational Readiness |
| Monitored Techniques Ratio | 11 / 12 techniques | Coverage Completeness |
| Analytical Confidence | 98% | Multi-Sensor Attestation |
| Primary Evidence Sources | SRC-CISA-KEV, SRC-MANDIANT-GOOGLE | 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 |
|---|---|---|---|
| T1190 | Exploit Public-Facing Application | HIGH | Suricata / Sigma |
| T1133 | External Remote Services | HIGH | Splunk SPL / Suricata |
| T1566 | Phishing | HIGH | Microsoft Defender |
| T1195 | Supply Chain Compromise | MEDIUM | YARA / SBOM Engine |
Architectural Telemetry Blind Spots
Section titled “Architectural Telemetry Blind Spots”Identified operational gaps where adversary tradecraft can evade current sensor placements:
- Blind Spot 1: Zero-day browser memory corruption before vendor signature dissemination.
- Blind Spot 2: Undocumented proprietary VPN protocol extensions operating without public RFC framing.
Prescriptive Detection Engineering Priorities
Section titled “Prescriptive Detection Engineering Priorities”Hermes recommends the following prioritized implementation roadmaps to close defense gaps:
- Priority Action 1: Enforce TLS interception on all inbound reverse proxies.
- Priority Action 2: Deploy perimeter request-smuggling normalization checks.