Updating PC-AWS-IAM-9 policy's RQL #95
Open
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updating PC-AWS-IAM-9 policy's RQL (AWS IAM Password policy is unsecure)
Motivation and Context
Current RQL is only covering a corner case by using logical AND’s meaning the policy only alerts if all options are not compliant. The proposed RQL uses logical OR’s to cover any deviation from the recommended values.
Also the current RQL only alerts if the minimum password length matches exactly 6. The proposed RQL alerts if the minimum password length is less than 14, in line with build policy CKV_AWS_10 “AWS IAM password policy does not have a minimum of 14 characters”
Finally to avoid false positives, I’ve added a condition to ignore the AWS default password policy (isDefaultPolicy = false) which is not compliant but present in every account.
How Has This Been Tested?
The proposed RQL has been tested in production environment with many different passwords policies.
Screenshots (if appropriate)
Types of changes
Checklist