2018 · United States · O - Public administration and defence · Data theft via third-party vendor
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft via third-party vendor
Strategy to Execution
Evidence coverage: 2/6 stages, weight 12/60
Decisive stage: entry (clearest evidence) · Alternative: Expertise to Execution
(1) The doctrinal expectation: the DoD holds its personnel data under formal rules even when that data is outsourced - its own statement describes the incident as involving PII of DoD personnel maintained by a single commercial vendor providing travel management services, an arrangement that presupposes contractor-assurance, protection and detection obligations running from the department to the vendor. (2) In practice, intruders breached that vendor and stole travel records with personal and credit card data of roughly 30,000 military and civilian personnel, and the intrusion was only discovered by a departmental cyber team on 4 October 2018, while the attack may have happened months ago and the DoD could not say when it occurred; the department then declined to identify the vendor and acted only after the fact, taking steps to have the contractor cease performance under its contracts. (3) This is a knowing-doing gap on the diagonal: the formal artefacts (contractor assurance for outsourced personnel data, monitoring and reporting expectations) existed, but they did not translate into operational reality - neither at the vendor, whose compromise the arrangement exposed, nor in the department's detection, which missed a likely months-long intrusion. The technical entry vector is not documented and is not load-bearing; the classification rests on the entry stage (the unmet trust boundary made the breach possible) reinforced by the detection stage (dwell of likely months), both pointing to Strategy to Execution. Recovery was not in play (no disruption) and the disclosure conduct (within eight days, with notifications and fraud protection) shows no documented gap, so the response stage does not compete. RM13 (Strategy to Execution lens): DoD's supplier-security requirements, contracts and monitoring for the travel-management vendor holding its personnel data did not translate into controlled third-party operation, since the vendor was breached and the department's first documented action was to halt its contract after the theft (causal role: Enabling). RM34 (Strategy to Execution lens): the department's monitoring and detection requirements were not operated effectively over the outsourced data flow, leaving an intrusion that may have run months undetected until an internal cyber team found it (causal role: Obscuring).
RM13 — Third-party / supply-chain trust boundaryRM34 — Monitoring / detection / alert-handling gapThe dataset's source_url (boston.com, 2018-10-12) returns 404 and has no Wayback snapshot; it was replaced by contemporaneous articles opened in full (Task & Purpose, TechTarget, BleepingComputer, Infosecurity Magazine, NGAUS, all relaying the AP report of 12-10-2018 and the Pentagon statement). The row's phrase granting the attackers access to the Pentagon network overstates the record: the DoD's own statement describes the breach as occurring at a single commercial vendor, and no source documents access to DoD networks; the classification follows the documented vendor-breach account. Attribution was not established (case file: not attributed; media-based attribution) and does not lower confidence. At the time reporting was unclear whether this incident involved the Defense Travel System itself (Task & Purpose noted it was not yet clear); a separate Defense Travel System network breach was disclosed on 8 November 2018 and was not merged into this case. Actor unattributed, entry vector undisclosed - neither is load-bearing for the DV-Type.