What is the reason for the RQL filter of the RDS Multi-AZ disabled Policy?

KRyu — Wed, 02 Sep 2020 17:47:28 GMT

Policy Name : AWS RDS instance with Multi-Availability Zone disabled.

Policy Mode : Prisma Cloud Default

RQL : config where cloud.type = 'aws' AND api.name = 'aws-rds-describe-db-instances' AND json.rule = '(engine does not contain aurora and engine does not contain sqlserver and engine does not contain docdb) and (multiAZ is false or multiAZ does not exist)'

Why exclude the aurora, sqlserver, and docdb engines?

Re: What is the reason for the RQL filter of the RDS Multi-AZ disabled Policy?

BCastillo — Wed, 14 Sep 2022 14:51:10 GMT

Before RQL fix:

config where cloud.type = 'aws' AND api.name = 'aws-rds-describe-db-instances' AND json.rule = 'multiAZ is false or multiAZ does not exist'

At one point it incorrectly was alerting on an Aurora DB, regardless of the multi-AZ configuration. The issue is that it was looking for the JSON item multiAZ is false or multiAZ does not exist, but for an Aurora DB, the JSON always returns the multi-AZ configuration as false (even if it is configured properly in a multi-az operation).

To avoid false positives, RQL is updated to ignore Microsoft sql and aurora database and look for Multi-AZ for other databases.

Multi AZ deployments for Oracle, PostgreSQL, MySQL, and MariaDB DB instances use Amazon's failover technology.
SQL Server DB instances use SQL Server Database Mirroring (DBM).

Regards,

topic What is the reason for the RQL filter of the RDS Multi-AZ disabled Policy? in Prisma Cloud Discussions

What is the reason for the RQL filter of the RDS Multi-AZ disabled Policy?

Re: What is the reason for the RQL filter of the RDS Multi-AZ disabled Policy?