As my illustrious colleague mentioned, we are starting a new research project, one we wanted to run for a while, about DECEPTION. While there is already Gartner research on the topic (this and this), we at Gartner GTP will approach this from an end-user perspective, as always.
So, in the next few weeks we will be running around asking questions such as:
- Why did you decide to employ deception and/or deploy deception tools?
- What helped you prioritize deception over other security technologies?
- What is/are your current use cases with deception technology?
- How did you test the tools?
- How do your daily operational practices around deception look like?
- What security processes and practices are affected by your use of deception?
- Any challenges with adopting deception tools in your organization?
Finally, a call to action! If you recently deployed deception tools, please let us know. Example vendors include TrapX Security, Attivo Networks, Illusive Networks and Cymmetria. If you are a vendor who somehow failed to brief us on your deception approaches, you know what to do.
Our related blog posts on deception:
- New Research: Deception Technologies!
- Yes, Give Deception a Chance!
- “Deception as Detection” or Give Deception a Chance?
Read Complimentary Relevant Research
Five Golden Rules for Creating Effective Security Policy
Policy writing is a risk communication exercise that is frequently performed by people who lack the skills needed to create good security...
View Relevant Webinars
What Matters When Securing IoT?
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.