After you complete initial setup, imper.ai should be operated as a living security control. This article outlines a practical day-to-day and week-to-week operating cadence to keep your deployment effective.
In this article
Daily checks
Confirm key integrations remain connected and operational
Spot-check verification activity for unusual spikes or unexpected failures
Escalate suspicious outcomes based on internal security process
Weekly checks
Review the Audit Log for unexpected admin changes or unusual access patterns
Confirm protected user scope still reflects current organizational risk
Review operator feedback for workflow friction, false positives, or process gaps
When to review configuration
Revisit configuration when any of the following occur:
Changes to identity provider policy (SSO changes, group changes, permission updates)
Communication platform changes (new meeting policies, app permission changes, tenant restrictions)
New high-risk populations emerge (new executives, M&A activity, re-org, expanded privileged access)
Unexpected changes in verification outcomes (increase in failures, unexplained risk signals)
Operational best practices
Start with the highest-risk workflow, validate it, then expand coverage gradually
Keep ownership clear: admins configure, operators execute, auditors review
Maintain a simple internal escalation rule for failed or suspicious verifications
Validate again after any major integration or policy change
Note: If you have not yet validated your environment, start with Validating Your Setup before establishing an ongoing operating cadence.