Microsoft Technology Licensing, LLC

Ian James McCarty

Dale R Rolf

Henry Lyons

Sencer Nuri Yeralan

Frank Joseph Bussell

Nicholas Allan Schwerzler

David John Janson

Minh Trong Tran

Thomas George Yaryan

Mehmet Iyigun

Hari R Pulapaka

Benjamin M Schultz

Scott Randall Shell

Frederick Justus Smith

John Andrew Starks

David John Linsley

Giridhar Viswanathan

Daniel Vasquez Lopez

Ankit Srivastava

Md Nazmus Sakib

Daryn Elliot Robbins

Stephen E Bensley

Kinshumann

Abhinav Mishra

JianMing M Zhou

Joshua David Ebersol

Systems are provided for generating, modifying and using SBOMs for facilitating risk assessment and threat mitigation for corresponding programs, and particularly for large programming builds. The creation and modification of the SBOMs includes processes for omitting declarations referenced in chunk SBOMs of program chunks incorporated into a final programming build associated with a build SBOM, but which are not actually utilized by the final programming build, as well as processes for adding new declarations for code segments that are not declared in the related chunk SBOMs, even though the code segments are utilized by the final programming build. Systems are also configured to use SBOMs in combination with configuration restriction records to assess and resolve threat events in a manner that can prevent unnecessary remedial actions for threat events that appear to be relevant to one or more files or dependencies incorporated into a program.

Systems and processes for creating software bill of materials for large distributed builds

Systems and processes for facilitating edits to software bill of materials

Embodiments are directed to managing software components loaded on a device by identifying a platform manifest having a valid certificate, confirming that the platform manifest is bound to the device, identifying components listed on the platform manifest, confirming that the listed components have a valid certificate, and loading listed components with valid certificates on the device. The components may be binaries and packages for an operating system. The components may be signed in an embedded manner or with detached signatures. The platform manifest may be bound to the device in a manner that allows for identification of unauthorized platform manifests.

Securely defining operating system composition without multiple authoring

Anonymous containers are discussed herein. An operating system running on a computing device, also referred to herein as a host operating system running on a host device, prevents an application from accessing personal information (e.g., user information or corporate information) by activating an anonymous container that is isolated from the host operating system. In order to create and activate the anonymous container, a container manager anonymizes the configuration and settings data of the host operating system, and injects the anonymous configuration and settings data into the anonymous container. Such anonymous configuration and settings data may include, by way of example and not limitation, application data, machine configuration data, and user settings data. The host operating system then allows the application to run in the anonymous container.

Anonymous containers

Growing community of inventors

Redmond, WA, United States of America

Ian James McCarty