AI Security Training Template and Checklist
A ready-to-run AI security program and the rollout checklist to go with it. Train every team, then see who is actually covered.
Reviewed by Abhijit Rao, AVP & Business Head, India
- A seven-module AI security program, with audience and coverage for each
- A rollout checklist mapped to your own AI acceptable-use and control framework
- A team readiness matrix that shows where AI risk is unmanaged
- An acceptable-use and refresher cadence as tools change
What is inside
- A seven-module AI security program, with audience and required coverage for each session.
- A 10-point rollout checklist you can map to your AI acceptable-use policy and control framework and mark off as you go.
- A team readiness matrix that scores each team and shows where AI risk is unmanaged.
- An acceptable-use and refresher cadence so training keeps pace with new tools and risks.
Who it is for
Anyone who has to plan what people learn, and answer for whether it landed.
- L&D and training teams
- People managers and team leads
- Heads of function and department
- HR business partners
- Compliance and risk teams
- Onboarding and enablement teams
- Operations and delivery leads
- COOs and HR directors
How to use this template in 4 steps
- Pick your format. Download the PDF to share, the Word file to edit, or the Excel file to work in live. All three are free.
- Make it yours. Adapt the sections, fields and wording to your team, roles and process so it fits how you actually work.
- Put it to work. Fill it in, circulate it to stakeholders for sign-off, or roll it out to your team.
- Track and improve. Review it on a set cadence and refine it as your goals, roles and priorities change.
What is inside
- A seven-module AI security program, with audience and required coverage for each session.
- A 10-point rollout checklist you can map to your AI acceptable-use policy and control framework and mark off as you go.
- A team readiness matrix that scores each team and shows where AI risk is unmanaged.
- An acceptable-use and refresher cadence so training keeps pace with new tools and risks.
Adapt the modules and checklist to your own AI acceptable-use policy, approved tools and control framework. This is a starting structure, not a substitute for your security team's AI requirements.
The training program template
Seven modules covering the AI risks that actually cause exposure. Run the full set for new joiners and heavy AI users, then use the refresher and role-specific modules through the year.
| Module | Audience | Duration | What it must cover |
|---|---|---|---|
| 1. AI risk and acceptable use | All staff | 20 min | What AI tools are approved, what they may and may not be used for, and where the policy lives. |
| 2. Data leakage into AI tools | All staff | 25 min | What must never be pasted into public tools: customer, personal, confidential and regulated data. |
| 3. Shadow AI | All staff, IT | 20 min | Why unapproved tools are a risk, and the easy path to request one instead of going around security. |
| 4. Prompt injection | Engineering, product | 30 min | How untrusted content can hijack a model's instructions, and how to design against it in AI features. |
| 5. Model and output risk | All staff | 25 min | Hallucination, bias and confident wrong answers, and why AI output must be verified before it is used. |
| 6. AI in the build | Engineering, data | 35 min | Securing prompts, keys and training data, and guarding against data poisoning and leakage in AI features. |
| 7. Annual refresher | All staff | 20 min | Updated tools and risks, a recent anonymised incident, and a short knowledge check for evidence. |
Delivering the refresher and knowledge check through an LMS gives you dated completion per person and per team, the evidence an auditor or a customer security review asks for.
The rollout checklist
Ten steps to get AI security training live and keep it current. Tick items to track your own progress, it stays in this browser. The download has the same list with an owner column.
- AI acceptable-use policy published and acknowledgedPolicyOn change
- Approved AI tools list maintained and sharedToolingOngoing
- New joiners trained within their first weekOnboardingPer hire
- Data-handling rules for AI tools drilledData protectionOngoing
- Easy route to request a new AI tool publishedShadow AIOngoing
- Prompt injection covered for engineering and productBuild securityOn change
- Output-verification expectation set for AI-assisted workOutput riskOngoing
- AI features reviewed for prompt, key and data riskBuild securityQuarterly
- Completion tracked by team, not just org-wideGovernanceOngoing
- Refresher updated and completed as tools changeGovernanceQuarterly
The most common gap is shadow AI. An org-wide 90 percent completion means little if a whole team is using an unapproved tool that never appears in your policy or your logs.
Team readiness at a glance
The checklist tells you what is missing overall. This matrix tells you which teams are behind. Score each team on the five AI behaviours that carry the most risk. In Excel the readiness and gaps calculate as you type.
| Team | People | Acceptable use | Data leakage | Shadow AI | Prompt injection | Output risk | Ready |
|---|---|---|---|---|---|---|---|
| Security / IT | 40 | 2 | 2 | 2 | 2 | 2 | 100% |
| Engineering | 60 | 2 | 1 | 1 | 2 | 1 | 70% |
| Marketing | 45 | 1 | 1 | 0 | 1 | 1 | 40% |
| Customer support | 90 | 1 | 0 | 1 | 1 | 1 | 40% |
| Sales | 120 | 1 | 1 | 1 | 1 | 2 | 60% |
| Coverage at required | 40% | 20% | 20% | 40% | 40% | 62% |
Customer support is the exposure here: no data-leakage discipline, and support agents paste real customer records into AI tools to draft replies faster.
The annual AI security calendar
| Timing | Action | Owner |
|---|---|---|
| On joining | Modules 1 to 3 in the first week, policy acknowledged. | L&D and IT |
| Monthly | Review approved-tools list, shadow-AI requests and completion by team. | Security |
| Quarterly | Refresh the training for new tools and run a spot check on usage. | Security |
| For engineering and product | Prompt injection and AI-in-the-build deep dive. | Security and Eng |
| Annual, all staff | Refresher module and knowledge check, tracked per team. | L&D |
| After any incident or near miss | Targeted micro-training on the specific AI failure, fast. | Security |
How to run it
- Publish an acceptable-use policy first
People cannot follow a rule that does not exist, so define what is allowed before you train on it.
- Draw the data line clearly
Teach exactly what must never be pasted into a public AI tool: customer, personal and confidential data.
- Surface shadow AI, do not just ban it
Give an easy route to request tools, so usage comes into the open instead of going underground.
- Teach prompt injection and output risk
Show how untrusted content can hijack a prompt, and why AI output must be verified before it is used.
- Track completion by team
Roll it up per team so a non-compliant department is visible before a leak happens.
- Refresh as the tools change
AI tools and risks move monthly, so review the policy and update the training on a set cadence.
Frontline teams reach 45 percent-plus completion on Disprz when training is delivered in short, mobile modules in the local language, the format this program is built for.
Common mistakes this pack prevents
- Banning AI tools on paper while the whole company quietly uses them anyway.
- No clear line on what data may never be pasted into a public AI tool.
- Trusting AI output as fact and shipping confident wrong answers to customers.
- An org-wide completion number that hides a whole team on unapproved tools.
- No dated records, so there is nothing to show an auditor or a customer security review.
Which format should you use?
| Format | Best for | What is inside | Editable | Size |
|---|---|---|---|---|
| Sharing and print | The full template, formatted to print or circulate | No | 55 KB | |
| Word | Editing the wording | Every section as editable text you can adapt | Yes | 86 KB |
| Excel | Filling it in live | The grid and fields set up as a working spreadsheet | Yes | 65 KB |
Questions people ask
Is AI security training mandatory?
How often should AI security training happen?
Can I adapt the modules and checklist?
Does the Excel tracker work in Google Sheets?
Do I have to fill the form three times?
An AI policy is only a control if people finish the training. That is the part we run.
Bring your teams to a 30-minute working session. We will show how Disprz delivers AI security training in short mobile modules and rolls completion up by team, so your next audit or board update is a two-minute export.