APIs, SBOMs, and Static Evaluation


As a part of an ongoing effort to maintain you knowledgeable about our newest work, this weblog submit summarizes some current publications from the SEI within the areas of software programming interfaces (APIs), software program payments of supplies (SBOMs), safe growth, Structure Evaluation and Design Language (AADL), and static evaluation.

These publications spotlight the most recent work from SEI technologists in these areas. This submit features a itemizing of every publication, creator(s), and hyperlinks the place they are often accessed on the SEI web site.

Software Programming Interface (API) Vulnerabilities and Dangers
by McKinley Sconiers-Hasan

Net-accessible software 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 strategies about the way to repair or scale back their impression. Suggestions embody utilizing a typical API documentation course of, utilizing automated testing, and guaranteeing the safety of the id 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 numerous 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), common challenges and inquiries to ask, and 5 particular use instances. It concludes with conclusions and suggestions.

SBOMs are presently in early and ranging phases of adoption throughout business and throughout the DoD. There are nonetheless points with the standard (e.g., completeness, accuracy, forex, and so on.) of the SBOMs being produced, in addition to adherence to the minimal important parts recognized by the U.S. Division of Commerce. Legacy programs in addition to cloud-based programs current challenges for producing SBOMs. The DoD is presently growing proposed steering for addressing the SBOM requirement by packages.

Given this early part of adoption, it is strongly recommended that SBOMs be used to enhance however not change the present strategies utilized by Operational Check (OT) personnel in efficiency of the testing features and to not rely solely on the SBOM data. The constraints aren’t intrinsic, and we are able to anticipate that SBOMs will show to be more and more important and helpful for OT actions.
Learn the SEI white paper.

Safe Techniques 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 deal with these challenges is to design and construct safer options. On this webcast, Tim Chick discusses how safety will be an integral facet of the complete software program lifecycle. The important thing to success is to observe deliberate engineering practices centered on lowering safety dangers by the usage of software program assurance methods.

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 methods 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 elements within the mannequin. Modes and transitions can happen on any degree of the element hierarchy. The mixtures of element modes (known as system operation modes or SOMs) outline the system’s configurations. You will need to know which SOMs can really happen within the system, particularly within the space of system security, as a result of a system could include elements that shouldn’t be energetic concurrently, for instance, a automotive’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. Nonetheless, 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-Based mostly 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 present talents and future wants for the aim of supporting strategic choices concerning what is required and the way to successfully obtain it. Each enterprise and authorities acquisition domains use CBP for monetary success or to design well-balanced protection programs. 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 learning laptop science on the College of Nebraska, however he didn’t like it. 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.

Further Sources

View the most recent SEI analysis within the SEI Digital Library.
View the most recent podcasts within the SEI Podcast Sequence.
View the most recent installments within the SEI Webcast Sequence.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *