Get desktop application:
View/edit binary Protocol Buffers messages
[Grafeas](https://grafeas.io) API. Retrieves analysis results of Cloud components such as Docker container images. Analysis results are stored as a series of occurrences. An `Occurrence` contains information about a specific analysis instance on a resource. An occurrence refers to a `Note`. A note contains details describing the analysis and is generally stored in a separate project, called a `Provider`. Multiple occurrences can refer to the same note. For example, an SSL vulnerability could affect multiple images. In this case, there would be one note for the vulnerability and an occurrence for each image with the vulnerability referring to that note.
Gets the specified occurrence.
Request to get an occurrence.
The name of the occurrence in the form of `projects/[PROJECT_ID]/occurrences/[OCCURRENCE_ID]`.
Lists occurrences for the specified project.
Request to list occurrences.
The name of the project to list occurrences for in the form of `projects/[PROJECT_ID]`.
The filter expression.
Number of occurrences to return in the list. Must be positive. Max allowed page size is 1000. If not specified, page size defaults to 20.
Token to provide to skip to a particular spot in the list.
Response for listing occurrences.
The occurrences requested.
The next pagination token in the list response. It should be used as `page_token` for the following request. An empty value means no more results.
Deletes the specified occurrence. For example, use this method to delete an occurrence when the occurrence is no longer applicable for the given resource.
Request to delete an occurrence.
The name of the occurrence in the form of `projects/[PROJECT_ID]/occurrences/[OCCURRENCE_ID]`.
Creates a new occurrence.
Request to create a new occurrence.
The name of the project in the form of `projects/[PROJECT_ID]`, under which the occurrence is to be created.
The occurrence to create.
Creates new occurrences in batch.
Request to create occurrences in batch.
The name of the project in the form of `projects/[PROJECT_ID]`, under which the occurrences are to be created.
The occurrences to create. Max allowed length is 1000.
Response for creating occurrences in batch.
The occurrences that were created.
Updates the specified occurrence.
Request to update an occurrence.
The name of the occurrence in the form of `projects/[PROJECT_ID]/occurrences/[OCCURRENCE_ID]`.
The updated occurrence.
The fields to update.
Gets the note attached to the specified occurrence. Consumer projects can use this method to get a note that belongs to a provider project.
Request to get the note to which the specified occurrence is attached.
The name of the occurrence in the form of `projects/[PROJECT_ID]/occurrences/[OCCURRENCE_ID]`.
Gets the specified note.
Request to get a note.
The name of the note in the form of `projects/[PROVIDER_ID]/notes/[NOTE_ID]`.
Lists notes for the specified project.
Request to list notes.
The name of the project to list notes for in the form of `projects/[PROJECT_ID]`.
The filter expression.
Number of notes to return in the list. Must be positive. Max allowed page size is 1000. If not specified, page size defaults to 20.
Token to provide to skip to a particular spot in the list.
Response for listing notes.
The notes requested.
The next pagination token in the list response. It should be used as `page_token` for the following request. An empty value means no more results.
Deletes the specified note.
Request to delete a note.
The name of the note in the form of `projects/[PROVIDER_ID]/notes/[NOTE_ID]`.
Creates a new note.
Request to create a new note.
The name of the project in the form of `projects/[PROJECT_ID]`, under which the note is to be created.
The ID to use for this note.
The note to create.
Creates new notes in batch.
Request to create notes in batch.
The name of the project in the form of `projects/[PROJECT_ID]`, under which the notes are to be created.
The notes to create. Max allowed length is 1000.
Response for creating notes in batch.
The notes that were created.
Updates the specified note.
Request to update a note.
The name of the note in the form of `projects/[PROVIDER_ID]/notes/[NOTE_ID]`.
The updated note.
The fields to update.
Lists occurrences referencing the specified note. Provider projects can use this method to get all occurrences across consumer projects referencing the specified note.
Request to list occurrences for a note.
The name of the note to list occurrences for in the form of `projects/[PROVIDER_ID]/notes/[NOTE_ID]`.
The filter expression.
Number of occurrences to return in the list.
Token to provide to skip to a particular spot in the list.
Response for listing occurrences for a note.
The occurrences attached to the specified note.
Token to provide to skip to a particular spot in the list.
An alias to a repo revision.
Used in:
,The alias kind.
The alias name.
The type of an alias.
Used in:
Unknown.
Git tag.
Git branch.
Used to specify non-standard aliases. For example, if a Git repo has a ref named "refs/foo/bar".
Instruction set architectures supported by various package managers.
Used in:
, ,Unknown architecture.
X86 architecture.
X64 architecture.
Artifact describes a build product.
Used in:
Hash or checksum value of a binary, or Docker Registry 2.0 digest of a container.
Artifact ID, if any; for container images, this will be a URL by digest like `gcr.io/projectID/imagename@sha256:123456`.
Related artifact names. This may be the path to a binary or jar file, or in the case of a container build, the name used to push the container image to Google Container Registry, as presented to `docker push`. Note that a single Artifact ID can have multiple names, for example if two tags are applied to one image.
Note kind that represents a logical attestation "role" or "authority". For example, an organization might have one `Authority` for "QA" and one for "build". This note is intended to act strictly as a grouping mechanism for the attached occurrences (Attestations). This grouping mechanism also provides a security boundary, since IAM ACLs gate the ability for a principle to attach an occurrence to a given note. It also provides a single point of lookup to find all attached attestation occurrences, even if they don't all live in the same project.
Used in:
Hint hints at the purpose of the attestation authority.
This submessage provides human-readable hints about the purpose of the authority. Because the name of a note acts as its resource reference, it is important to disambiguate the canonical name of the Note (which might be a UUID for security purposes) from "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify.
Used in:
Required. The human readable name of this attestation authority, for example "qa".
Occurrence that represents a single "attestation". The authenticity of an attestation can be verified using the attached signature. If the verifier trusts the public key of the signer, then verifying the signature is sufficient to establish trust. In this circumstance, the authority to which this attestation is attached is primarily useful for lookup (how to find this attestation if you already know the authority and artifact to be verified) and intent (for which authority this attestation was intended to sign.
Used in:
,Required. The serialized payload that is verified by one or more `signatures`.
One or more signatures over `serialized_payload`. Verifier implementations should consider this attestation message verified if at least one `signature` verifies `serialized_payload`. See `Signature` in common.proto for more details on signature structure and verification.
One or more JWTs encoding a self-contained attestation. Each JWT encodes the payload that it verifies within the JWT itself. Verifier implementation SHOULD ignore the `serialized_payload` field when verifying these JWTs. If only JWTs are present on this AttestationOccurrence, then the `serialized_payload` SHOULD be left empty. Each JWT SHOULD encode a claim specific to the `resource_uri` of this Occurrence, but this is not validated by Grafeas metadata API implementations. The JWT itself is opaque to Grafeas.
BaseImage describes a base image of a container image.
Used in:
The name of the base image.
The repository name in which the base image is from.
The number of layers that the base image is composed of.
Note holding the version of the provider's builder and the signature of the provenance message in the build details occurrence.
Used in:
Required. Immutable. Version of the builder which produced this build.
Details of a build occurrence.
Used in:
The actual provenance for the build.
Serialized JSON representation of the provenance, used in generating the build signature in the corresponding build note. After verifying the signature, `provenance_bytes` can be unmarshalled and compared to the provenance to confirm that it is unchanged. A base64-encoded string representation of the provenance bytes is used for the signature in order to interoperate with openssl which expects this format for signature verification. The serialized form is captured both to avoid ambiguity in how the provenance is marshalled to json as well to prevent incompatibilities with future changes.
Deprecated. See InTotoStatement for the replacement. In-toto Provenance representation as defined in spec.
In-toto Statement representation as defined in spec. The intoto_statement can contain any type of provenance. The serialized payload of the statement can be stored and signed in the Occurrence's envelope.
In-Toto Slsa Provenance V1 represents a slsa provenance meeting the slsa spec, wrapped in an in-toto statement. This allows for direct jsonification of a to-spec in-toto slsa statement with a to-spec slsa provenance.
Provenance of a build. Contains all information needed to verify the full details about the build from source to completion.
Used in:
Required. Unique identifier of the build.
ID of the project.
Commands requested by the build.
Output of the build.
Time at which the build was created.
Time at which execution of the build was started.
Time at which execution of the build was finished.
E-mail address of the user who initiated this build. Note that this was the user's e-mail address at the time the build was initiated; this address may not represent the same end-user for all time.
URI where any logs for this provenance were written.
Details of the Source input to the build.
Trigger identifier if the build was triggered automatically; empty if not.
Special options applied to this build. This is a catch-all field where build providers can enter any desired additional details.
Version string of the builder at the time this build was executed.
Used in:
Common Vulnerability Scoring System. For details, see https://www.first.org/cvss/specification-document This is a message we will try to use for storing various versions of CVSS rather than making a separate proto for storing a specific version.
Used in:
,The base score is a function of the base metric scores.
Base Metrics Represents the intrinsic characteristics of a vulnerability that are constant over time and across user environments.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
CVSS Version.
Used in:
,Common Vulnerability Scoring System version 3. For details, see https://www.first.org/cvss/specification-document
Used in:
The base score is a function of the base metric scores.
Base Metrics Represents the intrinsic characteristics of a vulnerability that are constant over time and across user environments.
Used in:
Used in:
Used in:
Used in:
Used in:
Used in:
A CloudRepoSourceContext denotes a particular revision in a Google Cloud Source Repo.
Used in:
The ID of the repo.
A revision in a Cloud Repo can be identified by either its revision ID or its alias.
A revision ID.
An alias, which may be a branch or tag.
Command describes a step performed as part of the build pipeline.
Used in:
Required. Name of the command, as presented on the command line, or if the command is packaged as a Docker container, as presented to `docker pull`.
Environment variables set before running this command.
Command-line arguments used when executing this command.
Working directory (relative to project source root) used when running this command.
Optional unique identifier for this command, used in wait_for to reference this command as a dependency.
The ID(s) of the command(s) that this command depends on.
Indicates that the builder claims certain fields in this message to be complete.
Used in:
If true, the builder claims that recipe.arguments is complete, meaning that all external inputs are properly captured in the recipe.
If true, the builder claims that recipe.environment is claimed to be complete.
If true, the builder claims that materials are complete, usually through some controls to prevent network access. Sometimes called "hermetic".
Used in:
The title that identifies this compliance check.
A description about this compliance check.
The OS and config versions the benchmark applies to.
A rationale for the existence of this compliance check.
A description of remediation steps if the compliance check fails.
Serialized scan instructions with a predefined format.
Potential impact of the suggested remediation
A compliance check that is a CIS benchmark.
Used in:
An indication that the compliance checks in the associated ComplianceNote were not satisfied for particular resources or a specified reason.
Used in:
The OS and config version the benchmark was run on.
Describes the CIS benchmark version that is applicable to a given OS and os version.
Used in:
,The CPE URI (https://cpe.mitre.org/specification/) this benchmark is applicable to.
The name of the document that defines this benchmark, e.g. "CIS Container-Optimized OS".
The version of the benchmark. This is set to the version of the OS-specific CIS document the benchmark is defined in.
Used in:
DSSEHint hints at the purpose of the attestation authority.
This submessage provides human-readable hints about the purpose of the authority. Because the name of a note acts as its resource reference, it is important to disambiguate the canonical name of the Note (which might be a UUID for security purposes) from "readable" names more suitable for debug output. Note that these hints should not be used to look up authorities in security sensitive contexts, such as when looking up attestations to verify.
Used in:
Required. The human readable name of this attestation authority, for example "cloudbuild-prod".
Deprecated. Prefer to use a regular Occurrence, and populate the Envelope at the top level of the Occurrence.
Used in:
If doing something security critical, make sure to verify the signatures in this metadata.
An artifact that can be deployed in some runtime.
Used in:
Required. Resource URI for the artifact being deployed.
The period during which some deployable was active in a runtime.
Used in:
Identity of the user that triggered this deployment.
Required. Beginning of the lifetime of this deployment.
End of the lifetime of this deployment.
Configuration used to create this deployment.
Address of the runtime element hosting this deployment.
Output only. Resource URI for the artifact being deployed taken from the deployable field with the same name.
Platform hosting this deployment.
Types of platforms.
Used in:
Unknown.
Google Container Engine.
Google App Engine: Flexible Environment.
Custom user-defined platform.
Digest information.
Used in:
`SHA1`, `SHA512` etc.
Value of the digest.
A note that indicates a type of analysis a provider would perform. This note exists in a provider's project. A `Discovery` occurrence is created in a consumer's project at the start of analysis.
Used in:
Required. Immutable. The kind of analysis that is handled by this discovery.
Provides information about the analysis status of a discovered resource.
Used in:
Whether the resource is continuously analyzed.
The status of discovery for the resource.
Indicates any errors encountered during analysis of a resource. There could be 0 or more of these errors.
When an error is encountered this will contain a LocalizedMessage under details to show to the user. The LocalizedMessage is output only and populated by the API.
The CPE of the resource being scanned.
The last time this resource was scanned.
The time occurrences related to this discovery occurrence were archived.
The status of an SBOM generation.
The status of an vulnerability attestation generation.
Indicates which analysis completed successfully. Multiple types of analysis can be performed on a single resource.
Used in:
Analysis status for a resource. Currently for initial analysis only (not updated in continuous analysis).
Used in:
Unknown.
Resource is known but no action has been taken yet.
Resource is being analyzed.
Analysis has finished successfully.
Analysis has completed.
Analysis has finished unsuccessfully, the analysis itself is in a bad state.
The resource is known not to be supported.
Whether the resource is continuously analyzed.
Used in:
Unknown.
The resource is continuously analyzed.
The resource is ignored for continuous analysis.
The status of an SBOM generation.
Used in:
The progress of the SBOM generation.
If there was an error generating an SBOM, this will indicate what that error was.
An enum indicating the progress of the SBOM generation.
Used in:
Default unknown state.
SBOM scanning is pending.
SBOM scanning has completed.
The status of an vulnerability attestation generation.
Used in:
The last time we attempted to generate an attestation.
The success/failure state of the latest attestation attempt.
If failure, the error reason for why the attestation generation failed.
An enum indicating the state of the attestation generation.
Used in:
Default unknown state.
Attestation was successfully generated and stored.
Attestation was unsuccessfully generated and stored.
This represents a particular channel of distribution for a given package. E.g., Debian's jessie-backports dpkg mirror.
Used in:
The cpe_uri in [CPE format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package.
The CPU architecture for which packages in this distribution channel were built.
The latest available version of this package in this distribution channel.
A freeform string denoting the maintainer of this package.
The distribution channel-specific homepage for this package.
The distribution channel-specific description of this package.
MUST match https://github.com/secure-systems-lab/dsse/blob/master/envelope.proto. An authenticated message of arbitrary type.
Used in:
,Used in:
,Container message for hashes of byte content of files, used in source messages to verify integrity of source input to the build.
Used in:
Required. Collection of file hashes.
Indicates the location at which a package was found.
Used in:
,For jars that are contained inside .war files, this filepath can indicate the path to war file combined with the path to jar file.
Each package found in a file should have its own layer metadata (that is, information from the origin layer of the package).
A set of properties that uniquely identify a given Docker image.
Used in:
,Required. The layer ID of the final layer in the Docker image's v1 representation.
Required. The ordered list of v2 blobs that represent a given image.
Output only. The name of the image's v2 blobs computed via: [bottom] := v2_blob[bottom] [N] := sha256(v2_blob[N] + " " + v2_name[N+1]) Only the name of the final blob is kept.
A SourceContext referring to a Gerrit project.
Used in:
The URI of a running Gerrit instance.
The full project name within the host. Projects may be nested, so "project/subproject" is a valid project name. The "repo name" is the hostURI/project.
A revision in a Gerrit project can be identified by either its revision ID or its alias.
A revision (commit) ID.
An alias, which may be a branch or tag.
A GitSourceContext denotes a particular revision in a third party Git repository (e.g., GitHub).
Used in:
Git repository URL.
Git commit hash.
Container message for hash values.
Used in:
Required. The type of hash that was performed, e.g. "SHA-256".
Required. The hash value.
Basis describes the base image portion (Note) of the DockerImage relationship. Linked occurrences are derived from this or an equivalent image via: FROM <Basis.resource_url> Or an equivalent reference, e.g., a tag of the resource_url.
Used in:
Required. Immutable. The resource_url for the resource representing the basis of associated occurrence images.
Required. Immutable. The fingerprint of the base image.
Details of the derived image portion of the DockerImage relationship. This image would be produced from a Dockerfile with FROM <DockerImage.Basis in attached Note>.
Used in:
Required. The fingerprint of the derived image.
Output only. The number of layers by which this image differs from the associated image basis.
This contains layer-specific metadata, if populated it has length "distance" and is ordered with [distance] being the layer immediately following the base image and [1] being the final layer.
Output only. This contains the base image URL for the derived image occurrence.
Used in:
,required
Identifies the configuration used for the build. When combined with materials, this SHOULD fully describe the build, such that re-running this recipe results in bit-for-bit identical output (if the build is reproducible).
required
The collection of artifacts that influenced the build including sources, dependencies, build tools, base images, and so on. This is considered to be incomplete unless metadata.completeness.materials is true. Unset or null is equivalent to empty.
Used in:
InToto spec defined at https://github.com/in-toto/attestation/tree/main/spec#statement
Used in:
Used in:
Used in:
Used in:
, ,Used in:
Keep in sync with schema at https://github.com/slsa-framework/slsa/blob/main/docs/provenance/schema/v1/provenance.proto Builder renamed to ProvenanceBuilder because of Java conflicts.
Used in:
Spec defined at https://github.com/in-toto/attestation/tree/main/spec#statement The serialized InTotoStatement will be stored as Envelope.payload. Envelope.payloadType is always "application/vnd.in-toto+json".
Used in:
,Always `https://in-toto.io/Statement/v0.1`.
`https://slsa.dev/provenance/v0.1` for SlsaProvenance.
Used in:
The compact encoding of a JWS, which is always three base64 encoded strings joined by periods. For details, see: https://tools.ietf.org/html/rfc7515.html#section-3.1
Layer holds metadata specific to a layer of a Docker image.
Used in:
Required. The recovered Dockerfile directive used to construct this layer. See https://docs.docker.com/engine/reference/builder/ for more information.
The recovered arguments to the Dockerfile directive.
Details about the layer a package was found in.
Used in:
The index of the layer in the container image.
The diff ID (typically a sha256 hash) of the layer in the container image.
The layer chain ID (sha256 hash) of the layer in the container image. https://github.com/opencontainers/image-spec/blob/main/config.md#layer-chainid
The layer build command that was used to build the layer. This may not be found in all layers depending on how the container image is built.
The base images the layer is found within.
License information.
Used in:
,Often a single license can be used to represent the licensing terms. Sometimes it is necessary to include a choice of one or more licenses or some combination of license identifiers. Examples: "LGPL-2.1-only OR MIT", "LGPL-2.1-only AND MIT", "GPL-2.0-or-later WITH Bison-exception-2.2".
Comments
An occurrence of a particular package installation found within a system's filesystem. E.g., glibc was found in `/var/lib/dpkg/status`.
Used in:
Deprecated. The CPE URI in [CPE format](https://cpe.mitre.org/specification/)
Deprecated. The version installed at this location.
The path from which we gathered that this package/version is installed.
Other properties of the build.
Used in:
Identifies the particular build invocation, which can be useful for finding associated logs or other ad-hoc analysis. The value SHOULD be globally unique, per in-toto Provenance spec.
The timestamp of when the build started.
The timestamp of when the build completed.
Indicates that the builder claims certain fields in this message to be complete.
If true, the builder claims that running the recipe on materials will produce bit-for-bit identical output.
Details about files that caused a compliance check to fail.
display_command is a single command that can be used to display a list of non compliant files. When there is no such command, we can also iterate a list of non compliant file using 'path'.
Used in:
Empty if `display_command` is set.
Command to display the non-compliant files.
Explains why a file is non compliant for a CIS check.
A type of analysis that can be done for a resource.
Used as response type in: Grafeas.CreateNote, Grafeas.GetNote, Grafeas.GetOccurrenceNote, Grafeas.UpdateNote
Used as field type in:
, , , ,Output only. The name of the note in the form of `projects/[PROVIDER_ID]/notes/[NOTE_ID]`.
A one sentence description of this note.
A detailed description of this note.
Output only. The type of analysis. This field can be used as a filter in list requests.
URLs associated with this note.
Time of expiration for this note. Empty if note does not expire.
Output only. The time this note was created. This field can be used as a filter in list requests.
Output only. The time this note was last updated. This field can be used as a filter in list requests.
Other notes related to this note.
Required. Immutable. The type of analysis this note represents.
A note describing a package vulnerability.
A note describing build provenance for a verifiable build.
A note describing a base image.
A note describing a package hosted by various package managers.
A note describing something that can be deployed.
A note describing the initial analysis of a resource.
A note describing an attestation role.
A note describing available package upgrades.
A note describing a compliance check.
A note describing a dsse attestation note.
A note describing a vulnerability assessment.
A note describing an SBOM reference.
A note describing a secret.
Kind represents the kinds of notes supported.
Used in:
, ,Default value. This value is unused.
The note and occurrence represent a package vulnerability.
The note and occurrence assert build provenance.
This represents an image basis relationship.
This represents a package installed via a package manager.
The note and occurrence track deployment events.
The note and occurrence track the initial discovery status of a resource.
This represents a logical "role" that can attest to artifacts.
This represents an available package upgrade.
This represents a Compliance Note
This represents a DSSE attestation Note
This represents a Vulnerability Assessment.
This represents an SBOM Reference.
This represents a secret.
An instance of an analysis type that has been found on a resource.
Used as response type in: Grafeas.CreateOccurrence, Grafeas.GetOccurrence, Grafeas.UpdateOccurrence
Used as field type in:
, , , , ,Output only. The name of the occurrence in the form of `projects/[PROJECT_ID]/occurrences/[OCCURRENCE_ID]`.
Required. Immutable. A URI that represents the resource for which the occurrence applies. For example, `https://gcr.io/project/image@sha256:123abc` for a Docker image.
Required. Immutable. The analysis note associated with this occurrence, in the form of `projects/[PROVIDER_ID]/notes/[NOTE_ID]`. This field can be used as a filter in list requests.
Output only. This explicitly denotes which of the occurrence details are specified. This field can be used as a filter in list requests.
A description of actions that can be taken to remedy the note.
Output only. The time this occurrence was created.
Output only. The time this occurrence was last updated.
Required. Immutable. Describes the details of the note kind found on this resource.
Describes a security vulnerability.
Describes a verifiable build.
Describes how this resource derives from the basis in the associated note.
Describes the installation of a package on the linked resource.
Describes the deployment of an artifact on a runtime.
Describes when a resource was discovered.
Describes an attestation of an artifact.
Describes an available package upgrade on the linked resource.
Describes a compliance violation on a linked resource.
Describes an attestation of an artifact using dsse.
Describes a specific SBOM reference occurrences.
Describes a secret.
https://github.com/secure-systems-lab/dsse
PackageNote represents a particular package version.
Used in:
The name of the package.
Deprecated. The various channels by which a package is distributed.
The type of package; whether native or non native (e.g., ruby gems, node.js packages, etc.).
The cpe_uri in [CPE format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package. The cpe_uri will be blank for language packages.
The CPU architecture for which packages in this distribution channel were built. Architecture will be blank for language packages.
The version of the package.
A freeform text denoting the maintainer of this package.
The homepage for this package.
The description of this package.
Licenses that have been declared by the authors of the package.
Hash value, typically a file digest, that allows unique identification a specific package.
Details on how a particular software package was installed on a system.
Used in:
The name of the installed package.
All of the places within the filesystem versions of this package have been found.
The type of package; whether native or non native (e.g., ruby gems, node.js packages, etc.).
The cpe_uri in [CPE format](https://cpe.mitre.org/specification/) denoting the package manager version distributing a package. The cpe_uri will be blank for language packages.
The CPU architecture for which packages in this distribution channel were built. Architecture will be blank for language packages.
Licenses that have been declared by the authors of the package.
The version of the package.
Selects a repo using a Google Cloud Platform project ID (e.g., winged-cargo-31) and a repo name within that project.
Used in:
The ID of the project.
The name of the repo. Leave empty for the default repo.
Steps taken to build the artifact. For a TaskRun, typically each container corresponds to one step in the recipe.
Used in:
URI indicating what type of recipe was performed. It determines the meaning of recipe.entryPoint, recipe.arguments, recipe.environment, and materials.
Index in materials containing the recipe steps that are not implied by recipe.type. For example, if the recipe type were "make", then this would point to the source containing the Makefile, not the make program itself. Set to -1 if the recipe doesn't come from a material, as zero is default unset value for int64.
String identifying the entry point into the build. This is often a path to a configuration file and/or a target label within that file. The syntax and meaning are defined by recipe.type. For example, if the recipe type were "make", then this would reference the directory in which to run make as well as which target to use.
Collection of all external inputs that influenced the build on top of recipe.definedInMaterial and recipe.entryPoint. For example, if the recipe type were "make", then this might be the flags passed to make aside from the target, which is captured in recipe.entryPoint. Since the arguments field can greatly vary in structure, depending on the builder and recipe type, this is of form "Any".
Any other builder-controlled inputs necessary for correctly evaluating the recipe. Usually only needed for reproducing the build but not evaluated as part of policy. Since the environment field can greatly vary in structure, depending on the builder and recipe type, this is of form "Any".
Metadata for any related URL information.
Used in:
, , , ,Specific URL associated with the resource.
Label to describe usage of the URL.
A unique identifier for a Cloud Repo.
Used in:
A cloud repo can be identified by either its project ID and repository name combination, or its globally unique identifier.
A combination of a project ID and a repo name.
A server-assigned, globally unique identifier.
The note representing an SBOM reference.
Used in:
The format that SBOM takes. E.g. may be spdx, cyclonedx, etc...
The version of the format that the SBOM takes. E.g. if the format is spdx, the version may be 2.3.
The occurrence representing an SBOM reference as applied to a specific resource. The occurrence follows the DSSE specification. See https://github.com/secure-systems-lab/dsse/blob/master/envelope.md for more details.
Used in:
The actual payload that contains the SBOM reference data.
The kind of payload that SbomReferenceIntotoPayload takes. Since it's in the intoto format, this value is expected to be 'application/vnd.in-toto+json'.
The signatures over the payload.
The actual payload that contains the SBOM Reference data. The payload follows the intoto statement specification. See https://github.com/in-toto/attestation/blob/main/spec/v1.0/statement.md for more details.
Used in:
Identifier for the schema of the Statement.
URI identifying the type of the Predicate.
Set of software artifacts that the attestation applies to. Each element represents a single software artifact.
Additional parameters of the Predicate. Includes the actual data about the SBOM.
A predicate which describes the SBOM being referenced.
Used in:
The person or system referring this predicate to the consumer.
The location of the SBOM.
The mime type of the SBOM.
A map of algorithm to digest of the contents of the SBOM.
Kind of secret.
Used in:
Unspecified
The secret kind is unknown.
A GCP service account key per: https://cloud.google.com/iam/docs/creating-managing-service-account-keys
The location of the secret.
Used in:
The detailed location of the secret.
The secret is found from a file.
The note representing a secret.
Used in:
(message has no fields)
The occurrence provides details of a secret.
Used in:
Type of secret.
Locations where the secret is detected.
Status of the secret.
The status of the secret with a timestamp.
Used in:
The status of the secret.
The time the secret status was last updated.
Optional message about the status code.
The status of the secret.
Used in:
Unspecified
The status of the secret is unknown.
The secret is valid.
The secret is invalid.
Note provider assigned severity/impact ranking.
Used in:
, , , ,Unknown.
Minimal severity.
Low severity.
Medium severity.
High severity.
Critical severity.
Verifiers (e.g. Kritis implementations) MUST verify signatures with respect to the trust anchors defined in policy (e.g. a Kritis policy). Typically this means that the verifier has been configured with a map from `public_key_id` to public key material (and any required parameters, e.g. signing algorithm). In particular, verification implementations MUST NOT treat the signature `public_key_id` as anything more than a key lookup hint. The `public_key_id` DOES NOT validate or authenticate a public key; it only provides a mechanism for quickly selecting a public key ALREADY CONFIGURED on the verifier through a trusted channel. Verification implementations MUST reject signatures in any of the following circumstances: * The `public_key_id` is not recognized by the verifier. * The public key that `public_key_id` refers to does not verify the signature with respect to the payload. The `signature` contents SHOULD NOT be "attached" (where the payload is included with the serialized `signature` bytes). Verifiers MUST ignore any "attached" payload and only verify signatures with respect to explicitly provided payload (e.g. a `payload` field on the proto message that holds this Signature, or the canonical serialization of the proto message that holds this signature).
Used in:
The content of the signature, an opaque bytestring. The payload that this signature verifies MUST be unambiguously provided with the Signature during verification. A wrapper message might provide the payload explicitly. Alternatively, a message might have a canonical serialization that can always be unambiguously computed to derive the payload.
The identifier for the public key that verifies this signature. * The `public_key_id` is required. * The `public_key_id` SHOULD be an RFC3986 conformant URI. * When possible, the `public_key_id` SHOULD be an immutable reference, such as a cryptographic digest. Examples of valid `public_key_id`s: OpenPGP V4 public key fingerprint: * "openpgp4fpr:74FAF3B861BDA0870C7B6DEF607E48D2A663AEEA" See https://www.iana.org/assignments/uri-schemes/prov/openpgp4fpr for more details on this scheme. RFC6920 digest-named SubjectPublicKeyInfo (digest of the DER serialization): * "ni:///sha-256;cD9o9Cq6LG3jD0iKXqEi_vdjJGecm_iXkbqVoScViaU" * "nih:///sha-256;703f68f42aba2c6de30f488a5ea122fef76324679c9bf89791ba95a1271589a5"
Used in:
required
Identifies the configuration used for the build. When combined with materials, this SHOULD fully describe the build, such that re-running this recipe results in bit-for-bit identical output (if the build is reproducible).
required
The collection of artifacts that influenced the build including sources, dependencies, build tools, base images, and so on. This is considered to be incomplete unless metadata.completeness.materials is true. Unset or null is equivalent to empty.
Used in:
Used in:
Indicates that the builder claims certain fields in this message to be complete.
Used in:
If true, the builder claims that recipe.arguments is complete, meaning that all external inputs are properly captured in the recipe.
If true, the builder claims that recipe.environment is claimed to be complete.
If true, the builder claims that materials are complete, usually through some controls to prevent network access. Sometimes called "hermetic".
Other properties of the build.
Used in:
Identifies the particular build invocation, which can be useful for finding associated logs or other ad-hoc analysis. The value SHOULD be globally unique, per in-toto Provenance spec.
The timestamp of when the build started.
The timestamp of when the build completed.
Indicates that the builder claims certain fields in this message to be complete.
If true, the builder claims that running the recipe on materials will produce bit-for-bit identical output.
Steps taken to build the artifact. For a TaskRun, typically each container corresponds to one step in the recipe.
Used in:
URI indicating what type of recipe was performed. It determines the meaning of recipe.entryPoint, recipe.arguments, recipe.environment, and materials.
Index in materials containing the recipe steps that are not implied by recipe.type. For example, if the recipe type were "make", then this would point to the source containing the Makefile, not the make program itself. Set to -1 if the recipe doesn't come from a material, as zero is default unset value for int64.
String identifying the entry point into the build. This is often a path to a configuration file and/or a target label within that file. The syntax and meaning are defined by recipe.type. For example, if the recipe type were "make", then this would reference the directory in which to run make as well as which target to use.
Collection of all external inputs that influenced the build on top of recipe.definedInMaterial and recipe.entryPoint. For example, if the recipe type were "make", then this might be the flags passed to make aside from the target, which is captured in recipe.entryPoint. Depending on the recipe Type, the structure may be different.
Any other builder-controlled inputs necessary for correctly evaluating the recipe. Usually only needed for reproducing the build but not evaluated as part of policy. Depending on the recipe Type, the structure may be different.
See full explanation of fields at slsa.dev/provenance/v0.2.
Used in:
Identifies the entity that executed the recipe, which is trusted to have correctly performed the operation and populated this provenance.
Used in:
Indicates that the builder claims certain fields in this message to be complete.
Used in:
Describes where the config file that kicked off the build came from. This is effectively a pointer to the source where buildConfig came from.
Used in:
Identifies the event that kicked off the build.
Used in:
The collection of artifacts that influenced the build including sources, dependencies, build tools, base images, and so on.
Used in:
Other properties of the build.
Used in:
Source describes the location of the source used for the build.
Used in:
If provided, the input binary artifacts for the build came from this location.
Hash(es) of the build source, which can be used to verify that the original source integrity was maintained in the build. The keys to this map are file paths used as build source and the values contain the hash values for those files. If the build source came in a single package such as a gzipped tarfile (.tar.gz), the FileHash will be for the single path to that file.
If provided, the source code used for the build came from this location.
If provided, some of the source code used for the build may be found in these locations, in the case where the source repository had multiple remotes or submodules. This list will not include the context specified in the context field.
A SourceContext is a reference to a tree of files. A SourceContext together with a path point to a unique revision of a single file or directory.
Used in:
A SourceContext can refer any one of the following types of repositories.
A SourceContext referring to a revision in a Google Cloud Source Repo.
A SourceContext referring to a Gerrit project.
A SourceContext referring to any third party Git repo (e.g., GitHub).
Labels with user defined metadata.
Used in:
, ,`"<ALGORITHM>": "<HEX_VALUE>"` Algorithms can be e.g. sha256, sha512 See https://github.com/in-toto/attestation/blob/main/spec/field_types.md#DigestSet
The Upgrade Distribution represents metadata about the Upgrade for each operating system (CPE). Some distributions have additional metadata around updates, classifying them into various categories and severities.
Used in:
,Required - The specific operating system this metadata applies to. See https://cpe.mitre.org/specification/.
The operating system classification of this Upgrade, as specified by the upstream operating system upgrade feed. For Windows the classification is one of the category_ids listed at https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ff357803(v=vs.85)
The severity as specified by the upstream operating system.
The cve tied to this Upgrade.
An Upgrade Note represents a potential upgrade of a package to a given version. For each package version combination (i.e. bash 4.0, bash 4.1, bash 4.1.2), there will be an Upgrade Note. For Windows, windows_update field represents the information related to the update.
Used in:
Required for non-Windows OS. The package this Upgrade is for.
Required for non-Windows OS. The version of the package in machine + human readable form.
Metadata about the upgrade for each specific operating system.
Required for Windows OS. Represents the metadata about the Windows update.
An Upgrade Occurrence represents that a specific resource_url could install a specific upgrade. This presence is supplied via local sources (i.e. it is present in the mirror and the running system has noticed its availability). For Windows, both distribution and windows_update contain information for the Windows update.
Used in:
Required for non-Windows OS. The package this Upgrade is for.
Required for non-Windows OS. The version of the package in a machine + human readable form.
Metadata about the upgrade for available for the specific operating system for the resource_url. This allows efficient filtering, as well as making it easier to use the occurrence.
Required for Windows OS. Represents the metadata about the Windows update.
Version contains structured information about the version of a package.
Used in:
, , , , , , ,Used to correct mistakes in the version numbering scheme.
Required only when version kind is NORMAL. The main part of the version name.
The iteration of the package build from the above version.
Whether this version is specifying part of an inclusive range. Grafeas does not have the capability to specify version ranges; instead we have fields that specify start version and end versions. At times this is insufficient - we also need to specify whether the version is included in the range or is excluded from the range. This boolean is expected to be set to true when the version is included in a range.
Required. Distinguishes between sentinel MIN/MAX versions and normal versions.
Human readable version string. This string is of the form <epoch>:<name>-<revision> and is only set when kind is NORMAL.
Whether this is an ordinary package version or a sentinel MIN/MAX version.
Used in:
Unknown.
A standard package version.
A special version representing negative infinity.
A special version representing positive infinity.
A single VulnerabilityAssessmentNote represents one particular product's vulnerability assessment for one CVE.
Used in:
The title of the note. E.g. `Vex-Debian-11.4`
A one sentence description of this Vex.
A detailed description of this Vex.
Identifies the language used by this document, corresponding to IETF BCP 47 / RFC 5646.
Publisher details of this Note.
The product affected by this vex.
Represents a vulnerability assessment for the product.
Assessment provides all information that is related to a single vulnerability for this product.
Used in:
Holds the MITRE standard Common Vulnerabilities and Exposures (CVE) tracking number for the vulnerability. Deprecated: Use vulnerability_id instead to denote CVEs.
The vulnerability identifier for this Assessment. Will hold one of common identifiers e.g. CVE, GHSA etc.
A one sentence description of this Vex.
A detailed description of this Vex.
Holds a list of references associated with this vulnerability item and assessment. These uris have additional information about the vulnerability and the assessment itself. E.g. Link to a document which details how this assessment concluded the state of this vulnerability.
Provides the state of this Vulnerability assessment.
Contains information about the impact of this vulnerability, this will change with time.
Justification provides the justification when the state of the assessment if NOT_AFFECTED.
Specifies details on how to handle (and presumably, fix) a vulnerability.
Justification provides the justification when the state of the assessment if NOT_AFFECTED.
Used in:
,The justification type for this vulnerability.
Additional details on why this justification was chosen.
Provides the type of justification.
Used in:
JUSTIFICATION_TYPE_UNSPECIFIED.
The vulnerable component is not present in the product.
The vulnerable code is not present. Typically this case occurs when source code is configured or built in a way that excludes the vulnerable code.
The vulnerable code can not be executed. Typically this case occurs when the product includes the vulnerable code but does not call or use the vulnerable code.
The vulnerable code cannot be controlled by an attacker to exploit the vulnerability.
The product includes built-in protections or features that prevent exploitation of the vulnerability. These built-in protections cannot be subverted by the attacker and cannot be configured or disabled by the user. These mitigations completely prevent exploitation based on known attack vectors.
Specifies details on how to handle (and presumably, fix) a vulnerability.
Used in:
,The type of remediation that can be applied.
Contains a comprehensive human-readable discussion of the remediation.
Contains the URL where to obtain the remediation.
The type of remediation that can be applied.
Used in:
No remediation type specified.
A MITIGATION is available.
No fix is planned.
Not available.
A vendor fix is available.
A workaround is available.
Provides the state of this Vulnerability assessment.
Used in:
,No state is specified.
This product is known to be affected by this vulnerability.
This product is known to be not affected by this vulnerability.
This product contains a fix for this vulnerability.
It is not known yet whether these versions are or are not affected by the vulnerability. However, it is still under investigation.
Product contains information about a product and how to uniquely identify it. (-- api-linter: core::0123::resource-annotation=disabled aip.dev/not-precedent: Product is not a separate resource. --)
Used in:
Name of the product.
Token that identifies a product so that it can be referred to from other parts in the document. There is no predefined format as long as it uniquely identifies a group in the context of the current document.
Contains a URI which is vendor-specific. Example: The artifact repository URL of an image.
Publisher contains information about the publisher of this Note. (-- api-linter: core::0123::resource-annotation=disabled aip.dev/not-precedent: Publisher is not a separate resource. --)
Used in:
Name of the publisher. Examples: 'Google', 'Google Cloud Platform'.
Provides information about the authority of the issuing party to release the document, in particular, the party's constituency and responsibilities or other obligations.
The context or namespace. Contains a URL which is under control of the issuing party and can be used as a globally unique identifier for that issuing party. Example: https://csaf.io
A security vulnerability that can be found in resources.
Used in:
The CVSS score of this vulnerability. CVSS score is on a scale of 0 - 10 where 0 indicates low severity and 10 indicates high severity.
The note provider assigned severity of this vulnerability.
Details of all known distros and packages affected by this vulnerability.
The full description of the CVSSv3 for this vulnerability.
Windows details get their own format because the information format and model don't match a normal detail. Specifically Windows updates are done as patches, thus Windows vulnerabilities really are a missing package, rather than a package being at an incorrect version.
The time this information was last changed at the source. This is an upstream timestamp from the underlying information source - e.g. Ubuntu security tracker.
CVSS version used to populate cvss_score and severity.
The full description of the v2 CVSS for this vulnerability.
A detail for a distro and package affected by this vulnerability and its associated fix (if one is available).
Used in:
The distro assigned severity of this vulnerability.
A vendor-specific description of this vulnerability.
The type of package; whether native or non native (e.g., ruby gems, node.js packages, etc.).
Required. The [CPE URI](https://cpe.mitre.org/specification/) this vulnerability affects.
Required. The package this vulnerability affects.
The version number at the start of an interval in which this vulnerability exists. A vulnerability can affect a package between version numbers that are disjoint sets of intervals (example: [1.0.0-1.1.0], [2.4.6-2.4.8] and [4.5.6-4.6.8]) each of which will be represented in its own Detail. If a specific affected version is provided by a vulnerability database, affected_version_start and affected_version_end will be the same in that Detail.
The version number at the end of an interval in which this vulnerability exists. A vulnerability can affect a package between version numbers that are disjoint sets of intervals (example: [1.0.0-1.1.0], [2.4.6-2.4.8] and [4.5.6-4.6.8]) each of which will be represented in its own Detail. If a specific affected version is provided by a vulnerability database, affected_version_start and affected_version_end will be the same in that Detail.
The distro recommended [CPE URI](https://cpe.mitre.org/specification/) to update to that contains a fix for this vulnerability. It is possible for this to be different from the affected_cpe_uri.
The distro recommended package to update to that contains a fix for this vulnerability. It is possible for this to be different from the affected_package.
The distro recommended version to update to that contains a fix for this vulnerability. Setting this to VersionKind.MAXIMUM means no such version is yet available.
Whether this detail is obsolete. Occurrences are expected not to point to obsolete details.
The time this information was last changed at the source. This is an upstream timestamp from the underlying information source - e.g. Ubuntu security tracker.
The source from which the information in this Detail was obtained.
The name of the vendor of the product.
Used in:
Required. The [CPE URI](https://cpe.mitre.org/specification/) this vulnerability affects.
Required. The name of this vulnerability.
The description of this vulnerability.
Required. The names of the KBs which have hotfixes to mitigate this vulnerability. Note that there may be multiple hotfixes (and thus multiple KBs) that mitigate a given vulnerability. Currently any listed KBs presence is considered a fix.
Used in:
The KB name (generally of the form KB[0-9]+ (e.g., KB123456)).
A link to the KB in the [Windows update catalog] (https://www.catalog.update.microsoft.com/).
An occurrence of a severity vulnerability on a resource.
Used in:
The type of package; whether native or non native (e.g., ruby gems, node.js packages, etc.).
Output only. The note provider assigned severity of this vulnerability.
Output only. The CVSS score of this vulnerability. CVSS score is on a scale of 0 - 10 where 0 indicates low severity and 10 indicates high severity.
The cvss v3 score for the vulnerability.
Required. The set of affected locations and their fixes (if available) within the associated resource.
Output only. A one sentence description of this vulnerability.
Output only. A detailed description of this vulnerability.
Output only. URLs related to this vulnerability.
The distro assigned severity for this vulnerability when it is available, otherwise this is the note provider assigned severity. When there are multiple PackageIssues for this vulnerability, they can have different effective severities because some might be provided by the distro while others are provided by the language ecosystem for a language pack. For this reason, it is advised to use the effective severity on the PackageIssue level. In the case where multiple PackageIssues have differing effective severities, this field should be the highest severity for any of the PackageIssues.
Output only. Whether at least one of the affected packages has a fix available.
Output only. CVSS version used to populate cvss_score and severity.
The cvss v2 score for the vulnerability.
Occurrence-specific extra details about the vulnerability.
A detail for a distro and package this vulnerability occurrence was found in and its associated fix (if one is available).
Used in:
Required. The [CPE URI](https://cpe.mitre.org/specification/) this vulnerability was found in.
Required. The package this vulnerability was found in.
Required. The version of the package that is installed on the resource affected by this vulnerability.
The [CPE URI](https://cpe.mitre.org/specification/) this vulnerability was fixed in. It is possible for this to be different from the affected_cpe_uri.
The package this vulnerability was fixed in. It is possible for this to be different from the affected_package.
Required. The version of the package this vulnerability was fixed in. Setting this to VersionKind.MAXIMUM means no fix is yet available.
Output only. Whether a fix is available for this package.
The type of package (e.g. OS, MAVEN, GO).
The distro or language system assigned severity for this vulnerability when that is available and note provider assigned severity when it is not available.
The location at which this package was found.
VexAssessment provides all publisher provided Vex information that is related to this vulnerability.
Used in:
Holds the MITRE standard Common Vulnerabilities and Exposures (CVE) tracking number for the vulnerability. Deprecated: Use vulnerability_id instead to denote CVEs.
The vulnerability identifier for this Assessment. Will hold one of common identifiers e.g. CVE, GHSA etc.
Holds a list of references associated with this vulnerability item and assessment.
The VulnerabilityAssessment note from which this VexAssessment was generated. This will be of the form: `projects/[PROJECT_ID]/notes/[NOTE_ID]`. (-- api-linter: core::0122::name-suffix=disabled aip.dev/not-precedent: The suffix is kept for consistency. --)
Provides the state of this Vulnerability assessment.
Contains information about the impact of this vulnerability, this will change with time.
Specifies details on how to handle (and presumably, fix) a vulnerability.
Justification provides the justification when the state of the assessment if NOT_AFFECTED.
Windows Update represents the metadata about the update for the Windows operating system. The fields in this message come from the Windows Update API documented at https://docs.microsoft.com/en-us/windows/win32/api/wuapi/nn-wuapi-iupdate.
Used in:
,Required - The unique identifier for the update.
The localized title of the update.
The localized description of the update.
The list of categories to which the update belongs.
The Microsoft Knowledge Base article IDs that are associated with the update.
The hyperlink to the support information for the update.
The last published timestamp of the update.
The category to which the update belongs.
Used in:
The identifier of the category.
The localized name of the category.
The unique identifier of the update.
Used in:
The revision independent identifier of the update.
The revision number of the update.