# secure container image Published articles for secure container image. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to transition to secure container images with new migration guides DevFeed: [How to transition to secure container images with new migration guides]() Original publisher: [Read original article]() Published: 2024-05-22T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [migration](), [container images](), [container-security](), [APK](), [Dockerfile](), [Package manager](), [Bash](), [Zsh](), [Debian]() Tags: [and-best-practices](), [apk](), [base-images](), [bash](), [best-practices](), [build](), [chainguard](), [chainguard-images](), [container](), [container-based-application](), [container-images](), [container-security](), [container-security-strategy](), [cves](), [debian](), [dependencies](), [docker-hub-image](), [dockerfiles](), [guides](), [how-to](), [image-migration](), [migration](), [migration-guides](), [python-image](), [secure-container-image](), [secure-container-images]() ### AI overview This guide explains how to migrate container images to Chainguard Images for smaller image sizes, fewer vulnerabilities, and continuous maintenance. It covers using -dev images for shells and package managers, installing bash or zsh when needed, searching for packages with apk, and adapting Dockerfiles and entrypoint scripts. ### Source excerpt Struggling to adopt secure container images? Our new migration guides provide step-by-step instructions and best practices for a smooth transition. ## Chainguard Images April 2024: Secure, reliable, feature-rich DevFeed: [Chainguard Images April 2024: Secure, reliable, feature-rich]() Original publisher: [Read original article]() Published: 2024-05-09T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [supply-chain-security](), [container images](), [Security](), [Open Source](), [FFmpeg (Fast Forward Moving Picture Experts Group)](), [MATLAB](), [Kubernetes]() Tags: [chainguard](), [chainguard-images](), [compliance](), [container-images](), [ffmpeg](), [fips](), [fips-compliance](), [harbor](), [kubernetes](), [open-source](), [release](), [rstudio](), [secure-container-image](), [security](), [software-supply-chain](), [software-supply-chain-security](), [tesseract](), [valkey](), [vulnerability]() ### AI overview Chainguard announces approximately 60 new Chainguard Images in its April 2024 release. The hardened, minimal images focus on software supply chain security, reliability, and reduced CVE exposure, with FIPS variants available for some images. Featured additions include rstudio, Harbor, FFmpeg, Tesseract, and Valkey. ### Source excerpt Explore the latest features and security enhancements in Chainguard Images (April 2024 release). Strengthen your software supply chain. ## A guide on how to use Chainguard Images for public catalog tier users DevFeed: [A guide on how to use Chainguard Images for public catalog tier users]() Original publisher: [Read original article]() Published: 2023-06-23T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [migration](), [supply-chain-security](), [Open Source]() Tags: [chaingaurd-images](), [chainguard](), [chainguard-images](), [container](), [container-image-registry](), [container-images](), [guide](), [how-to](), [images](), [migration](), [open-source](), [open-source-software](), [secure-by-default](), [secure-container-image](), [secure-minimal-image](), [software-supply-chain](), [wolfi]() ### AI overview This guide explains a policy change affecting Chainguard Images public catalog users. From August 16, 2023, public-tier users can pull only the latest tags and continue to pull images by digest; access to other tags requires a Standard or Custom catalog subscription. It describes the impact on existing build processes, authentication errors, migration options, and technical approaches for using images without version tags. ### Source excerpt Learn about the upcoming Chainguard Images catalog changes and the actions required for Public tier users. ## A thought experiment on using low-vulnerability Chainguard Images to speed government software delivery DevFeed: [A thought experiment on using low-vulnerability Chainguard Images to speed government software delivery]() Original publisher: [Read original article]() Published: 2023-06-20T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Containers](), [chainguard images](), [authority to operate](), [vulnerability management](), [chainguard](), [chainguard labs](), [Security]() Tags: [ato](), [authority-to-operate](), [chainguard](), [chainguard-images](), [chainguard-labs](), [container-security](), [containers](), [fedramp](), [government](), [image-cves](), [secure-container-image](), [secure-minimal-image](), [security](), [vulnerability-management](), [vulnerability-scanner]() ### AI overview This opinion article proposes studying whether Chainguard Images with zero-known or low vulnerability counts could reduce timelines and staff costs in government Authority to Operate processes. It presents this as a hypothesis requiring comparison with other ATO processes, not as a demonstrated result. ### Source excerpt Discover how 0-known vulnerability containers from Chainguard Labs could accelerate software delivery to the government. ## Fortify, comply and conquer FedRAMP with Chainguard Images DevFeed: [Fortify, comply and conquer FedRAMP with Chainguard Images]() Original publisher: [Read original article]() Published: 2023-05-25T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [vulnerability scanning](), [container images](), [vulnerability](), [Security](), [supply-chain-security](), [Linux]() Tags: [chainguard-images](), [compliance](), [container-images](), [container-security](), [cve](), [fedramp](), [fips](), [hardened-image](), [linux](), [nist](), [secure-container-image](), [security](), [software-supply-chain](), [vulnerability](), [vulnerability-management](), [vulnerability-scanning]() ### AI overview This article explains how Chainguard Images can help cloud service providers and federal agencies achieve or maintain FedRAMP authorization. It describes FedRAMP requirements for hardened container images, recurring vulnerability scanning, NVD identifiers, CVSSv3 scores, and vulnerability remediation tracking. It presents Chainguard Images as secure, continuously updated base images built from source on the hardened Wolfi Linux un-distribution. ### Source excerpt Learn how Chainguard Images can you achieve or maintain your FedRAMP compliance authorization with secure-by-default base images. ## How to explain the CISA software attestation requirements to your board DevFeed: [How to explain the CISA software attestation requirements to your board]() Original publisher: [Read original article]() Published: 2023-05-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [cisa](), [cybersecurity and infrastructure security agency](), [software bill of materials](), [Security]() Tags: [attestation](), [chainguard](), [cisa](), [container-security](), [government](), [national-cybersecurity-strategy](), [nist](), [policy](), [sbom](), [sboms](), [secure-container-image](), [secure-software](), [self-attestation](), [signing-artifacts](), [sigstore](), [software-artifact-signing](), [software-bill-of-materials](), [software-supply-chain-security](), [ssdf]() ### AI overview This article explains how software companies can brief their boards on CISA software attestation requirements and the broader federal software supply chain security policy landscape. It discusses Executive Order 14028, SBOMs, secure software development, CISA's Secure Software Development Attestation Form, and the requirements in OMB Memorandum M-22-18, including alignment with NIST guidance. ### Source excerpt CISA's draft self-attestation form clarifies the minimum requirements that software developers must meet to comply with OMB Memorandum M-22-18.