Shop / Policies & standards
Secure AI agents before they act: own identities and short-lived scoped tokens, tool and tool-server hardening, prompt injection boundaries, data leakage controls and human approval gates.
Why AI agents need their own security standard →
Word (.docx). Editable, with highlighted placeholders and guidance notes you delete before publishing.
Aligned with the frameworks named. Templates support your program; they don't certify compliance.
Small and medium organizations, security leads, consultants and MSPs who want a structured starting point instead of a blank page.
No. It's a template: a guideline based on common industry practice. Review each requirement, remove what doesn't apply, set values you can meet, and have the final version reviewed by people who know your systems and obligations.
After checkout you get an instant download link by email from our payment partner.
The licence covers use within your own organization. Consultants and MSPs who want to use templates with clients should contact us.
See our licence and refund policy.
Plan your move to post-quantum cryptography (ML-KEM, ML-DSA, SLH-DSA) in plain language: what PQC is, a cryptographic inventory, harvest-now-decrypt-later priorities, hybrid key exchange, 2030/2031/2035 milestones and crypto agility.
Three standards for the newest risks: help desk impersonation and mass file theft (STD-03), AI agents acting on your systems (STD-04) and the move to post-quantum cryptography (STD-05).
Use alongside your own licensed copy of the standard. CyberGlass does not sell or reproduce standard text.
Based on NIST CSF 2.0. Republished courtesy of the National Institute of Standards and Technology. NIST does not endorse CyberGlass.