AI Compliance & Cyber · November 10, 2026

AI Compliance & Cyber Brief — November 10, 2026

The risk keeps moving out of the model and into everything around it: the skills an agent loads, the permissions it holds, and the evidence it cannot edit. This week: NIST's framework status, a pattern in AI certification announcements, a report on how even official agent skills can trust the wrong file, and NIST's proposed design tenets for agent identity. Where an item rests on one vendor's report, or on secondhand coverage, it says so.

The 30-second version

NIST AI RMF is still version 1.0, and the revision has no public draft

Talking point

Anyone telling you there is an 'AI RMF 2.0' owes you a NIST link, because NIST's page still lists 1.0 as current, says it is being revised, and shows no draft, version number or date. The practical read is to build on the four functions now, since an inventory and an impact assessment will still be the starting point after the revision lands. And 'we follow the NIST AI RMF' means very little until someone names which outcomes they actually implemented.

Content angle

Post or podcast segment: 'Which part of the framework?' Contrast the word 'aligned' with a one-page list of what a company can actually show: an AI inventory, a go/no-go decision before launch, a written list of what it cannot measure, and a kill switch. Readiness is a repeatable method, not a feeling, and Pilot Fixer clients usually have the policy and none of the artifacts. Workshop: have leaders score a twelve-row artifact list as absent, partial or done.

Lens: Executive AI readiness orientation — methodology and technology, not law. This brief is orientation on methodology and technology, not legal or compliance advice, and not a certification.

NIST AI RMF & ISO 42001 Maturity

Framework status and certification signals, read for what they do and do not evidence.

NIST AI RMFFramework StatusReadiness Signal

NIST AI RMF is still version 1.0, and the revision has no public draft

NIST's own page says the framework is being revised under the White House AI Action Plan; no draft, version number or date has been published.

Talking point

Anyone telling you there is an 'AI RMF 2.0' owes you a NIST link, because NIST's page still lists 1.0 as current, says it is being revised, and shows no draft, version number or date. The practical read is to build on the four functions now, since an inventory and an impact assessment will still be the starting point after the revision lands. And 'we follow the NIST AI RMF' means very little until someone names which outcomes they actually implemented.

Content angle

Post or podcast segment: 'Which part of the framework?' Contrast the word 'aligned' with a one-page list of what a company can actually show: an AI inventory, a go/no-go decision before launch, a written list of what it cannot measure, and a kill switch. Readiness is a repeatable method, not a feeling, and Pilot Fixer clients usually have the policy and none of the artifacts. Workshop: have leaders score a twelve-row artifact list as absent, partial or done.

Source: NIST: AI Risk Management Framework; Security Boulevard: NIST AI RMF in Practice

ISO 42001Procurement SignalReadiness Signal

ISO 42001 certificates are turning into routine vendor announcements

Within days, an IT-management software vendor, a work-management platform and a Korean public arboretum institute each announced certification.

Talking point

The badge is moving from differentiator to baseline: when software vendors, work platforms and even a public arboretum institute announce the same standard within days, your customers' vendors will start answering questionnaires with it. That makes the one question that never changes more valuable, which is what the certificate's scope actually covers. Last week's Mitsubishi example, a management system around agents rather than any model, is the template for reading these.

Content angle

Short post: 'Three certificates, one question.' Take any vendor's 42001 announcement and ask three scope questions: which products, which sites and which AI uses sit inside the boundary. Small-business workshop: read your most important AI vendor's certificate scope and write down what it does and does not tell you about the tool your people actually use. This is the translation job, auditor language into CEO language.

Source: Business Wire via Yahoo Finance: NinjaOne Achieves ISO 42001 Certification; Seoul Economic Daily: Korea Arboreta and Gardens Institute Wins International AI Standard

Technical Governance & Controls

Where agent risk actually lives: in the code and permissions around the model.

Agent SkillsSupply ChainReadiness Signal

Anthropic's official document skills load a file from a shared folder without checking who put it there

Air Security reports that the helper behind the Word, PowerPoint and Excel skills preloads a library from a fixed temp path; Anthropic is reported to consider it outside its security boundary.

Talking point

This is not a clever attack on a model. It is an old pattern: a trusted helper runs whatever file it finds in a shared temp folder. Air Security says the document skills load a library from a fixed path with no check on who wrote it, so anything else that can write to that folder could run code as the user. The vendor reportedly sees it as outside its boundary because it only happens inside a sandbox, and both positions are worth knowing. What generalizes is the lesson: a skill is code your agent runs, and 'official' tells you who wrote it, not that nobody should review it.

Content angle

Post: 'A skill is software.' Frame it for non-technical leaders: you would not let an employee install an unreviewed program from a shared drive, yet agent skills, plugins and extensions are exactly that. Ten-minute workshop: list every skill, plugin and extension installed on one team's agents, who approved each, and who owns updates. Pair it with last week's coding-agent configuration card and the human-layer point that people install whatever makes the work easy. DoCRA-flavored angle (my framing, not new DoCRA writing): reasonable care includes knowing what code your agents execute.

Source: Air Security: Office Party, a flaw in Anthropic's official skills; Air Security: OpenAI Sesame (October 14, 2026)

NISTAgent IdentityAccess ControlReadiness Signal

NIST proposes ten design tenets for agent identity, and says guardrails alone are not enough

An NCCoE blog post offers an initial checklist: distinct agent identities, short-lived access, policy separated from the model's reasoning, deterministic access decisions, and tamper-evident logs the agent cannot edit.

Talking point

NIST's agent identity team says what many security leaders have been circling: because a model takes instructions and data in one stream, the line between what an agent tries to do and what it is allowed to do has to be built into the architecture, and 'guardrails alone are insufficient.' Two of the ten tenets are the ones to remember. Access decisions should be deterministic, with model judgment only as an input, and the record of what an agent did has to live where the agent cannot edit it. It is a proposal, not a standard, but it is a ready-made list for asking a vendor what they actually built.

Content angle

Post or talk segment: 'The agent is not the policy.' Pick tenets seven, eight and ten and turn each into one question a CEO can ask a vendor. Use the contrast between a prompt that says 'do not' and a permission the agent simply does not have. Workshop: take one agent in the business and answer all ten tenets as yes, no or don't know; the 'don't know' count is the finding. Ties to Pilot Fixer, since pilots stall when nobody owns the permission layer.

Source: NIST: Design Tenets for Agent Identity Management Systems

Bottom line

Bottom line

Keep reading

Next briefs

Get the briefs in your inbox

AI in the News, Legal Signal, Compliance & Cyber, and ROI briefs — written for executives. No spam, unsubscribe anytime.