Carnegie Mellon University
Browse (116.35 kB)

10 Lessons in Security Operations and Incident Management.

Download (116.35 kB)
online resource
posted on 2024-03-06, 23:36 authored by Robin RuefleRobin Ruefle

Incident response is a critical need throughout government and industry as cyber threat actors look to compromise critical assets within organizations with cascading, often  catastrophic, effects. In 2021, for example, a hacker allegedly accessed a Florida water treatment plant's computer systems and poisoned the water supply. Within the U.S. critical national infrastructure, 77 percent of organizations have seen a rise in insider-driven cyber threats over the last three years. The 2023 IBM Cost of a Data Breach reoport highlights the crucial role of having a well-tested incident response  plan. Companies without a tested plan in place will face 82 percent higher costs in the event of a cyber attack, compared to those that have  implemented and tested such a plan. Researchers in the SEI CERT Division compiled 10 lessons learned from our more than 35 years of developing and working with incident response and security teams throughout the globe. These lessons are relevant to incident response teams contending with an ever-evolving cyber threat landscape. In honor of the CERT Division (also referred to the CERT Coordination Center in our work with the Forum of Incident Response and Security Teams) celebrating 35 years of operation, in this blog post we take a look back at some of the lessons learned from our Cyber Security Incident Response Team (CSIRT) capacity building experiences that also apply to other areas of security operations.


Publisher Statement

This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be construed as an official Government position, policy, or decision, unless designated by other documentation. References herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute. This report was prepared for the SEI Administrative Agent AFLCMC/AZS 5 Eglin Street Hanscom AFB, MA 01731-2100. NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution.

Copyright Statement

Copyright 2024 Carnegie Mellon University.

Usage metrics


    Ref. manager