How to Connect Datadog to SecureSpect
Connect your Datadog account to automate security monitoring evidence collection — log management, anomaly detection, and alert policy checks.
Ready to connect? Follow the steps in SecureSpect — the integration dialog walks you through the same process described here.
Open Integrations →Overview
SecureSpect connects to Datadog using a read-only API key and Application key pair. The integration collects evidence around your security monitoring posture: log retention, anomaly detection monitors, alert policies, and SLO definitions — all mapped to SOC 2 CC7 (System Operations) controls.
What Gets Monitored
- Log management — Log index retention settings, archive configurations
- Monitors — Security monitors active, anomaly detection configured
- SLOs — SLO definitions and current error budget status
- Audit trail — Audit log collection enabled
- Integrations — AWS, GitHub, and other connected sources
Step 1 — Create Read-Only Credentials
Datadog requires both an API key and an Application key for API access.
API Key:
securespect-read and copy the key.Application Key:
securespect-read and copy the key.Minimum Application Key scopes:
monitors_readlogs_read_configslos_readaudit_logs_read
Step 2 — Connect in SecureSpect
The first scan completes within 10 minutes.
Step 3 — Map Monitors to SOC 2 Controls
SecureSpect automatically maps Datadog monitors tagged with soc2:true to the relevant control criteria. Add this tag to your critical security monitors in Datadog:
# Tag an existing monitor via Datadog CLI
datadog monitor update 12345678 --tags "soc2:true,env:production"
Common Findings After First Scan
| Finding | Remediation |
| Log retention < 365 days | Update index retention in Datadog → Logs → Configuration |
| No anomaly detection monitors active | Create a monitor with the Anomaly algorithm |
| Audit trail not enabled | Enable in Org Settings → Security → Audit Trail |
| SLOs not defined | Create SLOs for availability-critical services |