Five priorities,
five mechanisms — sample of how each one can be implemented
The Senior Minister of State's five priorities — issued in the same week MAS convened bank CEOs over Mythos and ran the cross-bank fraud Proof-of-Value — read in plain English as a list every CISO already agrees with. Read architecturally, they describe five distinct mechanisms, each requiring different metadata, different platform, different governance. This brief separates them, animates each mechanism, and names what the bank actually builds.
The five priorities - Each one is structurally different from the others. The first is about the shape of time — the window between disclosure and exploitation, and what the bank does to compress its own response inside that window. The second is about the shape of the asset graph — what is and is not under management. The third is about the cadence of detection — periodic versus continuous, two completely different operating models. The fourth is about internal AI governance — the bank as a deployer of AI, with all the lifecycle controls that implies. The fifth is about external AI deployment in defence — the bank using AI offensively against the threat surface.
The architect's reading: this is not a calendar exercise. It is a question about the velocity of your risk register. If your risk assessment refreshes annually, and the disclosure-to-exploitation gap has compressed from weeks to hours, your register is producing stale truths by construction. The remedy is structural — the risk register has to become a real-time data product joined against vulnerability feeds, asset state, and threat intelligence, rather than a quarterly committee artefact.
OT is the harder half. IT teams have spent two decades building patch cadence; OT teams in BFSI (ATM networks, branch automation, payment terminals, building management systems sitting one network hop from core) have not. The supervisory expectation now folds OT into the same surface as IT, which means the bank's asset register has to span both — and most don't.
Mechanism · the window narrows
Animated · CSS-onlyWhat the bank builds.
The architect's reading: the asset register is a single source of truth, not a CMDB. CMDBs describe what should exist; asset visibility describes what does exist. The two diverge constantly. The supervisory expectation is that the gap between them is bounded, monitored, and shrinking — which means the bank needs at minimum two passes that run independently and reconcile to one another. One pass is the declared CMDB. The other is the discovered surface — externally via attack-surface management, internally via cloud-native discovery, and contractually via third-party registers.
Shadow cloud is the single most under-managed surface in most banks. A team spinning up a Snowflake account on a corporate card to ship a Q3 dashboard is, by definition, an unmanaged asset. The fix is not policy. The fix is making the right path easier than the shadow path — paved-road platforms with secure defaults, financed and paved deep enough that the shadow option stops looking attractive.
Mechanism · sweep, reveal, govern
Animated · radarWhat the bank builds.
The architect's reading: this is the operating-model rewire behind Priority 1. Periodic and continuous are not points on the same scale; they are different paradigms. Periodic produces evidence; continuous produces signal. Periodic generates findings to fix; continuous generates alerts to triage. Periodic is owned by audit; continuous is owned by the SOC. The control surface that supervisors will increasingly look at is the second one — and the bank's investment profile has to follow.
The hardest move is not technical. It is cultural — letting go of the comfort of the annual penetration test as the primary evidence of cyber posture. Pen tests don't go away, but they become one input among many feeding a continuous-control surface that is always running. The board MI pack stops being "results of last year's pen test" and starts being "live posture over the past 30 days, against rolling thresholds".
Mechanism · pulse versus stream
Animated · two cadencesWhat the bank builds.
The architect's reading: this is the priority that directly maps to the MAS AIRM Guidelines. Pillar 3 of AIRM (lifecycle controls) is the same animal as the CSA Addendum on Securing Agentic AI — different vocabulary, same controlled lifecycle from data sourcing through retirement, with explicit gates between phases. The architect's job is to make sure the bank does not run two parallel programmes (one for AIRM, one for cyber) producing two parallel evidence vaults that don't reconcile. One lifecycle. One evidence vault. Two readers.
The agentic dimension is the new pressure point. Traditional AI governance assumes a model that produces a prediction; agentic AI assumes a system that takes actions. Once an AI agent has tool-use, code-execution, or write-access to bank systems, the cyber risk surface expands materially. The control framework has to recognise that and govern it differently — capability-based access, audit trails on every tool invocation, and circuit breakers on autonomous action.
Mechanism · gates light up as the use case progresses
Animated · 6 stagesWhat the bank builds.
The architect's reading: asymmetry is the strategic problem. The attacker has access to AI capability that compresses vulnerability discovery from months to hours. The defender that runs only conventional tooling will lose that race by construction. The fifth priority is the only one of the five framed positively — it tells the bank to use the same kind of capability the attacker is using, and to do so before the asymmetry becomes uncatchable.
The Senior Minister's qualification matters: "to avoid dependence on any single external provider". That is a deliberate signal. A bank that hands its defensive AI capability to a single vendor — including a single foundation-model provider — has converted one strategic risk into another. The architect's response is a portfolio posture: at least two foundation-model providers, in-house fine-tuning where it adds defensive value, and a clear separation between off-the-shelf capabilities and capabilities that must be built in.
Mechanism · the race, with and without defensive AI
Animated · two lanesWhat the bank builds.
Five priorities, one operating fabric.
Read across the five mechanisms and a single architecture emerges. The five priorities require, in aggregate, four shared surfaces:
1. The asset graph — declared, discovered, contracted; reconciled weekly. This serves Priorities 1, 2, and 3 without exception.
2. The continuous-detection plane — telemetry, automated detection, runbook-driven response. Priorities 1 and 3 cannot exist without it; Priority 5 lives on top of it.
3. The AI lifecycle & evidence vault — one lifecycle, one evidence vault, two readers (AIRM 2LoD and cyber 2LoD). Priority 4 is built on it; Priority 5 governs against it.
4. The defensive-AI stack — multi-vendor by design, in-house fine-tuning where strategic, regulator-coordinated where shared. Priority 5 sits here.
The most common architectural mistake will be to build five separate programmes with five separate owners and five separate tooling decisions. The supervisory expectation, the underlying threat model, and the resource constraints of every BFSI architecture function all argue against that. One fabric, four surfaces, five mechanisms running on top.
That is the design the architect should defend. It is also — not coincidentally — the design that maps cleanly onto the MAS AIRM Guidelines, the MAS POV connector, and the CSA Addendum on Securing Agentic AI. The supervisor has been signalling the same picture from three different angles. The architect's job is to draw it.
And it is the line that ties all five priorities together. The architect's job is to make sure that when the board is told it owns these risks, the metadata, the platform, and the controls underneath are real enough that the ownership is more than a phrase. The five mechanisms in this brief — the shrinking window, the asset graph, the cadence shift, the AI lifecycle, and the defensive-AI race — are the load-bearing pieces. Each one is animatable because each one is, fundamentally, a process about the movement of state through time. The bank that can render them, govern them, and reconcile them is the bank that can survive what comes next.
The supervisor has now signalled this from three angles within a single week — the POV announcement, the CEO convening, and the five-priorities article. Three angles, one architecture. The next twelve months are about building it.