Session workspace
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.
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.
Counted from the register itself. A risk shows here only when a finding raises it and you rate it.
Each bar is the work itself, counted as it happens in this visit.
Everything on this board counts this visit only. Leave the page and it resets — like a real workshop.
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.
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.
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.
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.
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.
| Item | Suite | Method | Status | Conclusion |
|---|
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.
| Lesson | Plain-words risk | Status | Conclusion |
|---|
The tester sleeps when idle — the first run can take up to a minute to wake it.
Engine output — the evidence
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.
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.
| Scenario | Framework ref | Status | Your call | Auditor's call |
|---|
The evidence
Your call
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.
| Framework | Kind | Tier | Where it lives |
|---|---|---|---|
| The standard library — the twelve | |||
| ISO/IEC 27001:2022 | Compliance | Licensed | Full Scan — reaches 25 of the 29 controls |
| NIST CSF 2.0 | Compliance | Free | Full Scan |
| SOC 2 (Trust Services Criteria) | Compliance | Licensed | Full Scan — reaches 26 of the 29 controls |
| PCI DSS v4.0 | Compliance | Licensed | Full Scan — reaches 22 of the 29 controls · template in Policy Pack Part II |
| HIPAA Security Rule | Compliance | Free | Full Scan · templates in Policy Pack Part II |
| GDPR (EU 2016/679) | Compliance | Free | Full Scan — reaches 26 of the 29 controls |
| CIS Controls v8 | Compliance | Free | Full Scan — reaches 19 of the 29 controls |
| HITRUST CSF | Compliance | Licensed | Full Scan |
| NIST SP 800-53 (Rev. 5) | Compliance | Free | Full Scan |
| CSA Cloud Controls Matrix v4 | Compliance | Free | Full Scan — reaches 22 of the 29 controls |
| ISO/IEC 42001:2023 | Compliance | Licensed | Full Scan — reaches 12 of the 29 controls · ISO 42001 Board and Academy |
| COBIT 2019 | Compliance | Licensed | Full Scan — reaches 11 of the 29 controls |
| Krypton's additional eleven | |||
| NIST SP 800-171 | Compliance | Free | Full Scan |
| CMMC 2.0 (Level 2) | Compliance | Free | Full Scan |
| FedRAMP | Compliance | Free | Full Scan |
| NIST AI RMF 1.0 | Compliance | Free | Full Scan |
| SOC 1 (SSAE 18 / ISAE 3402) | Compliance | Licensed | Full Scan — reaches 11 of the 29 controls |
| ISO 9001:2015 | Compliance | Licensed | Full Scan — reaches 10 of the 29 controls |
| OWASP Top 10:2025 | Risk | Free | Full Scan |
| OWASP API Security Top 10:2023 | Risk | Free | Full Scan |
| OWASP LLM Top 10:2025 | Risk | Free | Full Scan |
| MITRE ATT&CK (Enterprise) | Risk | Free | Full Scan |
| MITRE ATLAS (AI Threat Matrix) | Risk | Free | Full Scan |
All 23 score in a Full Scan today.
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.
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.
| Risk | Source | Likelihood | Impact | Rating | Treatment |
|---|
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.
| Policy | Part | Owner | Status |
|---|---|---|---|
| Part I — Terafram internal policies | |||
| POL-001 · Information Security Policy | Part I | CISO | Approved |
| POL-002 · Access Control Policy | Part I | IT Security | Approved |
| POL-003 · Data Classification Policy | Part I | Data Gov | Approved |
| POL-004 · Incident Response Policy | Part I | SecOps | Approved |
| POL-005 · Backup & Recovery Policy | Part I | Infrastructure | Approved |
| POL-006 · Acceptable Use Policy | Part I | HR | Approved |
| POL-007 · Vendor Management Policy | Part I | Procurement | Approved |
| POL-008 · Encryption Policy | Part I | IT Security | Approved |
| POL-009 · Data Retention & Disposal Policy | Part I | GRC | Approved |
| POL-010 · Secure Software Development & Change Policy | Part I | CTO + AppSec | Approved |
| POL-011 · Business Continuity & Contingency Policy | Part I | Operations | Approved |
| POL-012 · Logging & Monitoring Policy | Part I | SecOps | Approved |
| POL-013 · AI Acceptable Use & Governance Policy | Part I | Founder | Approved |
| POL-014 · Privacy & Data Protection Policy | Part I | Privacy | Approved |
| Part II — Client adoption templates | |||
| POL-015 · HIPAA Privacy & Security Policy | Part II | Privacy & Security Officer | Client template |
| POL-016 · HIPAA Minimum Necessary Standard Policy | Part II | Privacy Officer | Client template |
| POL-017 · HIPAA Breach Notification Policy | Part II | Privacy + Legal | Client template |
| POL-018 · HIPAA Workforce Sanction Policy | Part II | HR + Privacy Officer | Client template |
| POL-019 · PCI DSS Cardholder Data Protection Policy | Part II | CISO + Compliance | Client template |
The texts are issued inside a guided adoption, not downloaded here — a template in the wrong scope is paper compliance.
Approved for issue by the founder on 25 October 2026 and published in the pack the same day.
| Version | Status | Date |
|---|---|---|
| 1.0 | Approved for issue | 25 October 2026 |
| 1.1 | Credential line completed to the full standing set | 25 October 2026 |
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.
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.
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.
References for this policy:
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: ______
Thirty minutes with the founder — not a sales rep. Bring your scenario; leave with your scope.
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.
| Station | Manual part | Beat | Chain link | Status |
|---|
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.
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 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.
| Code | Objective | Controls | Evidenced by | Method | Status | Conclusion |
|---|
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.
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.
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.
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 — 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.
Sample assets only — names, scores and reasons are illustrative.
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.comThe 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 workspacePrefer to talk it through first? Book a free consultation — thirty minutes with me, not a sales rep.
Book a free consultationI 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