TruckStop

Your policy audit report.

This is how your audit report will look for the policies you selected.

Sample data Example selection: SOX change-control recipe, Production safety, Developer safety and Secrets protection — 6 rules · 4 Runtime · 2 Post-run audit
6Rules in this selection
1,284Checks run
37Findings
7Insufficient evidence

Findings over time

37 illustrative findings across four weeks.

Week 1Week 2Week 3Week 4

Findings by rule

25 runtime decisions · 12 post-run findings.

Release branch protection10
Change-control evidence8
Production configuration files7
Credential file access5
Credentials in code changes4
Deployment approval3

Checked during workReviewed afterward

Runtime

What the checks decided while an agent worked.

Checks run
1,284
Denials issued
14
Recorded, not stopped
11
Confirmed prevention
not measured
Post-run

What a review of finished work reported. An audit prevents nothing.

Audit runs
48
Findings
12
No findings in this scope
29
Insufficient evidence
7

Recent findings

RuleCheckedWhat the check sawOutcome
Change-control evidencePost-runa release-related change carried no passing test or security evidence tied to that revisionPotential control exception · a missing receipt, not a regulatory determination
Credentials in code changesPost-runa credential-shaped string was added in the reviewed changeExposure risk detected · recorded afterward, nothing was prevented
Release branch protectionRuntimea push targeted a restricted release branchDenial issued · host outcome unknown
Production configuration filesRuntimean edit targeted a protected configuration fileRecorded, not stopped
Change-control evidencePost-runthe verification receipt for this change could not be readInsufficient evidence · neither a pass nor a failure

Each label above is a starter rule in the library, shown by what it protects. Release branch protection is No agent push to a protected branch. Production configuration files is Protected paths. Credential file access is Keep agents out of credential files. Deployment approval is Require approval before deploying to production. Change-control evidence is Require verification evidence tied to the release being approved. Credentials in code changes is Flag newly added credentials in code or configuration.

Sample data. Runtime decisions and post-run findings are shown separately.