Setup GuideDatadogIntegrationMonitoringSIEMSetup

How to Connect Datadog to SecureSpect

Connect your Datadog account to automate security monitoring evidence collection — log management, anomaly detection, and alert policy checks.

SecureSpect Team··6 min read

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:

  • Go to Organization Settings → API Keys → New Key.
  • Name it securespect-read and copy the key.
  • Application Key:

  • Go to Organization Settings → Application Keys → New Key.
  • Name it securespect-read and copy the key.
  • Under Scopes, grant only Read scopes — deselect any write or management permissions.
  • Minimum Application Key scopes:

    • monitors_read
    • logs_read_config
    • slos_read
    • audit_logs_read

    Step 2 — Connect in SecureSpect

  • Navigate to Integrations → Datadog → Connect.
  • Select your Datadog site (US1, US3, EU1, etc.).
  • Enter your API Key and Application Key.
  • Click Verify & Save.
  • 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

    FindingRemediation
    |---|---|
    Log retention < 365 daysUpdate index retention in Datadog → Logs → Configuration
    No anomaly detection monitors activeCreate a monitor with the Anomaly algorithm
    Audit trail not enabledEnable in Org Settings → Security → Audit Trail
    SLOs not definedCreate SLOs for availability-critical services

    Automate your SOC 2 evidence collection

    Connect your AWS and GitHub environments and start collecting audit-ready evidence today. Free to start.

    Start Free →More Articles