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

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

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

L1 Bithead

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?

1 REPLY 1

L2 Linker

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,

  • 2582 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!