Two publications on the same day moved security assurance out of guidance and into what buyers must ask for — NCSC UK telling firewall customers to make forensic observability an evaluation criterion, and eighteen agencies adding component hashes, licences and generation context to the SBOM minimum elements

Neither of these publications is binding on a Swiss body, and neither asks a SOC to do anything on Monday. They matter because they change the leverage available at the only point where a defender can influence a vendor's engineering priorities — the specification a buyer writes.

NCSC UK's post makes the argument explicitly. It defines the property it wants: "forensic observability means giving defenders reliable ways to understand what a device is doing, what it has done and whether it can still be trusted after an incident. This includes telemetry, logging, configuration state, and the ability to collect forensic data from both memory and data at rest" (NCSC UK, 2026-07-29). The target is the edge — firewalls, VPN gateways and the other appliances sitting at trust boundaries — where the current situation is that establishing what happened after an intrusion depends on reverse engineering or specialist vulnerability research rather than on anything the product provides. And it names the forcing function rather than appealing to vendors: "Buyers: If your edge devices don't have this feature, push for it. The fastest route to widespread adoption may be for customers to ask for these capabilities as standard." The post also confirms that "the NCSC has been working with international partners to develop a reference architecture for forensic observability in network appliances and similar devices," with the goal of describing a practical approach vendors can adopt while maintaining strong security boundaries — in development, not yet published. Sophos, quoted in the post reflecting on its own long-running edge-device intrusion investigation, says it is encouraging anyone buying a firewall to make forensic observability part of their evaluation criteria. The relevance to this constituency is immediate and concrete: every one of this year's edge-appliance compromise stories, and several in this week's own coverage, turned on whether the appliance could tell its owner what had happened to it.

The same day, an eighteen-agency group led by CISA, the NSA and the FBI — including Germany's BSI, France's ANSSI and NCSC-NL among the co-authors — published the 2026 Minimum Elements for a Software Bill of Materials, replacing the 2021 baseline after a public comment period that drew "more than 90 comments." CISA states that "the minimum elements in this revision apply to SBOMs for all software, including open-source software, AI software, and software-as-a-service (SaaS)" (CISA, 2026-07-29) — a scope clarification rather than a set of AI-specific fields; the guidance document is explicit that it does not introduce additional elements for AI-system SBOMs. What it does add is a set of required data fields that make an SBOM verifiable rather than merely descriptive: an SBOM author signature, data format name and version, generation context, tool name and version, SBOM version, component hash value and hash algorithm, and component licence (CISA and partners, 2026-07-29). The component hash is the consequential one: it is defined as the output of applying a cryptographic hash to the executable component artefact, which turns a component list into something an inventory can be matched against rather than a set of names and version strings that may or may not describe what actually shipped.