Download presentation
Presentation is loading. Please wait.
1
Growing Your Incident Response Toolbox
Jonny Sweeny, GSEC GCWN GCIH GWAS Incident Response Manager June 24, 2018 Copyright 2009, Trustees of Indiana University. This work is the intellectual property of IU. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.
2
What do IR tools get us? Decreased detect-to-block times
Improved ability to track down users and computers End-user self-service remediation
3
Main Content Area Bullet point one Bullet point two Bullet point three
Bullet point four Bullet point five
4
What this talk is not about:
Proactive tools to identify/notice activity (i.e. IDS)
5
Outline How to grow the toolbox Categories of tools: Lookup/processing
Communications Blocking Self-Service How IU implemented these tools
6
Clicking, double-clicking
You have to know about tools before you can grow your toolbox This video clip of The IT Crowd is © Channel Four Television Corporation
7
How to grow the toolbox Start collecting connection logs (Syslog)
NetFlow or SFlow data Other login records too (DNS, AD, LDAP, Kerberos, Webmail, CAS) Consider log retention rollover Get the logs into a database Write event query code Streamline notification (canned messages) Streamline blocking Provide easy lookup for support staff Provide self-service remediation At #1, talk about who/where to get logs from. -- show of hands: who is collecting this data now? --FOIA requests == a reason to *not* store for too long At #2, talk about *how* to import to a database. Mention named pipes. 7
8
Are you from the past? The importance of clear communications
This video clip of The IT Crowd is © Channel Four Television Corporation
9
Communications tools
10
Blocking tools Disable Accounts DHCP AD Group WDDX VPN Dialup
~Tracking blocks – we log all block actions. Helps us see machines that keep showing up. ~Make sure and point out how blocking can be complicated but unifying it helps a lot. ~Compare: scramble versus disable. MAC Address SuperBlock Scripted https post SOAP Null route injections WPA2 802.1x Scramble Passphrase 10
11
Self-Service
12
Self-Service Unblocks
Unblocking used to take a lot of our time. Now users do it themselves. 12
13
Demonstrate Smite, Notify & Remediation
I will now attempt a live demo…wish me luck!!
14
Demo processing of sample DMCA notice
15
DMCA quiz
16
DMCA Automation
17
DMCA User Maintenance
18
Demonstrate Charts
19
Demonstrate Database
20
Whitelist / Blacklist
21
SOAP Services
22
Tech Specs Future plans Written in Perl 12,800 lines of code
Has been a side project; first went live Oct 2007 Future plans Digital signatures Better notification to support teams at block time
23
Questions? Jonny Sweeny jsweeny@iu.edu
Webmail spammer (and brute force) detection scripts Keyboard shortcuts Juggle Jonny Sweeny
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.