AI policy development
Acceptable use, data classification, approvals, procurement questions and incident handling, written in a page staff will actually read.
Create an AI policy- Standards
- ISO/IEC 42001 · NIST AI RMF
- Testing
- Adversarial, tool-aware
Why this matters now
AI is already in use inside most organisations, usually before governance catches up. AI policy development gives you control without blocking work that is genuinely useful.
What the engagement covers
Each area below is a defined part of the engagement, with an owner, an output and a date.
Acceptable use
What staff may and may not put into AI tools, in one page.
Confidential data
Clear classification rules for what must never leave your control.
Approvals
A lightweight route to approve new AI tools without shadow adoption.
Procurement
Security and governance questions built into vendor selection.
Incidents
How to report and handle an AI-related incident.
How the work runs
The same sequence on every engagement, so you know what happens next.
Inventory
Establish what AI is actually in use, including tools adopted without approval.
Assess
Evaluate each use case for security, privacy, legal and model risk.
Control
Apply proportionate controls: policy, access, logging, approval points and monitoring.
Test
Adversarial testing against the deployed system, including indirect injection paths.
Govern
Reporting, review and change control so governance keeps up with adoption.
What you get out of it
Adoption without blind spots
Useful AI work continues; the uncontrolled parts get controlled.
Standards alignment
Mapped to ISO/IEC 42001 and ISO/IEC 27001 so one programme serves both.
Tested, not assumed
Controls verified by adversarial testing against the live system.
Before you enquire
How quickly can this start?
Who actually does the work?
How is this priced?
Where to go next
Create an AI policy
One scoping call with the consultant who would run the work. No obligation, no charge.