Krypton Audit Console Built by Terry Afram-Kumi · CISA · PMP · MSc · ISO/IEC 27001:2022 Lead Auditor · AI Security & Governance Certified — Founder, Terafram Back to kryptongrc.com

Session workspace

Krypton Audit Console

Test a cloud policy against a real engine. Practise the call an auditor makes on evidence. Every number on this board comes from your own actions in this visit.

Status · Ready — nothing tested yet Period · This visit Suites · Policy Tester · Practice Lab

Dashboard

This visit · live session
PTNot started
0 / 4
Lessons tested
✓No runs yet
0 / 0
Rules passed
PLNot started
0 / 5
Lab calls judged
TLNot started
0 / 9
Trilogy stations
RRAll clear
0
Open risks

SSession score

Session score
Nothing tested yet

Run a lesson or judge a scenario and the score wakes up.

The ring counts passed lessons plus agreed calls over every check attempted. Nothing attempted, no score — the ring waits for work.

RRisk distribution

High0
Medium0
Low0

Counted from the register itself. A risk shows here only when a finding raises it and you rate it.

CSuite progress

Policy Tester0 / 4
Practice Lab0 / 5
Trilogy Lab0 / 9
ISO 42001 Board0 / 9

Each bar is the work itself, counted as it happens in this visit.

Fixes applied: 0
Session detail
Calls agreed with the auditor0 / 0
Rules progress
Agreed progress

Everything on this board counts this visit only. Leave the page and it resets — like a real workshop.

Program

A working GRC program is a chain: risk, controls, evidence, reporting. A finding at one step becomes the work of the next. Every step below is a room in this console — start at the top or jump straight to the step you need.

Knowledge checks

The five lab scenarios are the checks. Each one hands you an evidence pack, takes your call and marks it against the auditor's conclusion.

1

Executive summary

2

Objective & scope

This workspace tests cloud policy rules against a live policy engine and trains audit judgement on evidence packs. It is a teaching and demonstration workspace, not an audit of any real organisation. Nothing here examines a live estate, a client system or a named company. The lessons use published sample configurations. The scenarios use written evidence packs prepared for training.

3

Methodology & audit approach

The work runs on CISA audit method with PMP execution discipline. Evidence comes before conclusions. Every policy verdict traces back to the engine output printed with the run. Every lab conclusion traces back to the auditor's stated reasoning on the evidence pack. A result you cannot trace is a result you cannot defend, so this workspace shows its working for every call it records.

Operational Audit Logic

CISA — Audit · PMP — Audit Execution · Security AI — AI Governance

Full closed-loop audit software, from beginning to end.

4

Provisions

One row per item across both suites. Status and conclusion reflect your latest action in this visit. Review jumps to the item in its room.

ItemSuiteMethodStatusConclusion

Policy Tester

Four short lessons. Each one starts broken on purpose. Pick a lesson, press run and watch it fail. Then apply the fix — by hand or with one click — and run it again to watch it pass. You cannot break anything here.

LessonPlain-words riskStatusConclusion

The tester sleeps when idle — the first run can take up to a minute to wake it.

See the code

Two short files run every test. The setup states what exists. The rule states what should be true. Both are editable — the engine judges whatever you hand it.

The facts, written as a list. This is the claim being tested.

The test, written so a computer checks it the same way every single time.

The policy tester is adapted from the open-source GRC Playground by Ashley Pearce (MIT). Scenarios and page by Terafram.

Practice Lab

Pick a scenario. Read the situation and the evidence, then commit to a call. The auditor's conclusion waits behind your answer. You can revisit any scenario — your latest call is the one that counts.

ScenarioFramework refStatusYour callAuditor's call

Frameworks

23 frameworks in the engine

The frameworks are the lenses. The work underneath them is one set of 29 controls. A Full Scan answers those controls once and the result reads against every framework the controls honestly reach — no framework is handed a number its evidence did not earn.

A framework score is an auditor's view of where you stand against it. It is not a certification. Terafram does not issue certifications — we give guidance and assurance.
FrameworkKindTierWhere it lives
The standard library — the twelve
ISO/IEC 27001:2022ComplianceLicensedFull Scan — reaches 25 of the 29 controls
NIST CSF 2.0ComplianceFreeFull Scan
SOC 2 (Trust Services Criteria)ComplianceLicensedFull Scan — reaches 26 of the 29 controls
PCI DSS v4.0ComplianceLicensedFull Scan — reaches 22 of the 29 controls · template in Policy Pack Part II
HIPAA Security RuleComplianceFreeFull Scan · templates in Policy Pack Part II
GDPR (EU 2016/679)ComplianceFreeFull Scan — reaches 26 of the 29 controls
CIS Controls v8ComplianceFreeFull Scan — reaches 19 of the 29 controls
HITRUST CSFComplianceLicensedFull Scan
NIST SP 800-53 (Rev. 5)ComplianceFreeFull Scan
CSA Cloud Controls Matrix v4ComplianceFreeFull Scan — reaches 22 of the 29 controls
ISO/IEC 42001:2023ComplianceLicensedFull Scan — reaches 12 of the 29 controls · ISO 42001 Board and Academy
COBIT 2019ComplianceLicensedFull Scan — reaches 11 of the 29 controls
Krypton's additional eleven
NIST SP 800-171ComplianceFreeFull Scan
CMMC 2.0 (Level 2)ComplianceFreeFull Scan
FedRAMPComplianceFreeFull Scan
NIST AI RMF 1.0ComplianceFreeFull Scan
SOC 1 (SSAE 18 / ISAE 3402)ComplianceLicensedFull Scan — reaches 11 of the 29 controls
ISO 9001:2015ComplianceLicensedFull Scan — reaches 10 of the 29 controls
OWASP Top 10:2025RiskFreeFull Scan
OWASP API Security Top 10:2023RiskFreeFull Scan
OWASP LLM Top 10:2025RiskFreeFull Scan
MITRE ATT&CK (Enterprise)RiskFreeFull Scan
MITRE ATLAS (AI Threat Matrix)RiskFreeFull Scan

All 23 score in a Full Scan today.

Risk Register

Findings become risks here. A failed policy lesson raises a risk. A scenario the auditor calls Not operating raises a risk. Rate each one, choose a treatment and watch the register clear as the causes get fixed.

Likelihood × impact

Rows are likelihood, columns are impact. The number in a cell is how many rated risks sit there.

No risks raised yet. Fail a policy lesson or judge a scenario Not operating and the finding lands here as a risk.

Policy Pack

Terafram keeps two sets of policies. Part I is the house set — the fourteen policies Terafram itself runs on, approved on 25 October 2026 and in force today. Part II is the client set — templates for programmes such as HIPAA and PCI DSS, issued to a client organisation for its own adoption, with an auditor guiding the work. This room is the register of both sets.

We don't issue certification but we give guidance and assurance. Terafram is not a certification body. Guidance walks the adoption with you. Assurance is an auditor's independent view of where you stand.
PolicyPartOwnerStatus
Part I — Terafram internal policies
POL-001 · Information Security PolicyPart ICISOApproved
POL-002 · Access Control PolicyPart IIT SecurityApproved
POL-003 · Data Classification PolicyPart IData GovApproved
POL-004 · Incident Response PolicyPart ISecOpsApproved
POL-005 · Backup & Recovery PolicyPart IInfrastructureApproved
POL-006 · Acceptable Use PolicyPart IHRApproved
POL-007 · Vendor Management PolicyPart IProcurementApproved
POL-008 · Encryption PolicyPart IIT SecurityApproved
POL-009 · Data Retention & Disposal PolicyPart IGRCApproved
POL-010 · Secure Software Development & Change PolicyPart ICTO + AppSecApproved
POL-011 · Business Continuity & Contingency PolicyPart IOperationsApproved
POL-012 · Logging & Monitoring PolicyPart ISecOpsApproved
POL-013 · AI Acceptable Use & Governance PolicyPart IFounderApproved
POL-014 · Privacy & Data Protection PolicyPart IPrivacyApproved
Part II — Client adoption templates
POL-015 · HIPAA Privacy & Security PolicyPart IIPrivacy & Security OfficerClient template
POL-016 · HIPAA Minimum Necessary Standard PolicyPart IIPrivacy OfficerClient template
POL-017 · HIPAA Breach Notification PolicyPart IIPrivacy + LegalClient template
POL-018 · HIPAA Workforce Sanction PolicyPart IIHR + Privacy OfficerClient template
POL-019 · PCI DSS Cardholder Data Protection PolicyPart IICISO + ComplianceClient template

The texts are issued inside a guided adoption, not downloaded here — a template in the wrong scope is paper compliance.

POL-020 · AI Adoption Policy Client template Approved for issue
Approval progress
  • ✓Drafted
  • ✓Reviewed
  • ✓Approved
  • ✓Published

Approved for issue by the founder on 25 October 2026 and published in the pack the same day.

Version history
VersionStatusDate
1.0Approved for issue25 October 2026
1.1Credential line completed to the full standing set25 October 2026
Auditor's note
We don't issue certification but we give guidance and assurance — an auditor's independent view of where you stand.
Terafram — Controlled Document · Client Adoption Template

AI Adoption Policy

Owner: AI Governance Lead
Version: 1.1
Status: Client adoption template — approved for issue, 25 October 2026
Issued: 25 October 2026
Review: At least annually
1. Purpose

This policy governs how the adopting organisation's workforce adopts and uses artificial intelligence tools. It brings AI use into the open, classifies every tool before it is used and fixes the rules for the data a tool may touch, the review its output must pass and the limits its agents must work inside.

2. Scope

This policy applies to every use of an AI tool, AI feature or AI agent by the adopting organisation's workforce, including employees, contractors and temporary staff, at any location and on any device used for work. It covers tools bought by the organisation, tools provided inside other software and tools adopted by individuals on their own.

3. Policy Statements
Approved Approved with masking Restricted

Twelve auditable statements govern classification before use, data gating, human review of output, agent limits and AI incidents — issued in full inside a guided adoption.

7. Related Controls

References for this policy:

  • ISO/IEC 42001 — Artificial intelligence management systems. This template is aligned to the principles of ISO/IEC 42001 as a statement of design intent only. Adoption of this template is not a claim of certification to or conformity with ISO/IEC 42001.
  • POL-013 — AI Acceptable Use & Governance Policy: the internal twin of this template, which Terafram itself operates under Part I of this pack.

Issued by: Terry Afram-Kumi · Founder, Terafram · CISA · PMP · MSc · ISO/IEC 27001:2022 Lead Auditor · AI Security & Governance Certified — 25 October 2026

Adopted by (client): ______ · Date: ______

How a guided adoption runs
1 · Scenario first Your situation, told in your facts. The worked example shows the shape your adoption follows.
2 · Scope agreed What the policy governs gets named: the data, the systems, the people. What sits outside it gets named too.
3 · Template issued The template leaves Terafram with your owners and your systems written in, ready for your leadership to read.
4 · Client adopts Your leadership signs. Adoption is the client's act; the policy becomes yours on that signature.
5 · Auditor verifies A CISA pass over the evidence: does the policy operate, not just exist?
Adopt with a guide

Thirty minutes with the founder — not a sales rep. Bring your scenario; leave with your scope.

Book a free consultation

Trilogy Lab

This room runs on one chain, in this order: Policy → Controls → Risk → Remediation → Report Generation. Policy is the foundation. Controls are tested against it. Findings become risks. Risks get remediated. The report is generated from what actually happened. No step is skipped and none is reordered.

Every station below is real execution. The documents are the approved policies themselves, quoted word for word. The tests run on the live engine. The register and the report are the same ones the rest of this console uses. There are no invented scenarios here and no answer keys written for the occasion — where a station checks your work, the ground truth is a real document or a real manifest — and the reveal quotes it.

StationManual partBeatChain linkStatus

The policies quoted in this room are the approved Terafram documents. The engine is the same live engine the Policy Tester uses. What you type into the builders stays in this page — it is never stored and never sent anywhere except the engine calls the tester already makes.

ISO 42001 Board

0/9 objectives tested

This board tracks the session's own work against the structure of ISO/IEC 42001 Annex A — the standard's nine objectives and its 38 controls. A row moves only when the work that evidences it actually happens in this console. Conclusions here are the lab's verdicts on session work — they are not a certification claim, for anyone, ever.

The management-system spine — Clauses 4 to 10
Clause 4Context
Clause 5Leadership
Clause 6Planning
Clause 7Support
Clause 8Operation
Clause 9Performance evaluation
Clause 10Improvement

The nine objectives below sit under this spine. The spine is the standard's shape alone — every state on the board comes from your work in this visit.

CodeObjectiveControlsEvidenced byMethodStatusConclusion

A note on the two document-review rows: opening the Policy Pack room is the review event. Reading the governed document is the act those rows record — the same way an auditor's document review is work, not a glance.

The 42001 Academy — learn it by running it

Twelve modules across five phases. Every module's lesson is a real Terafram document, its lab is a real execution in this console, its artefact is a real output and its check is a judgement against a real text. A module completes when its lab event really happens in this session — the same events that move the board above. The session report, sealed, is the academy's final artefact.

Modules completed 0/12

One honest note on shared work: a single piece of work can complete two modules where the work is genuinely the same. The plan built at Trilogy Station 4 completes both 2.2 and 4.1 — the plan is where the interested parties get named and where competence gets planned, so one artefact honestly carries both.

Nothing on this board is stored. Leave the page and every row returns to Not tested — the evidence was the session itself.

Evidence & Results

The register for this visit. Every policy run keeps its full engine output as its evidence. Every lab judgement keeps your call beside the auditor's call.

Nothing here yet. Your first policy verdict and your first lab judgement land here the moment they happen.

AI Data Readiness

Demo data — sample assets

AI Data Readiness — which assets are safe to feed into AI / LLM training, RAG or prompts — plus what must be masked or excluded. Sensitive and regulated data is the risk. This register is a sample: it shows the shape of the review. It does not evaluate any real system.

No register loaded yet. Load the sample register to see six sample assets with a readiness bar, a verdict and a reason for each one.

Three doors from here

The main site

The Krypton Audit Console is the workshop. The main site carries the full story: how Krypton works, the frameworks it covers and the pricing.

Visit kryptongrc.com

Your own estate, tested for real

The Playground judges sample files. The workspace judges yours — assessments across 20+ frameworks, cloud evidence collected and sealed, agents tested before they act. Express is free. Your first full scan is free.

Enter the Krypton GRC workspace

Talk it through first

Prefer to talk it through first? Book a free consultation — thirty minutes with me, not a sales rep.

Book a free consultation

Why I give this away

I am Terry Afram-Kumi. I audit for a living and I built Krypton GRC so a verdict never depends on who is asking. The Playground is the front porch: small, free and honest about what it proves. If it teaches you the pattern, it has done its job — and if you want the pattern run across your whole estate, you know where the door is. Teaching with it? Run it in your classes and your videos — that is what it is for.

Built by Terry Afram-Kumi · CISA · PMP · MSc · ISO/IEC 27001:2022 Lead Auditor · AI Security & Governance Certified — Founder, Terafram