1. Home
  2. Frameworks
  3. SOC 2

SOC 2

Evidence for the whole observation period, not one screenshot.

A SOC 2 Type II report looks at how controls operated over months. ACSE checks the cloud configuration behind the Security, Availability and Confidentiality criteria on every scan, and keeps a signed record of each finding, its fix and who approved it.

Audit packages from sealed casesSealed cases stack into an audit package organized per framework control.AUDIT PACKAGESEALED CASESpci dss 4.0.1 · q3 · per control
01

Operating evidence, continuously

Scans run on a schedule and every result is recorded, so you can show how a control held over the period.

02

Change management your auditor can follow

Each fix shows what changed, who approved it and how it was verified, in a record they can check offline.

03

A scope you can defend

ACSE tracks the criteria cloud configuration supports and says so. The rest stay with your team.

Coverage

Tracked criteria with a check behind them

ACSE tracks 38 points from the Common Criteria (Security) and the Availability and Confidentiality criteria. Many describe processes rather than configuration, which is why fewer are backed by checks. Controls without a check are listed as manual, beside the score, so nothing quietly drops out of view.

AWS
8 of 38 tracked criteria
Google Cloud
7 of 38 tracked criteria
Azure
5 of 38 tracked criteria

A case, start to finish

What your auditor can see

  1. FindingThe check that failed, the resource and the criteria it affects.
  2. ProposalThe change as code, validated against a plan, with its blast radius and recovery plan.
  3. DecisionA security approver who did not author the change decides with MFA, bound to the exact view they saw.
  4. VerificationAfter the change applies, ACSE re-reads the resource and watches it through an observation window before sealing the case.
Sealed, signed, ready for auditFour signed records for one change, from the approval decision to the verification, each pointing at the hash of the record before it, closed with a seal.RECORD 21decision · approveprev 3f0a…RECORD 22merge observedprev 9c1e…RECORD 23observed stateprev 71b2…RECORD 24verificationverdict: compliantprev e04d…SEALED · OBSERVATION WINDOW CLOSED ·✓

Offline verification

Your auditor checks it without an account

Export a case and your auditor verifies its signatures and hash chain on their own machine, with independent command-line verifiers in Python and TypeScript that must agree.

The records live in your own cloud, under retention lock, so the evidence does not depend on ACSE being reachable.

Verified offlineAn auditor opens a case bundle on their own machine with no network and no ACSE account. The verifier confirms the chain, the signatures and the seal, and two independent verifiers agree.CASE BUNDLEacse-verify bundle.zip✓ chain intact✓ signatures valid✓ seal validpython and typescript agreeno network · no acse account

Questions

What people ask us

Does ACSE give us a SOC 2 report?

No. A SOC 2 report comes from an independent CPA firm. ACSE checks the cloud configuration behind the criteria it tracks and keeps evidence your auditor can verify.

Can ACSE help with the observation period?

Yes. Scans run on a schedule, and each result and each fix is recorded with its time, so you can show how a tracked control held across the period, including any time it failed and how quickly it was fixed.

Which criteria does ACSE track?

The Common Criteria for Security, plus the Availability and Confidentiality criteria. Processing Integrity and Privacy are not tracked.

Talk to us

See ACSE on your cloud.

Tell us what you run and what your auditors ask for. We’ll show you the loop end to end: a real finding, a fix as code, an approval with MFA and the sealed record.