| 2.1.5 Disaster Recovery (DR) Plan | CIS Oracle MySQL Community Server 8.4 v1.0.0 L1 OS Linux on Linux | Unix | CONTINGENCY PLANNING |
| 2.1.5 Disaster Recovery (DR) Plan | CIS MySQL 8.0 Community Linux OS L1 v1.1.0 | Unix | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS MySQL 5.7 Enterprise Windows OS L1 v2.0.0 | Windows | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS MySQL 5.6 Community Windows OS L1 v2.0.0 | Windows | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS MySQL 5.7 Community Windows OS L1 v2.0.0 | Windows | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS MySQL 5.6 Community Database L1 v2.0.0 | MySQLDB | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS MySQL 5.7 Enterprise Linux OS L1 v2.0.0 | Unix | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS Oracle MySQL Enterprise Edition 8.4 v1.0.0 L1 MySQL OS Linux | Unix | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS MariaDB 10.6 Database L1 v1.1.0 | MySQLDB | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS MySQL 5.6 Community Linux OS L1 v2.0.0 | Unix | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS MySQL 5.7 Community Linux OS L1 v2.0.0 | Unix | CONTINGENCY PLANNING |
| 2.1.6 Disaster Recovery (DR) Plan | CIS MySQL 8.0 Enterprise Linux OS L1 v1.4.0 | Unix | CONTINGENCY PLANNING |
| 2.1.6 Disaster recovery plan | CIS MySQL 5.6 Enterprise Windows OS L1 v2.0.0 | Windows | CONTINGENCY PLANNING |
| 2.1.6 Disaster recovery plan | CIS MySQL 5.6 Enterprise Linux OS L1 v2.0.0 | Unix | CONTINGENCY PLANNING |
| 2.1.6 Disaster recovery plan | CIS MySQL 5.6 Enterprise Database L1 v2.0.0 | MySQLDB | CONTINGENCY PLANNING |
| 4.3 Ensure that the DATA_RETENTION_TIME_IN_DAYS parameter is set to 90 for critical data | CIS Snowflake Foundations v1.0.0 L2 | Snowflake | CONTINGENCY PLANNING |
| 9.3.5 Ensure the Key Vault is Recoverable | CIS Microsoft Azure Foundations v4.0.0 L1 | microsoft_azure | CONTINGENCY PLANNING |
| 10.1.1 Ensure soft delete for Azure File Shares is Enabled | CIS Microsoft Azure Foundations v4.0.0 L1 | microsoft_azure | CONTINGENCY PLANNING |
| 10.2.1 Ensure that soft delete for blobs on Azure Blob Storage storage accounts is Enabled | CIS Microsoft Azure Foundations v4.0.0 L1 | microsoft_azure | CONTINGENCY PLANNING |
| 10.2.2 Ensure 'Versioning' is set to 'Enabled' on Azure Blob Storage storage accounts | CIS Microsoft Azure Foundations v4.0.0 L2 | microsoft_azure | CONTINGENCY PLANNING |
| 10.3.6 Ensure Soft Delete is Enabled for Azure Containers and Blob Storage | CIS Microsoft Azure Foundations v4.0.0 L1 | microsoft_azure | CONTINGENCY PLANNING |
| 10.3.12 Ensure Redundancy is set to 'geo-redundant storage (GRS)' on critical Azure Storage Accounts | CIS Microsoft Azure Foundations v4.0.0 L2 | microsoft_azure | CONTINGENCY PLANNING |
| MS.DEFENDER.4.5v1 - A list of apps that are restricted from accessing files protected by DLP policy SHOULD be defined. | CISA SCuBA Microsoft 365 Defender v1.5.0 | microsoft_azure | ACCESS CONTROL, SECURITY ASSESSMENT AND AUTHORIZATION, CONFIGURATION MANAGEMENT, CONTINGENCY PLANNING, IDENTIFICATION AND AUTHENTICATION, RISK ASSESSMENT, SYSTEM AND COMMUNICATIONS PROTECTION, SYSTEM AND INFORMATION INTEGRITY |
| MS.DEFENDER.4.6v1 - The custom policy SHOULD include an action to block access to sensitive | CISA SCuBA Microsoft 365 Defender v1.5.0 | microsoft_azure | ACCESS CONTROL, SECURITY ASSESSMENT AND AUTHORIZATION, CONFIGURATION MANAGEMENT, CONTINGENCY PLANNING, IDENTIFICATION AND AUTHENTICATION, RISK ASSESSMENT, SYSTEM AND COMMUNICATIONS PROTECTION, SYSTEM AND INFORMATION INTEGRITY |
