As a part of an ongoing effort to maintain you knowledgeable about our newest work, this weblog put up summarizes some current publications from the SEI within the areas of utility programming interfaces (APIs), software program payments of supplies (SBOMs), safe improvement, Structure Evaluation and Design Language (AADL), and static evaluation.
These publications spotlight the newest work from SEI technologists in these areas. This put up features a itemizing of every publication, writer(s), and hyperlinks the place they are often accessed on the SEI web site.
Utility Programming Interface (API) Vulnerabilities and Dangers
by McKinley Sconiers-Hasan
Internet-accessible utility programming interfaces (APIs) are more and more frequent, and they’re usually designed and applied in a method that creates safety dangers. Constructing on a taxonomy from OWASP, this report describes 11 frequent vulnerabilities and three dangers associated to APIs, offering options about tips on how to repair or scale back their affect. Suggestions embody utilizing a normal API documentation course of, utilizing automated testing, and guaranteeing the safety of the identification and entry administration system.
Learn the SEI Particular Report.
Software program Invoice of Supplies (SBOM) Concerns for Operational Check & Analysis Actions
by Michael Bandor
This white paper appears at potential roles for SBOM inside varied Operational Check & Analysis (OT&E) actions. It appears on the historical past and background of SBOMs, current developments (as of the creation of the white paper), basic challenges and inquiries to ask, and 5 particular use instances. It concludes with conclusions and proposals.
SBOMs are presently in early and ranging phases of adoption throughout trade and throughout the DoD. There are nonetheless points with the standard (e.g., completeness, accuracy, forex, and so forth.) of the SBOMs being produced, in addition to adherence to the minimal important components recognized by the U.S. Division of Commerce. Legacy techniques in addition to cloud-based techniques current challenges for producing SBOMs. The DoD is presently creating proposed steerage for addressing the SBOM requirement by applications.
Given this early part of adoption, it is strongly recommended that SBOMs be used to reinforce however not exchange the present strategies utilized by Operational Check (OT) personnel in efficiency of the testing capabilities and to not rely solely on the SBOM data. The restrictions should not intrinsic, and we will count on that SBOMs will show to be more and more important and helpful for OT actions.
Learn the SEI white paper.
Safe Programs Don’t Occur by Accident
by Timothy A. Chick
Most cybersecurity breaches are as a consequence of defects in design or code, together with each coding and logic errors. One of the best ways to handle these challenges is to design and construct safer options. On this webcast, Tim Chick discusses how safety could be an integral side of your entire software program lifecycle. The important thing to success is to comply with deliberate engineering practices targeted on decreasing safety dangers by means of the usage of software program assurance strategies.
What attendees will be taught:
- the significance of cybersecurity, together with examples of safety failures
- qualities to take a look at when evaluating third-party software program
- the connection between high quality and safety
- engineering strategies used all through the event lifecycle to scale back cyber dangers
View the webcast.
Reachability of System Operation Modes in AADL
by Lutz Wrage
Parts in an AADL (Structure Evaluation and Design Language) mannequin can have modes that decide which subcomponents and connections are energetic. Transitions between modes are triggered by occasions originating from the modeled system’s setting or from different parts within the mannequin. Modes and transitions can happen on any stage of the part hierarchy. The mixtures of part modes (referred to as system operation modes or SOMs) outline the system’s configurations. It is very important know which SOMs can truly happen within the system, particularly within the space of system security, as a result of a system might comprise parts that shouldn’t be energetic concurrently, for instance, a automobile’s brake and accelerator. This report presents an algorithm that constructs the set of reachable SOMs for a given AADL mannequin and the transitions between them.
Learn the SEI Technical Report.
Automated Restore of Static Evaluation Alerts
by David Svoboda
Builders know that static evaluation helps make code safer. Nevertheless, heuristic static evaluation instruments usually produce numerous false positives, hindering their usefulness. On this podcast, David Svoboda, a software program safety engineer within the SEI’s CERT Division, discusses Redemption, a brand new open-source software from the SEI that robotically repairs frequent errors in C/C++ code generated from static evaluation alerts, making code safer and static evaluation much less overwhelming.
Hearken to/view the podcast.
Navigating Functionality-Primarily based Planning: The Advantages, Challenges, and Implementation Necessities
By Anandi Hira and William Nichols
Functionality-based planning (CBP) defines a framework for acquisition and design that encompasses a complete view of current skills and future wants for the aim of supporting strategic selections concerning what is required and tips on how to successfully obtain it. Each enterprise and authorities acquisition domains use CBP for monetary success or to design well-balanced protection techniques. Unsurprisingly, the definitions range throughout these domains. This paper endeavors to reconcile these definitions to supply a overarching view of CBP, its potential, and sensible implementation of its rules.
Learn the white paper.
My Story in Computing, with Sam Procter
by Sam Procter
Sam Procter, an SEI senior structure researcher, began out finding out laptop science on the College of Nebraska, however he didn’t find it irresistible. It wasn’t till he took his first software program engineering course that he knew he’d discovered his profession path. On this SEI podcast, Procter discusses early influences that formed his profession, the significance of embracing several types of variety in his analysis and work, and the worth of work-life steadiness.
Hearken to/view the podcast.
Extra Assets
View the newest SEI analysis within the SEI Digital Library.
View the newest podcasts within the SEI Podcast Collection.
View the newest installments within the SEI Webcast Collection.