< ciso
brief />
Tag Banner

All news with #sbom tag

41 articles

AWS Security Hub adds organization-wide SBOM inventory

🔒 AWS Security Hub now provides a centralized Software Bill of Materials (SBOM) inventory that gives security teams a continuously updated view of packages and applications across compute resources. The inventory is built from SBOMs Amazon Inspector generates for EC2 instances, ECR images, and Lambda functions, and it lists packages with version, type, and resource counts. Users can filter and group results, view per-resource Installed software, and query via the Security Hub API. The feature is included with Security Hub Essentials, requires no additional enablement, and is available in all Regions where Security Hub is offered.
read more →

GitHub launches npm package firewall in preview

🛡️ GitHub is previewing a package firewall that blocks suspicious npm packages at install time by inspecting metadata requests and package downloads. The feature, available to GitHub Enterprise Cloud customers, sits between endpoints or internal registries and upstream repositories and enforces policies like minimum package age, malware advisories, SLSA attestations, and install-script checks. Administrators configure controls and can approve exception requests for blocked packages.
read more →

Build a quantum-resistant ML‑DSA software supply chain

🔒 This article explains how to deploy ML‑DSA (Module‑Lattice‑Based Digital Signature Algorithm) signing across a software supply chain using AWS services. It shows how to create an ML‑DSA certificate hierarchy with AWS Private CA, manage ML‑DSA keys in AWS KMS, and authenticate build agents with AWS IAM Roles Anywhere to sign binaries, container images, and SBOMs. The post is Part 1 of a two‑part series aimed at builders and provides practical steps, tooling notes, and operational guidance for integrating quantum‑resistant signatures today.
read more →

One Evidence Graph Instead of Multiple BOM Programs

🔍 In this analysis, the author argues that enterprises should avoid running separate bill-of-materials (BOM) programs for software, cryptography, AI models, authorization and runtime artifacts. Instead, organizations need a federated evidence graph that links domain-specific records via a common envelope and relationship semantics so incident responders can answer cross-cutting questions about affected products, exposure and remediation. The piece details standards, pilot steps and governance to ensure accuracy, trust and least-disclosure practices.
read more →

Red Hat's Lightwell Remediates 400+ Java Vulnerabilities

🔒 Red Hat's open-source security initiative Lightwell has remediated over 400 novel vulnerabilities across core Java libraries since launching in June. The company announced the general availability of the Lightwell Clearinghouse after a pilot phase, aiming to validate AI-generated reports and reduce noise for maintainers. Backed by IBM and supported by major financial institutions, Lightwell offers continuous signed binaries, SBOMs and a premium clearinghouse for targeted backports to production systems.
read more →

How Chainguard Scaled to One Billion Build Manifests

🔧 Over six months Chainguard doubled its output from 500 million to over 1 billion container build manifests, surpassing 3,000 images and 675,000 versions. The article explains what a build manifest represents and how Chainguard OS and Chainguard Factory produce continuous, reproducible artifacts with SLSA Level 3 provenance, Sigstore signatures, and SBOMs. It describes the transition from an event-driven Factory to Factory 2.0 (DriftlessAF), which uses continuous reconciliation, redundant work queues, and targeted AI to remove toil and accelerate rebuild velocity. The piece argues that faster rebuilds are essential to staying ahead of AI-enabled attackers and outlines future expansion and open sourcing of DriftlessAF.
read more →

Supply Chain Risks in the Modern SDLC

🔍 Unit 42 details how supply chain attacks have escalated, shifting adversaries from finished applications to the developer tooling and CI/CD pipelines that build software. The report examines incidents like ChainDrop, Axios, and Shai-Hulud to show how malicious preinstall scripts, account hijacks, and memory scraping steal credentials and self-propagate. It argues that SBOMs alone are insufficient and recommends continuous visibility, execution controls, ephemeral CI servers, and short-lived credentials to stop autonomous malware.
read more →

Extend Amazon Inspector SBOM Generator with Plugins

🔍 Amazon Inspector’s SBOM Generator (inspector-sbomgen) now supports a plugin system that lets developers add custom package collectors without recompiling or waiting for official releases. The post explains how to scaffold plugins, the discovery-collection pipeline, testing with Lua fixtures, and IDE support for rapid iteration. It also details the sandboxed safety model, artifact tracing via source_path, and how plugin-generated components integrate with Amazon Inspector for vulnerability scanning.
read more →

Mitigation Guidance for Software Supply Chain Compromise

🔒 Google Threat Intelligence Group and Mandiant outline recent trends in large-scale open source supply chain compromises observed in 2025–2026 and provide practical mitigation and hardening recommendations. The post highlights actor techniques such as repository compromise, malicious package injection, and abuse of CI/CD triggers, and emphasizes increased risk from AI-enabled workflows. It recommends inventories, SBOMs/ABOMs, SDLC threat modeling, active risk monitoring, and configuration controls to reduce exposure.
read more →

GKE Blueprint for Securing AI Workloads at Scale

🔒 This article presents a blueprint for securing AI workloads on Google Kubernetes Engine (GKE), consolidating controls across Google Cloud services and GKE features to create a secure-by-default platform. It covers three layers—infrastructure, supply chain, and application—and details capabilities such as Confidential GKE Nodes, Workload Identity Federation, k8s-aibom for AI SBOMs, Model Armor, and the GKE Inference Gateway. The blueprint recommends a three-phase rollout: Deploy, Operate, and Govern, and emphasizes integrating Google Cloud controls to maintain security at enterprise scale.
read more →

AWS Security Hub adds AI inventory for visibility

🛡️ AWS Security Hub now offers an AI inventory that gives central security teams a continuously updated, organization-wide view of AI assets and their security posture. It automatically discovers AI workloads via managed-service integration, SBOM analysis for self-hosted workloads, and GuardDuty DNS telemetry for external API endpoints. Discovered assets are mapped to underlying infrastructure and correlated with security findings to help prioritize remediation. The feature is included with Security Hub Essentials at no additional cost and is available in all commercial AWS Regions where Security Hub is offered.
read more →

Open-source k8s‑aibom for automated AI BOMs

🔍 k8s-aibom is an unprivileged Kubernetes controller that continuously monitors cluster workloads to detect AI runtimes and generate standard CycloneDX 1.6 Machine Learning Bill of Materials (ML-BOMs). It runs as a single Deployment with zero developer friction—no sidecars, no privileged DaemonSets—and exports deterministic BOMs to in-cluster CRs and optional external sinks like Google Cloud Storage. Designed for audit-grade evidence, it supports compliance frameworks and GitOps workflows.
read more →

How AI Is Rewriting Software Supply Chain Risk

🛡️ Software supply chain security has evolved as AI tools and agents become integral to builds. What used to be a question of third‑party packages and transitive dependencies now includes models, agents, prompts, and autonomous tooling as provenance concerns. Teams must extend lineage to models and pipeline actions, and prioritize findings by actual exploitability to avoid alert overload. The discussion surfaces in a webinar on July 22 covering new research and practical program changes.
read more →

Insignary Closes SBOM Accuracy Gap with Binary Clarity

🔍 Insignary Clarity delivers binary-first analysis that inspects what is actually built, shipped, and deployed to produce accurate SBOMs and identify open-source components that never appear in manifests. The platform generates AIBOMs, performs reachability analysis to prioritize exploitable vulnerabilities, and provides continuous alerts by monitoring stored SBOMs against updated CVE sources. Insignary is cited across multiple Gartner reports and positioned to help organizations meet evolving global regulatory requirements for binary-verified SBOMs.
read more →

OpenSSF Warns of Poor CRA Readiness in Open Source

🔒 The Open Source Security Foundation (OpenSSF) warns of broad unfamiliarity and structural unreadiness for the EU Cyber Resilience Act (CRA), with 66% of surveyed manufacturers and developers reporting limited awareness. The report highlights confusion over applicability, deadlines, penalties and roles like manufacturers versus stewards, and notes low adoption of full Software Bills of Materials (SBOMs). OpenSSF also flags risky reliance on private forks and passive upstream dependence as potential compliance failures.
read more →

EU Cyber Resilience Act: Product Safety and Deadlines

🛡️The EU Cyber Resilience Act (CRA) shifts focus from development practices to product safety, extending CE-like obligations to software, firmware, backend services and connected devices. It mandates SBOMs, minimum support lifecycles, and rapid reporting: organizations must have vulnerability and incident processes in place by Sept 11 and report exploited flaws within 24 hours, with full reports in three days. Many vendors and CIOs remain unprepared, particularly around automated SBOMs, open source obligations, and the wider conformity assessments the law introduces.
read more →

Kaspersky Container Security: Practical Team Insights

🔒 Kaspersky Container Security (KCS) is presented as a comprehensive platform that reaches beyond registry image scanning to secure container workflows across development and production. The Product Security Team uses KCS in CI/CD pipelines, registry correlation, and cluster runtime monitoring to tie findings to specific artifacts, pipelines, and scan times. KCS computes risk ratings, supports SBOM processing, and produces reports in SARIF, CycloneDX, SPDX and standard formats to integrate with AppSec and internal tooling.
read more →

G7 Issues Minimum SBOM Elements for AI Supply Chains

🔍 A G7 Cybersecurity Working Group paper published on 12 May defines minimum elements for software bills of materials (SBOMs) tailored to AI systems, aiming to boost transparency across AI supply chains. It outlines seven clusters — Metadata, System Level Properties, Models, Dataset Properties, Key Performance Indicators, Infrastructure and Security Properties — to guide producers and users. The guidance stresses clusters are non-mandatory, that SBOMs alone are insufficient, and recommends linking SBOMs to vulnerability, advisory and tooling ecosystems.
read more →

CISA's AI SBOM Guidance Expands Supply‑Chain Oversight

🔍 The US Cybersecurity and Infrastructure Security Agency (CISA), working with G7 cyber partners, released supplemental minimum elements for an AI software bill of materials to document models, datasets, software components, providers, licenses, and other dependencies. The guidance extends traditional SBOM concepts into AI and is positioned to support procurement and vendor-risk assessments while remaining non‑exhaustive and non‑mandatory. Security teams should press vendors for model provenance, training and update practices, and runtime controls, but must recognize AI SBOMs provide visibility rather than assurance.
read more →

Malicious litellm Wheel Found in Python Package Index

⚠️ TrueSec reports a malicious supply-chain compromise in the Python Package Index package litellm version 1.82.8. The published wheel contains a malicious .pth file named litellm_init.pth (34,628 bytes) that the Python interpreter executes automatically on every startup, without requiring any explicit import of the module. This behavior enables silent, persistent code execution on affected systems and increases the risk to downstream projects and production environments. The incident underscores the urgent need for SBOMs, SLSA, and SigStore adoption to harden supply-chain defenses.
read more →