Definition
Credential Eviction techniques disable or remove compromised credentials from a computer network.
Implementation perspective
Credential Eviction should be treated as a technical defensive capability rather than a product checkbox. In practice, teams should define the protected scope, the conditions under which the technique acts, and the observable evidence that demonstrates the intended behavior. For this technique, likely engineering context includes Credential, User Account.
Use the technique to remove adversary access, malicious objects, processes, credentials, or persistence from the defended environment.
Questions to ask
- What evidence or decision threshold authorizes eviction?
- Which sessions, credentials, processes, objects, or dependencies must be removed together?
- How is business impact controlled while preventing the adversary from retaining access?
- What validation confirms that persistence and alternate access paths no longer remain?
Evidence and validation
- Approved containment and eviction procedures
- Case records showing the trigger, authorization, and actions taken
- Credential, session, object, or process invalidation records
- Post-action scans and monitoring showing that access did not recur
Common failure patterns
- Visible symptoms are removed while credentials, persistence, or alternate paths remain.
- Eviction begins before the scope is understood and causes the adversary to change behavior prematurely.
- Recovery and business restoration occur without post-eviction validation.
This implementation perspective is original Bare Metal Cyber educational content. It does not replace the official D3FEND definition or establish that a specific product implements the technique.
Technique hierarchy
Top-level family
Parent techniques
None listed at this level.
Direct child techniques
Artifacts and ontology entities
These relationships describe how D3FEND connects a defensive technique to artifacts or other ontology entities. They describe graph semantics, not a product certification.
Show inferred artifact relationship paths (3)
Offensive-technique relationships
These relationships are generated from D3FEND graph paths and are explicitly experimental. They should be treated as hypotheses for defensive analysis—not as proof that the technique prevents, detects, or removes an offensive behavior.
ATT&CK Enterprise (37)
ATT&CK for ICS (4)
Authoritative sources
- Open this technique on the official D3FEND website ↗
- Open the official ontology resources ↗
- Account monitoring ↗Forescout Technologies · Chunhui Zhan, Siying Yang · PatentReference
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by The MITRE Corporation. MITRE D3FEND™ and the D3FEND logo are trademarks of The MITRE Corporation. MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. Use of D3FEND source material is subject to the official Terms of Use.