Carnegie Mellon University
Browse

Secure by Design at CERT

Download (116.35 kB)
online resource
posted on 2023-10-10, 23:17 authored by Gregory TouhillGregory Touhill

A troubling development in the cyber realm is society’s acceptance of the expectation that all software is released with defects that must be dealt with through patches, most of which follow exploitation of weaknesses in the software by nefarious actors. In a recent address to the nation from Carnegie Mellon University, Jen Easterly, director of the Cybersecurity Infrastructure Security Agency (CISA), noted that this “normalization of deviance” has meant that we are accepting software products that fail to approach our own standards for safety. In her address, Easterly cited work by Diane Vaughn, who wrote about the 1986 Challenger disaster and the decisions leading up to it. Vaughan’s book characterized an environment in which people become so accustomed to a deviant behavior that they don't consider it as deviant. Unfortunately, as Easterly noted, we have become inured to ransomware and cyber attacks, so she called upon technology and software producers to shift left and incorporate security earlier in the development lifecycle to ensure that robust security is a feature of every product that the public, military, and government uses.   A troubling development in the cyber realm is society’s acceptance of the expectation that all software is released with defects that must be dealt with through patches, most of which follow exploitation of weaknesses in the software by nefarious actors. In a recent address to the nation from Carnegie Mellon University, Jen Easterly, director of the Cybersecurity Infrastructure Security Agency (CISA), noted that this “normalization of deviance” has meant that we are accepting software products that fail to approach our own standards for safety. In her address, Easterly cited work by Diane Vaughan, who wrote about the 1986 Challenger disaster and the decisions leading up to it. Vaughan’s book characterized an environment in which people become so accustomed to a deviant behavior that they don't consider it as deviant. Unfortunately, as Easterly noted, we have become inured to ransomware and cyber attacks, so she called upon technology and software producers to shift left and incorporate security earlier in the development lifecycle to ensure that robust security is a feature of every product that the public, military, and government uses.   Within days of Easterly’s speech, the White House released the national cybersecurity strategy, which, among other things, calls for more expansive regulation to shift responsibility for secure software products and services onto technology manufacturers who have traditionally relied on users to configure security into their products. This notion of secure by design has been a long-standing tenet of all the work that we undertake at the SEI and, in particular, our CERT Division, which specializes in cybersecurity engineering and resilience research and development. In this post, I will highlight our continued and longstanding efforts to ensure security by design in fielded software. 

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 2023 Carnegie Mellon University.

Usage metrics

    Exports

    RefWorks
    BibTeX
    Ref. manager
    Endnote
    DataCite
    NLM
    DC