Sigscan is a tool to primarily discover and report signed container images within a registry. Any OCI-compliant registry is supported for Sigstore/cosign signatures as well as registries that support OCI artifacts (currently ACR, ECR, oras-project/registry, and Zot)
For Sigstore/cosign signatures we are following the Signature spec and detecting any optional PEM-encoded x509 certificates.
For OCI Artifacts and NotaryV2 signatures we are following the Signature Specification and detecting any Signature Manifest where artifact type is application/vnd.cncf.notary.signature. From there we are extracting annotations that have the io.cncf.notary.x509chain.thumbprint#S256 metadata.
Sigscan can also be used to scan the filesystem to discover and report on signed JAR as well as EXE files. Sigscan will extract the signer certificate subjectname as well as the countersigner/timestamp (if available) subjectname.
Sigscan is made available under the Apache 2.0 license, see LICENSE.
| Name | Compatibility | Notes |
|---|---|---|
| ghcr.io | ✔️ | |
| docker.io | ✔️ | |
| ACR | ✔️ | |
| Docker Registry V2 | ✔️ | |
| ORAS Project registry v1.0.0-rc.3 | ✔️ | |
| Zot v1.4.3 | ✔️ | |
| ECR (private) | ✔️ | |
| ECR (public) | ✔️ | us-east-1 only per AWS CLI issue |
| GCR (public) | ✔️ | |
| GCR (private) | ❌ | |
| GAR | ✔️ | Non-compliant Referrers API |
| Type | Compatibility | Notes |
|---|---|---|
| JAR | ✔️ | |
| EXE | ✔️ |
| Type | Compatibility | Notes |
|---|---|---|
| OWASP CycloneDX | ✔️ | application/vnd.cyclonedx |
| Linux Foundation SPDX | ✔️ | application/spdx+json |
| OASIS SARIF | ✔️ | application/sarif+json |
On macOS and Linux, if you have Homebrew you can install Sigscan with:
brew install venafi/tap/sigscanThis will also install man pages and shell completion.
Binaries for common platforms and architectures are provided on the releases.
Man pages are also attached to the release.
You can generate shell completion from Sigscan itself with sigscan completion.
If you have Go installed you can install Sigscan using Go directly.
go install github.com/venafi/sigscan@latestSigscan can be used to list out details of all the signed container images in the registry:
Make sure you are authenticated to the registry as needed.
Note: If you are on Windows ANSI Terminal Control support (introduced in Windows 10 console build 16257 and later) is not enabled by default. This will affect the table view when using the displaying the output table via --output pretty. Run sigscan in a PowerShell console as opposed to a CMD console. A workaround exists by running the following in Admin Mode:
Set-ItemProperty HKCU:\Console VirtualTerminalLevel -Type DWORD 1
$ sigscan repo myregistry --output pretty --username myuser --password supersecretpasswordInspecting an organization's ECR public repositories:
$ sigscan repo public.ecr.aws --output prettyInspecting an organization's GHCR repositories:
$ sigscan repo ghcr.io --output pretty --org myorg --username myuser --password supersecretpasswordExport them for further audit:
$ sigscan repo localhost:5010 --output json --insecure | jq '.registry.signatures[].subjectname'
"CN=dev.venafidemo.com,OU=Solution Architects,O=Venafi\\, Inc.,L=San Jose,ST=CA,C=US"
"CN=dev.venafidemo.com,OU=Solution Architects,O=Venafi\\, Inc.,L=San Jose,ST=CA,C=US"Inspecting the filesystem for signed artifacts
$ sigscan fs test/tempdir1/ test/tempdir2 --output json | jqEXE and Jar file types are currently supported
While parts of sigscan are stable, we are continuing to experiment and add new features. The following feature set is not considered stable yet, but we are commiteted to stabilizing it over time!
While the cosign code for uploading, signing, retrieving, and verifying several artifact types is stable, the format specifications for some of those types may not be considered stable yet.
These include:
- The SBOM specification for storing SBOMs in a container registry
sigscan provides experimental support for discovery of SBOM (see above for list of tested mediaTypes) signatures via the cosign artifact signature mediatype application/vnd.dev.cosign.artifact.sig.v1+json
Sigscan supports username/password as well as token credentials via the CLI arguments, and also supports the Docker credential store. If no credentials are supplied via the CLI then Sigscan will check the local Docker credential store.
Sigscan will detect certificates/thumbprints in most cases However, there are some limitations to bear in mind while using Sigscan:
- Sigscan supports HTTP (insecure) as well as HTTPS endpoints
- Sigscan supports Sigstore/cosign certificates however currently only returns the subject name.
- Sigscan supports NotaryV2 signatures however only returns the SHA256 thumbprint of the certificate. Consumer of this client would be required to validate this thumbprint against a trusted certificate store.
- Sigscan does not verify or validate the signature.
The usage documentation for Sigscan is included in the help text.
Invoke a command with --help for usage instructions, or see the manual pages.
![@dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=64&v=4){kind=small}
