Register:Home5 recordsSHA3-256 chainedhead sha3:30c092bbc9b638106e4ca19858aa661d070e75c369dbdf8f80577a592b818265Intact
REC 0000Genesissha3-256268f6dae680fb58face3879d5394d31f254c67a6753360597715cd7282a97edcprev:a32090232926

Compliance evidence for cloud and AI systems, kept in your tenant.

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:268f6dae680fintact

Read only. Fourteen days. No sales call.

01Inside your tenant02Hash chained03Gaps declared04Independently verifiable

Built for

  • ATO and continuous authorization
  • CMMC Level 2
  • FedRAMP 20x
  • NIST 800-53 and 800-171
  • OMB M-25-21 AI inventories
REC 0001The three layerssha3-256914cc15ce3a33d4538ec65c56326a949f7d393986baa277ad57b5897a2f35cbfprev:268f6dae680f
REC 0002The filtersha3-256d96de3e6b1b98110f39ad8652c3eec68c91ddfbf9b9aa390be47b3211e700f0cprev:914cc15ce3a3

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-25636f8c0d01f1a7d3308eca088bba887533a2ec1ef0591f5ffa0f1affc210695a9prev:d96de3e6b1b9

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-25630c092bbc9b638106e4ca19858aa661d070e75c369dbdf8f80577a592b818265prev:36f8c0d01f1a

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 0000Genesis268f6dae680fa32090232926
REC 0001The three layers914cc15ce3a3268f6dae680f
REC 0002The filterd96de3e6b1b9914cc15ce3a3
REC 0003The boundary36f8c0d01f1ad96de3e6b1b9
REC 0004The honest note30c092bbc9b636f8c0d01f1a

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:30c092bbc9b6. The product does the same thing to your evidence.