Bedrock guardrails use sensitive information filters to block or mask detected PII and custom pattern matches in prompts and responses.
The evaluation looks for guardrails with this filtering configured.
Risk
Absent filtering, prompts or outputs can reveal PII, credentials, or financial records, compromising confidentiality.
- Exposed tokens enable unauthorized access and data tampering (integrity)
- Disclosed customer details facilitate fraud and identity theft, with potential lateral movement
Run this check with Prowler CLI
prowler aws --checks bedrock_guardrail_sensitive_information_filter_enabled
Recommendation
Enable and tune sensitive information filters for inputs and outputs.
- Use
BLOCKfor high-risk disclosures;ANONYMIZEwhen context is needed - Add custom regex for org-specific IDs
- Apply least privilege and data minimization
- Test regularly and monitor outcomes as part of defense-in-depth
Remediation
CLI
aws bedrock update-guardrail --guardrail-identifier <example_resource_id> --sensitive-information-policy-config '{"piiEntitiesConfig":[{"type":"EMAIL","action":"ANONYMIZE"}]}'
Other
- Sign in to the AWS Console and open Amazon Bedrock
- Go to Guardrails and select <example_resource_name>
- Click Edit (or Open draft) and open Sensitive information filters
- Add PII type EMAIL and set action to Mask (or Block)
- Click Save
Source Code
Resource Type
Other