Altiri AGKL · Altiri Governed Knowledge Layer
Connect the documentation behind your security program.
AGKL is an approach to building a client-owned knowledge layer from the policies, controls, evidence, findings, and decisions your organization already needs to manage.
From scattered files to connected records
The goal is to make the basis for a statement easier to locate, review, and maintain.
1. Define the scope and structure
Identify the program, information boundaries, record types, owners, and sources included in the engagement.
2. Link the records and evidence
Connect control descriptions to policies, supporting artifacts, findings, and follow-up actions. Use readable files and explicit references so the relationships remain inspectable.
3. Establish review and change control
Define who reviews each record, what prompts an update, and how changes are recorded. Keep missing evidence and unresolved questions visible.
Client ownership and deployment
The engagement defines the infrastructure, access boundaries, information handling, and handoff requirements. The knowledge records are designed to remain readable and portable after the engagement ends.
Open conventions and implementation support
Altiri maintains okf-grc, an open-source project with conventions, tools, and fictional examples for structured compliance knowledge. AGKL adds the organization-specific design, implementation, and review process agreed in the consulting scope.
AI-assisted use
Where AI assistance is included, its permitted sources, model hosting, access, review responsibilities, and approval process should be explicitly defined. Answers and proposed updates still require verification against the underlying record.
Engagement options
An initial engagement can organize a defined body of documentation and establish its maintenance process. Ongoing support can help owners review records, address gaps, and maintain the agreed structure. Deliverables and pricing depend on scope.