Definition
A Decoy Object is created and deployed for the purposes of deceiving attackers.
Technique Overview
Decoy objects are typically configured with detectable means of communication but do not have any legitimate business purpose. Any communication via or to these objects should be logged and analyzed to find potential indicators of compromise for a possible past or future attack against other systems.
Implementation perspective
Decoy Object 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, File, Network Resource.
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
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.
Show inferred artifact relationship paths (3)
NIST SP 800-53 relationships
The relation label is preserved from the D3FEND ontology. It is not converted into a claim that the control automatically implements or validates this technique.
ATT&CK Enterprise mitigation relationships
These links come from the D3FEND ontology’s ATT&CK mitigation mapping. They help users navigate between the knowledge bases and do not guarantee mitigation effectiveness.
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 (125)
Showing the first 60 of 125 source-derived relationships. Open the official D3FEND technique for the current graph view.
ATT&CK for ICS (11)
Authoritative sources
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.