Deckard

Ready for your audit

Security and compliance engineering

The security controls SOC 2, HIPAA, ISO 27001 and PCI DSS require, built into your systems, with audit evidence gathered as you go.

Quarterly access reviewQ3 cycle
  1. 42 accounts pulled from OktaEach pull timestamped and signed
  2. Manager sign-offs in from the HR systemOne named manager per account
  3. 1 account unused for 90 daysIts owner confirms or removes itDue Friday

Control holds with 1 exception · Tracked until the exception closes

Passing

Gathered for the quarter from the systems themselves.

The access review, recorded as it runs

TodayScreenshots in a folder

Rebuilt by hand before each audit

01Connect
Read fromOkta, hourly
Sources6, by export and API
Covers52 controls
02Collect
SignatureEvery item, on arrival
TrailSealed, timestamped
Evidence kept7 years
03Check
ReviewerYour security lead
Items this cycle1,874
Audit windowNov 3 to 14
OutReady for the auditorComplete
EvidencePulled from each system
Readiness reviewOct 20
AttestationYour auditor’s

Controls we put in

Evidence is kept in Probo; Gitleaks, Trivy and Sigstore check every code change.

  1. 01Each control matched to the standard you are working toward
  2. 02Checks on every code change: leaked passwords, licenses, signatures
  3. 03Single sign-on, and only the access each person or system needs
  4. 04Evidence collected automatically, on tools you host
  5. 05Encryption, logging and record keeping, set up and written down
  6. 06Access that changes by itself when people join, move or leave
Yours at the end

compliance/

controls/52 controls as code

collectors/Pulls from 6 sources

gates/Each code check, with its failure message

mapping/Which control meets which rule

See it work

Controls, checked every hour

Four checks before code goes live

Secure delivery pipeline: every commit passes four gates, in order, before production; in the build shown the dependency policy stops it, so the signature and production are not reached A commit passes four gates in order: the secrets scan, static analysis (SAST), the dependency policy for licenses and rules, and the signature. Only signed builds reach production, with the SBOM, the list of every package in the build. The build shown passed the secrets scan and static analysis, then the dependency policy stopped it: GPL‑3.0 in a transitive dependency. The signature, production and its SBOM are drawn dashed, not reached.

How it goes live

  1. 01 · Optional

    Gap review

    What your standard requires against what runs today

  2. 02 · Optional

    One area first

    Access control fully in place and recorded, before the rest

  3. 03 · Security engineering

    Controls and checks

    Every control, code check and the evidence store

  4. 04 · Ongoing

    Audit window

    Evidence keeps collecting across the audit period

Name the standard you need to meet

We come back with a fixed-price scope.