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. 1 Scope controls Compliance ManagerControl.List
  2. 2 Collect evidence Control OwnerEvidence.Collect
    • Owners produce their own evidence
  3. 3 Test controls Security EngineerControl.Test
  4. 4 Raise findings Compliance ManagerFinding.Raise
  5. 5 Remediate or except Security EngineerFinding.Close
    • Separation of test and remediation
  6. 6 Sign attestation Chief Information Security OfficerAttestation.Sign
    • 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.

  1. 1
    Scope controls
    Fix the control set for the period and confirm every one has a named owner.
    Compliance ManagerControl.List
  2. 2
    Collect evidence
    Produce the artifact each control requires, from the system wherever possible.
    Control OwnerEvidence.Collect
  3. 3
    Test controls
    Run the test against collected evidence; automated controls test continuously.
    Security EngineerControl.Test
  4. 4
    Raise findings
    Open a finding for every control that did not operate, with severity and a due date.
    Compliance ManagerFinding.Raise
  5. 5
    Remediate or except
    Fix and verify, or route to the risk committee for a time-boxed exception.
    Security EngineerFinding.Close
  6. 6
    Sign attestation
    Sign the period statement once findings are closed or formally accepted.
    Chief Information Security OfficerAttestation.Sign

Owned end to end by Chief Information Security Officer.

SOP / runbook

The same process as a numbered operating procedure.

PurposeScoping through signed attestation — the loop an auditor asks you to evidence.
OwnerChief Information Security Officer
TriggerQuarterly assurance cycle opens.
  1. 1. Scope controls
    Fix the control set for the period and confirm every one has a named owner.
    Performed by Compliance Manager
  2. 2. Collect evidence
    Produce the artifact each control requires, from the system wherever possible.
    Performed by Control Owner
  3. 3. Test controls
    Run the test against collected evidence; automated controls test continuously.
    Performed by Security Engineer
  4. 4. Raise findings
    Open a finding for every control that did not operate, with severity and a due date.
    Performed by Compliance Manager
  5. 5. Remediate or except
    Fix and verify, or route to the risk committee for a time-boxed exception.
    Performed by Security Engineer
  6. 6. Sign attestation
    Sign 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 Officer
    Accountable for the control environment as a whole.
    Sign attestation
    • Compliance Manager
      Runs the calendar, the evidence register, and the audit relationship.
      Scope controlsRaise findings
      • Control Owner
        Operates a specific control and produces its evidence.
        Collect evidence
    • Security Engineer
      Automates control tests and remediates technical findings.
      Test controlsRemediate or except
    • Risk Committee Chair
      Approves 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.

StepChief Information Security OfficerCompliance ManagerControl OwnerSecurity EngineerRisk Committee Chair
Scope controlsAR
Collect evidenceACRC
Test controlsAR
Raise findingsARC
Remediate or exceptACRC
Sign attestationRCC

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.

    Attestation.Sign
  • Signature is the cisos access

    One signature, one accountable person. Delegation defeats the point of signing.

    Attestation.Sign Chief Information Security Officer
  • Exceptions go to committee access

    Accepting a gap is a risk decision, not an engineering one.

    Exception.Approve Risk Committee ChairChief Information Security Officer
  • 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.

    Finding.Close Security EngineerCompliance Manager
  • Owners produce their own evidence access

    Evidence comes from the control’s owner, so provenance is never in question.

    Evidence.Collect Control OwnerCompliance Manager

Product

What gets built on top of it — the data, the screens, the API.

Data model

The entities, their fields, and how they relate.

Control TestList

One 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
Evidence Collect

An artifact collected to demonstrate a control operated as designed.

  • collectedOn date required
  • source enum required system · screenshot · attestation · log-export
  • period string required
Finding RaiseClose

A 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
Exception Approve

A documented, time-boxed acceptance of a control gap.

  • rationale text required
  • expiresOn date required
  • compensating string
Attestation Sign

The 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
Control Register 🔒
Control register.
Control tablesummary
/findings/:id
Finding Detail 🔒
Finding detail.
Finding formactions
/evidence
Evidence Register 🔒
Evidence register.
Evidence table
/exceptions
Exception Log 🔒
Exception log.
Exception actions

Example UI

A working admin table and detail form, built from the fields.

Control Register Test
RefObjectiveOwnerCadenceAutomated
CC6.1Logical access is restricted to authorised usersPlatformcontinuoustrue
CC7.2Security events are monitored and triagedSecOpscontinuoustrue
CC8.1Changes are authorised before deploymentEngineeringmonthlyfalse
CC1.4Personnel complete security trainingPeopleannualfalse
Control detail

API surface

The endpoints, grouped by namespace, with their operations.

Assurance/api/assurance

Control, evidence, finding, and attestation operations.

  • GET /api/assurance/controls Control.List The control register.
  • POST /api/assurance/controls/{id}/test Control.Test Run a control test.
  • GET /api/assurance/evidence Evidence.List Evidence for the period.
  • POST /api/assurance/evidence Evidence.Collect Attach evidence.
  • GET /api/assurance/findings Finding.List Open findings by severity.
  • POST /api/assurance/findings/{id}/close Finding.Close Close a finding.
  • POST /api/assurance/attestations Attestation.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.

AssuranceWeb
nextjs 15
Register, findings, and evidence surfaces.
BastionAssurance.Product.Web
ControlService
nestjs 10
Control register and test orchestration.
BastionAssurance.Product.Api
EvidenceCollector
express 4
Pulls system evidence on the control cadence.
BastionAssurance.Operational
FindingService
nestjs 10
Findings, exceptions, and remediation state.
BastionAssurance.Product.Api
AssuranceDb
postgres 16
Controls, evidence, findings, attestations.
BastionAssurance.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.

dev
Control authoring and test development.
Providers
AWScloudAuroradatabase
Cells
none
staging
Audit rehearsal against last period’s data.
Providers
AWScloudAuroradatabaseOktaauth
Cells
none
prod
The register of record.
Providers
AWScloudAuroradatabaseOktaauthS3ObjectLockstorageSplunkmonitoring
Cells
AssuranceWebControlServiceEvidenceCollectorFindingServiceAssuranceDb

Access-control matrix

Which role may perform which operation, derived not declared.

OperationChief Information Security OfficerCompliance ManagerControl OwnerSecurity EngineerRisk Committee Chair
Evidence.CollectOwners produce their own evidence✓✓
Finding.CloseSeparation of test and remediation✓✓
Exception.ApproveExceptions go to committee✓✓
Attestation.SignSignature is the cisos✓
No access rule governs
Control.TestControl.ListEvidence.ListFinding.RaiseFinding.ListAttestation.Read

Derived, 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. 1. Download the template

    The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.

    Download Bastion Assurance as JSON
  2. 2. 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. 3. Join the waitlist

    The hosted product runs your model for your team and your agents.

Which of these sounds like you? Pick as many as apply.

The most useful box on this page. Rough is fine, and “nowhere, honestly” is a real answer and a common one.

We reply by hand, usually within a day. No sequence, no drip, no spam.