Definition
A Credential created for the purpose of deceiving an adversary.
How it works
A detection analytic is developed to determine when a user uses decoy credentials. Subsequent actions by that user may be monitored or controlled by the defender.
A credential may be:
- Domain username and password
- Local system username and password
Considerations
- Decoy credentials should be integrated with a larger decoy environment to ensure that when decoy credentials are compromised, the credentials are used to interact with a decoy asset that is being monitored.
- Continuous maintenance and updates are needed to ensure the legitimacy of the larger decoy environment and specifically the assets that utilize the decoy credentials.
Implementation perspective
Decoy User Credential 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.
Use the technique to present controlled information, services, or artifacts that shape adversary behavior and create observable interaction.
Questions to ask
- What behavior is the deceptive element intended to attract, delay, reveal, or redirect?
- How is the deceptive element made plausible without creating unacceptable operational risk?
- Which interactions are monitored, and who investigates them?
- How is the deceptive environment isolated from production systems and sensitive data?
Evidence and validation
- Design records describing the deception objective and placement
- Isolation and containment test results
- Monitoring and alert-routing configuration
- Interaction records and documented investigative outcomes
Common failure patterns
- The deceptive element is obvious, stale, or inconsistent with the surrounding environment.
- Interactions are collected but not reviewed or connected to response processes.
- The decoy introduces a new pathway to production data or systems.
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
Direct child techniques
None listed at this level.
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.
Explicit technique relationships
Show inferred artifact relationship paths (1)
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 (20)
ATT&CK for ICS (3)
Authoritative sources
- Open this technique on the official D3FEND website ↗
- Open the official ontology resources ↗
- Decoy and deceptive data object technology ↗Cymmetria Inc · Dean Sysman; Gadi Evron; Imri Goldberg; Itamar Sher; Shmuel Ur · PatentReference
- Decoy network-based service for deceiving attackers ↗Amazon Technologies · Thomas Stickle · PatentReference
- System and method for identifying the presence of malware using mini-traps set at network endpoints ↗Fidelis Cybersecurity Solutions Inc · Doron Kolton; Rami Mizrahi; Omer Zohar; Benny Ben-Rabi; Alex Barbalat; Shlomi Gabai · 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.