Review generated findings and identify compliance gaps.
What this page shows: Findings are gaps or follow-up items from assessment answers and available evidence. Findings help decide what to fix, what evidence is needed, and what should appear in the report pack. Live connector findings remain parked until approved.
Import offline metadata via the Evidence Package page to begin local mapping.
Start an assessment to generate candidate findings. No remediation required at this time.
Row-level security and tenant isolation verification.
Validation of production environment keys.
Failsafes against unintended persistence.
Logging and audit trails active.
Safe dry-run notification paths.
Mocked subscription checks.
Disaster recovery runbooks.
End-to-end basic operation.
Redaction of tokens, OAuth, emails, keys.
Local readiness only: This panel surfaces local offline proofs. Missing credentials/session/MFA act as a controlled blocker, not a crash. Raw secrets, OAuth URLs, real emails, and billing keys are never rendered.
Human Prerequisites Missing:
Provide these credentials and boundary conditions via the secure operator path. Do not paste secrets into chat or UI.
Run a local audit to gather evidence.
Preview/guided findings should be reviewed before being treated as final.
Review the list below. Assign owners or due dates to move them forward.
Total tracked
0
Open
0
Closed
0
Critical/high open
0
Closure rate
0%
Status breakdown
Evidence is tracked as metadata and references. File upload, storage buckets, connector verification, and AI evidence analysis are not enabled in this release.
Next actions
| Finding | Severity | Status | Owner | Due | Remediation note |
|---|