Overview#
Use of decoys and traps to detect attackers early. Honey tokens, fake credentials, and deceptive services alert defenders when touched.
Core objectives#
- Establish shared definitions of Deception Technology for security, engineering, and leadership teams.
- Connect Deception Technology activities to measurable risk reduction and resilience goals.
- Provide onboarding notes so new team members can quickly understand how Deception Technology works here.
Implementation notes#
- Identify the primary owner for Deception Technology, the data sources involved, and the systems affected.
- Document the minimum viable process, tooling, and runbooks that keep Deception Technology healthy.
- Map Deception Technology practices to standards such as ISO/IEC 27001, NIST CSF, or CIS Controls.
Operational signals#
- Leading indicators: early warnings that Deception Technology might degrade (e.g., backlog growth, noisy alerts, or missed SLAs).
- Lagging indicators: realized impact that shows Deception Technology failed or needs investment (e.g., incidents, audit findings).
- Feedback loops: retrospectives and metrics reviews that tune Deception Technology continuously.
Related practices#
- Align Deception Technology with defense-in-depth planning, threat modeling, and disaster recovery tests.
- Communicate updates to stakeholders through concise briefs, dashboards, and internal FAQs.
- Pair Deception Technology improvements with tabletop exercises to validate expectations.