Combined audit case-file pack
All eight finding workpapers in one reviewer pack. Open it without leaving the dashboard.
Audit evidence, engineered.
An IAM control-testing workbench that turns identity data into traceable findings, reviewer workpapers, and audit-ready evidence.
01 · System
Audit automation with a visible chain of evidence.
The workbench automates the data-testable portion of IAM / ITGC testing while keeping control logic, evidence, severity, and reviewer judgment separate and inspectable.
What happens in one run
Synthetic enterprise evidence is generated, normalized, tested, documented, and released as reviewer-facing artifacts.
01 · EvidenceHR, identities, MFA, roles, entitlements, reviews.
02 · ControlsEight independent tests evaluate IAM / ITGC conditions.
03 · FindingsExceptions become structured audit findings with severity.
04 · WorkpapersEvidence is retained, hashed, and published to PDF case files.
Why the output is reviewer-ready
RepeatabilitySeeded source data and regression tests
TraceabilitySource evidence → finding → hash → workpaper
ExplainabilityCriteria · Condition · Cause · Risk · Recommendation
BoundaryAutomation supports — never replaces — professional judgment
HR feedterminations / JML
+
Identity directoryusers / MFA / roles
+
Entitlementsroles / approvals
→
Normalized evidence
→
Control engine8 tests
Audit trail
←
Finding + severityrule-derived
→
Evidence hash
→
Reports + PDFs
→
Reviewer dashboard
02 · Control results
Eight controls. Every exception inspectable.
Search or filter the generated findings. Open any row to inspect its audit logic, retained evidence, hash, and individual workpaper.
FindingControl / riskSeverityExceptions
03 · Reviewer artifacts
Open the evidence. Stay in the review.
Open any finding, report, or workpaper without losing your place.
Management audit report
The generated executive report is rendered as a readable document in the same interface — not a raw Markdown dead end.
Audit workpaper field guide
Explains how to read criteria, condition, cause, risk, evidence, evidence hashes, and scope.
Individual finding workpapers
8 workpapersEach file is connected to the finding generated by the control engine.
04 · Quality assurance
Tested before release.
Engine tests and artifact checks run before release.
01
Detection tests
Injected control failures must be found by the expected tests.
02
False-positive guard
Clean scenarios are tested so the engine does not only prove it can fail.
03
Artifact validation
Every workpaper path is checked and every PDF must be parseable before release.
04
Explicit boundary
Walkthroughs, design assessment, compensating controls, management inquiry, and professional judgment remain human work.