PlaygroundSecurity & compliance
Bastion Assurance
Fictional companySecurity & compliance
A security and compliance function running control ownership, evidence collection, findings, and attestation on one operating model.
Modeled on
- SOC 2 Trust Services Criteria: Control references (CC1–CC9) and the five criteria categories.
- NIST SP 800-53 Rev. 5: Control family mappings — AC, AU, CM, IR.
- NIST OSCAL: Catalog, profile, assessment result, and plan-of-action-and-milestones artifacts.
The genome map
Roles in their reporting line, the process step by step with the role on each step, the rules on the steps they govern, and the resources the work acts on. Select a role to see what it reaches.
Roles Select a role to see its reach.
Control Assurance Operated by Chief Information Security Officer
Scoping through signed attestation — the loop an auditor asks you to evidence.
- 1 Scope controls
- 2 Collect evidence
- Owners produce their own evidence
- 3 Test controls
- 4 Raise findings
- 5 Remediate or except
- Separation of test and remediation
- 6 Sign attestation
- No attestation with open critical findings
- Signature is the cisos
Resources
- Control
- Evidence
- Finding
- Exception
- Attestation
Rules on no step They govern operations outside the process.
- Exceptions go to committee
Three questions this genome answers
Each answer comes from the compiled genome alone. Pick another subject and the answer changes in place.
Compliance Manager, Control Owner may perform Evidence.Collect. The rule: Owners produce their own evidence.
These steps wait for Compliance Manager:
- Scope controls Control Assurance
- Raise findings Control Assurance
Compliance Manager, Security Engineer act on Control, by a process step or under an access rule.
Every artifact from one genome
The same derivations and renderers the Playground runs, here for Bastion Assurance at build time. Open it in the Playground to pick your own set.
Operations
How the work actually runs — who owns what, in what order, under which rules.
Process flow
The end-to-end sequence, each step with its owner.
Scoping through signed attestation — the loop an auditor asks you to evidence.
- 1Scope controlsFix the control set for the period and confirm every one has a named owner.
- 2Collect evidenceProduce the artifact each control requires, from the system wherever possible.
- 3Test controlsRun the test against collected evidence; automated controls test continuously.
- 4Raise findingsOpen a finding for every control that did not operate, with severity and a due date.
- 5Remediate or exceptFix and verify, or route to the risk committee for a time-boxed exception.
- 6Sign attestationSign the period statement once findings are closed or formally accepted.
Owned end to end by Chief Information Security Officer.
SOP / runbook
The same process as a numbered operating procedure.
- 1. Scope controlsFix the control set for the period and confirm every one has a named owner.Performed by Compliance Manager
- 2. Collect evidenceProduce the artifact each control requires, from the system wherever possible.Performed by Control Owner
- 3. Test controlsRun the test against collected evidence; automated controls test continuously.Performed by Security Engineer
- 4. Raise findingsOpen a finding for every control that did not operate, with severity and a due date.Performed by Compliance Manager
- 5. Remediate or exceptFix and verify, or route to the risk committee for a time-boxed exception.Performed by Security Engineer
- 6. Sign attestationSign the period statement once findings are closed or formally accepted.Performed by Chief Information Security Officer
Key positions
The roles this operation needs and who reports to whom.
Control Environment
- Chief Information Security OfficerAccountable for the control environment as a whole.Sign attestation
- Compliance ManagerRuns the calendar, the evidence register, and the audit relationship.Scope controlsRaise findings
- Control OwnerOperates a specific control and produces its evidence.Collect evidence
- Security EngineerAutomates control tests and remediates technical findings.Test controlsRemediate or except
- Risk Committee ChairApproves exceptions and accepted risk.
Each chip is a step of the process that role owns.
RACI matrix
Every step against every role — responsible, accountable, consulted.
| Step | Chief Information Security Officer | Compliance Manager | Control Owner | Security Engineer | Risk Committee Chair |
|---|---|---|---|---|---|
| Scope controls | A | R | |||
| Collect evidence | A | C | R | C | |
| Test controls | A | R | |||
| Raise findings | A | R | C | ||
| Remediate or except | A | C | R | C | |
| Sign attestation | R | C | C |
R responsible · A accountable · C consulted — derived from step owners, the process operator, and access rules.
Policies & rules
The constraints that govern each operation, stated as rules.
- No attestation with open critical findings condition
The period cannot be attested while a critical finding is open and unaccepted.
- Signature is the cisos access
One signature, one accountable person. Delegation defeats the point of signing.
- Exceptions go to committee access
Accepting a gap is a risk decision, not an engineering one.
- Separation of test and remediation access
The person who closes a finding is not the person who tested it — the whole basis of the evidence.
- Owners produce their own evidence access
Evidence comes from the control’s owner, so provenance is never in question.
Product
What gets built on top of it — the data, the screens, the API.
Data model
The entities, their fields, and how they relate.
TestListOne control from the framework, with its owner and testing cadence.
- reference string required
- objective text required
- frequency enum required continuous · monthly · quarterly · annual
- criteria enum required security · availability · confidentiality · processing-integrity · privacy
- nistMapping string
- automated boolean
CollectAn artifact collected to demonstrate a control operated as designed.
- collectedOn date required
- source enum required system · screenshot · attestation · log-export
- period string required
RaiseCloseA control that did not operate as designed, with its severity and remediation owner.
- severity enum required low · moderate · high · critical
- summary text required
- dueOn date
- status enum required open · remediating · closed · accepted
ApproveA documented, time-boxed acceptance of a control gap.
- rationale text required
- expiresOn date required
- compensating string
SignThe signed statement that the control set operated for a period.
- period string required
- signedOn date
- scope string required
Screen map
Every route and the page it resolves to.
Shell: AssuranceShell
/controls/findings/:id/evidence/exceptionsExample UI
A working admin table and detail form, built from the fields.
| Ref | Objective | Owner | Cadence | Automated |
|---|---|---|---|---|
| CC6.1 | Logical access is restricted to authorised users | Platform | continuous | true |
| CC7.2 | Security events are monitored and triaged | SecOps | continuous | true |
| CC8.1 | Changes are authorised before deployment | Engineering | monthly | false |
| CC1.4 | Personnel complete security training | People | annual | false |
API surface
The endpoints, grouped by namespace, with their operations.
/api/assuranceControl, evidence, finding, and attestation operations.
- GET
/api/assurance/controlsControl.List The control register. - POST
/api/assurance/controls/{id}/testControl.Test Run a control test. - GET
/api/assurance/evidenceEvidence.List Evidence for the period. - POST
/api/assurance/evidenceEvidence.Collect Attach evidence. - GET
/api/assurance/findingsFinding.List Open findings by severity. - POST
/api/assurance/findings/{id}/closeFinding.Close Close a finding. - POST
/api/assurance/attestationsAttestation.Sign Sign the period attestation.
Technology
Where it runs and who can reach it.
Architecture diagram
The cells this runs on and what talks to what.
BastionAssurance.Product.WebBastionAssurance.Product.ApiBastionAssurance.OperationalBastionAssurance.Product.ApiBastionAssurance.Product.Core- AssuranceWeb → ControlService register
- AssuranceWeb → FindingService findings
- EvidenceCollector → ControlService evidence.collected
- ControlService → FindingService control.failed
- ControlService → AssuranceDb depends-on
- FindingService → AssuranceDb depends-on
Environment topology
Dev, staging, and production, with the providers behind each.
Access-control matrix
Which role may perform which operation, derived not declared.
| Operation | Chief Information Security Officer | Compliance Manager | Control Owner | Security Engineer | Risk Committee Chair |
|---|---|---|---|---|---|
Evidence.CollectOwners produce their own evidence | ✓ | ✓ | |||
Finding.CloseSeparation of test and remediation | ✓ | ✓ | |||
Exception.ApproveExceptions go to committee | ✓ | ✓ | |||
Attestation.SignSignature is the cisos | ✓ |
Control.TestControl.ListEvidence.ListFinding.RaiseFinding.ListAttestation.ReadDerived, not declared — this is the list an audit asks about.
Make yours
Start from Bastion Assurance and change what differs, or pick another company as your template. Three ways in:
1. Download the template
The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.
Download Bastion Assurance as JSON2. Start an agent from it
Paste this into an agent that has the DNA MCP server connected. It drafts your model in the conversation and saves only when you ask.
Use the DNA MCP server (https://agents.dna.codes) to help me model how my company works. Start from the Bastion Assurance genome at https://dna.codes/genome/security.json. It is an example company, not mine. Read its roles, process steps, rules and resources, then ask me how my company differs. Draft my company's operating model in this conversation, as structure/v1 and behaviour/v1 documents, and use `validate` on each draft. Do not save anything: call `apply` only when I ask you to save.
3. Join the waitlist
The hosted product runs your model for your team and your agents.