compliance.tf

Azure subscriptions should have at least one Application Insights resource configured

Azure subscription contains at least one Application Insights resource collecting application telemetry (metrics, traces, logs) for monitored workloads. The check determines whether telemetry collection exists at the subscription level.

What this control checks

Subscription has at least one Application Insights resource collecting application telemetry.

Framework mappings

The clauses this control is mapped to in each framework.

PCI DSS v4.0

  • 5.3.4: Anti-malware mechanisms and processes are active, maintained, and monitored.
  • 10.2.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
  • 10.2.1.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
  • 10.2.1.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
  • 10.2.1.3: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
14 more clauses
  • 10.2.1.4: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
  • 10.2.1.5: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
  • 10.2.1.6: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
  • 10.2.1.7: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
  • 10.2.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
  • 10.4.1: Audit logs are reviewed to identify anomalies or suspicious activity.
  • 10.4.1.1: Audit logs are reviewed to identify anomalies or suspicious activity.
  • 10.4.2: Audit logs are reviewed to identify anomalies or suspicious activity.
  • 10.6.3: Time-synchronization mechanisms support consistent time settings across all systems.
  • 10.7.1: Failures of critical security control systems are detected, reported, and responded to promptly.
  • 10.7.2: Failures of critical security control systems are detected, reported, and responded to promptly.
  • A1.2.1: Multi-tenant service providers facilitate logging and incident response for all customers.
  • A3.3.1: PCI DSS is incorporated into business-as-usual (BAU) activities.
  • A3.5.1: Suspicious events are identified and responded to.

NIS2 Directive (EU 2022/2555)

  • 3 Incident handling
  • 5 Supply chain security

CIS Azure Benchmark v4.0.0

  • 7.1.3.1 Ensure Application Insights are Configured

CIS Azure Benchmark v5.0.0

  • 6.1.3.1 Ensure Application Insights are Configured

CIS Azure Benchmark v2.0.0

  • 5.3.1 Ensure Application Insights are Configured

CIS Azure Benchmark v2.1.0

  • 5.3.1 Ensure Application Insights are Configured

CIS Azure Benchmark v3.0.0

  • 6.3.1 Ensure Application Insights are Configured

HIPAA Security Rule 2003

  • 164.308(a)(1)(ii)(D): Administrative Safeguards
  • 164.312(b) Audit controls

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

  • Compliance.tf Control: azure_appinsights_ensure_is_configured
  • Prowler Check: appinsights_ensure_is_configured

Last reviewed: 2026-10-11

View all Azure controls →

On this page

Ask AI about this

Help improve this page