Azure Compliance ControlsAzure Database for MySQL
MySQL flexible servers should have 'audit_log_events' configured to include 'CONNECTION'
Checks that the Azure Database for MySQL Flexible Server audit configuration includes the `CONNECTION` event in the `audit_log_events` setting. Without that event included, login attempts are not captured by the audit configuration.
What this control checks
MySQL flexible server audit_log_events includes CONNECTION
Framework mappings
The clauses this control is mapped to in each framework.
- CC7.2: The entity monitors system components and the operation of those components for anomalies that are indicative of malicious acts, natural disasters, and errors affecting the entity's ability to meet its objectives; anomalies are analyzed to determine whether they represent security events.
- CC7.3 The entity evaluates security events to determine whether they could or have resulted in a failure of the entity to meet its objectives (security incidents) and, if so, takes actions to prevent or address such failures
- A.8.15 Logging
- 2 Risk management policy
- 3 Incident handling
- 11 Access control
- AM-01.01AC The information collected about assets is considered in logging and monitoring applications to identify the impact on cloud services and functions in case of events that could lead to a breach of protection objectives, and to support information provided to affected cloud service...
- DEV-08.02B The configuration of these system components ensures that all changes to system components in the production environment are recorded and can be traced back to the individuals or system components contributing to their development, deployment or implementation.
- OPS-11.02AC Cloud service derived data, including log data, is taken into consideration in regulatory compliance assessments.
- OPS-15.01AC On request of the cloud service customer, the cloud service provider provides the logs relating to the cloud service customer in an appropriate form and in a timely manner so that the cloud service customer can investigate any incidents relating to them.
- OPS-15.01B The log data generated (cloud service derived data and cloud service provider data) allows an unambiguous identification of user accesses at tenant level to support (forensic) analysis in the event of an incident.
6 more clauses
- OPS-15.02B Each logged event shall include a time/date stamp to ensure accurate and traceable records.
- OPS-15.03B The cloud service provider is able to support forensic analysis of incidents and to retain a chain of evidence. This implies that the cloud service provider capture the state of infrastructure components and network communication during security events.
- OPS-26.05B The cloud service provider implements monitoring measures to ensure system components comply with hardening specifications.
- PSS-04.01B The cloud service provided is equipped with error handling and logging mechanisms for system components under the responsibility of the cloud service customer. These enable cloud users to obtain security-related information about the security status of the cloud service as well as the...
- SIM-03.06B All documents and evidence that provide details on security incidents related to the cloud service are archived in a way that could be used as evidence in court. Security mechanisms and processes for protecting all the information about security incidents related to the cloud service...
- SIM-03.07B The analysis process also ensures traceability of the entire kill chain of a security incident.
- 4.4.4 Ensure server parameter 'audit_log_events' has 'CONNECTION' set for MySQL Database Server
- 4.4.4 Ensure server parameter 'audit_log_events' has 'CONNECTION' set for MySQL Database Server
- 5.3.4 Ensure server parameter 'audit_log_events' has 'CONNECTION' set for MySQL flexible Server
- 164.312(b) Audit controls
Related controls
- MySQL flexible servers should have 'require_secure_transport' set to 'ON'
- MySQL flexible servers should have 'tls_version' set to 'TLSv1.2' or higher
- MySQL servers should have public network access disabled
- Azure subscriptions should have a 'Diagnostic Setting' configured for Subscription Activity Logs
- PostgreSQL flexible servers should have 'log_checkpoints' set to 'ON'
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
mysql_flexible_server_audit_logging_events_connection_set - Powerpipe Control:
azure_compliance.control.mysql_flexible_server_audit_logging_events_connection_set - Prowler Check:
mysql_flexible_server_audit_log_connection_activated
Last reviewed: 2026-10-13