Software provenance validation
AssigneeMicrosoft Technology Licensing, LLC
InventorsClaire Novotny, Jared Parsons, Jason R. Shaver, Jobst-Immo Landwerth, Richard Steele Gibson, Tomas Matousek
Life of this patent
Estimating the term…
Loading patent…
AssigneeMicrosoft Technology Licensing, LLC
InventorsClaire Novotny, Jared Parsons, Jason R. Shaver, Jobst-Immo Landwerth, Richard Steele Gibson, Tomas Matousek
Estimating the term…
Software provenance validation reports whether a validation binary matches the source code, resources, and other parts, as well as the compiler, runtime, operating system, and other context, which is specified in a provenance manifest for a release binary. Part context checksums, software versions, tool parameters, and other aspects of a build are checked. Certification signatures, timestamps, certain version differences, source code locations, and other data may be ignored for validation purposes. A provenance manifest may include other provenance manifests, including binary rewrite manifests. The provenance manifest may be stored in a debugger file with symbol information, or stored separately. Partial matches may be reported, with details of what matches or does not match. After provenance of a binary is validated, the binary's source code can be analyzed for vulnerabilities, thereby enhancing software supply chain security.
A computing system equipped for software provenance validation, the computing system comprising:
A method for software provenance validation, the method comprising:
A computer-readable storage device configured with data and instructions which upon execution by a processor cause a computing system to perform a method for software provenance validation, the method comprising:
Dependencies are inferred from the claim text.