Mark Your Calendars!
Another stop in the IT Governance Tour! . . .
An Indiana Bankers’ Association Workshop!
The new NIST Cyber Security Framework is heavy on Incident Response. Executives are starting to talk like “it’s not a matter of if, it’s a matter of when.”
When we choose “accept” as a risk response decision, we rely on our ability to respond if a threat truly does exploit a vulnerability. Even when we select “mitigate,” controls can sometimes break. Technology never works the way it’s supposed to. Disasters happen. Thus we have all developed . . . whether formally or informally . . . our Incident Response Processes. This workshop will help streamline your processes that mitigate CyberSecurity risk.
June 4th, 2015 9am to 4pm
IBA Training Center
Who Should Attend
- Incident Response Teams: technical and non-technical members. Information Security Officers, Security Officers, Public Relations handlers, HR legal and compliance, and of course network management and operations.
- Information Security Officers (or whoever in your organization is responsible for overseeing the Incident Response process.)
- Anybody interested in compliance with the NIST CyberSecurity Standard will also find this workshop very helpful.
- Board-Level Incident Response Policy
- Incident Response Plan
- Decision Tree
- Incident Management and Reporting Tools
- Media Kit
- Customer Communication Kit
A large focus will also be on requirements for network monitoring, security monitoring, and Security Information and Event Management.
Incident Response as a Control
- Risk Response Elections
- The Mitigation of Impact
- Turning Lemons into Lemonade
Incident Response as a Process
- Fitting Incident Response into your existing IT Governance program.
- Creating an Incident Response Policy that your Board understands.
Building the Incident Response Team.
- Incident Response Team responsibilities and how to streamline meetings for maximum productivity.
- Incident response planning.
- Creating and using a decision tree.
- Integrating incident response into your existing Risk Management Program.
- Identifying Potential Incidents, Incident Detection
- Managed Security Service Providers and how to put them on your team.
- Monitoring techniques, reporting methodologies, and how to maximize their value. (SIEMs, IRT Agendas, Decision Trees)
- Broadcast Awareness and Incident Escalation
- When do we have to inform our customers?
- Ongoing Incident Communication Concerns
- Dealing with the Media, your Customers, and your Employees during an incident.
- When to bring law enforcement in, and how to actually get something done. Forensics do’s and don’ts.
The NIST CyberSecurity Framework
- NIST’s new CyberSecurity Framework at a High Level
- How this Framework impacts “requirements” for Incident Response
- (Unless the guidance has already been released) Why we think the NIST CyberSecurity Framework will soon become a requirement for banks.
- How to steer your Incident Response Program into a direction that will conform with this framework.
About the Speaker
Dan Hadaway, CRISC, CISA, CISM
Dan is managing partner of Infotex, Inc, an Indiana Bankers Association preferred service provider in many areas of information technology including Managed Security Services, Network Monitoring, IT Auditing, and Information Security Training. Dan speaks regularly at conventions, conferences, and workshops. He is the facilitator of the IBA’s Annual Information Technology Security Conference, and is published in various trade magazines including Hoosier Banker and the ABA’s Compliance Magazine.
Read his work at blog.infotex.com.
Original article by Dan Hadaway CRISC CISA CISM. Founder and Managing Partner, infotex
Dans New Leaf is a fun blog to inspire thought in the area of IT Governance.
In this short video, Mike, our “Envoy from the SIEM”, walks us through how data flows
Dan’s reflection on the past 20 years. A Dan’s New Leaf post about predictions. If yo
Welcome Webinar Attendees! You can download a zip folder with all three of the delive
Another awareness poster for YOUR customers (and users). Now that we have our own em