Skip to content
AI Policy Generator

Policies and internal rules · Standard · Security

AI Security Baseline

Minimum security controls for AI workloads: identity and access, data and prompt protection, prompt injection, model supply chain and logging.

GROU LLC · built on AI Business Core, by Vreinn · · How we verify sources

Who it helps

IT and security teams integrating AI models or APIs into their systems.

Who uses it
CISO, IT, architecture, security, data and technical implementation teams
Usual owner
CISO; information security
Formats
DOCX, PDF
Languages
Español, English
Approximate length
4 pages
Length
Standard. A complete policy, procedure, plan or guide, with roles, deadlines and evidence.
Document type
Policies and internal rules. Rules your organization approves and staff follow: what is allowed, what is not and who decides.
Document code
APG-SEC-001. APG is the AI Policy Generator collection, SEC the area (Security) and the number identifies the document. Use it to cite the document in your document system.

Preview

Excerpt generated from the document: the "How to use this document" section, the title and the first two sections, plus the full table of contents. The rest of the text is not shown.

APG-SEC-001 · Version 1.1.0 · sources as of November 4, 2026

How to use this document

  • What it is for. This is a base standard with the minimum security controls for AI systems: governance, identity and access, data and prompts, prompt injection, agents, model supply chain, secure development, testing, logging, incidents and models hosted on the organization's own infrastructure. It supplements, and does not replace, the general information security policy.
  • Who should own it. Information security, with the IT, architecture and data science teams applying the controls under the direction of each system owner. Enter the function in [RESPONSIBLE FUNCTION] and the person in [OWNER].
  • Decisions to take first. Decide which deployment profiles you have (P1 to P5) and at which level you adopt the standard (Basic, Standard or Reinforced); then use "Module selection" to keep only the sections and rows that apply to you. Also decide which tools you will use for each control (secrets manager, centralized logging, filters), how long logs are kept (LOG-04) and who approves exceptions (Section 6).
  • Fields to complete. Replace the bracketed fields, such as [ORGANIZATION NAME], [AI COMMITTEE], [REVIEW FREQUENCY] and [COMPLETE]. Keep [OPTIONAL] clauses only if they apply.
  • Country variants. This document has no country variants. Breach and incident notification deadlines, product cybersecurity rules and legal restrictions on models based on their origin vary: identify them in "Related regulatory references" and connect them to INC-03 and to each model's provenance sheet.
  • Review. Ask IT, architecture and data science to confirm that the controls fit their platforms, and the data protection officer (or the country's equivalent role) and legal to validate the controls on personal data, retention and notification.
  • Approval and publication. Have it approved by the AI lead or [AI COMMITTEE], record the approval in "Version history" and publish it for the teams that design, integrate or operate AI systems.

Module selection

Profile or level What to keep
All Sections 1 to 4, 6 to 8 and, within Section 5, the rows whose profile is "All" or one of yours
P1 Uses AI inside software it buys Rows tagged P1; Sections 5.4 and 5.7 only if you also have P2 to P5
P2 Integrates models through APIs or RAG Rows tagged P2
P3 Hosts models, including open-weight models Rows tagged P3 and Section 5.12
P4 Trains or fine-tunes models Rows tagged P4
P5 Uses agents that act in systems Rows tagged P5 and Section 5.5
Basic level Rows with no level marker
Standard level Unmarked rows and [STANDARD LEVEL] rows
Reinforced level All rows, including [REINFORCED LEVEL] rows

Delete the sections and rows that do not apply to your organization.

AI Security Baseline

Field Value
Organization [LEGAL ENTITY NAME]
Owning function [RESPONSIBLE FUNCTION]
Standard owner [OWNER]
Approved by [APPROVED BY]
Effective date [DATE]
Review frequency [REVIEW FREQUENCY]
Deployment profiles adopted [COMPLETE: P1, P2, P3, P4, P5]
Level adopted [COMPLETE: Basic, Standard or Reinforced]
Contact for questions and exceptions [AI GOVERNANCE EMAIL]

1. Purpose

1.1 This standard sets the minimum security controls that [ORGANIZATION NAME] applies to AI systems to protect the confidentiality, integrity and availability of models, weights, data, prompts, integrations and outputs.

1.2 It addresses AI-specific risks, such as prompt injection, data poisoning, model extraction, information leakage through outputs, excessive agent autonomy, model supply chain compromise and hidden behaviors in third-party models, in addition to traditional security risks.

2. Scope

2.1 It applies to:

a) AI features enabled in contracted applications and AI assistants for staff, to the extent the organization can configure them (P1);
b) integrations with third-party AI models or APIs, including retrieval-augmented generation (RAG) applications and their knowledge bases and vector stores (P2);
c) models hosted on owned or rented infrastructure, including open-weight models of any origin, and their inference servers (P3);
d) models trained or fine-tuned by the organization and their training infrastructure (P4);
e) AI agents that use tools or take actions in other systems (P5);
f) staff, contractors and vendors who design, integrate or operate these systems.

2.2 The rules for staff use of AI tools are in the "Responsible AI Use Policy (Including Generative AI)"; this standard applies to their technical configuration.

Full table of contents of the document:

  • 1. Purpose
  • 2. Scope
  • 3. Definitions
  • 4. Profiles and application levels
  • 5. Controls
  • 6. Exceptions
  • 7. Verification
  • 8. Review of the standard
  • Implementation aids
  • Related regulatory references
  • Version history

Rules in the registry whose obligations relate to this base document, based on our reading of the sources. It does not mean they apply to you.

Argentina

Brazil

Chile

Ecuador

European Union

International standards

Mexico

Peru

United States (federal)

Illinois

Kits that include this document

Includes 6 documents

B2B Vendor Kit for Customer Questionnaires

Base documents on topics that procurement questionnaires from banks and US clients often cover: policy, inventory, impact assessment, incidents, vendors and security.

USD 169USD 274

Complete kit · available to buy

Includes 7 documents

Self-Hosted and Open-Weight Models Kit

Seven base documents for hosting in-house or open-weight models: provenance, security baseline, adversarial testing, architecture, model card, life cycle and rollback.

USD 149USD 233

Complete kit · available to buy

Includes 8 documents

AI Agents Kit

Six base documents for agents that act in systems: autonomy and permissions policy, integration map, adversarial testing, human oversight, rollback and incident response.

USD 169USD 292

Complete kit · available to buy

Includes 91 documents

Complete pack

Every sellable template in the catalog in a single pack: base policies, procedures, registers, notices and matrices to adapt with your own team, at a flat price below the sum of the individual documents.

USD 297USD 3393

Complete kit · available to buy

What AI Policy Generator is and how it works