The document discusses hacking back and argues that it is a bad idea for several reasons. Hacking back refers to using offensive hacking techniques to retaliate against or profile attackers. However, hacking back could have legal repercussions and attribution of attacks is difficult. Additionally, most organizations are not skilled enough to hack back without risk and there are better uses of time than retaliation. Hacking back also risks escalating conflicts. The document concludes by asking for questions.

1. Hacking Back
Is A Bad Idea
Steven Maske
SOURCE Boston 2013

2. Who Am I
Steven Maske
 Email: steven@stevenmaske.com
 Twitter: @ITSecurity
 Blog: securityramblings.com
Please Complete The Survey :-)

3. DISCLAIMER
The opinions expressed here are my own
and do not necessarily represent those of
my employer or any group I am affiliated
with. This talk is intended to provoke
thought on the subject and is not intended
as advice. Every business is different and
sufficient due diligence should be exercised
when determining the appropriate
response to an attack.

4. What is Hacking Back?

5. Definition
hack∙ing back [hak-ing bak]
verb
1. The act of using offensive techniques to
retaliate for a real or perceived attack.
2. The use of offensive techniques in an
attempt to gain access to the attackers
system for the purpose of alleviating the
attack or profiling the attacker.

6. Definition
Hacking Back ≠ Active Defense

7. Legal Repercussions

8. Attribution

9. You’re Not That Good

10. You Have Better
Things To Do

11. Escalation

12. Conclusion

13. Questions?

14. Contact
Steven Maske
 Email: steven@stevenmaske.com
 Twitter: @ITSecurity
 Blog: securityramblings.com
Please Complete The Survey