Bedrock Guardrail Missing PII / Sensitive-Information Protection
Nothing filters personal data out of prompts or responses, so sensitive information can be sent to and returned by the model unredacted.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Exposure and fragility, security posture and single points of failure.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Add sensitive-information protection to the guardrail.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Bedrock Guardrails on AWS
- The fix, by hand
- Open the guardrail in the Bedrock console.
- Add a Sensitive information filter (PII entities and/or regex patterns).
- Set the action to Block or Mask as appropriate.
- Publish a new guardrail version and point consumers at it.
These are the steps the finding carries in the product.
- Category
- Security. Risky configurations: privileged containers, containers running as root, host networking, ingress without TLS.
- Where it appears
- The Risk tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1615- Full reference
Bedrock Guardrail Missing PII / Sensitive-Information Protection
Related checks
See the security findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.