Bedrock,For applications routed through RedactWall.
Compatible applications you explicitly configure to route through RedactWall send Bedrock requests through the gateway. Requests and responses on that route are checked before forwarding; direct provider traffic remains outside the gateway.
What that looks like
A routed data-team application sends customer records to a Bedrock model
Stopped, and the attempt is on the record.
A Bedrock response returns through RedactWall with an account number
Caught before the application sees it.
A team points an application at a different Bedrock model
The approved policy applies when the compatible application continues to use the RedactWall route.
What it takes to switch on
Configure each compatible application to use the RedactWall gateway endpoint for Bedrock traffic. Only requests and responses that use that route are governed.
How far this is proven
Built to the vendor’s own connection and testedThis connection decides before data leaves. See Disclosures for how far it is proven today.
Every limit, in one place: Disclosures.
Review the proposed first pilot
The proposed first pilot covers ChatGPT text in managed Chrome and a separately verified Anthropic gateway path. Other integrations are part of the broader product.
- Coverage is published for this integration
- Proof status is shown explicitly
- Pilot scope is agreed before onboarding