feat(aws): add rolesanywhere service and pqc trust anchor check#11319
Open
pedrooot wants to merge 1 commit into
Open
Conversation
099647f to
82a62d9
Compare
0812fda to
47fc913
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
IAM Roles Anywhere trust anchors are the root of trust for workloads that authenticate to AWS with X.509 certificates. A weak (RSA/ECC) signing CA could let a quantum-capable attacker forge certificates and gain unauthorized access. AWS now supports ML-DSA (NIST FIPS 204) trust anchors, and Prowler had no IAM Roles Anywhere service.
Description
Introduces the IAM Roles Anywhere (
rolesanywhere) service and therolesanywhere_trust_anchor_pqc_pkicheck. For trust anchors whose source isAWS_ACM_PCA, the linked Private CA'sKeyAlgorithmis checked against a configurable allowlist (rolesanywhere_pqc_pca_key_algorithms, defaults:ML_DSA_44,ML_DSA_65,ML_DSA_87). Trust anchors backed by an externalCERTIFICATE_BUNDLEare reported as fail with remediation guidance, since their signature algorithm cannot be inspected from the IAM Roles Anywhere API alone. Severity: low.Important
Depends on #11318 (
acmpcaservice). The check importsacmpca_clientto resolve the backing CA's key algorithm, so this PR is stacked onfeat/acmpca-certificate-authority-pqc-key-algorithmand should be merged after #11318. GitHub will retarget this PR's base tomasterautomatically once #11318 is merged.Steps to review
prowler/providers/aws/services/rolesanywhere/(rolesanywhere_service.py,rolesanywhere_client.py)prowler/providers/aws/services/rolesanywhere/rolesanywhere_trust_anchor_pqc_pki/poetry run pytest tests/providers/aws/services/rolesanywhere/ -vprowler aws --check rolesanywhere_trust_anchor_pqc_pkiChecklist
Community Checklist
SDK/CLI
rolesanywhere:ListTrustAnchorsto bothpermissions/prowler-additions-policy.jsonand the CloudFormation scan-role template.License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.