Monitor workflow

Why monitor after assess#

An initial scan gives a baseline. Monitor keeps that baseline alive by running scheduled assessments and raising alerts when crypto inventory or policy posture changes.

1) Manage schedules#

• Create schedule: POST /tenant/schedules
• List active schedules: GET /tenant/schedules
• Inspect run history: GET /tenant/schedules/{schedule_id}/runs
• Pause or tune cadence: PATCH /tenant/schedules/{schedule_id}

2) Track drift and anomalies#

Use the public drift index for external attestation views and tenant analytics for internal operations. Combine GET /pqc/index/drift with GET /tenant/drift-intel to separate ecosystem-level movement from tenant-specific regressions.

3) Route alerts and notifications#

Register destinations with POST /tenant/webhooks, test delivery, then monitor dead-letter entries through GET /tenant/webhooks/dlq. Re-send failed deliveries with POST /tenant/webhooks/replay.

4) Close the loop#

Feed high-severity drift into remediation by linking schedule runs to POST /tenant/scans/{scan_id}/remediation/automate, then run POST /tenant/scans/{scan_id}/remediation/verify to prove the control is restored.