# vulnerability management A proactive strategy and process for identifying, tracking, prioritizing, and remediating security vulnerabilities in IT systems and software. 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 Confluent Uses Third-Party Risk Assessments to Support Vendor Due Diligence DevFeed: [How Confluent Uses Third-Party Risk Assessments to Support Vendor Due Diligence]() Original publisher: [Read original article]() Author: Bethany Carter Published: 2026-09-15T16:40:06Z Content type: article Language: en Sources: [Confluent: Data in motion]() Topics: [Security](), [Business Security](), [vulnerability management](), [Cloud]() Tags: [apra](), [automated](), [cloud](), [compliance](), [confluent](), [confluent-cloud](), [data-protection](), [gdpr](), [identity](), [iso](), [nist](), [security](), [standards](), [third-party](), [trust-center](), [vulnerability-management]() ### AI overview Confluent explains how its Trust Center provides third-party risk assessment reports to support vendor security, resilience, compliance, procurement, and customer due diligence. The article describes assessments including ProcessUnity Global Risk Exchange and control mapping to customer frameworks. ### Source excerpt Confluent's Trust Center simplifies vendor risk reviews with CyberGRX, CyberVadis, SIG, CAIQ, and TruSight/KY3P assessments. ## August 2026 Security Release DevFeed: [August 2026 Security Release]() Original publisher: [Read original article]() Author: Sebastian Silbermann Published: 2026-08-25T18:00:00Z Content type: release Language: en Sources: [Next.js Blog]() Topics: [Next.js](), [Security](), [vulnerability](), [vulnerability management](), [Open Source](), [Vercel]() Tags: [bug-bounty](), [next-js](), [open-source](), [release](), [security](), [vercel](), [vulnerability](), [vulnerability-management]() ### AI overview Next.js released versions 16.3.3 and 15.5.24 to address critical vulnerabilities, including unauthenticated remote code execution through AVIF image optimization and on Windows-hosted servers. The patched releases disable AVIF optimization until an upstream fix is propagated. ### Source excerpt The August 2026 security release for Next.js is now available ## AAOS SDV - Secure by Design DevFeed: [AAOS SDV - Secure by Design]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-24T16:00:31Z Content type: article Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [Android](), [Security](), [SELinux](), [virtualization](), [vulnerability management](), [Process](), [Resilience](), [Google]() Tags: [android](), [android-security](), [article](), [automotive](), [blog](), [deep-dive](), [google](), [process](), [resilience](), [security](), [selinux](), [virtualization](), [vulnerabilities](), [vulnerability-management]() ### AI overview AAOS SDV is presented as a secure-by-design platform for software-defined vehicles. The article explains how virtualization isolates co-hosted domains, while Android UID-based process sandboxes, POSIX capabilities, and SELinux enforce least privilege and deny-by-default access. It also describes vulnerability response, penetration testing, security audits, and architectural reviews. ### Source excerpt Posted by Markus Vill, Software Engineer, Sean Keys, Security Engineer, and Istvan Nador, Software Engineer, Android Auto At Google, we believe our products should be secure by design, which is why we built the Android Automotive Operating System for Software Defined Vehicle (AAOS SDV) on existing, market-proven platforms, leveraging virtualization technologies like Cuttlefish. While our release announcements focused on the features, this blog post outlines some of the security concepts. Foundation: Domain IsolationVirtualization to isolate co-hosted instances The current trend of consolidating Electronic Control Units (ECUs) into a single chip reduces isolation by running multiple domains side-by-side. While AAOS SDV instances provide internal isolation mechanisms, it is often preferable to run logical domains independently. For instance, a cluster and an infotainment system have distinct requirements. We use virtual machines to run multiple instances in parallel, ensuring that sharing remains explicit and isolation is the default behavior. Inherited Android Security AAOS SDV evolved from Microdroid, a minimalistic Android version optimized for privacy virtual machines (pVM). This lineage provides Android platform engineers with established security features they already know. Process Isolation & Deny by Default AAOS SDV follows Android's User ID (UID)-based isolation model to set up a sandbox for each application. Each service runs in a dedicated process with a unique UID to manage access rights, data directories, and other restrictions. We employ Portable Operating System Interface (POSIX) capabilities to strictly limit operations and pair this with Security-Enhanced Linux (SELinux) to enforce a "deny-by-default" posture. This approach restricts each service to the absolute minimum required, meaning missing configurations block access rather than creating an over-permissive system. We apply this same strategy to our communication permission system, as explained l ## Why the CVE doom cycle cannot be solved by working harder DevFeed: [Why the CVE doom cycle cannot be solved by working harder]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [vulnerability management](), [Automation](), [container-security](), [Vulnerabilities](), [configuration]() Tags: [automation](), [container-image-security](), [cve](), [false-positives](), [secure-by-design](), [security](), [vulnerability-management]() ### AI overview The article argues that the recurring cycle of scanning, triaging, patching, and redeploying container images cannot be solved by working harder or using faster scanners. Because vulnerability findings and CVEs accumulate faster than manual remediation can handle, it recommends embedding vulnerability management into the platform through secure-by-design practices, golden paths, and automation. ### Source excerpt Manual CVE triage doesn't scale. Break the CVE doom cycle by shifting vulnerability management into the platform with golden paths and automation ## Understanding platform engineering's role in staying compliant with the EU's CRA DevFeed: [Understanding platform engineering's role in staying compliant with the EU's CRA]() Original publisher: [Read original article]() Author: Nigel Douglas Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [Security](), [vulnerability management](), [supply-chain-security](), [incident]() Tags: [compliance](), [cyber-resilience-act](), [engineering](), [eu](), [idp](), [incident](), [platform](), [platform-engineering](), [policy](), [regulatory](), [sboms](), [secure-by-default](), [secure-software](), [security](), [software-supply-chain](), [supply-chain](), [vulnerabilities](), [vulnerability-management]() ### AI overview The article explains how platform engineering can operationalize compliance with the EU's Cyber Resilience Act by embedding secure-by-default practices, automated SBOMs, and rapid incident reporting into an Internal Development Platform. It also outlines CRA compliance milestones and manufacturer responsibilities, including vulnerability management and security updates. ### Source excerpt The EU's Cyber Resilience Act (CRA) mandates secure software by design. Discover how platform engineering operationalizes compliance by embedding secure-by-default standards, automated SBOMs, and rapid incident reporting into your Internal Development Platform (IDP). This approach transforms compliance into a frictionless golden path ## Vulnerability management core capabilities every platform should have DevFeed: [Vulnerability management core capabilities every platform should have]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [vulnerability management](), [Security](), [Architecture & Design](), [Open Source]() Tags: [open-source](), [scale](), [security](), [shift-left](), [vulnerabilities](), [vulnerability-management]() ### AI overview The article argues that platform teams should move vulnerability management into the platform so secure behavior becomes the default. It describes hardened images, policy-as-code, secure templates, secret rotation, scanning, and automated remediation as core capabilities for reducing developer toil, cognitive load, and vulnerability-related risk. ### Source excerpt Core platform capabilities to shift vulnerability management down: hardened images, policy-as-code, secure templates, secret rotation, scanning, and remediation ## Hydrate, Hack, Repeat: Security Summer Camp 2026 DevFeed: [Hydrate, Hack, Repeat: Security Summer Camp 2026]() Original publisher: [Read original article]() Author: jgamblin Published: 2026-07-22T21:34:54Z Content type: opinion Language: en Sources: [Jerry Gamblin]() Topics: [Security](), [vulnerability management](), [vulnerability](), [data](), [Artificial Intelligence]() Tags: [2026](), [ai](), [black-hat](), [bsides](), [cisa](), [con](), [cves](), [data](), [kev-catalog](), [management](), [models](), [research](), [security](), [talks](), [uncategorized](), [vulnerability](), [vulnerability-management]() ### AI overview A personal guide to the author's 2026 security conference schedule, new role as Head of Research at Empirical Security, and recommended CVE and vulnerability talks. It argues that effective vulnerability management requires granular, transparent, accurate data, citing the growth in CVEs and the limited share listed in CISA KEV. ### Source excerpt My schedule, a new role at Empirical Security, and the CVE and vulnerability talks worth your time. It is almost the first week of August, which means it is time to point myself at the desert one more time. BSides Las Vegas, Black Hat, and DEF CON all land back to back, and for me ... Read more ## How to Govern Autonomous Agents in Enterprise AI Factories DevFeed: [How to Govern Autonomous Agents in Enterprise AI Factories]() Original publisher: [Read original article]() Author: Michelle Horton Published: 2026-06-29T15:50:13Z Content type: tutorial Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [Artificial Intelligence](), [AI Factory](), [systems](), [vulnerability management](), [configuration](), [Network](), [SOC](), [ide](), [browser](), [Terminal]() Tags: [agentic-ai-generative-ai](), [agents](), [ai](), [ai-agent](), [ai-factory](), [architecture](), [autonomous](), [autonomous-agents](), [browser](), [data-center-cloud](), [enterprise](), [featured](), [ide](), [mlops](), [network](), [openshell](), [policy](), [soc](), [telemetry](), [vulnerability-management]() ### AI overview This tutorial presents NVIDIA's Secure Agent Workspace Reference Design for governing autonomous AI agents in enterprise environments. It explains how to separate the presentation layer from managed agent execution and enforce identity, network access, credentials, runtime policy, auditing, human review, and workspace isolation. ### Source excerpt AI agents are quickly moving beyond chat. They inspect code, run tests, read documents, search knowledge bases, query internal systems, and operate for hours on... ## Why risk acceptance isn't a viable option, with Jaya Baloo DevFeed: [Why risk acceptance isn't a viable option, with Jaya Baloo]() Original publisher: [Read original article]() Author: info@1password.com (Dave Lewis) Published: 2026-06-12T00:00:00Z Content type: article Language: en Sources: [Blog on 1Password Blog]() Topics: [Vulnerabilities](), [vulnerability management](), [Artificial Intelligence](), [Security](), [Large Language Model](), [Open Source Models & Datasets](), [Orchestration](), [Security, Privacy and Abuse Prevention]() Tags: [ai](), [apple](), [llms](), [open-source](), [orchestration](), [podcasts](), [security](), [vulnerabilities](), [vulnerability-management]() ### AI overview This podcast episode discusses the risks and hype surrounding AI-powered vulnerability discovery. Jaya Baloo argues that security teams should address existing weaknesses such as poor asset visibility, remediation backlogs, inconsistent logging, and weak operational practices, while also considering how smaller open-source models and effective orchestration can uncover vulnerabilities that larger systems miss. ### Source excerpt Listen to this episode on Apple Podcasts null Listen now Listen to this episode on Spotify null Listen now Anyone who thinks security leaders are humorless sticklers for the rules has never spent half an hour with Jaya Baloo. But in this episode of Chasing Entropy, Dave Lewis does just that, and the result is a frank and irreverent conversation that proves that security may be serious business, but it's still a fun job. Baloo is the co-founder and COO/CISO of Aisle, an AI-powered vulnerability management startup with the bold goal of "zero exploitable vulnerabilities." Baloo's career has spanned telecom, cryptography, enterprise security, and AI-driven security research, but her love of computers started when she got her first computer (a Commodore 64) at age 9. The conversation tracks her journey from early BBS war dialing and CompuServe stories to the modern challenge of defending organizations against increasingly autonomous systems. A major focus of the episode is the growing hype around AI-powered vulnerability discovery. Baloo acknowledges the seriousness of the threat, saying "It introduces this asymmetry in terms of attacker-defender advantage, where the advantage would strongly go to the attacker if they're capable of finding new and novel vulnerabilities, and the ability to exploit them, and potentially doing this at scale, autonomously." However, she cautions that fear of a Mythos-level model shouldn't leave security leaders feeling too overwhelmed to take action. "We have elevated this to a level of hype that is not that beneficial to actually doing something about the problem." Instead of panicking about the unknown, Baloo advises security to start by addressing the problems they are aware of. Organizations already struggle with asset visibility, remediation backlogs, inconsistent logging, and weak operational hygiene. AI may have increased the blast radius of these risks, but they existed long before LLMs. The discussion also explores how smaller, open ## Building the business case for a secure open source supply chain DevFeed: [Building the business case for a secure open source supply chain]() Original publisher: [Read original article]() Published: 2026-05-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Open Source](), [open-source-security](), [vulnerability management](), [cloud-infrastructure](), [CI/CD](), [distributed-systems](), [container images](), [engineering-culture]() Tags: [chainguard-assemble](), [chainguard-containers](), [chainguard-customers](), [cloud-infrastructure](), [cloud-native](), [compliance](), [container-images](), [continuous-delivery](), [cves](), [dependencies](), [distributed-systems](), [kyndryl](), [kyndryl-open-source](), [open-source](), [productivity](), [resilience](), [secure-open-source](), [software-supply-chain-security](), [supply-chain](), [vulnerabilities]() ### AI overview The article explains how organizations can build a business case for a secure open source supply chain. It describes a shift from framing open source security solely around CVEs, scanner results, and patching toward presenting trusted open source as a driver of productivity, resilience, and delivery speed. It also explains why traditional vulnerability management struggles with continuous delivery, distributed systems, frequently rebuilt container images, changing dependencies, and global cloud infrastructure. ### Source excerpt Learn how Kyndryl reframed open source security as a business driver -- reducing risk, lowering costs, and accelerating developer productivity. ## CMMC Phase 2, explained: Requirements, deadlines, and who's affected DevFeed: [CMMC Phase 2, explained: Requirements, deadlines, and who's affected]() Original publisher: [Read original article]() Published: 2026-04-29T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Cybersecurity](), [Security & Privacy](), [Cryptography](), [vulnerability management](), [vulnerability scanning](), [Encryption](), [MFA]() Tags: [certificates](), [cmmc](), [cmmc-container-images](), [cmmc-phase-2](), [cmvp](), [compliance](), [cve](), [cybersecurity-maturity-model-certification](), [fips](), [nist](), [sboms](), [stig](), [stigs](), [supply-chain](), [u-s-dod](), [vulnerability-management](), [vulnerability-scanning]() ### AI overview This article explains the requirements, deadlines, and scope of CMMC Phase 2. It describes the CMMC Level 2 certification requirements for organizations handling Controlled Unclassified Information or supporting Department of Defense and certain civilian agency contracts, including MFA, encryption, vulnerability scanning, supported systems, independent assessments, and compliance documentation. ### Source excerpt CMMC Phase 2 and NIST 800-171 are here. Learn how Chainguard helps teams meet compliance with FIPS, STIGs, and zero-CVE containers. ## PCI DSS Compliance: What Digital Businesses Need to Know DevFeed: [PCI DSS Compliance: What Digital Businesses Need to Know]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Security](), [Social engineering](), [Network Segmentation](), [TLS (Transport Layer Security)](), [vulnerability management](), [SIEM, Security](), [Software as a service](), [tokenization]() Tags: [compliance](), [digital-products](), [firewalls](), [mfa](), [network-segmentation](), [pci-dss](), [saas](), [scope](), [security](), [siem](), [tls](), [tokenization](), [vulnerability-management]() ### AI overview This guide explains how PCI DSS applies to digital businesses that accept card payments, including SaaS companies and sellers of digital products. It outlines the standard's 12 requirements and discusses controls for networks, account data, vulnerabilities, access, monitoring, and information security. It also covers card-not-present transactions, recurring billing, and tokenization. ### Source excerpt PCI DSS compliance explained for digital businesses. Understand the 12 requirements, compliance levels, and how to reduce your scope when selling digital products online. ## Intelligent security at ClickHouse speed: How Cogent Security built an AI-native vulnerability management platform DevFeed: [Intelligent security at ClickHouse speed: How Cogent Security built an AI-native vulnerability management platform]() Original publisher: [Read original article]() Author: ClickHouse Published: 2026-03-24T06:58:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [vulnerability management](), [Vulnerabilities](), [Artificial Intelligence](), [Security](), [AI Development](), [Database](), [Software](), [Architecture & Design]() Tags: [agent](), [agentic](), [agents](), [ai](), [architecture](), [clickhouse](), [coding](), [data](), [database](), [latency](), [security](), [speed](), [vulnerabilities](), [vulnerability-management]() ### AI overview Cogent Security uses ClickHouse to power an AI-native vulnerability management platform that serves billions of security findings at sub-second speeds. Migrating from Postgres reduced P90 query latency from five seconds to under one second at 100 million rows, while an agentic loop architecture and ClickHouse projections improved Chart Agent accuracy from 40% to 94%. ### Source excerpt "The key thing that ClickHouse unlocks for AI is speed. Everything we do needs to be done at machine speed to counter AI-enabled attackers." Karan Gugle, Founding Engineer ## Staying Ahead with ESP32 Security Updates DevFeed: [Staying Ahead with ESP32 Security Updates]() Original publisher: [Read original article]() Author: John Lee Published: 2026-03-05T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Security](), [vulnerability management](), [cyber resilience act](), [dashboards](), [ESP-IDF](), [Espressif](), [software bill of materials]() Tags: [blog](), [cyber-resilience-act](), [dashboards](), [esp-idf](), [esp32](), [espressif](), [iot](), [lts](), [ota](), [sbom](), [security](), [vulnerability]() ### AI overview This article explains how the ESP32 ecosystem supports long-term firmware security and compliance under regulations such as the EU Cyber Resilience Act. It covers vulnerability management, secure OTA updates, Long-Term Support branches, the ESP-IDF Security Dashboard, and SBOMs for tracking affected components and patched versions. ### Source excerpt This article explains how manufacturers can use the ESP32 ecosystem to build and maintain secure firmware over time, especially in light of new regulations like the EU Cyber Resilience Act. It highlights tools such as vulnerability dashboards, Long-Term Support branches, and secure OTA updates to ensure ongoing compliance and device security. ## Forrester TEI study: Chainguard Containers delivered 233% return on investment DevFeed: [Forrester TEI study: Chainguard Containers delivered 233% return on investment]() Original publisher: [Read original article]() Published: 2026-02-18T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard containers](), [container-security](), [chainguard](), [vulnerability management](), [Containers](), [Vulnerabilities](), [Application Security](), [Open Source]() Tags: [chainguard](), [chainguard-containers](), [chainguard-forrester](), [chainguard-roi](), [chainguard-value](), [cmmc](), [compliance](), [container-security](), [containers](), [forrester-tei](), [open-source](), [pci-dss](), [security](), [vulnerabilities](), [vulnerability-management]() ### AI overview A Forrester Consulting Total Economic Impact study commissioned by Chainguard reports that customers using Chainguard Containers achieved a 233% return on investment over three years, with $2.5 million in benefits and payback in less than six months. The article attributes these results to reduced vulnerabilities, simpler maintenance, and lower compliance overhead, supported by minimal zero-CVE container images and automated remediation. ### Source excerpt Explore the latest Forrester Consulting Total Economic Impact™ (TEI) study, commissioned by Chainguard. ## Announcing AWS Inspector scanner support for Chainguard Libraries DevFeed: [Announcing AWS Inspector scanner support for Chainguard Libraries]() Original publisher: [Read original article]() Published: 2025-11-24T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard libraries](), [Amazon Web Services](), [vulnerability management](), [Malware](), [vulnerability](), [container images](), [Python](), [Django](), [Flask]() Tags: [amazon-scanner-support](), [aws](), [aws-inspector](), [chainguard-aws-integration](), [chainguard-libraries](), [chainguard-libraries-for-python](), [chainguard-libraries-for-python-aws](), [chainguard-packages](), [container-images](), [cve](), [cve-remediation](), [django](), [flask](), [malware](), [malware-prevention](), [python](), [security](), [vulnerabilities](), [vulnerability](), [vulnerability-management]() ### AI overview Chainguard Libraries for Python now integrates with Amazon Inspector's enhanced scanning for Amazon ECR. The integration provides malware prevention, recognition of Chainguard-remediated CVEs, and a unified view of container and library vulnerabilities across AWS workloads. ### Source excerpt Chainguard Libraries now integrates with AWS Inspector, bringing proactive malware prevention, CVE remediation, and vulnerability visibility across AWS workloads ## Get up to Speed on FedRAMP 20x DevFeed: [Get up to Speed on FedRAMP 20x]() Original publisher: [Read original article]() Published: 2025-10-23T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Cloud](), [DevSecOps](), [Security](), [supply-chain-security](), [Vulnerabilities](), [vulnerability management](), [Cloud Native Ecosystem](), [Containers](), [Automation](), [Authorization](), [Software as a service]() Tags: [2025](), [2026](), [ato](), [automation](), [chainguard-compliance](), [chainguard-containers](), [chainguard-fedramp-solution](), [chainguard-for-fedramp](), [cloud](), [cloud-native](), [compliance](), [containers](), [containers-for-fedramp](), [devsecops](), [fedramp](), [fedramp-20x](), [fedramp-containers](), [provenance](), [saas](), [security](), [software-supply-chain](), [standards](), [vulnerability-management]() ### AI overview FedRAMP 20x modernizes cloud authorization through continuous, automation-driven assurance, machine-readable documentation, and streamlined assessment processes. The article explains implications for containerized workloads, vulnerability management, software supply-chain security, ATOs, and organizations transitioning from FedRAMP Rev. 5. ### Source excerpt FedRAMP 20x is transforming cloud compliance with automation and continuous security. Learn how Chainguard Containers simplify 20x readiness with 0-CVE images. ## Jerry Gamblin Announces Two CVE Ecosystem Talks at BSides Las Vegas and DEF CON DevFeed: [Jerry Gamblin Announces Two CVE Ecosystem Talks at BSides Las Vegas and DEF CON]() Original publisher: [Read original article]() Author: jgamblin Published: 2025-07-30T18:05:00Z Content type: opinion Language: en Sources: [Jerry Gamblin]() Topics: [Security](), [vulnerability management](), [Open Source]() Tags: [black-hat](), [bsides](), [cves](), [infosec](), [management](), [open-source](), [security](), [uncategorized]() ### AI overview Jerry Gamblin announces that he will give two talks on the CVE ecosystem during Security Summer Camp, including appearances at BSides Las Vegas and the AppSec Village at DEF CON. ### Source excerpt It's that time of year again! The first week of August means my annual trip to the desert for "Security Summer Camp"--the whirlwind of BSides Las Vegas, Black Hat, and DEF CON. It's always an exhausting but amazing week, and I can't wait to dive in, catch up with everyone, and talk about what I've ... Read more ## Introducing Scanfrog: Dodge Container Vulnerabilities DevFeed: [Introducing Scanfrog: Dodge Container Vulnerabilities]() Original publisher: [Read original article]() Published: 2025-07-30T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Containers](), [vulnerability scanning](), [vulnerability management](), [grype](), [chainguard](), [chainguard containers](), [Security](), [Terminal](), [arcade](), [Open Source]() Tags: [anchore](), [chainguard](), [chainguard-containers](), [container](), [container-image](), [container-image-vulnerabilities](), [container-images](), [containers](), [free](), [games](), [grype](), [management](), [open-source](), [scanfrog](), [security](), [terminal](), [vulnerabilities](), [vulnerability-scanner](), [vulnerability-scanning]() ### AI overview Scanfrog is a Frogger-style terminal game that turns vulnerabilities found in a container image into game obstacles. It uses Grype, a free and open-source vulnerability scanner, to create levels based on vulnerability-scanning results and illustrates why reducing vulnerabilities improves software security. ### Source excerpt Scanfrog is a Frogger-style game created by one of Chainguard's engineers to showcase how difficult it can be to dodge vulnerabilities in containers. ## Understanding CRA Compliance: Overcoming Challenges with an Integrated Security Testing Approach DevFeed: [Understanding CRA Compliance: Overcoming Challenges with an Integrated Security Testing Approach]() Original publisher: [Read original article]() Author: Snyk Team Published: 2025-06-25T23:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Security](), [Testing](), [vulnerability management](), [DevOps](), [Tooling](), [Vulnerabilities](), [Development](), [Open Source]() Tags: [awareness](), [best-practices](), [blog](), [community](), [compliance](), [cra-requirements](), [cyber-resilience-act](), [cybersecurity](), [dependencies](), [deployment](), [developer](), [developers](), [development](), [devops](), [engineering](), [eu](), [scanners](), [secure-by-design](), [security](), [snyk-code](), [snyk-iac](), [snyk-learn](), [snyk-open-source](), [testing](), [vulnerabilities](), [vulnerability](), [vulnerability-management](), [workflows]() ### AI overview This article explains how the Cyber Resilience Act (CRA) changes software delivery expectations for organizations serving the EU. It highlights continuous security validation across proprietary code, open source libraries, and third-party dependencies, and recommends integrated security testing, secure-by-design practices, aligned teams, modern tooling, and security embedded in daily development workflows. ### Source excerpt Learn how to meet CRA requirements with integrated security testing, secure-by-design workflows, and scalable practices for modern dev teams. ## How R1 Universities Can Simplify CMMC 2.0 Compliance with Chainguard Containers DevFeed: [How R1 Universities Can Simplify CMMC 2.0 Compliance with Chainguard Containers]() Original publisher: [Read original article]() Published: 2025-06-04T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard containers](), [Containers](), [vulnerability management](), [Vulnerabilities](), [Security](), [chainguard](), [chainguard os](), [Automation](), [Linux](), [Malware](), [systems]() Tags: [2025](), [chainguard](), [chainguard-containers](), [chainguard-factory](), [chainguard-os](), [cmmc](), [cmmc-2-0](), [compliance](), [containers](), [cve](), [cve-remediation](), [cves](), [funding](), [linux](), [malware](), [management](), [security](), [software](), [systems](), [vulnerabilities](), [zero-cves]() ### AI overview This article explains how Chainguard Containers may help R1 universities prepare for CMMC 2.0 Level 2 requirements tied to Department of Defense research contracts. It focuses on vulnerability-management controls, including timely identification, reporting, remediation, malware protection, and risk assessment, and describes Chainguard's minimal container images, Chainguard OS, and Chainguard Factory. ### Source excerpt With CMMC 2.0 compliance becoming an important prerequisite to research funding for R1 universities, Chainguard Containers are the perfect solution. See how. ## How Seemplicity scaled real-time security analytics with Postgres CDC and ClickHouse DevFeed: [How Seemplicity scaled real-time security analytics with Postgres CDC and ClickHouse]() Original publisher: [Read original article]() Author: ClickHouse Published: 2025-05-29T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [real-time](), [Application Security](), [vulnerability management](), [Security & compliance, Cloud security](), [dashboards](), [Architecture & Design](), [Back end]() Tags: [analytics](), [application-security](), [backend](), [clickhouse](), [cloud-security](), [dashboards](), [database](), [postgres](), [real-time](), [scale](), [speed](), [vulnerability-management]() ### AI overview The article explains how Seemplicity scaled its real-time security analytics platform by separating operational workloads in Postgres from analytical workloads in ClickHouse Cloud. Postgres CDC, using PeerDB now part of ClickPipes, replicates security findings into ClickHouse, enabling faster dashboards, vulnerability prioritization, and actionable remediation workflows as data volumes and customer requirements grow. ### Source excerpt "I knew a managed product built by engineers, whose goal in life is to transform bits from Postgres into ClickHouse, would be better than anything we could do ourselves." Tal Shargal, Chief Architect ## Overcoming AppSec Challenges in FinServ: How CIBC Balances Speed, Security, and Compliance DevFeed: [Overcoming AppSec Challenges in FinServ: How CIBC Balances Speed, Security, and Compliance]() Original publisher: [Read original article]() Author: Snyk Team Published: 2025-03-20T04:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Application Security](), [Security, Privacy and Abuse Prevention](), [DevSecOps](), [vulnerability management](), [Artificial Intelligence](), [Automation](), [threat detection](), [cloud-infrastructure](), [Cybercrime]() Tags: [ai](), [application-security](), [automation](), [blog](), [cloud-infrastructure](), [community](), [compliance](), [customer](), [customer-featured](), [data-privacy](), [devsecops](), [executive](), [financial-services](), [finserv](), [interest](), [pci-dss](), [security](), [soc-2](), [threat-detection](), [vulnerability-management]() ### AI overview This article distills a fireside-chat discussion about application security challenges in financial services, featuring Snyk's Field CTO and CIBC's Senior Director of Security Service Management. It covers the tension between rapid innovation and strict compliance, risks from cybercrime, data privacy, cloud infrastructure, third-party services, legacy systems, and modern applications, and the role of automation, continuous security testing, monitoring, DevSecOps, AI-driven tools, and human oversight in vulnerability management. ### Source excerpt Join Snyk's Field CTO, Steven Schmidt, and Mihai Saveschi, Senior Director of Security Service Management at CIBC, for an exclusive fireside chat on the evolving landscape of application security in financial services. ## Snyk and ServiceNow: Streamlining Vulnerability Management with ServiceNow VR Assignment Rules DevFeed: [Snyk and ServiceNow: Streamlining Vulnerability Management with ServiceNow VR Assignment Rules]() Original publisher: [Read original article]() Author: Sarah Conway Published: 2025-03-12T04:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [vulnerability management](), [Application Security](), [Automation](), [configuration](), [data]() Tags: [application-security](), [automation](), [awareness](), [blog](), [community](), [compliance](), [configuration](), [developer](), [developer-security-platform](), [enterprise](), [integration](), [related-content](), [security](), [snyk](), [snyk-learn](), [visibility](), [vulnerability-management](), [workflows]() ### AI overview This article explains how ServiceNow Vulnerability Assignment rules can automate routing vulnerability remediation tasks by correlating vulnerability data with CMDB fields. It also describes how Snyk's Application Vulnerability Response integration with ServiceNow improves application security visibility, productivity, accuracy, and consistency. ### Source excerpt Learn how to optimize vulnerability management with ServiceNow Vulnerability Assignment rules and Snyk's AppVR integration. Automate workflows, improve security visibility and reduce risks. Explore real-world examples and enhance your application security strategy. [Next page]()