Control frameworkCompliance & AuditCertification-oriented controls

ISO/IEC 27001

Regions

Global

Source references

4 source references

Control areas

8 mapped control areas

Deployment options

Regulated SaaS, Private cloud

About this template

An information security management system needs a documented scope and a decision about every listed control. AI traffic often arrives after that work is finished and fits none of the existing entries. This starter offers a first control description for that traffic, and certification remains an audit outcome.

Teams reach for this material when a customer questionnaire or an internal auditor asks the question. The answer has to name a control, an owner and a piece of evidence. Configuration provides the third one.

The chain here is short on purpose. Six stages run in order. Injection screening, an identity check, redaction, a classification block list, output scoring and a request marker. Nothing waits for a person and no source check runs.

Classification is the interesting part. A prompt that carries confidential, restricted, internal only or proprietary wording is refused. That behavior puts something real behind a classification policy, instead of a label in a document.

National identifier numbers are masked before a prompt is sent, which supports the cloud privacy standards this starter references. Answers must reach a combined score of 0.80 and an accuracy score of 0.80.

Supplier management, continuity planning and internal audit remain management system work. Certification comes from an accredited body after an audit, and no configuration produces it. Add a review step yourself when your risk treatment calls for one.

Source frameworks, standards and obligations

ISO/IEC 27001:2022ISO/IEC 27002:2022ISO/IEC 27017:2015 (Cloud Security)ISO/IEC 27018:2025 (PII in Public Clouds)

Control areas mapped by this template

Access control
Audit logging
Incident response
Data encryption
Vulnerability management
Risk management
Business continuity
Supplier management

Deployment options

Regulated SaaS
Private cloud

Adapt the template in three steps

1

Review the scope

Confirm that the regions, source references, control areas and deployment options fit your use case.

2

Adapt the configuration

Open the template in the Verdictan console. Set its policies, thresholds, routing and review requirements for your environment.

3

Test before deployment

Test each policy outcome. Confirm that allowed, redacted, blocked and reviewed requests behave as expected.