A Handbook in Washington, a Law in Singapore: The Governance Gap PMOs Actually Fill

Posted on by

Two documents delivered in 2026 that both claim to tell a board how to govern cyber risk. One is a handbook. The other is law. The distance between the two is where most PMOs currently sit, translating voluntary best practice into something a director can actually be held to.

The Handbook: Comprehensive, Voluntary, US-Focused

In April 2026, the National Association of Corporate Directors and the Internet Security Alliance released the fifth edition of the Director’s Handbook on Cyber-Risk Oversight. It is thorough. Six principles cover treating cyber security as a strategic risk, monitoring legal and disclosure exposure, building board oversight structures, adopting an enterprise risk framework, guiding measurement and reporting, and encouraging systemic resilience. It cites more than 600 million tracked cyberattacks a day and projected annual cybercrime losses approaching 20 trillion dollars globally. What it does not do, because it is guidance rather than statute, is compel a single board anywhere to act on any of it.

 

The Law: Narrower, Binding, and Personal

Singapore closed that gap for its own critical infrastructure operators in 2026 with an updated Cybersecurity Code of Practice. Boards of operators across eleven sectors, energy, telecommunications, water, healthcare, banking, aviation, maritime, government and more, must now maintain a documented resilience framework covering risk tolerance, mitigation, transfer and recovery, reviewed at least annually. Certification deadlines follow in December 2026 and December 2027. Directors can face personal liability where a company fails to prevent or properly respond to an incident because of a lack of the skill, care or diligence the role required. That is a materially different proposition from reading a handbook. It converts board oversight from a best-practice expectation into a standard a director can be judged against.

 

The Gap Between Them Is Where PMOs Live

Most organisations operating internationally will encounter both models at once, comprehensive American guidance describing what good oversight looks like, and a narrower but binding Asian regulatory standard describing what oversight is legally required to look like. Neither one, on its own, tells a PMO what to actually build. The handbook is too broad to implement directly. The code is too sector-specific to generalise from. The practical work, translating six abstract principles into a working reporting cadence, a named accountable owner, and evidence a board can point to if asked, sits squarely inside the PMO’s remit rather than the CISO’s alone or the board’s alone.

 

What a PMO Should Build From Both

A credible cyber governance structure borrows the handbook’s breadth and the code’s specificity. That means a documented framework reviewed at a fixed interval, not an annual slide nobody revisits, a named board-level owner who can answer for the organisation’s posture in plain language, and evidence, tested and dated, that oversight was real rather than assumed. Boards do not need another handbook to read. They need proof that what the last one said actually happened.

Four Countries, Four Health Systems, the Same Cyber Risk Tier

Posted on by

By August 2026, four European countries, Poland, the UK, France and Germany, had entered the critical tier of a healthcare cyber risk index covering 30 nations. France was still rebuilding more than 1,000 workstations and roughly 200 applications, five months after an October 2025 attack hit eight sites. Germany’s Unimed incident had disrupted care for more than 135,000 people across connected institutions. Every one of these countries has invested heavily in hospital cyber security. None of that investment, on its own, has been enough.

 

The Diagnosis Is Cultural, Not Technical

Research published by King’s College London in March 2026 offers a specific explanation for why. Reviewing NHS Trust cyber resilience, the researchers concluded that ransomware remains the most acute threat facing hospitals not primarily because of a technology gap, but because of inconsistent governance maturity and, more pointedly, a cultural rather than technical or financial constraint. Trusts with comparable budgets and comparable tooling still show wildly different resilience outcomes, which points toward leadership and accountability structures as the actual variable rather than the size of the security budget.

 

A Framework Built Around Ownership, Not Just Controls

The KCL research proposes what it calls a Cyber Leadership Framework, built on board-level ownership of cyber risk, an empowered CIO or CISO with real authority rather than a title, and a deliberate effort to connect technical controls to what actually happens in a ward or a clinic rather than treating cyber security as a parallel IT concern. Its most structurally significant recommendation is greater centralisation of core cyber capabilities and shared services across otherwise fragmented Trusts, replacing dozens of individually under-resourced security functions with fewer, better-resourced shared ones.

 

The Same Fragmentation Problem Shows Up Across Borders

That fragmentation is not a uniquely British problem. The Black Book Europe-30 Healthcare Cyber Risk Pressure Index, measuring attack pressure, clinical digital dependence, supplier concentration and recovery friction across 30 countries, found 13 of them sitting in the two highest risk bands, with Poland, the UK, France and Germany specifically flagged as critical. Each of these health systems is organised differently, some more centralised than the NHS, some more fragmented, and all four still ended up in the same risk category. Centralisation on its own is not a guaranteed fix. What the KCL research adds is the missing piece, shared capability paired with genuine board-level accountability, rather than shared capability alone.

 

What This Means for Healthcare Programme Governance

A healthcare PMO reviewing cyber resilience investment should treat the KCL framework as a diagnostic tool rather than an NHS-specific recommendation. The practical test is straightforward: can a board member currently name who owns cyber risk for their organisation, describe what shared capability actually exists beyond their own site, and point to when that capability was last tested under real pressure rather than reviewed on paper. France’s five-month rebuild and Germany’s 135,000-person incident both suggest that answering those questions honestly, before an attack rather than after one, is the entire point of the exercise.

Pre-Mortem: The Post Office’s Horizon Replacement

Posted on by

On 24 August 2026, the Post Office finally signed contracts with all three suppliers meant to replace Fujitsu’s Horizon system, the software behind Britain’s most widespread miscarriage of justice. Accenture takes over day-to-day running of the current system and is building the new back end, OneView Commerce will supply new till software for branches, and Escher will supply the software configuring individual transactions. Getting all three suppliers under contract at once, after a legal challenge and six delays to the same signing, is a genuine achievement: for the first time since the programme began, Fujitsu’s exit has a complete supplier line-up rather than a plan on paper.

This Pre-Mortem asks the questions a post-mortem would ask, before failure is possible: what is being bet on, what single assumption could break it, what got decided before the safeguards existed, who carries the pager when it fails, and what proof would settle whether it worked. It is the diligence a troubled, high-stakes programme deserves before its next test, not after.

 

The Bet

The Post Office is betting that three specialist suppliers working in parallel succeed where the government’s own auditors said success was structurally unlikely. The Cabinet Office’s Infrastructure and Projects Authority, in a 2024 review that rated the programme’s delivery unachievable, also found the Post Office board “not sufficiently experienced in technical matters to take decisions and make judgements on risk,” even as the organisation cut the programme’s own staffing by 70% on a delivery timescale experts called unrealistic. The bill has since grown to £1.1 billion, more than six times the £180 million forecast when the project began in 2021. The August signings are the moment that bet stops being theoretical.

 

The Assumption

The load-bearing belief is that Fujitsu’s departure now has a fixed date attached to it. It does not. Fujitsu’s existing Horizon contract carries a built-in option that could extend the relationship into 2028, regardless of how quickly the new suppliers deliver. Nothing in the August signings closes that option or replaces it with a firmer commitment. A three-supplier replacement can succeed completely, on its own schedule, and still share Post Office counters with the system it was built to replace for longer than any public document currently commits to.

 

The Sequence

The signing due in June was delayed six times before it happened in August, as a mandatory standstill period, the window in which a losing bidder can contest a procurement decision, was repeatedly extended around the original £170 million till-software contract. The losing bidder was Escher. Rather than resolve matters through that same competitive process, the Post Office created a separate contract and, a procurement notice later confirmed, awarded it directly to Escher without any competitive tender, worth £14.4 million, on the grounds that Escher alone owns the software needed to configure branch transactions. The fix for one procurement problem arrived only after that problem had already delayed delivery by months.

 

The Pager

Post Office CEO Neil Brocklehurst put his name to the official announcement of the completed supplier line-up, calling it “another important step forward” and describing the replacement as “one of the most significant changes” the organisation is making. He is the named executive carrying the transformation as a whole. But no individual, at the Post Office or in government, has been publicly named as accountable for the sixfold growth in cost since 2021, or for the procurement correction that delayed signing by months. The £1.1 billion and the delay sit with “the programme,” a description that assigns responsibility to no one in particular.

 

The Proof

In February 2026, the government committed £483 million in fresh funding, nearly half a billion pounds over two years, to support the move away from Fujitsu. Six months later, the announcement of the completed supplier line-up commits to no completion date and no performance metric: it states only that work is underway to establish detailed plans, timelines and delivery arrangements for a system that will be configured, tested and introduced in phases. Half a billion pounds of fresh funding has bought a supplier line-up, not yet a date. Eighteen months from now is roughly the point by which a working phased rollout, or its continued absence, should be publicly visible.

 

Verdict

If the three suppliers deliver a working, fully configured system, and Fujitsu’s exit is fixed in writing rather than left to an option that can run into 2028, the sixfold cost growth and the months of delayed signing will read as the price of getting a uniquely fraught IT replacement right rather than fast. If the timeline slips again, or the Escher direct award turns out to be the first of several sole-source corrections, the programme built to end Britain’s most damaging IT scandal will have spent well over a billion pounds relearning the same lesson about unaccountable decision-making that caused it.

One Token, Three Tools Deep, 2,500 Companies Across Five Continents

Posted on by

One leaked automation token. Three tools deep. Over 2,500 organisations across five continents exposed. That is the entire anatomy of 2026’s largest AI supply chain breach, and it took roughly forty minutes to happen.

How a Security Scanner Became the Weapon

In March 2026, a threat group tracked as TeamPCP compromised Trivy, a widely used open-source security scanner, through a leaked automation token. From there the attackers force-pushed malicious code into Trivy’s own version tags. When LiteLLM, a popular AI gateway that routes traffic between applications and model providers, pulled the poisoned scanner into its build pipeline, it published two compromised releases to PyPI, versions 1.82.7 and 1.82.8. A hidden file inside those packages executed automatically the moment Python started, no import required, harvesting cloud keys, repository tokens, SSH credentials, Kubernetes secrets and AI provider API keys from anyone who installed it. The malicious packages were live for roughly forty minutes before removal. That was enough.

 

A Genuinely Global Exposure List

CloudSEK’s analysis, later corroborated by an FBI advisory in July, identified more than 2,500 affected organisations and 434,000 exposed CI/CD pipelines. The named companies span the world rather than one region: AWS, Nvidia, Salesforce and Airbus’s US Space and Defense division from the US, Samsung Electronics and MediaTek from Asia, Siemens, Volkswagen and Munich Re from Germany, Thales and Orange from France, Roche from Switzerland, Philips from the Netherlands, Vodafone and the London Stock Exchange Group from the UK, and Thomson Reuters from Canada, alongside Cisco, FedEx, Deloitte and dozens more. This was never a story about one country’s technology sector. It was a demonstration of how deeply a single open-source dependency now sits underneath enterprise infrastructure everywhere.

 

The Same Argument, a Different Layer

This publication has already made the case that The September AI Outage Had Two Real Causes. Almost Everyone Reported One. LiteLLM extends that argument one layer deeper, into the software supply chain feeding the infrastructure itself. A vendor risk register that lists which cloud provider or model vendor an organisation depends on is no longer sufficient. It also needs to account for the open-source scanners, build tools and CI pipelines every one of those vendors quietly depends on, tools most procurement processes never ask about because nobody signed a contract for them.

 

What a PMO Should Actually Check

Three questions belong on every technology steering committee agenda this quarter. First, does anyone in the organisation maintain a current list of the open-source build and security tooling embedded in critical CI/CD pipelines, not just the paid vendors. Second, when was a leaked or rotated credential last tested as an actual incident scenario, rather than a line item in a policy document. Third, if a dependency three layers removed from a primary vendor were compromised tomorrow, how long would it take anyone to notice. The organisations named in the LiteLLM breach were not careless. They were exposed by a dependency most of them did not know they had, which is precisely the risk a vendor register built only around visible, contracted suppliers will always miss.

The September AI Outage Had Two Real Causes. Almost Everyone Reported One.

Posted on by

On the morning of 3 September 2026, ChatGPT, Claude and Grok all failed within roughly ninety minutes of each other. Within hours, most coverage had settled on a single explanation: a shared Microsoft Azure failure had taken down three competing AI platforms at once. The postmortems that actually exist tell a different story, and the difference matters more than the outage itself.

 

What Each Company Actually Said

SpaceXAI was the most direct. The company confirmed a failure at its Memphis compute facility, apologising to what it called its “impacted compute partners,” language that implies other organisations lease capacity in the same facility. Grok was down for roughly three and a half hours. OpenAI gave its own, separate explanation: an engineer identifying as the incident commander stated on Hacker News that the cause was a routing error inside OpenAI’s own infrastructure, surfacing roughly ninety minutes after SpaceXAI’s Memphis failure and unconnected to the GPT-6 Astra launch that followed the next day. Anthropic never published a technical cause at all. It confirmed elevated errors across several Claude models starting around 9:26am ET and reported the issue resolved, but the actual mechanism behind it was never disclosed.

 

Why the Azure Theory Doesn’t Hold Up

The Azure theory spread fast because it was the simplest explanation available in the first few hours, and it fit an existing assumption that most enterprise AI risk registers already carry: if these vendors compete, their infrastructure probably doesn’t overlap. It did not hold up. Microsoft logged no Azure incident for that window, and Cloudflare said in a statement that it was not experiencing any significant service disruptions. The timeline argues against one shared trigger too, SpaceXAI’s and Anthropic’s incidents began four minutes apart from each other, and OpenAI’s followed roughly ninety minutes later, a pattern that fits three separate incidents more comfortably than one shared one.

 

The Question Nobody Answered

The part worth noticing is not that the Azure story was wrong. It is that the two companies which did give an explanation gave two different ones, and the one that stayed quiet is the one whose incident opened four minutes before SpaceXAI’s, the tightest timing overlap of the three. Nobody, including Anthropic, ever confirmed or ruled out whether Claude’s infrastructure touches the same Memphis facility SpaceXAI apologised to its partners about. A vendor risk register cannot verify a question its own vendor never answers.

None of this means multi-vendor AI strategy is worthless. It means the diversification most risk registers assume is rarely something a customer can actually verify from the outside, and the one moment it gets tested, a real outage, is also the moment vendors are least likely to disclose the detail that would let you check. Two of three companies gave a specific, different cause. One gave none. Whichever of those a programme is depending on, the honest entry in a vendor risk register reads “unconfirmed,” not “diversified.”

Three Regulators, Three Continents, One 72-Hour Deadline Nobody Is Ready For

Posted on by

Three regulators, on three different continents, converged on almost the same number this year, entirely independently. Washington set 72 hours. Brussels set 72 hours, after an initial 24-hour early warning. Abu Dhabi’s own financial free zones set 24 to 72 hours, depending on which one is asking. None of them coordinated on this. All three concluded, at roughly the same time, that a cyber incident report cannot wait for an organisation to feel ready to send it.

 

What Each Regime Actually Requires

In the United States, the Cyber Incident Reporting for Critical Infrastructure Act, CIRCIA, is expected to be finalised this month. It will require covered entities across 16 critical infrastructure sectors, an estimated 300,000 organisations in total, to report a significant cyber incident within 72 hours and a ransomware payment within 24. In the European Union, the NIS2 Directive is already live. Essential entities, those with 250 or more staff or turnover above 50 million euros, across energy, healthcare, banking, water and digital infrastructure, must send an early warning within 24 hours, a full assessment within 72, and a final report within a month. In the UAE, the pattern repeats at the free zone level. Firms regulated by Abu Dhabi Global Market must report a material cyber incident to the regulator within 24 hours, weekends and public holidays included. Firms in the Dubai International Financial Centre generally work to a 72-hour window. Three jurisdictions, three legal systems, the same rough number.

 

Why This Is a Delivery Problem, Not a Legal One

Most organisations have handed this requirement to legal or compliance to interpret, which is the wrong owner. A 72-hour reporting deadline is not primarily a question of what the law says. It is a question of whether an organisation can detect an incident, assess its materiality, assemble the right people, and produce an accurate report, all inside three days, under pressure, without the benefit of hindsight. That is a programme capability, not a policy position. Legal can tell you what the deadline is. Legal cannot build the operating rhythm that hits it.

 

The Capability Most Organisations Are Missing

The gap rarely shows up in the reporting template. It shows up upstream, in whether anyone can say, inside the first few hours, what actually happened. A US hospital system’s own social media accounts were hijacked by the ransomware group that had already breached it, which posted ransom demands directly to the public before the organisation regained control, a case study in how quickly a slow, uncoordinated response becomes the story itself. A reporting deadline assumes an organisation already knows what it is looking at. Most of the work that determines whether a report is accurate, or even possible, happens before anyone opens the compliance template.

 

What a Real Programme Looks Like

A credible response to any of these three regimes looks less like a legal memo and more like a programme: a named incident commander, a materiality assessment framework agreed before an incident rather than during one, a communications protocol that assumes attackers may control channels an organisation thinks are its own, and a rehearsal cadence, not a policy filed away and never tested. None of that is jurisdiction-specific. An organisation that builds this properly for NIS2 has, with minor adjustment, built it for CIRCIA and for ADGM as well.

The interesting part of this story is not which country moved first. Three regulators, working independently on three continents, arrived at the same conclusion, that organisations cannot be trusted to disclose on their own timeline, so a timeline was imposed. Whichever regime applies, the question worth asking this quarter is simple. Could the organisation hit the deadline today, if the incident happened this afternoon?

93% Have Been Breached by Vulnerable AI Code. 30% Still Ship It Anyway.

Posted on by


Seventy per cent of developers believe AI-generated code carries more vulnerabilities than the code they write themselves. Thirty per cent ship it into production anyway, knowingly. Ninety-three per cent of the same respondents report at least one breach traced back to a vulnerable application. Awareness of the risk and action on the risk are not the same thing. They rarely are, according to every major AI risk study published so far this year.

 

The Core Finding Repeats Across Every Study That Looks

The Purple Book Community’s State of AI Risk Management 2026 report, surveying more than 650 senior cybersecurity leaders across North America and Europe between December 2025 and February 2026, found 59 per cent of organisations acknowledging shadow AI within their own environment, despite 90 per cent claiming confidence in their AI visibility. Seventy-eight per cent are already piloting or deploying agentic AI systems, and 73 per cent say AI-assisted development is outpacing their security review cycles. Fifty-one per cent run 11 or more separate security scanning tools, and 46 per cent of teams spend significant time triaging vulnerabilities that turn out not to matter. Governance has not kept pace with adoption. It has fallen further behind with each new AI capability organisations switch on.

 

The Global Maturity Picture Is Worse Than Any Single Region’s

The World Economic Forum’s Advancing Responsible AI Innovation research, covering 1,500 organisations worldwide, found 81 per cent still sitting in the earliest two stages of responsible AI maturity. Regional breakdowns make that global figure look almost optimistic. In Asia-Pacific, only 1 per cent of organisations have fully operationalised responsible AI practices, a gap researchers describe as more pronounced than the global average. Separate research from Dataiku found 94 per cent of CEOs suspect employees are already using generative AI tools without authorisation, while 75 per cent of data leaders admit low trust in their own organisation’s AI agent deployments.

 

The Middle East Shows a Different Symptom of the Same Disease

Middle Eastern enterprises are not struggling with pilots. Multiple regional AI advisory reports this year describe successful proof-of-concept projects stalling the moment organisations attempt enterprise-wide rollout, blocked by exactly the governance gap the global data points to: no clear ownership of AI risk decisions, inconsistent access controls, and the added complexity of navigating different data protection and AI-specific regulations across Gulf jurisdictions simultaneously. The technology performs in the pilot. The governance structure needed to scale it safely usually does not exist yet.

 

What This Means for How Organisations Govern AI Risk

Every regional variant of this research points to the same structural gap rather than three unrelated problems. A risk committee should treat confidence surveys as a warning sign rather than reassurance, ask specifically what percentage of AI-generated code has been reviewed rather than whether a review process exists on paper, and confirm who owns AI risk decisions before the next agentic AI pilot moves toward production. The pattern holding across North America, Europe, Asia-Pacific and the Gulf is consistent enough to stop treating it as one company’s oversight and start treating it as this year’s defining governance failure.

SAP Told Its Customers Which AI to Use. Three Per Cent Listened.

Posted on by

By February 2026, DSAG’s own Investment Report had already surfaced the gap SAP would spend the rest of the year trying to close by other means. Only 3 per cent of surveyed companies ran their production AI use cases on SAP’s own tools, while 77 per cent ran theirs on non-SAP solutions instead, Microsoft Copilot chief among them. Two months later, SAP rewrote its API policy. Section 2.2.2 of the new terms blocks external AI agents from calling SAP systems directly, prohibiting what it calls independent scheduling or execution of API calls. Every agentic use case now has to route through Joule, SAP’s own assistant, adding a second layer of inference and cost to anything a customer’s AI tools want to do inside SAP.

 

Two Competitors Bet the Opposite Way

Salesforce and ServiceNow read the same gap differently. Salesforce launched Headless 360 in April 2026, giving external agents direct access through REST, Model Context Protocol tools and the command line, no mandatory detour through a proprietary assistant required. ServiceNow’s Action Fabric, announced at Knowledge 2026, opened two decades of workflows and business rules to any agent through the same open standards. Neither company built a legal wall around its intelligence layer. Both are betting that customers will choose their AI because it is good, not because the contract requires it.

 

The Mandate Had a Structural Problem Too

Joule is only available to customers on RISE or GROW with SAP cloud contracts, which shuts out the thousands of organisations still running on-premise ECC. Support for ECC 6.0 ends in 2027, so over ten thousand customers are being asked to migrate their core system and adopt a mandated AI layer on the same timeline, set by the vendor rather than the customer. SAP’s own chief customer officer has disputed the DSAG survey’s reach, noting that fewer than 100 organisations responded, which is a fair challenge to the precision of the number. It does not explain why SAP is separately funding a hundred-million-euro partner investment programme to accelerate adoption of a product it says the market already wants.

 

The Hedge That Followed the Mandate

At Sapphire 2026, a few months after the API policy took effect, SAP quietly hedged its own bet. Alongside Joule Studio 2.0, it introduced an AI Agent Hub, described as vendor-agnostic governance for SAP and third-party agents alike, bundled into the platform at no extra charge. A company confident that mandating Joule had closed the gap DSAG measured in February would not need to build the open door it spent the spring telling customers they did not need.

 

The Question Every PMO Should Be Asking Now

None of this is really about SAP. Every PMO running a platform strategy right now is making the same call in miniature, whether to route AI agents through one sanctioned tool or leave the door open for whichever tool the business actually adopts. SAP had the market power to write the mandate into a contract, and it wrote that mandate only after its own user group had already published the adoption numbers it was meant to fix. Assume your organisation has less leverage than SAP did, and plan the exit clause before you write the mandate, not after the adoption numbers come back.

Your AI Steering Committee Meets Monthly. Your AI Ships Weekly.

Posted on by

Most AI governance committees meet on a monthly or quarterly cadence. Most AI systems do not wait for them.

Anthropic’s own release notes tell the story in a single scroll. Opus 5 launched in late July 2026, a step-change release over Opus 4.8, which was barely two months old at the time. Sonnet 5 landed a month before that, at the end of June. Opus 4.8 before that, in late May. Opus 4.7 before that, in April, with breaking API changes attached. Opus 4.5 in November 2025. Sonnet 4.5 in September. Six major model versions inside ten months, with incremental API and feature changes logged in between on a near-weekly basis. That is one vendor’s changelog. Most enterprises are running several.

 

The Governance Side Has Not Kept Pace

Deloitte’s 2026 State of AI in the Enterprise survey, covering 3,235 business and IT leaders across 24 countries, found that only 21% of organisations have a mature governance model in place for agentic AI. Meanwhile, 74% of the same leaders expect their organisation to be using AI agents at least moderately by 2027, with 23% expecting extensive use and 5% expecting full integration.

That is not a small gap closing gradually. It is deployment intent running well ahead of the governance capable of managing it, at the exact moment agentic systems are gaining the authority to act rather than just draft.

 

People Have Already Stopped Waiting

The gap does not sit quietly while committees catch up. A Cybernews survey of more than 1,000 US employees found that 59% use AI tools their employer never approved. Among executives and senior managers specifically, the same survey found 93% do the same. The people who would sit on the steering committee approving AI use are, by a wide margin, the people going around it.

That is the quiet part of this problem. The people with the authority to slow things down are the ones setting the pace of the tools rather than the pace of the committee.

 

What Happens When the Gap Surfaces

Gartner’s prediction for next year is specific: 40% of enterprises will have their autonomous AI efforts partly derailed by governance gaps discovered only after a production incident, not before one. Sanchit Vir Gogia of Greyhound Research, commenting on the same data, put the mechanism plainly: “the real governance problem is not model intelligence. It is delegated operational authority moving across trust boundaries faster than enterprises can instrument, constrain, or audit it.” His own warning, in his words: “Do not scale agents faster than you can govern their authority. A small number of well-governed agents will create more enterprise value than a sprawling estate of clever, fragile, over-permissioned digital apprentices.”

 

What Governance Cadence Actually Needs to Look Like

The fix is not more meetings. A committee that reviews AI deployment quarterly cannot govern a system that changes weekly, no matter how thorough each quarterly review is. What changes the equation is moving from periodic review to continuous, tiered oversight: automatic flags for any new agent or capability change above an agreed risk threshold, standing authority delegated to a smaller operational group empowered to act between full committee meetings, and a real audit trail that lets the full committee review what was approved at pace, after the fact, rather than approving everything before the fact and creating the exact bottleneck this problem describes.

Keeping oversight in place does not mean keeping the quarterly cadence that was designed for a technology that no longer exists.

 

The Question Worth Asking Before the Next Steering Committee Meeting

Ask what actually changed in your AI environment since the last meeting, specifically, not generally. If nobody in the room can answer that with real detail, the governance structure is reviewing a snapshot that was already out of date the moment the meeting started.

The organisations that get this right are not the ones meeting more often. They are the ones who redesigned what needs a meeting at all, and gave someone standing authority to handle everything else in between.

EU Cyber Resilience Act – Reporting Duty Begins on an Unfinished Platform

Posted on by

On 11 September 2026, the European Union’s Cyber Resilience Act began requiring manufacturers of products with digital elements to report actively exploited vulnerabilities and severe incidents within 24 hours of becoming aware of them. The duty runs through the EU Agency for Cybersecurity’s new Single Reporting Platform, which ENISA switched on the same day while describing it as having reached only “initial operating capability.” That the deadline and its supporting infrastructure arrived on the identical date is itself the story, and it comes with a genuine credit: a manufacturer selling into the EU can now file one exploited-vulnerability report and have it reach every relevant national authority, rather than notifying each member state separately.

This Pre-Mortem asks the questions a post-mortem would ask, before failure is possible: what is being bet on, what single assumption could break it, what got decided before the safeguards existed, who carries the pager when it fails, and what proof would settle whether it worked. It is the diligence a compressed rollout deserves before its first real test, not after.

 

The Bet

The EU is betting that centralising exploited-vulnerability and severe-incident reporting through one platform gives ENISA and national CSIRTs (Computer Security Incident Response Teams) EU-wide visibility into what is actually being attacked, and that manufacturers will treat a 24-hour clock as workable even while the tool underneath it is still being built out. The bet favours momentum over completeness. The European Commission’s own guidance on the CRA’s reporting obligations confirms the platform was already operational on 11 September 2026, the same day the 24-hour duty took effect, rather than waiting until it was finished. It also asks industry to build compliance discipline around a tool still being assembled, in the same quarter that discipline is tested.

 

The Assumption

The load-bearing belief is that a “single” platform stays meaningfully single even with core pieces missing. As the specialist tracker cyberresilienceact.eu reported on launch day itself, voluntary reporting under Article 15, a programming interface, and a field recording exactly when a manufacturer became aware of an incident all “did not arrive with it,” and access runs only through an Assigned Representative role via EU Login multi-factor authentication. If that gap persists, manufacturers with products across many jurisdictions and limited access routes could end up filing manually into individual CSIRTs anyway, the exact fragmentation Article 16 was written to end.

 

The Sequence

The Commission did not settle what counts as a manufacturer becoming “aware” of a reportable event, the trigger that starts every clock in the regime, until its guidance published on 27 July 2026, six weeks before the duty began. For most of the preceding compliance-planning year, manufacturers had no published definition of the one moment that decides whether a 24-hour window has even opened. ENISA’s own Assigned Representative registration guidance still carried dated updates in launch week itself, on 9 and 10 September 2026, the guidance for actually using the platform arriving alongside it rather than well ahead of it.

 

The Pager

ENISA’s Executive Director, Juhan Lepassaar, put his name to the launch, framing it as a step toward “a more resilient Digital Single Market,” and carries the operational pager for the platform itself. Above him sits European Commission Executive Vice-President for Tech Sovereignty, Security and Democracy Henna Virkkunen, who holds the political brief for EU cybersecurity policy, having worked on the Cyber Resilience Act dossier in Parliament. Beneath both, national market surveillance authorities enforce the penalty tier attached to Article 14 failures: up to €15 million, or 2.5 per cent of global turnover. No individual has been named as accountable for the missing programming interface and voluntary-reporting channel, only an agency-level pledge to keep improving.

 

The Proof

No public dashboard, uptime figure, or notification-volume metric has been attached to the platform’s launch, and ENISA’s own pledge to keep improving it carries no completion date. The measure that would actually settle the question, whether a report filed with one coordinating CSIRT reaches every other relevant CSIRT and ENISA at the speed the platform promises, has not been made public in any testable form. That will only become visible once a real, cross-border, multi-product incident runs through the system at volume, rather than from the demonstration traffic of launch week, and eighteen months allows roughly two CRA reporting cycles for that test to arrive.

 

Verdict

If ENISA closes the Single Reporting Platform’s programming-interface and voluntary-reporting gaps, and attaches a public date to doing so, before the platform faces its first genuinely cross-border, multi-CSIRT incident, then 11 September 2026 will read as a pragmatic phased launch that got the hardest deadline live on time. If those gaps are still open when that incident arrives, manufacturers already working to a 24-hour clock will discover that the single reporting platform was, in practice, still several platforms wearing one name.