Security Policy Set Audit for a Small Organisation
Check that policies are short, current and followed.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).
Audit our security policies. Titles and a summary of each policy, review dates and where staff find them: [POLICY_SET]. How policies are communicated and acknowledged: [COMMUNICATION]. Recent breaches of policy: [BREACHES]. Check for overlong policies nobody reads, contradictions, rules that no one follows, missing owners, review dates passed, and gaps in common topics such as acceptable use, access, incidents and suppliers. Compare policy with practice. Return a table with Policy, Problem, Risk (red, amber, green) and Fix, a plan to cut the set to what people can follow, and a one-page summary for new staff. Legal requirements are [VERIFY] for [JURISDICTION]. Also suggest a single page that lists every policy with owner, date and the one-sentence rule that matters most, and a method for collecting staff questions about unclear rules each year. Treat severity ratings as estimates from the evidence given, mark anything you could not verify [VERIFY], and recommend a qualified security professional confirm high-severity items before they are closed.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.