implementing-supply-chain-security-with-in-toto
FeaturedImplement software supply chain integrity verification for container builds using the in-toto framework to create cryptographically signed attestations across CI/CD pipeline steps.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- mukul975
- Repository
- mukul975/Anthropic-Cybersecurity-Skills
- Created
- 8 months ago
- Last Updated
- 2 months ago
- Language
- Python
- License
- Apache-2.0
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
supply-chain
Harden the software supply chain and add security scanning to CI — pinning, Renovate or Dependabot, SCA, SAST, secret, IaC and container scanning, SBOM, signing, SLSA provenance, license policy — with severity gates, GitHub Actions by default. Use for "add security scanning", "generate an SBOM", "sign our images".
supply-chain
Use when auditing security and supply chain in any codebase — trust boundaries, credential handling, injection surfaces, update/release integrity, CI permissions, dependency pinning. Assess by default, harden on request; provenance or it didn't happen.
java-supply-chain-security
Use when reviewing Maven or Gradle dependency risk, SBOM coverage, vulnerability findings, or Java release provenance. Covers compatible remediation and CI trust boundaries; container runtime configuration belongs to the deployment skill.