ASSOCIATED DRATA CONTROL
This test is part of the Databases Monitored and Alarmed control that ensures your company has implemented tools to monitor databases and notify appropriate personnel of any events or incidents, based on predetermined criteria.
WHAT TO DO IF A TEST FAILS
If Drata detects that database CPU monitoring is not enabled or that alerts have not been properly set up the test will fail. With a failed test you will receive a list of databases that lack CPU monitoring or administrative alerts.
To remediate a failed test, you will need to set up and configure monitoring for database CPUs to ensure they are monitored with alerts being sent to DB admins in an event or incident.
STEPS FOR PASSING
To ensure a validated state when testing for monitoring of the database CPU, please follow the steps listed in the table below. Once the provider steps have been completed, navigate back to Drata and execute the test.
NOTE: If you are using the Datadog integration for this test, please see this help article for the metrics to be used.
Provider / Technology | Provider Steps |
AWS - DocDB | Database Creation
Alarm Creation
Subscription Confirmation The subscription to the SNS topic used (or newly created) above must be confirmed for the test to pass.
Alternatively:
Note: You may also need to perform this check within Cluster Metrics on DocDB. Ensure that the conditions for DocDB cluster are Static -> Greater -> than 10 (units are in percentages) |
AWS - RDS | Database Creation
Alarm Creation - Database Instance
Alarm Creation - Database Cluster
Subscription Confirmation The subscription to the SNS topic used (or newly created) above must be confirmed for the test to pass.
Alternatively:
|
Azure - MariaDB, MySQL, PostgresSQL |
|
Azure - SQL |
|
Azure - SQL Managed Instance |
|
GCP - SQL | Database Creation
Alert Creation
|