cleanstart/cosign repository overview

Container Documentation for Cosign

Cosign is a container signing, verification, and storage solution designed to make supply chain security easier and more robust. It enables cryptographic signing and verification of container images, helping organizations maintain software supply chain integrity and implement secure container deployment practices.

📌 Base Foundation: Security-hardened, minimal base OS designed for enterprise containerized environments from Cleanstart Registry.

Key Features Core capabilities and strengths of this container

• Container image signing and verification
• Support for hardware security modules (HSM)
• Integration with OCI registries
• Keyless signing capabilities

Common Use Cases Typical scenarios where this container excels

• Software supply chain security
• Container image integrity verification
• CI/CD pipeline security
• Regulatory compliance requirements

Pull Latest Image Download the container image from the registry

docker pull cleanstart/cosign:latest

docker pull cleanstart/cosign:latest-dev

Basic Run Run the container with basic configuration

docker run -it --name cosign-test cleanstart/cosign:latest-dev

Production Deployment Deploy with production security settings

docker run -d --name cosign-prod \
  --read-only \
  --security-opt=no-new-privileges \
  --user 1000:1000 \
  cleanstart/cosign:latest

Volume Mount Mount local directory for persistent data

docker run -v $(pwd)/keys:/keys cleanstart/cosign:latest

Port Forwarding Run with custom port mappings

docker run -p 8080:80 cleanstart/cosign:latest

Environment Variables Configuration options available through environment variables

Security Best Practices Recommended security configurations and practices

• Use hardware security modules (HSM) for key storage
• Implement proper key management procedures
• Enable signature verification in CI/CD pipelines
• Regularly rotate signing keys
• Use separate keys for development and production
• Implement proper access controls for signing keys

Kubernetes Security Context Recommended security context for Kubernetes deployments

securityContext:
  runAsNonRoot: true
  runAsUser: 1000
  runAsGroup: 1000
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false
  capabilities:
    drop: ["ALL"]

Multi-Platform Images

docker pull --platform linux/amd64 cleanstart/cosign:latest
docker pull --platform linux/arm64 cleanstart/cosign:latest

⁠Documentation Resources

Essential links and resources for further information

CleanStart Images: https://images.cleanstart.com/⁠

Community Images:
Docker Hub: https://hub.docker.com/u/cleanstart⁠
GitHub: https://github.com/cleanstart-containers⁠
AWS ECR Public Gallery: https://gallery.ecr.aws/cleanstart/⁠

Presence on Social Media:
Community: https://www.linkedin.com/groups/18324021/⁠
YouTube: https://www.youtube.com/@CleanStartOfficial⁠

Contribute to Container Use Cases: https://github.com/cleanstart-dev/cleanstart-use-cases/⁠

Vulnerability Disclaimer

CleanStart offers Docker images that include third-party open-source libraries and packages maintained by independent contributors. While CleanStart maintains these images and applies industry-standard security practices, it cannot guarantee the security or integrity of upstream components beyond its control.

Users acknowledge and agree that open-source software may contain undiscovered vulnerabilities or introduce new risks through updates. CleanStart shall not be liable for security issues originating from third-party libraries, including but not limited to zero-day exploits, supply chain attacks, or contributor-introduced risks.

Security remains a shared responsibility: CleanStart provides updated images and guidance where possible, while users are responsible for evaluating deployments and implementing appropriate controls.