Policy

Writing an AI use policy that protects data

A short, clear rule on what may be entered into AI tools closes the most common leak route. IBM's research found that many organisations still have no AI governance policy.

Last reviewed against legislation.gov.uk, National Cyber Security Centre and OWASP GenAI Security Project. Sources

Factory site linked by wireless to a phone with a fingerprint and shield

The gap

Few have a policy

In IBM's 2025 study, 63% of the 600 organisations surveyed had no AI governance policies to manage AI or prevent shadow AI [5]. Samsung's reaction to its own case was a company-wide restriction, and it said it was working on safer ways to use the tools [8]. A policy sits between those two positions: it lets people keep using useful tools while setting limits on the data that goes into them. It also gives you something to point to when a mistake happens, and a record that staff were told what was expected.

What to include

Six parts

Green shield with a tick above a phone showing a fingerprint

Scope

Which tools it covers, including browser extensions and AI features inside other software.

Brick firewall with a flame in front of it

Data classes

What must never be entered: personal data, credentials, source code, unreleased financial information and client confidential material. OWASP lists these kinds of data among what an LLM can disclose [4].

Cloud above a green shield with a padlock beside a server stack

Approved tools

A named list, with what each may be used for.

Industrial site map with viruses hovering over buildings marked in red

Accountability

The NCSC says to clarify who is accountable for AI security [3]. Name the role.

Hand holding a phone showing a login form, a tick and a padlock

Reporting

How staff report a mistake, such as pasting the wrong file. Make it easy and blame-free so it is reported.

Ring of connected devices around a Wi-Fi symbol: house, camera, router, phone and bulb

Retention

Publish how long AI inputs and logs are kept, as OWASP advises for clear data retention and usage policies [4].

Rolling it out

In order

  1. 1

    Draft the rule on one page.
  2. 2

    Check it with legal and data protection.
  3. 3

    Name the approved tools before you publish the rule.
  4. 4

    Brief every team with an example from your own work.
  5. 5

    Review it when a new tool or supplier feature appears.

A rule people can follow

If the policy only says no, staff will work around it. Pair every prohibition with an approved alternative.

For why this matters, read shadow AI data leaks; for suppliers, supplier questions.

How CyPro can help

Need a hand working through this?

Finding out whether an incident reaches you is one job. Checking your own systems, tightening access and briefing the board are several more. CyPro's responders and consultants can take any of them on.

Incident responders containing an attack

Incident response

If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.

More on cypro.co.uk
Security analysts monitoring systems around the clock

24/7 security monitoring

Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.

More on cypro.co.uk
Security lead advising a board

Fractional CISO for the board

A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.

More on cypro.co.uk
Penetration tester probing an application for weaknesses

Penetration testing

A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.

More on cypro.co.uk
Cyber security consultants planning hardening work

Hardening and segmentation

Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.

More on cypro.co.uk
Scanner checking internet-facing systems for weaknesses

Vulnerability scanning

Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.

See the scanning service
Rocket launching from a cloud

Talk to a specialist

Worried this affects you?

If data has leaked through an AI tool or an exposed AI database, the first hours decide how much is lost and what you must report. An incident response team helps you contain it, work out what was exposed and meet your notification duties.