CTO's Perspective on Creating a Template for an Incident Response

When you have a security incident, do you have a documented incident response plan? If not, who makes the decisions? These incidents could result in a complicated and costly legal, regulatory, and/or security proceedings. The people, process, and technology responsible for responding to these incidents are collectively known as Incident Response (IR). For those who don’t yet have a set plan but are looking to establish one, having a template to reference can be helpful. There are number of key pieces that should be incorporated into every incident response plan. Join us for a panel discussion featuring our CTO, head of product management, and head of product strategy as they talk about executing an incident response plan. The discussion will cover: •How to create a template for IR •What are the critical elements of an IR plan •Testing frequency and methods to ensure you have a good IR plan in place About Our Key Speaker: Sam McLane leads Security Engineering at Arctic Wolf, bringing over 20 years of security experience to the team. Prior to joining Arctic Wolf, Sam led Product Management for and other sales functions for Blue Coat Systems’ Cloud Security Services business. Before Blue Coat, Sam was a sales leader at Lucent Technologies, managing the system engineering team for the eastern US. Prior to Lucent, Sam was a networking consultant at KPMG and network manager at Temple University.