-
Notifications
You must be signed in to change notification settings - Fork 69
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Hector Fernandez <[email protected]>
- Loading branch information
Showing
2 changed files
with
138 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,136 @@ | ||
# Predicate type: Vulnerabilities | ||
|
||
Type URI: https://in-toto.io/attestation/vulns/attribute-report | ||
|
||
Version: 0.1 | ||
|
||
## Purpose | ||
|
||
The definition of a vulnerability attestation type has been discussed in the past in [in-toto attestation](https://github.com/in-toto/attestation/issues/58) and [issue](https://github.com/sigstore/cosign/issues/442). However we need to identify two different purposes from these initial conversations: | ||
|
||
* The definition of a common format to represent the results of a vulnerability report. | ||
|
||
* The definition of a certain set of metadata fields that could help to consume these vulnerability attestations from the different scanning tools. | ||
|
||
Obviously the first goal is quite challenging and requires a bigger community to agree upon a specific format. As a consequence, the following attestation type focuses on the definition of that common metadata which could enable the beginning of an exportable and manageable vulnerability attestation. | ||
|
||
This document describes a vulnerability attestation type to represent vulnerability reports from the scanners in an "exportable" manner and independently of the format chosen to output the results. | ||
|
||
## Prerequisites | ||
|
||
The in-toto [attestation] framework and a [Vulnerability scanner tool]. | ||
|
||
## Use Cases | ||
|
||
When sharing the results of a vulnerability scan using an attestation, there is certain metadata that is crucial to trust and reuse this information. | ||
Information about the scanner used during the scanning is relevant to trust these resuls. The state of the vulnerability database used to search for vulnerabilities defines the accuracy of the results. Other metadata information such as the timestamp when the scan finished could define the reusability of these results. | ||
|
||
## Model | ||
|
||
This is a predicate type that fits within the larger [Attestation] framework. | ||
|
||
## Schema | ||
|
||
The schema of this predicate type is documented below. | ||
|
||
### Fields | ||
|
||
The fields that make up this predicate type are: | ||
|
||
The `subject` contains whatever software artifacts are to be associated with this vulnerability report document. | ||
The `predicate` contains a JSON-encoded data with the following fields: | ||
|
||
**scanner** | ||
|
||
> There are lots of container image scanners such as Trivy, Grype, Clair, etc. | ||
> This field describes which scanner is used while performing a container image scan, | ||
> as well as version information and which Vulnerability DB is used. | ||
**scanner.uri** string (ResourceURI), optional | ||
|
||
> > URI indicating the identity of the source of the scanner. | ||
**scanner.version** string (ResourceURI), optional | ||
|
||
> The version of the scanner. | ||
**scanner.db.uri** string (ResourceURI), optional | ||
|
||
> URI indicating the identity of the source of the Vulnerability DB. | ||
**scanner.db.version** string, optional | ||
|
||
> The version of the Vulnerability DB. | ||
**scanner.db.lastUpdate string (Timestamp), required** | ||
|
||
> The timestamp of when the vulnerability DB was updated last time. | ||
**scanner.result** object | ||
|
||
> This is the most important part of this field because it'll store the scan result as a whole. So, people might want | ||
> to use this field to take decisions based on them by making use of Policy Engines tooling whether allow or deny these images. | ||
**metadata.scanStartedOn string (Timestamp), required** | ||
|
||
> The timestamp of when the scan started. | ||
**metadata.scanFinishedOn string (Timestamp), required** | ||
|
||
> The timestamp of when the scan completed. | ||
## Example | ||
|
||
```jsonc | ||
{ | ||
"_type": "https://in-toto.io/Statement/v0.1", | ||
"subject": [ | ||
{ | ||
... | ||
} | ||
], | ||
// Predicate: | ||
"predicateType": "https://in-toto.io/attestation/vulns/attribute-report/v0.1", | ||
"predicate": { | ||
"invocation": { | ||
"parameters": [], | ||
// [ "--format=json", "--skip-db-update" ] | ||
"uri": "", | ||
// https://github.com/developer-guy/alpine/actions/runs/1071875574 | ||
"event_id": "", | ||
// 1071875574 | ||
"builder.id": "" | ||
// GitHub Actions | ||
}, | ||
"scanner": { | ||
"uri": "", | ||
// pkg:github/aquasecurity/trivy@244fd47e07d1004f0aed9 | ||
"version": "", | ||
// 0.19.2 | ||
"db": { | ||
"uri": "", | ||
// pkg:github/aquasecurity/trivy-db/commit/4c76bb580b2736d67751410fa4ab66d2b6b9b27d | ||
"version": "", | ||
// "v1-2021080612" | ||
"lastUpdate": "" | ||
// 2021-08-06T17:45:50.52Z | ||
}, | ||
"result": {} | ||
}, | ||
"metadata": { | ||
"scanStartedOn": "", | ||
// 2021-08-06T17:45:50.52Z | ||
"scanFinishedOn": "" | ||
// 2021-08-06T17:50:50.52Z | ||
} | ||
} | ||
} | ||
``` | ||
|
||
## Changelog and Migrations | ||
|
||
Not applicable for this initial version. | ||
|
||
[Attestation]: ../README.md | ||
|
||
|