What if you hit back? Counter-intelligence and Counter-attack Honeynet Project - project@honeynet.org What if you hit back? Counter-intelligence and Counter-attack Dave Dittrich University of Washington <dittrich @ cac.washington.edu> 11/14/2018
Honeynet Project - project@honeynet.org Overview Honeynet Project - project@honeynet.org Levels of Active Defense Use of “Intelligence” Case Studies Included as Examples Conclusion Discussion 11/14/2018
Levels of active defense Honeynet Project - project@honeynet.org Intelligence gathering locally Intelligence gathering remotely Actively tracing the attacker Actively retaliating against the attacker 11/14/2018
Honeynet Project - project@honeynet.org Intelligence (local) Honeynet Project - project@honeynet.org Host, IDS & Firewall Logs Malware artifacts & Sniffer Logs Network Traffic Case study: “BlennY” (1999) 11/14/2018
Intelligence (remote) Honeynet Project - project@honeynet.org External services Internal commands Malware artifacts Case study: Trin00 (1999) 11/14/2018
Honeynet Project - project@honeynet.org Active traceback Honeynet Project - project@honeynet.org Requires intelligence (local, remote) Requires active cooperation of remote site Requires careful correlation of logs Case study: mountd attacks (1998) 11/14/2018
Honeynet Project - project@honeynet.org Active retaliation Honeynet Project - project@honeynet.org Requires multiple levels of local/remote intelligence More remote, less trustworthy/accessible Attribution? Liability Case study: (not here!) 11/14/2018
Conclusion Locally, you have control Remotely, you don’t Attribution is hard Think very carefully 11/14/2018
Honeynet Project - project@honeynet.org Questions? Website: http://staff.washington.edu/dittrich/ Email: dittrich@cac.washington.edu 11/14/2018