Security, privacy & governance

Books matched to this capability.

5books in this track

L01 · User

Who is affectedOnly you
T12-L01

Decide What You May Paste Into AI at Work

Sort anything you want to paste into an AI tool as green, yellow or red in seconds, and turn a red request into a green one by anonymising, asking about the form instead of the content, or using an approved tool. For labs and small companies.

Outcome: Your last five pastes into an AI tool, each classified green, yellow or red with a one-line reason, and every red one rewritten; it passes when a colleague agrees with each colour and no rewrite still contains red material.

User12 minLast edited: Sep 23, 2026

L02 · Power user

Who is affectedYour team sees a bad document or a wrong figure
T12-L02

Clean the Copy, Label the Result, Spot the Trap

Before shared data goes into an assistant, make a working copy with only what the task needs and check names, dates, free text and hidden parts of the file. Let a second reader try to recognise someone. Say what AI did in a note that stays with the text, and stop when a document gives orders.

Outcome: A cleaned working copy for one real team task, with a method note and an AI-use note. It passes when a second reader who hasn't seen the original can't single anyone out, one result the task needs (a count, a grouping) comes out the same from the copy as from the original, and the AI-use note is still attached in the document where the result ended up.

Power user15 minLast edited: Sep 23, 2026

L03 · Builder

Who is affectedColleagues depend on something you built
T12-L03

Give an Unattended Workflow Limits and a Stop a Colleague Can Use

Before an n8n workflow runs without you, write its one-page operating rule and make the build obey it: a credential that can't do what the rule forbids, hard limits on items, time and model spend, a test set with known answers, and a deputy who can stop it without you.

Outcome: A published n8n workflow with its one-page operating rule and a filled-in test sheet for the five tests. It passes when all five tests pass, the credential can't perform any action the rule forbids, and the deputy stops the workflow from the rule alone while you watch without helping.

Builder22 minLast edited: Sep 23, 2026

L04 · Integrator

Who is affectedCompany or lab systems and real data are in the loop
T12-L04

Lock Down a Self-Hosted AI Service Before Real Data Goes In

Before real records reach a self-hosted assistant or workflow, check it from the outside in five steps, give it a service account that can only do its job, keep secrets out of files and Git, limit where it can send data, and prove a restore works, keys included. Every finding gets a fix, a date and IT's signature.

Outcome: A dated five-step audit of a self-hosted AI service: every finding with its fix, who fixed it and the retest result, plus one denied-access test and one restore test. It passes when every step has a result, no finding is open without a named person and a date, and IT has signed.

Integrator20 minLast edited: Sep 23, 2026

L05 · Operator

Who is affectedWork stops when it breaks, and it must survive you leaving
T12-L05

Keep One List of Every AI System Your Team Runs, and Make It Survive You

Find every AI system your team uses, including the unofficial ones, and keep one inventory with a risk tier, a responsible person and stand-in, the data touched and who is trained. Link the proof an auditor asks for, decide which uses shouldn't exist, and test the handover without you.

Outcome: An AI inventory for one team: every system with purpose, risk tier, responsible person and stand-in, data touched, training record, linked proof and next review date, plus a record of one 'author has left' test. It passes when a stand-in who didn't build any of the systems answers an auditor's five questions and handles a practice incident from the inventory alone.

Operator19 minLast edited: Sep 23, 2026