
AI-native compliance means using AI within a structured, reviewable compliance process—not simply adding a chatbot to a document repository. The working principle is straightforward: AI accelerates preparation and analysis, people approve consequential decisions, and evidence remains connected to every supported claim.
For a CTO, the architectural question is whether the system can represent the organization’s actual controls. A policy describes intended behavior. A configuration export shows a setting. A completed access review demonstrates an activity. These are different kinds of evidence, and generating fluent text does not make them interchangeable.
A useful workspace connects requirements, controls, systems, evidence, owners, tasks, and decisions. That structure lets teams reuse supported information across frameworks without confusing similar requirements with equivalent obligations.
Organizations often maintain policies in documents, evidence in folders, risks in spreadsheets, and remediation tasks in project tools. Audit narratives are then recreated from those scattered sources. Adding another framework frequently creates another copy of the same information.
The consequences extend beyond administrative effort. Separate teams can give engineers conflicting instructions about the same access-control process. One assessment may use an outdated architecture description while another uses the current version. A polished report can conceal an unresolved implementation gap.
The practical alternative is a shared control model with framework-specific views. Maintain the implementation once, attach appropriate evidence, and evaluate separately which requirements it supports. This reduces duplicate requests without erasing differences in scope, assessment periods, or legal duties.
Start with the organizational boundary: which service, legal entity, systems, locations, and providers are included? Record the framework version and the reason each obligation applies. Otherwise, AI may produce plausible mappings for requirements outside the actual scope.
The distinctions matter:
Treat applicability as an approved input, not an inference silently made by the model. For uncertain cases, create an explicit interpretation task with a responsible reviewer.
A practical minimum model should distinguish the requirement, implemented control, supporting evidence, and review decision. An uploaded file is not itself a control, and an approved policy is not proof that the procedure operates consistently.
| Object | Information to retain | Review question |
|---|---|---|
| Requirement | Source, version, scope, applicability rationale | Does this apply here? |
| Control | Implementation, systems, owner, exceptions | What actually happens? |
| Evidence | Origin, collection date, covered period, limitations | What does this prove? |
| Mapping | Supported overlap, remaining differences, rationale | How far can we reuse it? |
| Decision | Reviewer, outcome, date, follow-up | Who accepted this conclusion? |
Dependencies belong in the model too. A customer-facing application may rely on an identity provider, cloud infrastructure, and a managed support team. Evidence from one dependency must not automatically be treated as proof for the whole service.
This structure makes weak coverage visible: an access policy may be current while the review records are missing, or a configuration screenshot may cover only one environment.
AI can help extract relevant passages, suggest relationships, identify missing support, and draft control descriptions. Give it identified source versions and the actual implementation—not just control titles.
A useful mapping proposal explains which part overlaps, which evidence supports that overlap, and what remains unaddressed. Relationships are often many-to-many: one control supports several requirements, while one requirement needs several controls.
Incident handling illustrates the boundary. A shared response process can support multiple frameworks, but reporting thresholds, recipients, triggers, and deadlines may differ. Reusing the operational process does not discharge every notification duty.
Reviewers should check missing scope, conflicting sources, outdated references, and unsupported claims before approving reuse. Preserve the rationale with the relationship so a later framework or implementation change can be assessed intelligently. Our operational risk-register guide applies the same reviewed-assistance principle to scenarios and treatment decisions.
Collect evidence from authoritative systems through a controlled process, whether that involves manual exports or an evaluated collection mechanism. Record who collected it, when, and what population it covers. Do not assume an AI-enabled product automatically has access to operational systems.
AI-assisted extraction should retain the source passage or record supporting each conclusion. Review particularly carefully when documents contain conflicting statements, screenshots lack dates, or exported data excludes some accounts. Missing evidence should produce a question or task—not an invented assertion that the control works.
For generated documentation, use a consistent drafting pattern: purpose, scope, implementation, owner, evidence, exceptions, and review status. Distinguish intended procedures from observed operation. Reports should use reviewed controls and disclose material gaps rather than convert draft suggestions into final assurance.
Uploaded material also needs to be treated as untrusted input. Instructions embedded in documents must not override the review workflow or authorize actions. Read access for analysis should not imply permission to modify controls, approve decisions, or distribute reports.
Consider an illustrative SaaS team documenting one production service. Assume it has an approved access policy, a dated identity-provider export, quarterly review records, and an open task to remove two unnecessary administrator accounts. No savings or product performance are assumed.
The team first defines the boundary: production accounts are included; a separate research environment is excluded. It then links the policy to the intended review process and the completed records to the review activity.
AI proposes an access-control description and candidate framework mappings. The reviewer finds three issues:
The reviewer approves the supported description, rejects a claim that all privileged access is reviewed, and creates tasks for service-identity coverage and removal verification. Framework-specific mappings retain those limitations.
The deliverable is a reviewed control record with bounded evidence and open remediation. It is more useful than several confident narratives because engineers know what to fix and auditors can inspect what supports the claim.
Continuous compliance should mean maintaining evidence and decisions as relevant changes occur. It should not imply that AI continuously proves every control effective.
As a practical recommendation, combine scheduled reviews with change triggers: a new provider, a changed authentication design, a revised framework, an expired evidence period, or a significant incident. Identify the affected controls, mappings, owners, and reports, then request fresh evidence where necessary.
Keep statuses separate: proposed, awaiting evidence, reviewed, approved, and remediation open should not collapse into a single green indicator. Track measures such as overdue reviews, unsupported claims, unresolved exceptions, and the age of evidence. These reveal workload and assurance quality more clearly than document counts.
Compliance material exposes architecture, weaknesses, internal processes, and sometimes personal data. Evaluate hosting location alongside provider access, subprocessors, retention, deletion, model-use terms, and applicable transfer arrangements. EU or German data location alone does not establish sovereignty or GDPR compliance.
Apply least-privilege access and separate drafting from approval. Protect credentials and unnecessary personal information before uploading evidence. Require traceability for material changes and establish how reviewers challenge an AI conclusion. Human approval must mean inspecting support and resolving uncertainty, not clicking through a queue.
Secani supports a focused start: model a service or organizational unit using real target objects, connect its systems and external providers, and name owners and reviewers. Upload existing policies, exports, screenshots, and descriptions; link them to the requirements, controls, systems, or decisions they support. Use AI-assisted suggestions as drafts, check their sources, and preserve comments, approvals, and timestamps. Turn missing or outdated evidence into tasks rather than leaving it buried in documents.
For the first cycle, choose one control family and a short review cadence. Require a clear implementation description, current supporting evidence, reviewed mappings, and assigned gaps before expanding. The Secani documentation explains this starting workflow. Success is a traceable decision that the next reviewer can reproduce—not merely a larger collection of generated text.

AI governance · October 10, 2026 · 9 Min.
A source link does not make an AI verdict reliable. The relationship between a requirement, evidence, and the verdict must be testable.

AI governance · October 19, 2026 · 6 Min.
Three standards in three days: ISO/IEC 27090 for AI security, EN 18286 as the first harmonised standard under the EU AI Act and IEEE 2863 for AI governance at board level.

AI governance · October 18, 2026 · 5 Min.
ISO 27090 guides AI security work. ISO 42001 sets requirements for an AI management system. Here is how they differ and how to use them together.
Secani connects scopes, evidence, tasks, and AI agents in one shared workspace.