# container image compliance

Container image compliance is the practice of assessing container images and enforcing policies that ensure they meet security requirements, such as being free of known vulnerabilities.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## SonarQube container scanning is now generally available

DevFeed: [SonarQube container scanning is now generally available](<https://devfeed.tech/articles/sonarqube-container-scanning-is-now-generally-available-146295.md>)

Original publisher: [Read original article](<https://www.sonarsource.com/blog/sonarqube-container-scanning-is-now-available/>)

Author: Satinder Khasriya

Published: 2026-11-19T14:00:00Z

Content type: release

Language: en

Sources: [Sonar Blog](<https://devfeed.tech/sources/sonar-blog.md>)

Topics: [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container image vulnerabilities](<https://devfeed.tech/topics/container-image-vulnerabilities.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [advanced-security](<https://devfeed.tech/tags/advanced-security.md>), [build](<https://devfeed.tech/tags/build.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [fail](<https://devfeed.tech/tags/fail.md>), [malicious-packages](<https://devfeed.tech/tags/malicious-packages.md>), [organization](<https://devfeed.tech/tags/organization.md>), [results](<https://devfeed.tech/tags/results.md>), [risks](<https://devfeed.tech/tags/risks.md>), [scan](<https://devfeed.tech/tags/scan.md>), [scanner](<https://devfeed.tech/tags/scanner.md>), [scanning](<https://devfeed.tech/tags/scanning.md>), [security](<https://devfeed.tech/tags/security.md>), [sonarqube](<https://devfeed.tech/tags/sonarqube.md>), [sonarqube-advanced-security](<https://devfeed.tech/tags/sonarqube-advanced-security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Container scanning is generally available in SonarQube Advanced Security on SonarQube Cloud for Team and Enterprise plan customers, at no additional cost. It scans built and shipped container images for known vulnerabilities and malicious packages. Results appear under Container images in the organization and use the same workflow as dependency risks. CI builds can be configured to fail when findings meet or exceed a chosen severity. The supplied excerpt does not describe setup steps or scanner limitations.

### Source excerpt

Scan the container images you ship for known vulnerabilities and malicious packages. Now generally available in SonarQube Advanced Security. Learn more

## Enforcing zero-trust dependency policies in AWS CodeBuild with JFrog Curation

DevFeed: [Enforcing zero-trust dependency policies in AWS CodeBuild with JFrog Curation](<https://devfeed.tech/articles/enforcing-zero-trust-dependency-policies-in-aws-codebuild-with-jfrog-curation-139359.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/devops/enforcing-zero-trust-dependency-policies-in-aws-codebuild-with-jfrog-curation/>)

Author: Arik Yakir

Published: 2026-11-17T20:08:18Z

Content type: tutorial

Language: en

Sources: [AWS DevOps & Developer Productivity Blog](<https://devfeed.tech/sources/aws-devops-developer-productivity-blog.md>)

Topics: [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [Jfrog](<https://devfeed.tech/topics/jfrog.md>), [jfrog artifactory](<https://devfeed.tech/topics/jfrog-artifactory.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [jfrog xray](<https://devfeed.tech/topics/jfrog-xray.md>), [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>)

Tags: [403](<https://devfeed.tech/tags/403.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-codebuild](<https://devfeed.tech/tags/aws-codebuild.md>), [block](<https://devfeed.tech/tags/block.md>), [build](<https://devfeed.tech/tags/build.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [curation](<https://devfeed.tech/tags/curation.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [download](<https://devfeed.tech/tags/download.md>), [error](<https://devfeed.tech/tags/error.md>), [http](<https://devfeed.tech/tags/http.md>), [image](<https://devfeed.tech/tags/image.md>), [jfrog](<https://devfeed.tech/tags/jfrog.md>), [policies](<https://devfeed.tech/tags/policies.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [trust](<https://devfeed.tech/tags/trust.md>), [with](<https://devfeed.tech/tags/with.md>), [zero](<https://devfeed.tech/tags/zero.md>), [zero-trust](<https://devfeed.tech/tags/zero-trust.md>)

### AI overview

The walkthrough routes AWS CodeBuild dependency downloads through JFrog Artifactory, where JFrog Curation evaluates packages against policy before serving them. In the PyPI example, pip uses a curated index; a blocked package returns HTTP 403, fails the Docker build, and prevents the image from being pushed to Amazon ECR. The example blocks packages with CVSS scores of 9.0 or above. On failure, post-build scripting can query the Curation audit API for the policy and package details, including CVEs and recommended fixes when audit pass-through is enabled. The setup requires a JFrog tier with Curation, configured PyPI remote and virtual repositories, AWS permissions, and a token stored in Secrets Manager. The article presents Curation as prevention at download time and JFrog Xray as detection for components already present; supported package types include PyPI, npm, Maven, and Docker.

### Source excerpt

Integrate JFrog Curation into an AWS CodeBuild pipeline to block vulnerable and malicious open source packages at download time. A package that violates policy returns an HTTP 403 (Access Denied) error that fails the build, so a risky dependency never becomes a container image or reaches Amazon ECR.

## The Green Agent POV: Formulating the Fix for an Internet-Facing Container with Sensitive Data Access

DevFeed: [The Green Agent POV: Formulating the Fix for an Internet-Facing Container with Sensitive Data Access](<https://devfeed.tech/articles/the-green-agent-pov-formulating-the-fix-for-an-internet-facing-container-with-sensitive-data-access-133499.md>)

Original publisher: [Read original article](<https://www.wiz.io/blog/inside-green-agent-investigation>)

Author: Green Agent

Published: 2026-11-13T17:05:02Z

Content type: article

Language: en

Sources: [Wiz](<https://devfeed.tech/sources/wiz-blog-rss-feed.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [sensitive data](<https://devfeed.tech/topics/sensitive-data.md>), [network security](<https://devfeed.tech/topics/network-security.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>)

Tags: [000](<https://devfeed.tech/tags/000.md>), [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [3](<https://devfeed.tech/tags/3.md>), [agent](<https://devfeed.tech/tags/agent.md>), [business](<https://devfeed.tech/tags/business.md>), [business-continuity](<https://devfeed.tech/tags/business-continuity.md>), [container](<https://devfeed.tech/tags/container.md>), [data](<https://devfeed.tech/tags/data.md>), [green](<https://devfeed.tech/tags/green.md>), [internet](<https://devfeed.tech/tags/internet.md>), [merge](<https://devfeed.tech/tags/merge.md>), [plan](<https://devfeed.tech/tags/plan.md>), [pov](<https://devfeed.tech/tags/pov.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [remediation](<https://devfeed.tech/tags/remediation.md>), [security](<https://devfeed.tech/tags/security.md>), [sensitive-data](<https://devfeed.tech/tags/sensitive-data.md>), [with](<https://devfeed.tech/tags/with.md>), [wiz-agents](<https://devfeed.tech/tags/wiz-agents.md>)

### AI overview

Green Agent investigated a publicly reachable Kubernetes workload whose actively loaded Node.js Brotli vulnerability created a path to an IAM role and more than 5,000 sensitive S3 records. It traced the internet route and confirmed unauthenticated endpoints with no WAF or firewall, while determining that removing ingress would take down an intentionally public production service. Since vendor patches were available but image deployment would take time, it identified immediate cloud mitigations, including disabling service account token automount and narrowing IAM permissions, alongside permanent code and Terraform fixes. It traced relevant files to their repositories and owners, then assigned mitigation and fix plans. The account says the agent completed this work in minutes; it provides no independent evaluation of that claim.

### Source excerpt

See how the Green Agent balanced security urgency with business continuity to turn a toxic combination into an executable remediation plan and ready-to-merge pull requests.

## What's new in Kyverno 1.20

DevFeed: [What's new in Kyverno 1.20](<https://devfeed.tech/articles/what-s-new-in-kyverno-1-20-133514.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/12/whats-new-in-kyverno-1-20/>)

Author: Jim Bugwadia

Published: 2026-11-12T15:00:00Z

Content type: release

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [Kyverno](<https://devfeed.tech/topics/kyverno.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>), [rule-engine](<https://devfeed.tech/topics/rule-engine.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [Helm charts](<https://devfeed.tech/topics/helm-charts.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [absolute](<https://devfeed.tech/tags/absolute.md>), [admission](<https://devfeed.tech/tags/admission.md>), [admission-controller](<https://devfeed.tech/tags/admission-controller.md>), [after](<https://devfeed.tech/tags/after.md>), [ai](<https://devfeed.tech/tags/ai.md>), [cel](<https://devfeed.tech/tags/cel.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cli](<https://devfeed.tech/tags/cli.md>), [engine](<https://devfeed.tech/tags/engine.md>), [exceptions](<https://devfeed.tech/tags/exceptions.md>), [image](<https://devfeed.tech/tags/image.md>), [image-verification](<https://devfeed.tech/tags/image-verification.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kubernetes-security](<https://devfeed.tech/tags/kubernetes-security.md>), [kyverno](<https://devfeed.tech/tags/kyverno.md>), [news](<https://devfeed.tech/tags/news.md>), [policy](<https://devfeed.tech/tags/policy.md>), [policy-management](<https://devfeed.tech/tags/policy-management.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [verification](<https://devfeed.tech/tags/verification.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

Kyverno 1.20 removes execution of legacy policy types, including ClusterPolicy and CleanupPolicy, across controllers and the CLI. Existing resources remain but are marked not ready and unenforced; migrate them before upgrading. The Helm chart blocks upgrades when it finds legacy policies unless you acknowledge they will not be enforced. After upgrading, use `kyverno migrate` to update stored policy objects, and export legacy report history first because those results are pruned. The release also adds image verification for private Sigstore and GitHub attestations, CLI decision traces and OCI policy bundles, exception expiration and compensating controls for validating policies, and JSON mutation for object-root documents. Its CEL performance fix prepares each object once per request; reported engine benchmarks exclude webhook and API server latency. Kyverno 1.20 supports Kubernetes v1.34-v1.37; legacy CRDs are scheduled for removal in v1.21.

### Source excerpt

Kyverno 1.20 makes CEL the only policy engine and retires ClusterPolicy. See what changes for image verification, the CLI, exceptions and your upgrade.

## How ServiceNow Covers 90 Container Release Programs With SBOM-Driven Security

DevFeed: [How ServiceNow Covers 90 Container Release Programs With SBOM-Driven Security](<https://devfeed.tech/articles/how-servicenow-covers-90-container-release-programs-with-sbom-driven-security-136433.md>)

Original publisher: [Read original article](<https://anchore.com/blog/servicenow-container-release-sbom-driven-security/>)

Author: teamanchore

Published: 2026-11-10T13:05:00Z

Content type: article

Language: en

Sources: [Anchore](<https://devfeed.tech/sources/anchore.md>)

Topics: [anchore](<https://devfeed.tech/topics/anchore.md>), [Security](<https://devfeed.tech/topics/security.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>)

Tags: [alignment](<https://devfeed.tech/tags/alignment.md>), [anchore](<https://devfeed.tech/tags/anchore.md>), [anchore-enterprise](<https://devfeed.tech/tags/anchore-enterprise.md>), [api](<https://devfeed.tech/tags/api.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automation](<https://devfeed.tech/tags/automation.md>), [blog](<https://devfeed.tech/tags/blog.md>), [build](<https://devfeed.tech/tags/build.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [container](<https://devfeed.tech/tags/container.md>), [container-security](<https://devfeed.tech/tags/container-security.md>), [containerization](<https://devfeed.tech/tags/containerization.md>), [containerized](<https://devfeed.tech/tags/containerized.md>), [containers](<https://devfeed.tech/tags/containers.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [product-security](<https://devfeed.tech/tags/product-security.md>), [release](<https://devfeed.tech/tags/release.md>), [sbom](<https://devfeed.tech/tags/sbom.md>), [security](<https://devfeed.tech/tags/security.md>), [servicenow](<https://devfeed.tech/tags/servicenow.md>)

### AI overview

ServiceNow uses Anchore Enterprise to scan containers across 90 release programs, covering 80 internally hosted applications and 10 customer-hosted products. The team embeds scans early in development and CI/CD, creates security defects in existing workflows, and uses the API to send SBOMs, vulnerability data, and policy results into ServiceNow's systems of record. Repeating policy checks on every build supports consistent, auditable reviews; automated vulnerability management and remediation prioritization help a small security team support about 600 developers. Scanning keeps pace with release schedules ranging from weekly to every other month. Compliance requests for screenshots showing the computer's on-screen time and date still require a manual step.

### Source excerpt

The post How ServiceNow Covers 90 Container Release Programs With SBOM-Driven Security appeared first on Anchore.Picture a security team responsible for every container a platform ships. That's roughly 90 release programs: 80 applications hosted internally, 10 hosted for customers, all running on Kubernetes. Now picture that team being a fraction of the size of the developer base it supports. That's where ServiceNow's product security team found itself as its containerization [...]

## Insignary Releases Free Insignary-Chk Tool to Detect PHP2Shell and Node2Shell Exposure

DevFeed: [Insignary Releases Free Insignary-Chk Tool to Detect PHP2Shell and Node2Shell Exposure](<https://devfeed.tech/articles/insignary-releases-free-insignary-chk-tool-to-detect-php2shell-and-node2shell-exposure-122010.md>)

Original publisher: [Read original article](<https://hackernoon.com/insignary-releases-free-insignary-chk-tool-to-detect-php2shell-and-node2shell-exposure?source=rss>)

Author: CyberNewswire

Published: 2026-11-07T10:28:20Z

Content type: release

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [snyk-open-source](<https://devfeed.tech/topics/snyk-open-source.md>)

Tags: [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [brotli](<https://devfeed.tech/tags/brotli.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [containers](<https://devfeed.tech/tags/containers.md>), [crash](<https://devfeed.tech/tags/crash.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cve-2026-111497](<https://devfeed.tech/tags/cve-2026-111497.md>), [cves](<https://devfeed.tech/tags/cves.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-v4-0](<https://devfeed.tech/tags/cvss-v4-0.md>), [cyber-attack](<https://devfeed.tech/tags/cyber-attack.md>), [cyber-resilience](<https://devfeed.tech/tags/cyber-resilience.md>), [cyber-threats](<https://devfeed.tech/tags/cyber-threats.md>), [cybercrime](<https://devfeed.tech/tags/cybercrime.md>), [cybernewswire](<https://devfeed.tech/tags/cybernewswire.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [cybersecurity-tips](<https://devfeed.tech/tags/cybersecurity-tips.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [node2shell](<https://devfeed.tech/tags/node2shell.md>), [out-of-bounds-write](<https://devfeed.tech/tags/out-of-bounds-write.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [releases](<https://devfeed.tech/tags/releases.md>), [tool](<https://devfeed.tech/tags/tool.md>)

### AI overview

Insignary released insignary-chk, a free Linux x86_64 scanner for three listed CVEs affecting PHP, Node.js and Brotli. It reads files without changing them by default, sends no data over the network unless the user selects an option that connects to a specified address, and ranks findings by urgency: vulnerable software in use, installed but not running, and items needing manual review. It also checks Brotli copies outside Node.js. For end-of-life versions, it directs administrators to verify patch status with their Linux distribution vendor or upgrade; Node.js 20.x and earlier receive "Check with OS vendor" or "Unable to determine" statuses depending on installation source. The scanner requires no installation or registration, but supports neither Windows, macOS nor arm64. The release says it checks only the three listed CVEs.

### Source excerpt

Node2Shell (CVE-2026-111497) is an out-of-bounds write flaw in Google's Brotli decompression library, which Node.js bundles. Specially crafted

## CNCF Score project improved its security posture by joining the Docker-Sponsored Open Source Program

DevFeed: [CNCF Score project improved its security posture by joining the Docker-Sponsored Open Source Program](<https://devfeed.tech/articles/cncf-score-project-improved-its-security-posture-by-joining-the-docker-sponsored-open-source-program-119502.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/cncf-score-project-improved-its-security-posture-by-joining-the-docker-sponsored-open-source-program/>)

Author: Jennifer Kohl

Published: 2026-11-05T14:00:00Z

Content type: article

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [open-source-security](<https://devfeed.tech/topics/open-source-security.md>), [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [sigstore](<https://devfeed.tech/topics/sigstore.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [openssf](<https://devfeed.tech/topics/openssf.md>)

Tags: [cncf](<https://devfeed.tech/tags/cncf.md>), [community](<https://devfeed.tech/tags/community.md>), [container](<https://devfeed.tech/tags/container.md>), [container-security](<https://devfeed.tech/tags/container-security.md>), [docker](<https://devfeed.tech/tags/docker.md>), [dsos](<https://devfeed.tech/tags/dsos.md>), [hardened-images](<https://devfeed.tech/tags/hardened-images.md>), [images](<https://devfeed.tech/tags/images.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [score](<https://devfeed.tech/tags/score.md>), [security](<https://devfeed.tech/tags/security.md>), [security-posture](<https://devfeed.tech/tags/security-posture.md>)

### AI overview

Score adopted Docker's DSOS tooling to improve container security and release practices. It moved its images from GitHub Container Registry to Docker Hub and added Docker Scout comparisons on pull requests and registry scanning, reporting package changes, CVEs, image size, and policy compliance. Migrating to Docker Hardened Images required minimal Dockerfile changes: the score-radius image became 0.3 MB smaller with the same package count and zero CVEs; the Node.js sample image removed 22 packages and two CVEs. Score also replaced per-repository build steps with Docker's reusable GitHub Builder workflow, gaining signed SLSA provenance and SBOM attestations; GitHub OIDC avoids long-lived signing keys, and signed cache entries are verified before reuse. Docker Hub OIDC connections further replaced long-lived access tokens with short-lived workflow tokens. The article presents these as Score's implementation and results, with the builder migration involving a trade-off: Docker maintains the build implementation while projects control when it runs and its inputs.

### Source excerpt

See how CNCF Score improved container security with Docker Scout, Hardened Images, and the Docker-Sponsored Open Source Program.

## Web Application Security Testing: Types, Tools & Practices

DevFeed: [Web Application Security Testing: Types, Tools & Practices](<https://devfeed.tech/articles/web-application-security-testing-types-tools-practices-116612.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/web-application-security-testing>)

Author: Renny Shen

Published: 2026-10-30T00:00:00Z

Content type: article

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [Application Security](<https://devfeed.tech/topics/application-security.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [Security](<https://devfeed.tech/topics/security.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [staging](<https://devfeed.tech/topics/staging.md>), [XSS](<https://devfeed.tech/topics/xss.md>)

Tags: [and-best-practices](<https://devfeed.tech/tags/and-best-practices.md>), [application](<https://devfeed.tech/tags/application.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [application-security-testing](<https://devfeed.tech/tags/application-security-testing.md>), [best](<https://devfeed.tech/tags/best.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [dast](<https://devfeed.tech/tags/dast.md>), [learn](<https://devfeed.tech/tags/learn.md>), [practices](<https://devfeed.tech/tags/practices.md>), [sast](<https://devfeed.tech/tags/sast.md>), [security](<https://devfeed.tech/tags/security.md>), [security-testing](<https://devfeed.tech/tags/security-testing.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tool](<https://devfeed.tech/tags/tool.md>), [tools](<https://devfeed.tech/tags/tools.md>), [types](<https://devfeed.tech/tags/types.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [web](<https://devfeed.tech/tags/web.md>), [web-application-security](<https://devfeed.tech/tags/web-application-security.md>), [web-application-security-testing](<https://devfeed.tech/tags/web-application-security-testing.md>)

### AI overview

Web application security testing checks code, dependencies, and deployed behavior before release. SAST scans source code and can run from the first commit; SCA checks open source components; DAST probes a running app from outside; IAST observes code execution through an in-app agent. The excerpt recommends combining methods because SAST misses runtime and configuration flaws, while DAST cannot identify the faulty code line. It suggests SAST and SCA on every commit, image scans on each build, and DAST or IAST in staging, with findings correlated to reduce duplicate triage. Tool criteria include broad coverage, reachability-based prioritization, pipeline integration, correlation, and supply-chain support such as container scanning and SBOMs. Harness-specific claims describe pipeline scans that can stop builds, scanner integrations, and signed artifact provenance.

### Source excerpt

Web application security testing finds vulnerabilities before attackers do. Learn the types (SAST, DAST, IAST), tool criteria, and best practices. | Blog

## Ghost in the PHP2Shell: Why coordinated disclosure and patching will start moving faster

DevFeed: [Ghost in the PHP2Shell: Why coordinated disclosure and patching will start moving faster](<https://devfeed.tech/articles/ghost-in-the-php2shell-why-coordinated-disclosure-and-patching-will-start-moving-faster-105779.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/ghost-php2shell-coordinated-disclosure-faster>)

Author: Dania Durnas

Published: 2026-10-29T04:44:47.605032Z

Content type: opinion

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [patching](<https://devfeed.tech/tags/patching.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>)

### AI overview

PHP2Shell illustrates how AI-assisted vulnerability discovery and exploit development can compress response timelines: Calif and Wiz independently found the flaws, Aikido's AI Code Analysis rediscovered one within hours, and Trail of Bits built an exploit with Codex in a day. Leaked CVE identifiers prompted PHP to move its coordinated patch release forward, but the article reports exploitation attempts before the public pre-announcement and widespread attempts afterward. Shorter, tighter embargoes may reduce leak exposure, while giving downstream distributors, hosting providers, and protective services less time to prepare; Cloudflare, with advance notice, had WAF rules ready before the patch. As of October 27, Censys counted about 11.2 million PHP services on fixed versions and 32.5 million still affected among those reporting versions, with over 60 million not reporting a version. The article advises teams to inventory runtimes and dependencies, use timely incident sources that provide mitigations and deployable fixes, prepare for rapid patching, and lock dependencies rather than automatically upgrading everything. It describes Aikido's backported fixed images as one way to patch

### Source excerpt

PHP2Shell showed how fast AI turns a bug into an exploit. Here's why the disclosure should never happen this way again, and why it will anyway. Category: News

## One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images

DevFeed: [One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images](<https://devfeed.tech/articles/one-signed-answer-slsa-verification-summaries-for-registry-k8s-io-images-104466.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/28/registry-k8s-io-verification-summaries/>)

Author: The Kubernetes Authors

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [builder](<https://devfeed.tech/tags/builder.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [identity](<https://devfeed.tech/tags/identity.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [policy](<https://devfeed.tech/tags/policy.md>), [promotion](<https://devfeed.tech/tags/promotion.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [registry](<https://devfeed.tech/tags/registry.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

The Kubernetes image promoter now evaluates staging-image provenance against each project's policy in kubernetes/k8s.io, copies accepted attestations to registry.k8s.io, and publishes a signed SLSA verification summary (VSA) for each promoted image. Consumers can check the summary signer, verifier ID, result, and required build level with cosign and jq, or download it and run slsa-verifier with crane. Pin both signer and level: PASSED alone may mean only that promotion used a reviewed manifest, and an image without a policy can receive SLSA_BUILD_LEVEL_UNEVALUATED. SPO's v1.1.1 operator images, binaries, and Helm chart reach level 3; its bundle reaches only level 1 in that release, so a level 3 check fails. Projects need signed staging provenance, a manifest policy, and a test run. Cloud Build can provide level 1; level 3 requires provenance from an isolated GitHub workflow, then verification and attachment to the matching staging digest. Roll out policies in warn mode, test with kpromo cip, verify summaries, then use require to block violations. Summaries are created once at promotion, and most images promoted before October 2026 lack them; multi-architecture platform images need,

### Source excerpt

The Kubernetes community has been signing its container images since v1.24, and the images that kpromo, the Kubernetes image promoter (rewritten earlier this year), copies to registry.k8s.io get a signature. A signature answers one question: did this image go through the official promotion process? It does not answer the more interesting one: how was this image built, and from which source? Projects can attach signed SLSA provenance to their images to answer that. But to check it yourself, you have to know who builds each image, which identity signs its provenance, which builder it claims and which repository it comes from, for every project you pull from. That is a lot to ask, and in practice few people do it. Since October 2026, the image promoter does this work for you, once, at promotion time, and publishes the answer as a signed SLSA verification summary (VSA) for every image it promotes. In this blog post, I'd like to explain how it works, how you can verify it, and how your project can get its images verified at SLSA build level 1 or 3. How does it work? A project declares a provenance policy in its promoter manifest in kubernetes/k8s.io: who may sign its build attestations, which builders it trusts and at which level, and which source repositories its images come from. When a reviewed pull request promotes an image, the promoter evaluates the attestations of the staging image against that policy with the SLSA verifier, copies the accepted attestations to registry.k8s.io and writes the summary: flowchart LR build["Project build"] staging[("Staging registry")] policy["Provenance policy
in kubernetes/k8s.io"] promoter["Image promoter"] prod[("registry.k8s.io")] users["Users and clusters"] build -- "image and
signed provenance" --> staging staging --> promoter policy --> promoter promoter -- "image, attestations,
verification summary" --> prod prod -- "verify one summary" --> users The summaries are signed by a dedicated identity, promoter-summaries@

## Faster Answers, Fewer False Positives with Anchore Enterprise v6.3

DevFeed: [Faster Answers, Fewer False Positives with Anchore Enterprise v6.3](<https://devfeed.tech/articles/faster-answers-fewer-false-positives-with-anchore-enterprise-v6-3-115874.md>)

Original publisher: [Read original article](<https://anchore.com/blog/faster-answers-fewer-false-positives-with-anchore-enterprise-v6-3/>)

Author: Alex Rybak

Published: 2026-10-27T12:00:00Z

Content type: release

Language: en

Sources: [Anchore](<https://devfeed.tech/sources/anchore.md>)

Topics: [anchore](<https://devfeed.tech/topics/anchore.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-models](<https://devfeed.tech/tags/ai-models.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [anchore](<https://devfeed.tech/tags/anchore.md>), [anchore-enterprise](<https://devfeed.tech/tags/anchore-enterprise.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [axios](<https://devfeed.tech/tags/axios.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [blog](<https://devfeed.tech/tags/blog.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [false-positives](<https://devfeed.tech/tags/false-positives.md>), [model](<https://devfeed.tech/tags/model.md>), [package](<https://devfeed.tech/tags/package.md>), [search](<https://devfeed.tech/tags/search.md>), [security](<https://devfeed.tech/tags/security.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

Anchore Enterprise v6.3 adds four capabilities intended to shorten security triage. Quick Package Search finds application versions containing a package by name, optional version, or PURL, including cases where no CVE exists. Ubuntu ESM image scans use a separate vulnerability feed covering ESM fixes, reducing false positives for patched packages. Notifications describe vulnerability metadata changes, including CVSS score or severity, EPSS, and KEV status, so teams can respond when findings worsen. GGUF and Docker Models appear as packages in application versions and can be governed by a policy gate that either fails the pipeline or warns while allowing it to continue for parallel vetting.

### Source excerpt

The post Faster Answers, Fewer False Positives with Anchore Enterprise v6.3 appeared first on Anchore.Security teams rarely lack data. They lack time. When a new advisory lands, security teams spend the first hours on questions their tooling should already answer. Where does this package run? Is this finding real? Did its severity change since we triaged it? Is this AI model approved? Every manual search adds delay, and every [...]

## How to patch PHP2Shell with free Aikido Images

DevFeed: [How to patch PHP2Shell with free Aikido Images](<https://devfeed.tech/articles/how-to-patch-php2shell-with-free-aikido-images-101316.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/how-to-patch-php2shell-with-free-aikido-images>)

Author: Madeline Lawrence

Published: 2026-10-26T22:15:00Z

Content type: tutorial

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [chainguard cve remediation](<https://devfeed.tech/topics/chainguard-cve-remediation.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [7-4](<https://devfeed.tech/tags/7-4.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [containers](<https://devfeed.tech/tags/containers.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [free](<https://devfeed.tech/tags/free.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [images](<https://devfeed.tech/tags/images.md>), [patch](<https://devfeed.tech/tags/patch.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [product-updates](<https://devfeed.tech/tags/product-updates.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

PHP2Shell comprises two critical unauthenticated remote code execution flaws (CVE-2026-109618 and CVE-2026-109619); the article says exploitation has begun. PHP's fixes cover versions 8.2-8.5, while Aikido offers free container images with fixes backported across release lines 5.5-8.5 except 8.0, allowing many users to stay on their current line. The text gives Docker pull and Dockerfile examples and says to rebuild and redeploy every PHP image, restart workers, keep session.upload_progress.enabled=0, check the public site with Aikido's checker, and investigate possible compromise. PHP 8.0 and some variants are unavailable; users whose version is not listed are advised to update or seek a vendor backport. PHP's security team also provides source backports for 7.4-8.1.

### Source excerpt

Patch PHP2Shell (CVE-2026-109618 and CVE-2026-109619) with free Aikido Images for PHP 5.5 to 8.5. Stay on your current version with backported fixes. Category: Product Updates

## Security Tool Sprawl: How to Consolidate SAST, SCA, and CNAPP

DevFeed: [Security Tool Sprawl: How to Consolidate SAST, SCA, and CNAPP](<https://devfeed.tech/articles/security-tool-sprawl-how-to-consolidate-sast-sca-and-cnapp-101298.md>)

Original publisher: [Read original article](<https://www.ox.security/blog/three-ways-to-manage-cybersecurity-tool-sprawl-in-your-software-supply-chain/>)

Author: OX Security

Published: 2026-10-26T18:55:09Z

Content type: article

Language: en

Sources: [OX Security](<https://devfeed.tech/sources/ox-security.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>)

Tags: [ai-vibesec](<https://devfeed.tech/tags/ai-vibesec.md>), [api](<https://devfeed.tech/tags/api.md>), [api-discovery](<https://devfeed.tech/tags/api-discovery.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [aspm](<https://devfeed.tech/tags/aspm.md>), [aspm-tools](<https://devfeed.tech/tags/aspm-tools.md>), [cnapp](<https://devfeed.tech/tags/cnapp.md>), [code-security](<https://devfeed.tech/tags/code-security.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [ox-security](<https://devfeed.tech/tags/ox-security.md>), [sast](<https://devfeed.tech/tags/sast.md>), [sca](<https://devfeed.tech/tags/sca.md>), [security](<https://devfeed.tech/tags/security.md>), [security-tool-sprawl](<https://devfeed.tech/tags/security-tool-sprawl.md>), [security-tools](<https://devfeed.tech/tags/security-tools.md>), [tool-sprawl](<https://devfeed.tech/tags/tool-sprawl.md>)

### AI overview

Tool consolidation should preserve coverage across code, dependencies, cloud posture and runtime while connecting findings in shared context. SAST, SCA and CNAPP overlap around IaC and container scanning, but retain distinct roles: SAST analyzes first-party code, SCA tracks third-party components and licenses, and CNAPP covers cloud configuration, identity and running workloads. The text recommends inventorying tools and ownership, mapping coverage gaps and duplicates, unifying findings, then retiring tools only after at least one release cycle of parallel operation confirms coverage parity. Migration should also preserve custom rules, policies and developer workflows, and account for contract renewals. Risks include uncovered layers, loosely connected products presented as one platform, and vendor dependence without exit terms. The article excerpt also promotes OX's platform as an example; its capability claims are vendor-provided.

### Source excerpt

What Is Security Tool Sprawl? Security tool sprawl is the accumulation of security tools bought to fill one gap at a time, each with its own console, policy set, and finding format, until their coverage overlaps in some places and leaves gaps in others. The result is more findings, more consoles, and less certainty about [...] The post Security Tool Sprawl: How to Consolidate SAST, SCA, and CNAPP appeared first on OX Security.

## Pillow CVE-2026-112900: How to find and fix it with GitLab

DevFeed: [Pillow CVE-2026-112900: How to find and fix it with GitLab](<https://devfeed.tech/articles/pillow-cve-2026-112900-how-to-find-and-fix-it-with-gitlab-102392.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/pillow-cve-find-and-fix-with-gitlab/>)

Author: Daniel Abeles

Published: 2026-10-26T00:00:00Z

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Image](<https://devfeed.tech/topics/image.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [argument-injection](<https://devfeed.tech/tags/argument-injection.md>), [cve](<https://devfeed.tech/tags/cve.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-scanning](<https://devfeed.tech/tags/dependency-scanning.md>), [ghostscript](<https://devfeed.tech/tags/ghostscript.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [guide](<https://devfeed.tech/tags/guide.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [orbit](<https://devfeed.tech/tags/orbit.md>), [python](<https://devfeed.tech/tags/python.md>), [scanning](<https://devfeed.tech/tags/scanning.md>), [search](<https://devfeed.tech/tags/search.md>), [security](<https://devfeed.tech/tags/security.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>), [security-labs](<https://devfeed.tech/tags/security-labs.md>), [security-research](<https://devfeed.tech/tags/security-research.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Pillow versions 2.6.0 through 12.x are affected by CVE-2026-112900, a critical argument injection in the Ghostscript call used to render EPS images; the supplied text says no in-the-wild exploitation has been reported. Upgrade to Pillow 13.0.0 or later, checking distribution security trackers because package versions and fixes vary. Rebuild and redeploy containers, update pinned versions, and check upstream base images. If upgrading is delayed, use generated filenames, restrict accepted image formats, or remove Ghostscript where EPS support is unnecessary. The excerpt recommends locating dependencies with GitLab dependency and container scanning, GitLab Orbit, and code search, then prioritizing projects that combine Pillow, Ghostscript, and uploads. GitLab Duo Agent Platform can help create project issues and merge requests, but people still need to review and merge changes, run image-processing tests for changed TIFF and PNG behavior, and confirm deployment. GitLab products and managed infrastructure are stated to be unaffected.

### Source excerpt

GitLab is not affected by CVE-2026-112900 or the other vulnerabilities fixed in Pillow 13.0.0. GitLab products do not include the Pillow library, and our Security team has found no evidence of impact to GitLab-managed infrastructure. GitLab.com, GitLab Self-Managed, and GitLab Dedicated are not impacted. Pillow is one of the most widely used image libraries in the Python ecosystem. It often sits several layers down in a dependency tree, pulled in by a web framework, a thumbnailing service or an ML toolkit that nobody chose it for directly. On October 16, 2026, the Pillow project released version 13.0.0, and one of its security fixes is CVE-2026-112900: an argument injection in the way Pillow calls Ghostscript to render EPS images. The CVE record, published on October 19, rates it 9.2 (Critical) on CVSS 4.0. It affects every Pillow release from 2.6.0 up to, but not including, 13.0.0. No exploitation in the wild has been reported so far, but CISA's assessment marks it as automatable with total technical impact. Upgrade Pillow to 13.0.0 on every project and image that handles untrusted images, and remove Ghostscript from images that do not need EPS support. This guide is for security and platform teams with Python projects on GitLab. It covers the fixed version for each distribution, how the flaw works, the other High and Critical issues fixed in the same release, how to locate affected projects with dependency scanning, container scanning, GitLab Orbit, and code search, and how to remediate at scale with GitLab Duo Agent Platform. CVE-2026-112900 at a glance CVE-2026-112900 is an OS command and argument injection flaw in Pillow's EPS plugin, rated Critical (CVSS 4.0 score of 9.2) by the CVE Numbering Authority (CNA). The CVE record was published on October 19, 2026. FieldDetailCVECVE-2026-112900GitHub advisoryGHSA-w889-685w-c8fhTitlePillow: Argument Injection in Ghostscript call, potentially leading into RCEWeaknessCWE-88 (argument injection), CWE-78 (OS command injec

## Which PCI DSS requirements can Kubernetes policy enforce?

DevFeed: [Which PCI DSS requirements can Kubernetes policy enforce?](<https://devfeed.tech/articles/which-pci-dss-requirements-can-kubernetes-policy-enforce-104666.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/10/24/which-pci-dss-requirements-can-kubernetes-policy-enforce/>)

Author: Ritesh Patel

Published: 2026-10-24T23:00:00Z

Content type: article

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [Kyverno](<https://devfeed.tech/topics/kyverno.md>), [policy-as-code](<https://devfeed.tech/topics/policy-as-code.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [image tags vs digests](<https://devfeed.tech/topics/image-tags-vs-digests.md>)

Tags: [compliance](<https://devfeed.tech/tags/compliance.md>), [container-security](<https://devfeed.tech/tags/container-security.md>), [continuous-compliance](<https://devfeed.tech/tags/continuous-compliance.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kyverno](<https://devfeed.tech/tags/kyverno.md>), [kyverno-sharp-kubernetes](<https://devfeed.tech/tags/kyverno-sharp-kubernetes.md>), [pci-dss](<https://devfeed.tech/tags/pci-dss.md>), [policy](<https://devfeed.tech/tags/policy.md>)

### AI overview

Kubernetes admission policies can enforce PCI DSS v4.0.1 controls when the requirement maps to a workload setting: examples include blocking privileged or host access, limiting Secret references and RBAC wildcards, restricting image registries, requiring image digests or signatures, and requiring HTTPS at Ingress. These mappings are the article's interpretation, not PCI SSC guidance, and should be confirmed with a QSA; the cited requirement wording came from a public mirror because the official PDF returned HTTP 403. Kyverno policy reports show which resources passed or failed checks, but provide only partial evidence for inventory, configuration standards and patching; they are not a complete bill of materials or proof of CVE remediation. Policies cannot enforce identity, audit-log retention and review, anti-malware, vulnerability scanning and intrusion detection, or PCI scope. The suggested workflow is to document in-scope clusters, classify controls as enforceable, evidence-based or out of reach, review reports in non-blocking mode, fix findings, then enforce policies and record owners and evidence for external controls.

### Source excerpt

Kubernetes policy enforces the PCI DSS v4.0.1 rules on privileged pods, secrets, RBAC and image sources. It can't enforce logging, anti-malware or scope.

## How SBOM Management Lets ServiceNow Scale Security Without Scaling Headcount

DevFeed: [How SBOM Management Lets ServiceNow Scale Security Without Scaling Headcount](<https://devfeed.tech/articles/how-sbom-management-lets-servicenow-scale-security-without-scaling-headcount-109501.md>)

Original publisher: [Read original article](<https://anchore.com/case-studies/how-sbom-management-lets-servicenow-scale-security-without-scaling-headcount/>)

Author: Sonja Schweigert

Published: 2026-10-23T18:04:24Z

Content type: article

Language: en

Sources: [Anchore](<https://devfeed.tech/sources/anchore.md>)

Topics: [anchore](<https://devfeed.tech/topics/anchore.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>)

Tags: [anchore](<https://devfeed.tech/tags/anchore.md>), [anchore-enterprise](<https://devfeed.tech/tags/anchore-enterprise.md>), [case-studies](<https://devfeed.tech/tags/case-studies.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [container](<https://devfeed.tech/tags/container.md>), [containers](<https://devfeed.tech/tags/containers.md>), [developers](<https://devfeed.tech/tags/developers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [generation](<https://devfeed.tech/tags/generation.md>), [policy](<https://devfeed.tech/tags/policy.md>), [product-security](<https://devfeed.tech/tags/product-security.md>), [release](<https://devfeed.tech/tags/release.md>), [sbom](<https://devfeed.tech/tags/sbom.md>), [scale](<https://devfeed.tech/tags/scale.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [scanning](<https://devfeed.tech/tags/scanning.md>), [security](<https://devfeed.tech/tags/security.md>), [servicenow](<https://devfeed.tech/tags/servicenow.md>), [software](<https://devfeed.tech/tags/software.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

ServiceNow uses Anchore Enterprise in its CI/CD pipeline to scan containers, generate SBOMs, and apply policy checks across all 90 release programs--covering about 600 developers without growing its security team. Scans run early, create security defects in existing workflows, and send SBOMs, vulnerability data, and policy results by API into ServiceNow's systems of record. Policy evaluations also cover secrets and malware and produce auditable compliance evidence. The excerpt says customer requests for dated, on-screen screenshots remain the only manual compliance step.

### Source excerpt

The post How SBOM Management Lets ServiceNow Scale Security Without Scaling Headcount appeared first on Anchore.Santa Clara, CAwww.servicenow.com INDUSTRYEnterprise Software SBOM-Driven Scanning Keeps Pace With 600 Developers Shipping Containers ServiceNow's product security team uses Anchore Enterprise to bring consistent vulnerability scanning, SBOM generation, and policy-based compliance to every container it ships. That's 90 release programs and roughly 600 developers, covered without growing the small security team. Challenges Solutions Anchore Enterprise [...]

## PHP2Shell and eMudhra Patched

DevFeed: [PHP2Shell and eMudhra Patched](<https://devfeed.tech/articles/php2shell-and-emudhra-patched-101227.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/php2shell-and-emudhra-patched/>)

Author: Vishrut Iyengar

Published: 2026-10-23T13:08:08Z

Content type: news

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Docker](<https://devfeed.tech/topics/docker.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [apache](<https://devfeed.tech/tags/apache.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [composer](<https://devfeed.tech/tags/composer.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [docker](<https://devfeed.tech/tags/docker.md>), [emudhra](<https://devfeed.tech/tags/emudhra.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [image](<https://devfeed.tech/tags/image.md>), [patched](<https://devfeed.tech/tags/patched.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [products](<https://devfeed.tech/tags/products.md>), [published](<https://devfeed.tech/tags/published.md>), [security](<https://devfeed.tech/tags/security.md>), [store](<https://devfeed.tech/tags/store.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

The excerpt describes two container foundation risks: PHP2Shell vulnerabilities CVE-2026-109618 and CVE-2026-109619, which it says enable unauthenticated server code execution, and eight eMudhra intermediate certificates with computable private keys that could be used to issue trusted website certificates. Docker says it published a patched dhi.io/php image within 24 hours and rebuilt trust stores across its catalog; by 10pm UTC on October 22, almost all catalog tags had the fixed CA store. It says users should pull current DHI tags and redeploy, rebuild custom images based on DHI, and check the PHP version inside other containers before rebuilding on a patched base. DHI Enterprise customizations are rebuilt automatically when the base is patched. The account says SBOMs can verify the PHP version and CA store for each published tag.

### Source excerpt

PHP2Shell and the eMudhra certificate compromise landed in the same week. Docker published a fixed PHP image within 24 hours and rebuilt the trust store across the catalog.

## SonarQube container scanning is now in open beta

DevFeed: [SonarQube container scanning is now in open beta](<https://devfeed.tech/articles/sonarqube-container-scanning-is-now-in-open-beta-95911.md>)

Original publisher: [Read original article](<https://www.sonarsource.com/blog/container-scanning-open-beta/>)

Author: Satinder Khasriya

Published: 2026-10-22T13:00:00Z

Content type: release

Language: en

Sources: [Sonar Blog](<https://devfeed.tech/sources/sonar-blog.md>)

Topics: [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container image vulnerabilities](<https://devfeed.tech/topics/container-image-vulnerabilities.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>)

Tags: [advanced-security](<https://devfeed.tech/tags/advanced-security.md>), [beta](<https://devfeed.tech/tags/beta.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [cost](<https://devfeed.tech/tags/cost.md>), [customers](<https://devfeed.tech/tags/customers.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [images](<https://devfeed.tech/tags/images.md>), [malicious-packages](<https://devfeed.tech/tags/malicious-packages.md>), [open](<https://devfeed.tech/tags/open.md>), [scan](<https://devfeed.tech/tags/scan.md>), [scanning](<https://devfeed.tech/tags/scanning.md>), [security](<https://devfeed.tech/tags/security.md>), [sonarqube](<https://devfeed.tech/tags/sonarqube.md>), [sonarqube-advanced-security](<https://devfeed.tech/tags/sonarqube-advanced-security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

SonarQube Advanced Security container scanning is in open beta on SonarQube Cloud for Team and Enterprise customers at no additional cost. It checks container images for known vulnerabilities and malicious packages, including PHP2Shell (CVE-2026-109618 and CVE-2026-109619) in images that install PHP from a Linux distribution package. Results appear under Container images and use the dependency-risk workflow; CI can be configured to fail when findings meet or exceed a chosen severity.

### Source excerpt

Scan the container images you build and ship for vulnerabilities and malicious packages. Included with SonarQube Advanced Security. Join the open beta.

## Anchore is now an OpenChain Partner

DevFeed: [Anchore is now an OpenChain Partner](<https://devfeed.tech/articles/anchore-is-now-an-openchain-partner-109500.md>)

Original publisher: [Read original article](<https://anchore.com/blog/anchore-is-now-an-openchain-partner/>)

Author: Alex Rybak

Published: 2026-10-22T12:00:00Z

Content type: release

Language: en

Sources: [Anchore](<https://devfeed.tech/sources/anchore.md>)

Topics: [anchore](<https://devfeed.tech/topics/anchore.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [anchore](<https://devfeed.tech/tags/anchore.md>), [anchore-enterprise](<https://devfeed.tech/tags/anchore-enterprise.md>), [ato](<https://devfeed.tech/tags/ato.md>), [blog](<https://devfeed.tech/tags/blog.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [components](<https://devfeed.tech/tags/components.md>), [container](<https://devfeed.tech/tags/container.md>), [container-image](<https://devfeed.tech/tags/container-image.md>), [customer](<https://devfeed.tech/tags/customer.md>), [department](<https://devfeed.tech/tags/department.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [open](<https://devfeed.tech/tags/open.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [partner](<https://devfeed.tech/tags/partner.md>), [procurement](<https://devfeed.tech/tags/procurement.md>), [program](<https://devfeed.tech/tags/program.md>), [records](<https://devfeed.tech/tags/records.md>), [software](<https://devfeed.tech/tags/software.md>), [source](<https://devfeed.tech/tags/source.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

Anchore has joined the OpenChain Project as a Vendor partner. The post describes OpenChain's ISO/IEC 5230 standard for open source license compliance and ISO/IEC 18974 for security assurance, both of which call for knowing shipped components, assessing obligations and risks, and retaining verifiable records. Syft generates SBOMs and supports SPDX output; Grype scans SBOMs for vulnerabilities. Anchore Enterprise adds SBOM and vulnerability management, policy enforcement, and compliance validation across CI/CD and production. For a first check, the post suggests generating an SPDX JSON SBOM with Syft, then scanning it with Grype. It says federal teams can use the standards as a common benchmark and notes Anchore is referenced in two DoW guides.

### Source excerpt

The post Anchore is now an OpenChain Partner appeared first on Anchore.If your software runs on open source (and it almost certainly does), someone is eventually going to ask you to prove you manage it well. Maybe it's a customer's procurement team, or a contracting officer reviewing your ATO package. In that conversation, they're looking for a documented program and records that back it up. That's [...]

## ActiveState Partners with Docker to Secure the Open Source in Enterprise Containers

DevFeed: [ActiveState Partners with Docker to Secure the Open Source in Enterprise Containers](<https://devfeed.tech/articles/activestate-partners-with-docker-to-secure-the-open-source-in-enterprise-containers-95379.md>)

Original publisher: [Read original article](<https://www.docker.com/blog/docker-activestate-partnership/>)

Author: Jennifer Angeles

Published: 2026-10-22T11:30:00Z

Content type: release

Language: en

Sources: [Docker](<https://devfeed.tech/sources/docker.md>)

Topics: [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [apache-2-0](<https://devfeed.tech/tags/apache-2-0.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [build](<https://devfeed.tech/tags/build.md>), [built-from-source](<https://devfeed.tech/tags/built-from-source.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [container-security](<https://devfeed.tech/tags/container-security.md>), [containers](<https://devfeed.tech/tags/containers.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-hardened-images](<https://devfeed.tech/tags/docker-hardened-images.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [image](<https://devfeed.tech/tags/image.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [partners](<https://devfeed.tech/tags/partners.md>), [partnerships](<https://devfeed.tech/tags/partnerships.md>), [production](<https://devfeed.tech/tags/production.md>), [products](<https://devfeed.tech/tags/products.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [secure-software-supply-chain](<https://devfeed.tech/tags/secure-software-supply-chain.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Docker and ActiveState's reseller partnership combines Docker Hardened Images with ActiveState's curated open source packages to cover container bases and the dependencies added on top. Docker describes DHI as minimal images built from source, with signed SBOMs, SLSA Build Level 3 provenance, near-zero CVEs, and a 7-day SLA for critical and high-severity CVEs in production tiers. ActiveState's catalog spans more than a dozen language ecosystems; components are built from source, maintained under contractual remediation SLAs, and delivered through existing developer tools. The excerpt also claims 95% fewer CVEs and 90% faster remediation than community open source for ActiveState, with a 5-day SLA on critical vulnerabilities. The partnership is available now.

### Source excerpt

Container security spans the image, build, and runtime. See the practical steps that shrink your attack surface and keep vulnerabilities out of production.

## PHP2Shell: GitLab helps find and remediate critical PHP flaws

DevFeed: [PHP2Shell: GitLab helps find and remediate critical PHP flaws](<https://devfeed.tech/articles/php2shell-gitlab-helps-find-and-remediate-critical-php-flaws-96423.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/gitlab-helps-remediate-critical-php-flaws/>)

Author: Dinesh Bolkensteyn

Published: 2026-10-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [Composer](<https://devfeed.tech/topics/composer.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-v4-0](<https://devfeed.tech/tags/cvss-v4-0.md>), [drupal](<https://devfeed.tech/tags/drupal.md>), [features](<https://devfeed.tech/tags/features.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [mod-php](<https://devfeed.tech/tags/mod-php.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [platform-teams](<https://devfeed.tech/tags/platform-teams.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [run](<https://devfeed.tech/tags/run.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [security](<https://devfeed.tech/tags/security.md>), [security-labs](<https://devfeed.tech/tags/security-labs.md>)

### AI overview

PHP2Shell (CVE-2026-109618 and CVE-2026-109619) comprises two critical PHP engine flaws rated 9.2 on CVSS v4.0; an unauthenticated request can execute code before application code runs. GitLab says its services are unaffected. Upgrade every PHP web runtime and container to a listed fixed version or patched distribution package, restart PHP processes, and rebuild and redeploy images; framework, Composer, validation, and authentication changes do not fix the engine. GitLab container scanning finds package-installed PHP but misses source-built PHP, while exact code search covers declared files on the default branch but does not show what is running. Compare both with a runtime inventory; Kubernetes operational scanning has the same package-only limitation. Review internet-facing server logs from October 17 onward for PHPSESSID response cookies; a successful exploit may return HTTP 200 without errors. If exploitation is suspected, isolate and investigate, preserve evidence before restarting where possible, and rotate credentials accessible to PHP. The excerpt also notes GitLab Dedicated lacks exact code search and that a read-only remediation skill cannot verify inaccessible hosts.

### Source excerpt

GitLab is not affected by PHP2Shell (CVE-2026-109618 and CVE-2026-109619). The GitLab application is not written in PHP and does not run it to serve web requests, and our Security team has found no evidence of impact to GitLab-managed infrastructure. GitLab.com, GitLab Self-Managed, and GitLab Dedicated are not impacted. PHP is a widely used programming language that runs on web servers and powers popular platforms like WordPress, Drupal, and Magento, so a flaw in PHP itself can affect many websites and applications. On October 21, 2026, the PHP project fixed two critical remote code execution flaws in PHP, together known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). PHP rates both 9.2 on CVSS v4.0. The flaws are in the PHP engine, not in any framework, library, or application code, so there is no application-level fix. Any web server that runs PHP is affected, including NGINX and Apache. The PHP project confirmed the vulnerability on Apache with mod_php, where an unauthenticated request can achieve remote code execution before any application code runs. Upgrade every server and container that runs PHP to serve web requests to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or to your distribution's patched package now. This guide is for security and platform teams with PHP projects on GitLab. It covers the fixed version for each PHP branch and distribution, how to use GitLab features to locate PHP projects across your groups, how to track remediation, and how to check for signs of compromise. Upgrade PHP to a fixed version now Upgrade the PHP runtime on every host and in every container image to a fixed version. Framework updates, Composer updates, input validation, and authentication don't help, because PHP handles the request before application code runs. BranchFixed inPHP 8.5.x8.5.12PHP 8.4.x8.4.27PHP 8.3.x8.3.36PHP 8.2.x8.2.35 (end of life December 31, 2026)PHP 8.6 release candidates8.6.0RC4. The official php:8.6-rc image was still on RC3 on October 21, and RC3 do

## Critical PHP Security Release Coming Tomorrow (October 21)

DevFeed: [Critical PHP Security Release Coming Tomorrow (October 21)](<https://devfeed.tech/articles/critical-php-security-release-coming-tomorrow-october-21-91333.md>)

Original publisher: [Read original article](<https://laravel-news.com/php-critical-security-release>)

Author: Paul Redmond

Published: 2026-10-21T01:52:52Z

Content type: news

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [PHP](<https://devfeed.tech/topics/php.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [active-exploitation](<https://devfeed.tech/tags/active-exploitation.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [applications](<https://devfeed.tech/tags/applications.md>), [apps](<https://devfeed.tech/tags/apps.md>), [base-images](<https://devfeed.tech/tags/base-images.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-v4-0](<https://devfeed.tech/tags/cvss-v4-0.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [news](<https://devfeed.tech/tags/news.md>), [october](<https://devfeed.tech/tags/october.md>), [php](<https://devfeed.tech/tags/php.md>), [release](<https://devfeed.tech/tags/release.md>), [security](<https://devfeed.tech/tags/security.md>), [team](<https://devfeed.tech/tags/team.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [utc](<https://devfeed.tech/tags/utc.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

PHP plans to release fixes for two vulnerabilities rated CVSS 9.2 on October 21, 2026 at 14:00 UTC. The affected PHP versions and vulnerability details have not been disclosed; the PHP team encourages users to prepare to upgrade, and says it may release earlier if details become public or active exploitation is seen. Laravel says Forge and Cloud are also preparing patched base images for the PHP release and a separate Node.js security issue. Node.js has not confirmed its release time. Apps may need redeployment to pick up the updated images; Laravel is exploring silent patching and says it will notify users when the images are available.

### Source excerpt

The PHP security team will ship a release on October 21, 2026 at 14:00 UTC that fixes two critical vulnerabilities, both rated CVSS 9.2. Plan your upgrade now. The post Critical PHP Security Release Coming Tomorrow (October 21) appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## Beyond container image signing: How we enforce software supply chain policies at Datadog

DevFeed: [Beyond container image signing: How we enforce software supply chain policies at Datadog](<https://devfeed.tech/articles/beyond-container-image-signing-how-we-enforce-software-supply-chain-policies-at-datadog-91078.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/engineering/software-supply-chain-policy-enforcement/>)

Author: Callan Lamb; Brianna Heffernen

Published: 2026-10-20T00:00:00Z

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>), [Datadog](<https://devfeed.tech/sources/datadog.md>)

Topics: [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [software bill of materials](<https://devfeed.tech/topics/software-bill-of-materials.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [datadog](<https://devfeed.tech/topics/datadog.md>)

Tags: [code-security](<https://devfeed.tech/tags/code-security.md>), [container](<https://devfeed.tech/tags/container.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [policies](<https://devfeed.tech/tags/policies.md>), [security](<https://devfeed.tech/tags/security.md>), [signing](<https://devfeed.tech/tags/signing.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [turnstile](<https://devfeed.tech/tags/turnstile.md>)

### AI overview

Container image signatures show that an image is unchanged since signing, but cannot reveal risks introduced earlier in the build or source process. Datadog's Turnstile extends verification by collecting identity-bound, signed attestations across an artifact's life cycle and evaluating them against environment-specific policies at deployment. Its dd-attest library uses ephemeral keys tied to workload identities; policy-core retrieves and verifies attestations from the DynamoDB-backed Attestation Metadata Store, evaluates Rego policies with OPA, and records a signed Verification Summary Attestation that downstream systems can verify. Policies and related libraries are distributed as OCI artifacts and verified with TUF. Turnstile supports audit, warning, and blocking modes for progressive rollout. Across about 1 million evaluation traces in August 2026, the article reports a 92.8% policy cache hit rate, 75% per-artifact cache hit rate, and evaluation latency of 36 ms at P50 and 481 ms at P99.

### Source excerpt

Datadog built Turnstile to evaluate signed attestations and enforce software supply chain policies before container images are deployed.

## Vulnerabilities: Everything You've Wanted To Know

DevFeed: [Vulnerabilities: Everything You've Wanted To Know](<https://devfeed.tech/articles/vulnerabilities-everything-you-ve-wanted-to-know-66885.md>)

Original publisher: [Read original article](<https://blogs.vmware.com/cloud-foundation/2026/10/07/vulnerabilities-everything-you-want-know/>)

Author: bob plankers

Published: 2026-10-07T20:29:12Z

Content type: tutorial

Language: en

Sources: [VMware](<https://devfeed.tech/sources/vmware-blogs.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [common vulnerabilities and exposures](<https://devfeed.tech/topics/common-vulnerabilities-and-exposures.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [attack](<https://devfeed.tech/tags/attack.md>), [availability](<https://devfeed.tech/tags/availability.md>), [chaining](<https://devfeed.tech/tags/chaining.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [common-vulnerabilities-and-exposures](<https://devfeed.tech/tags/common-vulnerabilities-and-exposures.md>), [common-vulnerability-scoring-system](<https://devfeed.tech/tags/common-vulnerability-scoring-system.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [cybersecurity-awareness-month](<https://devfeed.tech/tags/cybersecurity-awareness-month.md>), [thing](<https://devfeed.tech/tags/thing.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

The article explains how to assess software vulnerabilities by considering exploitability, environment, attack paths, and the possibility of attackers chaining flaws. It outlines vulnerability terms and recommends checking advisories, prioritizing timely patching, and using isolation, hardening, and access controls to reduce risk.

### Source excerpt

(Day 5 of 22 in our Cybersecurity Awareness Month series. Today: vulnerabilities) AI is a force multiplier. Good folks use it to do their work faster and with more accuracy. Bad actors use it to... do their work faster and with more accuracy, too. One thing that AI definitely does faster is find vulnerabilities in ... Continued The post Vulnerabilities: Everything You've Wanted To Know appeared first on VMware Blogs.

[Next page](<https://devfeed.tech/topics/container-image-compliance.md?cursor=WyIyMDI2LTEwLTA3VDIwOjI5OjEyKzAwOjAwIiwgImQyMzFmNDNhLWUyYjAtNDA5ZC1iNjBmLTQ3MGJkMzIwMWI2NCJd>)