Carnegie Mellon University
Browse

Security Engineering Framework (SEF): Managing Security and Resilience Risks Across the Systems Lifecycle

Download (1.82 MB)
Version 2 2024-12-12, 19:02
Version 1 2024-12-12, 18:57
report
posted on 2024-12-12, 19:02 authored by Christopher AlbertsChristopher Alberts, Charles WallenCharles Wallen, Carol WoodyCarol Woody, Michael BandorMichael Bandor, Thomas MerendinoThomas Merendino

Software is a growing component of modern business- and mission-critical systems. As a result, software assurance is becoming increasingly important to organizations across all sectors. A key aspect of software assurance is keeping security and resilience risks within an acceptable tolerance across the systems lifecycle. The Security Engineering Framework (SEF) is a collection of software-focused engineering practices for managing security and resilience risks across the systems lifecycle. It provides a roadmap for building security and resilience into software-reliant systems and maintaining the system’s security/resilience capabilities during operations and sustainment (O&S). SEF practices help ensure that engineering processes, software, and tools are secure and resilient, reducing the risk that attackers will disrupt program and system information and assets. Acquisition programs can use the SEF to assess their current security/resilience engineering practices and chart a course for improvement, ultimately reducing security/resilience risks in deployed software-reliant systems. The SEF organizes practices into a hierarchy of goals and domains and provides in-depth guidance for all goals and practices. SEF guidance describes the capability represented by each goal and provides an elaboration of each practice in the framework. This report provides a detailed description of the SEF, including its organizing structure, practices, and guidance. 

History

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

    Exports

    RefWorks
    BibTeX
    Ref. manager
    Endnote
    DataCite
    NLM
    DC