Five things from the past working week that a UK board should know about, in the order I would raise them with a chair over coffee on Monday morning. It was a week in which the government put money behind AI-led defence, the PHP flaw that closed Whitehall sites last week turned up in a state-aligned toolkit, and a signals agency admitted it cannot count its own removable media. I have left out the noise. What survives has a decision attached.

1. The government has put £130 million behind AI-led cyber defence

Ahead of the Budget, the Chancellor's AI package set out £60 million for a National Cyber Shield, which includes a £25 million challenge fund, and £70 million for a National Exposure and Real-Time Vulnerability Centre that will use AI to find weaknesses across critical infrastructure and the wider economy. The Register reports that the announcement follows the PHP2Shell incident, and that the AI minister said AI had found 500 previously unknown flaws across parts of the public sector. Money is not capability, and neither the Shield nor the new centre exists yet. What exists today is the expectation that someone else will find your exposure before an attacker does.

For boards. Do not wait for a national service to tell you what you expose. Ask your security lead for the list of internet-facing systems as an attacker would see it, how often it is refreshed, and who owns each entry.

2. The PHP flaw is now in a state-aligned toolkit

Last week's PHP2Shell vulnerabilities, CVE-2026-109618 and CVE-2026-109619, have moved from emergency patching to deliberate campaigns. The Register reports that suspected Chinese attackers chained them with Fragnesia, a Linux kernel privilege-escalation flaw (CVE-2026-46300), to take root on 25 servers, including Palo Alto Networks firewalls running PAN-OS 12.1 and 12.2, in under 15 minutes. Dream, the Israeli firm that found it, says Unit 42 verified the tooling. The reported victims were in the US, Japan, Taiwan and South Korea, and CISA added Fragnesia to its Known Exploited Vulnerabilities catalogue on Wednesday. I found no confirmed UK victim. Separately, Cisco patched an actively exploited denial-of-service flaw, CVE-2026-76418, in the SSL VPN service on ASA and FTD firewalls.

For boards. Perimeter devices are where the chain started. Ask whether your firewalls and VPN gateways were patched for both PHP2Shell and Fragnesia, and who confirmed it.

3. Two supply chain stories, one lesson about secrets

LiteLLM's compromise, which I covered last week, began with a master key committed to a public GitHub repository on 27 May. The commit was removed but the key was never revoked, and the attacker used it on 10 October. Wiz puts downloads of the poisoned release at about 49,000. Meanwhile Radware found a campaign hiding commands in issue and pull request comments to run in workflows that trust outside content; The Register counts 83 malicious items across 61 public repositories, and two confirmed executions. Radware could not confirm any downstream compromise. In both cases the weakness was a secret that outlived its need, or a pipeline that trusted a stranger.

For boards. Ask when your engineers last rotated credentials after an exposure, not just removed them, and whether your build workflows run code from unauthenticated outsiders with secrets in reach.

4. GCHQ cannot say how many storage devices it has lost

The Investigatory Powers Commissioner's Office published its 2025 annual report on 29 October. Lord Leveson says GCHQ still cannot establish the scale, location or recoverability of lost removable media that may hold data relating to the Investigatory Powers Act. The Register reports that GCHQ puts the number at thousands, says its removable media system was not robust enough, and expects automated asset tracking by the end of the year. The issue was first raised several years ago. It is a good test of any inventory: if you cannot count it, you cannot say it has not left.

For boards. Ask for a count of removable media and laptops, and for the date of the last reconciliation against what is actually held. A number with a confidence level beats a reassurance.

5. A small UK reseller learned of its breach from Stripe

Shelly Store UK, an authorised reseller of Shelly smart home products, has told customers that payment card details may have been stolen after unauthorised software was found on its website and server. Shelly's own spokesperson says the reseller is not part of or owned by Shelly Group. Stripe raised the alarm, the ICO has been told, and one customer reported a £221.28 card transaction in Australia on 26 October, after an order on 12 October. The company cannot yet confirm whether data was copied.

For boards. Your payment provider may tell you about a breach before your own monitoring does. Ask who receives those warnings, how quickly they reach someone with authority to act, and whether your website's scripts are monitored for change.

The thread that ties this together

Every story this week comes back to knowing what you have and what it can reach: exposure nobody has listed, a key nobody revoked, drives nobody counted, a web server nobody was watching. The new national centres may help, but they will not make your inventory for you.

If a regulator, a payment provider or a researcher found a weakness in your estate on Monday, would you hear it from them or from your own records?