Converged Detection Engineering worked example. Use your browser's print dialog to save as PDF.

← Back to course
TLP:GREEN Limited Disclosure · SCORP² community members only
Exported by: verifying identity… Exported at:
Distribution notice. This document is for active SCORP² community members only. Unauthorized distribution will result in revocation of community membership.

Converged Detection Engineering · Viasat KA-SAT Worked Example

Traces the path an adversary takes, and the data and signal sources needed to detect each step

Converged Detection Engineering turns each AN-THR into one or more AN-ATT entries and, for each step on each path, enumerates the data and signal sources needed to observe it. Each attack path enumerates the ordered chain of structural elements the adversary touches from initial foothold to objective, anchored by TOE references; the source inventory aligned to those steps is the second deliverable. Incident Response Preparation uses both outputs to write detection signatures and response playbooks.

Platform anchor.
AST : FW : Firmware : 00 · SurfBeam2 modem firmware (parent chain SVC : DP : Data Plane : 00 → SEG : US : User : 00 → PCE : TE : Terrestrial : 00).
Threat anchor. AN : THR : Threat : 00 · Sandworm (GRU Unit 74455). TOE → AST : FW : Firmware : 00.

ATTEnumerated AN-ATT

One concrete path that an adversary realising the threat would traverse. Drawn from the publicly documented 2022 KA-SAT incident pattern.

FieldValue
IdentifierAN : ATT : Attack Path : 00
DescriptionMass modem firmware-wipe via management-plane abuse: external VPN appliance compromise → KA-SAT management network access → abuse of the legitimate modem management interface → push of AcidRain wiper as a firmware update payload → modem flash and SPI EEPROM overwritten, modems bricked.
Driven byAN : THR : Threat : 00 (Sandworm)
TOE chain (in order of traversal)SEG : GR : Ground : 00 → SVC : CP : Control Plane : 00 → AST : SW : Software : 00 → AST : FW : Firmware : 00
SourceViasat post-incident report, 30 March 2022; CISA AA22-110A; SentinelOne AcidRain technical analysis. Path confirmed by post-incident analysis on the KA-SAT network.
ConfidenceHigh. Path elements match the public reconstruction of the 24 February 2022 KA-SAT outage.

Step-by-step adversary actions on this path

Step 01 · Initial accessCompromise of an external VPN appliance facing the management networkAdversary obtains a foothold on a misconfigured remote-access VPN appliance with reachability to the KA-SAT management network. TOE: SEG : GR : Ground : 00
Step 02 · Lateral movementPivot into the management control planeAdversary uses VPN-derived credentials to reach the KA-SAT management control plane and authenticates with sufficient privilege to issue subscriber-modem commands. TOE: SVC : CP : Control Plane : 00
Step 03 · Action on objective (stage)Stage AcidRain wiper as a firmware-update payloadAdversary stages the AcidRain wiper, packaged so the modem management software accepts it as a legitimate update. TOE: AST : SW : Software : 00
Step 04 · Action on objective (deliver)Push the malicious firmware update across all reachable modemsManagement plane delivers the wiper payload to the SurfBeam2 modems, which flash the payload over their existing firmware and SPI EEPROM contents. TOE: AST : FW : Firmware : 00

Annotation criteria for every AN-ATT element

FieldRequired?What to capture
LAYER / TAG / LABEL / ORDINALRequiredAlways AN : ATT : Attack Path : NN.
DESCRIPTIONRequiredOne short narrative of the path from initial access to objective; no marketing.
DRIVEN BYRequiredThe AN-THR the path realises. Each AN-ATT names exactly one driver; if a path serves several threats, enumerate it once and add the others as cross-references.
TOE chainRequiredOrdered list of every structural element the adversary touches, written as fully-qualified enumerated identifiers.
STEPSRecommendedOne bullet per traversal step, each step naming the structural element it touches. Drives the source inventory below and the detection scope inherited downstream.
SOURCERequiredRed-team report, public incident analysis, government brief, or peer ISAC bulletin. Hypothetical paths must be marked exercise-only and segregated.
CONFIDENCERecommendedHow well the path is corroborated.

SRCData and signal source inventory

For each step on AN : ATT : Attack Path : 00, enumerate the data and signal source a defender needs to observe the step happening. Where no source exists, mark a detection gap. This inventory is a Converged Detection Engineering deliverable and is what Incident Response Preparation reads when authoring signatures.

Path step (TOE)Required data / signal sourceStatus on this platform
SEG : GR : Ground : 00VPN appliance authentication and session telemetry; egress NetFlow from the management subnet.Available; onboarded to SIEM under source id src-vpn-001.
SVC : CP : Control Plane : 00Management-plane authentication and authorization audit log; per-session command audit.Available; onboarded as src-mgmtcp-002.
AST : SW : Software : 00Modem-management software command audit; firmware-update API call log including payload hash and signing manifest reference.Available; onboarded as src-mgmtsw-003.
AST : FW : Firmware : 00Per-modem flash-write event with hash of the image actually written; signed-update verification result.Available; onboarded as src-modemfw-004.

Validation rules. Before declaring the source inventory complete: every AN-ATT step has at least one row; every "Available" status names a real source identifier the SIEM operator can resolve; gaps are recorded explicitly and assigned an owner before launch.

Attack path vs detection signature, kept clear. Converged Detection Engineering produces the map of paths and the source inventory aligned to each step. It does not produce signatures or playbooks. The detection signatures that fire on those sources, and the response playbooks the Security Operations Center runs when they fire, are Incident Response Preparation outputs. Mixing the two is the most common anti-pattern.
Attack path vs threat, kept clear. AN-THR is the actor and intent. AN-ATT is the traversal through the platform. One AN-THR can drive many AN-ATT paths.