What It Does
Hunt the build pipeline specifically, because poisoning it envelops everything downstream.
Observable indicator. Pipeline integrity is verified rather than assumed after contact.
Where It Sits
A technique is chosen from inside a form and emplaced on one layer. Both are the catalog’s own declarations; the position is counted in catalog order.
- Form of maneuverM7 CounterattackSeize the initiative and evict before the adversary reaches the objective.
- Terrain layerT4 Applications and WorkloadsThe urban terrain. Key terrain: The public service portal, the case processing system, public APIs.
- Position in the form6 of 17M7 carries 17 cataloged techniques; this is the 6th in catalog order.
Phases It Is Employed In
Employed in one phase of the campaign. A phase named here means at least this technique is live in it — not that the form it belongs to is the main effort.
- Phase IIIDominateHunt, contain, evict.
Controls That Assess It
The controls the catalog names against this technique. They are what an assessor would test to establish that it is emplaced and working — the indicator above is what shows it is working, which is a different question.
- KT-1 Decisive Point IdentificationKey Terrain and Decisive Points — To concentrate defensive effort on the small number of elements whose loss is decisive, so that priority is a stated judgment rather than an emergent property of the asset register.
- SM-6 Maneuver Effectiveness ValidationScheme of Maneuver — To replace assumed effectiveness with demonstrated effectiveness, so the coverage figure reflects what controls do rather than what was assumed of them.
In MITRE D3FEND
What this technique is called in MITRE’s countermeasure ontology. The join runs technique-to-technique: D3FEND catalogs countermeasures, and the thing with a countermeasure’s shape here is the technique, not the control.
- D3-CIA Container Image AnalysisModel tactic
- D3-SBV Service Binary VerificationDetect tactic
- D3-SEA Script Execution AnalysisDetect tactic
- D3-CNR Content RebuildIsolate tactic
- D3-CNS Content SubstitutionIsolate tactic
That a technique reaches a D3FEND countermeasure says the two describe the same defensive act. It does not say the countermeasure is deployed, configured, or working — that is an assessment finding about your estate, not a property of the framework.
Related Techniques
The catalog declares no relation for this entry, and no other entry names it — the inverse is derived here, so an incoming edge would show up even though this one never declared it. The techniques below share its assessment surface, which is the nearest adjacency the data supports.
Assessed Alongside
Not a declared relation: these are the techniques whose assessing controls overlap this one’s, ranked by how much of the two assessment surfaces coincide. Showing 6 of 13 that share at least one control.
- 1 shared controlM10.01 Indicator-to-Detection ConversionM10 Exploitation & Pursuit · TX Cross-Cutting
- SM-6
- 1 shared controlM2.03 Crown-Jewel EnclaveM2 Defense in Depth · T5 Data
- KT-1
- 1 shared controlM4.12 Denied-Path Register EnforcementM4 Obstacle / Canalization · T3 Networks
- SM-6
- 1 shared controlM7.09 Detection Engineering from HuntM7 Counterattack · TX Cross-Cutting
- SM-6
- 1 shared controlM7.10 Purple-Team ValidationM7 Counterattack · TX Cross-Cutting
- SM-6
- 1 shared controlM8.12 Degradation RehearsalM8 Isolation / Retrograde · TX Cross-Cutting
- SM-6