SANS: Incident Response: How to Fight Back

By Jen Spoon January 13, 2016

[vc_row][vc_column width=”2/3″ el_class=”form”][vc_row_inner][vc_column_inner][sm_custom_heading heading_tag=”h2″ font_style=”sm-semibold”]SANS: Incident Response: How to Fight Back[/sm_custom_heading][/vc_column_inner][/vc_row_inner][vc_row_inner el_class=”form”][vc_column_inner width=”1/4″][sm_image alt=”SANS: Incident Response: How to Fight Back” title=”SANS: Incident Response: How to Fight Back” align=”left” style=”sm-style-shadow” image=”5345″][/vc_column_inner][vc_column_inner width=”3/4″][sm_column_text]Most organizations have not proactively prepared for a breach. In fact, a majority of incident responders (52 percent) say they lack the necessary visibility into endpoint vulnerabilities. Without continuous data collection at the endpoint, preparing and responding to a breach is exponentially hampered. Download the SANS Institute’s latest industry survey to understand these key findings:

  • More than one-quarter of IR professionals (26%) are dissatisfied with their current organization’s IR capabilities, calling them ineffective
  • The definition of an incident remains broad, increasing the workload for already understaffed IR teams
  • Efficient response to security incidents is hindered by lack of time to review and practice IR procedures
  • Lack of formal IR response plans and defined team structures were identified as detriments to efficient incident handling
  • Organizations have not yet implemented the collection and correlation of threat intelligence
  • Automation and SIEM integration tools remain the focus to improve IR processes
  • Learn how to prepare for a breach—instead of reacting to one.

August 15, 2014; SANS Institute, Alissa Torres[/sm_column_text][/vc_column_inner][/vc_row_inner][/vc_column][vc_column width=”1/3″ el_class=”form”][sm_custom_heading heading_tag=”h3″ align=”sm-center” font_style=”sm-normal” uppercase=”yes”]Download Whitepaper[/sm_custom_heading][sm_contact_form id=”1740″ eloqua_campaign_id=”70180000000eZQu” eloqua_form=”WebsiteReg” eloqua_lead_source=”Website – Content Download” eloqua_member_status=”Downloaded” eloqua_last_download=”WP Incident Response How to Fight Back” eloqua_child_campaigns=”%5B%7B%22eloqua_child_campaign_id%22%3A%2270180000000eZQu%22%2C%22eloqua_child_form%22%3A%22WebsiteReg%22%2C%22eloqua_child_lead_source%22%3A%22Website%20-%20%20Content%20Download%22%7D%2C%7B%22eloqua_child_campaign_id%22%3A%2270180000000ee55%22%2C%22eloqua_child_form%22%3A%22WebsiteReg%22%2C%22eloqua_child_lead_source%22%3A%22Website%20-%20Content%20Download%22%7D%2C%7B%22eloqua_child_campaign_id%22%3A%2270180000000fChz%22%2C%22eloqua_child_form%22%3A%22WebsiteReg%22%2C%22eloqua_child_lead_source%22%3A%22Email%20Campaign%22%7D%5D” input_shape=”sm-shape-rounded”][/vc_column][/vc_row][vc_row][vc_column el_class=”ty”][vc_row_inner el_class=”ty”][vc_column_inner][sm_custom_heading heading_tag=”h2″ font_style=”sm-semibold”]Thank you for your interest in Carbon Black. Your file is available below.[/sm_custom_heading][sm_file][/vc_column_inner][/vc_row_inner][/vc_column][/vc_row]

comments

comments for this post are closed