Structured path for security, identity, and platform teams evaluating Sentyn or any NHI program. Stop immediately if a raw secret appears in UI, exports, or logs.
01 · Scope
- List AWS accounts, GitHub orgs, and Kubernetes clusters in scope for read-only discovery
- Confirm audit timeline and required evidence format (SOC2, ISO, customer questionnaire)
- Identify current owner coverage metric baseline, even if it is a spreadsheet today
02 · Connect
- Review connector permission manifests before any credential is accepted
- Validate read-only API calls against least-privilege documentation
- Confirm credentials are envelope-encrypted and never echoed after write
03 · Discover
- Run first sync and verify inventory count matches expectations within an order of magnitude
- Spot-check ten identities for external ID, connector source, and owner status field
- Confirm no raw secret values in database, API responses, or browser network tab
04 · Govern
- Triage unknown owner queue and assign at least one identity with evidence
- Verify conflicting owner signals remain visible, not silently merged
- Check owner coverage percentage updates on dashboard after assignment
05 · Respond
- Open one critical finding with blast radius evidence panel
- Walk findings state machine: new, triaged, acknowledged, or suppressed with reason
- Preview remediation scope without provider write execution
06 · Prove
- Export inventory, findings, and append-only audit sample in same session
- Confirm exports contain fingerprints and metadata only, never plaintext secrets
- Document fail criteria if cross-tenant data appears in negative tests