Definition
A decoy service, system, or environment, that is connected to the enterprise network, and simulates or emulates certain functionality to the network, without exposing full access to a production system.
How it works
Decoy honeypots are deployed within the enterprise environment that emulate certain services or portions of an OS to attract attackers.
Considerations
A connected honeynet provides a tradeoff between emulating certain functionality but not being as sophisticated as an integrated honeynet. The connected honeynet may not provide enough functionality to detect new attack patterns or zero day exploits but could provide enough functionality for specific known vulnerabilities.
Implementation perspective
Connected Honeynet 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 Decoy Artifact.
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 (1)
Authoritative sources
- Open this technique on the official D3FEND website ↗
- Open the official ontology resources ↗
- Modification of a Server to Mimic a Deception Mechanism ↗Acalvio Technologies Inc · Sreenivas Gukal, Rammohan Varadarajan · 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.