Logging & audit security checks across 10 apps

Audit logs, event retention and incident-response hooks — the evidence you need when something goes wrong, and the controls auditors ask for first.

Why it matters

Without audit logs retained long enough there is no incident investigation and no evidence to hand an auditor. NIS2 and DORA make logging, event retention and incident-response hooks explicit obligations rather than good practice.

Browse by app

• Azure 13 checks
• incident.io 11 checks
• Google Cloud 9 checks
• Microsoft 365 8 checks
• PagerDuty 7 checks
• AWS 6 checks
• Teleport 6 checks
• Anthropic 4 checks
• Datadog 3 checks
• Figma 3 checks

Highest-severity checks

The 8 most severe Logging & audit checks across all 10 apps — each links to the connector page where the setting, its remediation and its framework mapping are documented.

1. CloudTrail Not Logging — AWS severity: critical
2. Role Disables Session Recording — Teleport severity: critical
3. Service Without Escalation Policy — PagerDuty severity: critical
4. Session Recording Disabled — Teleport severity: critical
5. Alert Route No Escalation Path — incident.io severity: high
6. App Service Logging Disabled — Azure severity: high
7. Audit Logging Disabled — Datadog severity: high
8. Audit Logging Not Enabled — Google Cloud severity: high

Where to start

Connect Azure first — it carries the most Logging & audit checks in the catalog(setup guide, read-only access). A first scan takes about 15 minutes and reports every failing check on this page with its remediation steps.

All topics · Browse by app