Back to catalog
Static reviewDevelopment

Skill dossier

implementing-sigstore-for-software-signing

Source declaration

Implements Sigstore-based software signing and verification using Cosign keyless signing, Rekor transparency log verification, and Fulcio certificate authority integration to establish cryptographic provenance for container images, binaries, and software artifacts, including OIDC-based identity binding and CI/CD pipeline integration. Use when setting up keyless container/artifact signing, verifying signatures against the Rekor transparency log, or deploying Sigstore in a supply-chain security workflow.

The author's original description, preserved in English. It describes intent, not verified performance.

Implements Sigstore-based software signing and verification using Cosign keyless signing, Rekor transparency log verification, and Fulcio certificate authority integration to establish cryptographic provenance for container images, binaries, and software artifacts, including OIDC-based identity binding and CI/CD pipeline integration. Use when setting up keyless container/artifact signing, verifying signatures against the Rekor transparency log, or deploying Sigstore in a supply-chain security workflow.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Implements Sigstore-based software signing and verification using Cosign keyless signing, Rekor transparency log verification, and Fulcio certificate authority integration to establish cryptographic provenance for container images, binaries, and software artifacts, including OIDC-based identity binding and CI/CD pipeline integration. Use when setting up keyless container/artifact signing, verifying signatures against the Rekor transparency log, or deploying Sigstore in a supply-chain security workflow. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-sigstore-for-software-signing/SKILL.md:L86]
  • Step 1: Install and Configure Cosign [Source statement; provisional, not tested. Evidence: skills/implementing-sigstore-for-software-signing/SKILL.md:L88]
  • Step 2: Keyless Signing with Cosign and Fulcio [Source statement; provisional, not tested. Evidence: skills/implementing-sigstore-for-software-signing/SKILL.md:L96]
  • Step 3: Verify Signed Artifacts [Source statement; provisional, not tested. Evidence: skills/implementing-sigstore-for-software-signing/SKILL.md:L110]
  • Step 4: Query the Rekor Transparency Log [Source statement; provisional, not tested. Evidence: skills/implementing-sigstore-for-software-signing/SKILL.md:L123]
  • Step 5: Integrate into CI/CD Pipelines [Source statement; provisional, not tested. Evidence: skills/implementing-sigstore-for-software-signing/SKILL.md:L134]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-sigstore-for-software-signing/SKILL.md:L1-L65]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
46.5 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-sigstore-for-software-signing/LICENSEOther11 KB
skills/implementing-sigstore-for-software-signing/references/api-reference.mdReference5.1 KB
skills/implementing-sigstore-for-software-signing/scripts/agent.pyScript17.7 KB
skills/implementing-sigstore-for-software-signing/SKILL.mdInstruction12.6 KB

SKILL.md frontmatter

{
  "name": "implementing-sigstore-for-software-signing",
  "description": "Implements Sigstore-based software signing and verification using Cosign keyless signing, Rekor transparency log verification, and Fulcio certificate authority integration to establish cryptographic provenance for container images, binaries, and software artifacts, including OIDC-based identity binding and CI/CD pipeline integration. Use when setting up keyless container/artifact signing, verifying signatures against the Rekor transparency log, or deploying Sigstore in a supply-chain security workflow.\n",
  "domain": "cybersecurity",
  "subdomain": "supply-chain-security",
  "tags": [
    "sigstore",
    "cosign",
    "rekor",
    "fulcio",
    "software-signing",
    "supply-chain",
    "keyless-signing",
    "OIDC",
    "transparency-log"
  ],
  "version": "1.0.0",
  "author": "mukul975",
  "license": "Apache-2.0",
  "nist_csf": [
    "GV.SC-01",
    "GV.SC-03",
    "GV.SC-06",
    "GV.SC-07"
  ],
  "mitre_attack": [
    "T1078",
    "T1190",
    "T1059",
    "T1610",
    "T1611"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "resource-development",
      "initial-access",
      "stealth"
    ],
    "techniques": [
      {
        "id": "T1195",
        "name": "Supply Chain Compromise",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1608",
        "name": "Stage Capabilities",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "T1608.006",
        "name": "Stage Capabilities: SEO Poisoning",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "T1586",
        "name": "Compromise Accounts",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "T1070",
        "name": "Indicator Removal",
        "tactic": "stealth",
        "source": "attack"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Install and Configure Cosign

    Source-described action candidate under “Step 1: Install and Configure Cosign”; not verified execution.

  4. 04
    Action

    Install from binary release: Download the appropriate binary from the Cosign GitHub releases page and verify its checksum. On Linux: `curl -LO https://github.com/sigstore/cosign/releases/latest/download/cosign-linux-amd64 && chmod +x cosign-linux-amd64 && sudo mv cosign-linux-amd64 /usr/local/bin/cosign`

    Source-described action candidate under “Step 1: Install and Configure Cosign”; not verified execution.

  5. 05
    Action

    Verify installation: Run `cosign version` to confirm the version and check connectivity to Sigstore services with `cosign initialize` which fetches the TUF root of trust

    Source-described action candidate under “Step 1: Install and Configure Cosign”; not verified execution.

  6. 06
    Decision

    Configure custom infrastructure (optional): If running a private Sigstore stack, set `--fulcio-url`, `--rekor-url`, and `--oidc-issuer` flags or use environment variables `COSIGNREKORURL` and `COSIGNFULCIOURL`

    Source-described decision candidate under “Step 1: Install and Configure Cosign”; not verified execution.

Inspect all extracted workflow candidates (36 candidate steps)
  1. 07
    Action

    Step 2: Keyless Signing with Cosign and Fulcio

    Source-described action candidate under “Step 2: Keyless Signing with Cosign and Fulcio”; not verified execution.

  2. 08
    Action

    Sign a container image: Run `cosign sign <IMAGEDIGEST>` which triggers an OIDC authentication flow. Cosign generates an ephemeral key pair, obtains a short-lived certificate from Fulcio binding the public key to the OIDC identity, signs the image digest, and records the signing event in Rekor. The private key is destroyed immediately after signing.

    Source-described action candidate under “Step 2: Keyless Signing with Cosign and Fulcio”; not verified execution.

  3. 09
    Action

    Sign a blob (file): Run `cosign sign-blob <file> --bundle artifact.sigstore.json` to sign arbitrary files. The bundle contains the signature, certificate, timestamp, and Rekor inclusion proof.

    Source-described action candidate under “Step 2: Keyless Signing with Cosign and Fulcio”; not verified execution.

  4. 10
    Action

    Non-interactive signing in CI: Set `SIGSTOREIDTOKEN` environment variable with a valid OIDC token (e.g., from GitHub Actions OIDC or GCP workload identity) to skip the browser-based authentication flow:

    Source-described action candidate under “Step 2: Keyless Signing with Cosign and Fulcio”; not verified execution.

  5. 11
    Action

    Supported OIDC providers: Google (`https://accounts.google.com`), GitHub (`https://github.com/login/oauth`), Microsoft (`https://login.microsoftonline.com`), GitLab (`https://gitlab.com`), and custom providers registered with a private Fulcio instance

    Source-described action candidate under “Step 2: Keyless Signing with Cosign and Fulcio”; not verified execution.

  6. 12
    Action

    Step 3: Verify Signed Artifacts

    Source-described action candidate under “Step 3: Verify Signed Artifacts”; not verified execution.

  7. 13
    Action

    Verify a container image: Run `cosign verify <IMAGEURI> [email protected] --certificate-oidc-issuer=https://accounts.google.com` to confirm the image was signed by the specified identity. Cosign validates the certificate chain, checks the Rekor inclusion proof, and verifies the signature matches the current image digest.

    Source-described action candidate under “Step 3: Verify Signed Artifacts”; not verified execution.

  8. 14
    Action

    Verify a signed blob: Run `cosign verify-blob <file> --bundle artifact.sigstore.json [email protected] --certificate-oidc-issuer=https://accounts.google.com`

    Source-described action candidate under “Step 3: Verify Signed Artifacts”; not verified execution.

  9. 15
    Action

    Regex matching for CI identities: Use `--certificate-identity-regexp` to match CI workflow identities:

    Source-described action candidate under “Step 3: Verify Signed Artifacts”; not verified execution.

  10. 16
    Action

    Verification failure modes: Cosign returns a non-zero exit code on failure. Common failures include certificate identity mismatch, expired certificates without a valid Rekor timestamp, missing Rekor entry, and image digest mismatch (image was modified after signing).

    Source-described action candidate under “Step 3: Verify Signed Artifacts”; not verified execution.

  11. 17
    Action

    Step 4: Query the Rekor Transparency Log

    Source-described action candidate under “Step 4: Query the Rekor Transparency Log”; not verified execution.

  12. 18
    Action

    Search by email identity: Use `rekor-cli search --email [email protected]` to find all signing events for an identity

    Source-described action candidate under “Step 4: Query the Rekor Transparency Log”; not verified execution.

  13. 19
    Action

    Search by artifact hash: Use `rekor-cli search --sha sha256:<hash>` to find signing events for a specific artifact

    Source-described action candidate under “Step 4: Query the Rekor Transparency Log”; not verified execution.

  14. 20
    Action

    Retrieve and verify an entry: Use `rekor-cli get --uuid <entryuuid>` to retrieve full entry details including the certificate, signature, and artifact hash

    Source-described action candidate under “Step 4: Query the Rekor Transparency Log”; not verified execution.

  15. 21
    Action

    Verify log inclusion: Use `rekor-cli verify --entry-uuid <uuid>` to verify the entry's inclusion proof against the signed tree head, confirming the entry exists in the append-only log and has not been tampered with

    Source-described action candidate under “Step 4: Query the Rekor Transparency Log”; not verified execution.

  16. 22
    Action

    REST API queries: Query `https://rekor.sigstore.dev/api/v1/index/retrieve` with POST body `{"hash": "sha256:<hash>"}` to retrieve entry UUIDs, then fetch full entries from `/api/v1/log/entries/<uuid>`

    Source-described action candidate under “Step 4: Query the Rekor Transparency Log”; not verified execution.

  17. 23
    Action

    Monitor for consistency: Use the rekor-monitor tool or Omniwitness to continuously verify the log remains append-only and entries are never mutated or removed

    Source-described action candidate under “Step 4: Query the Rekor Transparency Log”; not verified execution.

  18. 24
    Action

    Step 5: Integrate into CI/CD Pipelines

    Source-described action candidate under “Step 5: Integrate into CI/CD Pipelines”; not verified execution.

  19. 25
    Action

    GitHub Actions: Use `sigstore/cosign-installer` action to install Cosign, then sign images using the GitHub OIDC token as the identity. The signing identity will be the workflow URL (e.g., `https://github.com/org/repo/.github/workflows/build.yml@refs/heads/main`).

    Source-described action candidate under “Step 5: Integrate into CI/CD Pipelines”; not verified execution.

  20. 26
    Action

    Kubernetes admission enforcement: Deploy Sigstore Policy Controller or Kyverno with Cosign verification policies to reject unsigned or incorrectly signed images at admission time

    Source-described action candidate under “Step 5: Integrate into CI/CD Pipelines”; not verified execution.

  21. 27
    Action

    Supply chain metadata: Use `cosign attest` to attach in-toto attestations (SLSA provenance, SBOM, vulnerability scan results) to images, signed with the same keyless flow, enabling consumers to verify both the artifact and its build metadata

    Source-described action candidate under “Step 5: Integrate into CI/CD Pipelines”; not verified execution.

  22. 28
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  23. 29
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  24. 30
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  25. 31
    Output

    Add `sigstore/cosign-installer@v3` to the GitHub Actions workflow and enable OIDC token permissions with `id-token: write`

    Source-described output candidate under “Scenario: Securing a Container Image Build Pipeline with Keyless Signing”; not verified execution.

  26. 32
    Action

    After building and pushing the image, sign it with `cosign sign $IMAGEDIGEST` using the GitHub Actions OIDC identity automatically

    Source-described action candidate under “Scenario: Securing a Container Image Build Pipeline with Keyless Signing”; not verified execution.

  27. 33
    Action

    Deploy Sigstore Policy Controller to the Kubernetes cluster with a ClusterImagePolicy requiring signatures from `--certificate-identity-regexp=https://github.com/myorg/myrepo/.` and `--certificate-oidc-issuer=https://token.actions.githubusercontent.com`

    Source-described action candidate under “Scenario: Securing a Container Image Build Pipeline with Keyless Signing”; not verified execution.

  28. 34
    Action

    Verify the signing entry appears in Rekor by querying with the image digest hash to confirm the transparency log recorded the event

    Source-described action candidate under “Scenario: Securing a Container Image Build Pipeline with Keyless Signing”; not verified execution.

  29. 35
    Action

    Test the admission controller by attempting to deploy an unsigned image and confirming it is rejected with a policy violation error

    Source-described action candidate under “Scenario: Securing a Container Image Build Pipeline with Keyless Signing”; not verified execution.

  30. 36
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

49 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

29 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 29 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

19 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 19 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-sigstore-for-software-signing/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/implementing-sigstore-for-software-signing/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-sigstore-for-software-signing
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.