Register:Home5 recordsSHA3-256 chainedhead sha3:cbf599890df7f785e51b70e504388048339d3af0fd139bcbfc4a58935d55df10Intact
REC 0000Genesissha3-2560fc30583a81c7633954b81a7bca012f7014a3fc3e69483c8afa16a4b61be9024prev:a32090232926

An evidence locker for systems that act without you.

PolicyCortex records what your cloud was, what changed it, and what your machines were allowed to do. Inside your tenant. Hash chained. Gaps declared, not hidden.

Verify in your tenant

Chain headsha3:0fc30583a81cintact

01Inside your tenant02Hash chained03Gaps declared04Independently verifiable
REC 0001The three layerssha3-2566f9a7308aaf8d8630c766716ad5988914a90f4856761ab994a783fcabd7561a6prev:0fc30583a81c
REC 0002The filtersha3-2569075a62557bac05860b2d09c60fc045eb08538042d32aa5ade65e9077c5b7845prev:6f9a7308aaf8

Five questions the evidence must answer.

  1. Q-01

    Your assessor asks for the configuration as of a date three months back. Can you produce it, or can you only produce today?

    Your answerGap declared · no answer on file

  2. Q-02

    An agent took an action overnight. Can you show the policy decision that permitted it, or only the record that it happened?

    Your answerGap declared · no answer on file

  3. Q-03

    Your collector was down for six hours. Does your evidence say so, or does it just have fewer rows?

    Your answerGap declared · no answer on file

  4. Q-04

    Someone with administrator rights can edit your audit table. What in your architecture makes that detectable?

    Your answerGap declared · no answer on file

  5. Q-05

    You are asked whether an AI system in your environment is in scope. Who answers, and from what data?

    Your answerGap declared · no answer on file

REC 0003The boundarysha3-2560dc7038ed6dec27c629ab9f3e5345bec63335adf3498449f3cc6bacfa40d1c2dprev:9075a62557ba

It runs where your data already is.

PolicyCortex evaluates policy, collects evidence and gates autonomous action inside your tenant. Nothing about your environment leaves it for us to work. There is no telemetry pipeline pointed at our servers, because a company whose product is proof should not be asking you to trust an outbound connection.

Live readout: policy, evidence, and gating stay inside the wall. Illustrative records; the shape is real.

REC 0004The honest notesha3-256cbf599890df7f785e51b70e504388048339d3af0fd139bcbfc4a58935d55df10prev:0dc7038ed6de

We are not for everyone.

If you need a checklist and a score, there are good products for that and we will point you at them. If you are accountable for what an autonomous system does in a regulated environment, and you have already worked out that logs and evidence are different words, request verification access.

Register colophonRecomputable by a second party
SeqLabelSHA3-256Prev
REC 0000Genesis0fc30583a81ca32090232926
REC 0001The three layers6f9a7308aaf80fc30583a81c
REC 0002The filter9075a62557ba6f9a7308aaf8
REC 0003The boundary0dc7038ed6de9075a62557ba
REC 0004The honest notecbf599890df70dc7038ed6de

The record headers on this page are SHA3-256 digests of this page's own copy, chained in sequence from a fixed genesis value. Edit one word anywhere above and every digest after it changes. Head of chain: sha3:cbf599890df7. The product does the same thing to your evidence.