Login Get a Demo
01 Integration · Amazon Bedrock

Build on Bedrock. Prove it’s safe.

Your teams are shipping on Amazon Bedrock faster than anyone can review it. Cranium ONE finds every Bedrock model in your code, inspects every prompt and response, and hands you the evidence that it’s under control.

02 Across the AI Trust Loop

What Cranium ONE does with Amazon Bedrock.

01Discover02Observe03Govern04Secure05Prove↻ Continuously
Discover

Find Bedrock in your code

CodeSensor builds an AI Bill of Materials for every repository — models, datasets, technologies and infrastructure — including Bedrock Runtime calls made from .NET. AgentSensor maps agents built with Amazon Strands: their models, tools, handoffs and MCP servers.

Observe

See every prompt and response

Guardian inspects the traffic between your application and the Bedrock model. In Listen mode it evaluates a copy in parallel, so you get sessions, events and every signal triggered without touching the request path.

Govern

Write the policy per use case

Profiles decide which signals matter — PII, PHI and PCI, secrets, jailbreaks, instruction override, prompt leaking — and what happens to each: block, modify or pass.

Secure

Enforce it in line

Switch a profile to Enforce and Guardian sits between your app and Bedrock, acting on prompts and responses before they land. Prove the profile first with Cannon, which runs whole prompt collections through it in one run.

Prove

Show your work

Trace explains every verdict from deterministic, purpose-built classifiers, and AI Cards turn the record into evidence mapped to the EU AI Act, NIST AI RMF and ISO 42001.

03 Connect

Three steps. No rip-and-replace.

Cranium ONE works with the stack you already run. Your policy stays yours — we make it enforceable.

  1. 01
    Add the model

    In Guardian, add a Bedrock model with its vendor model ID and the IAM Role ARN Cranium should assume.

  2. 02
    Start in Listen

    Point your application through Guardian. Listen mode evaluates traffic in parallel and changes nothing.

  3. 03
    Tune, then Enforce

    Tune the profile, test it with Cannon, then switch to Enforce when the verdicts look right.

04 Questions

Cranium ONE & Amazon Bedrock, answered.

How does Cranium ONE connect to Amazon Bedrock?

You add a Bedrock model in Guardian with its vendor model ID and an IAM Role ARN. Cranium uses that role to reach the model, so there are no long-lived access keys to store.

Does Cranium sit in the path of my Bedrock traffic?

Only if you choose. In Listen mode Guardian evaluates a copy of the traffic in parallel and changes nothing. In Enforce mode it runs in line between your application and the model, and can block, modify or pass each prompt and response.

Can Cranium find Bedrock usage we did not know about?

CodeSensor scans your GitHub, GitLab, Bitbucket and Azure DevOps repositories and records the models each one calls in an AI Bill of Materials, including Bedrock Runtime calls from .NET code. AgentSensor maps agents built with Amazon Strands. Scans can run weekly, monthly or on every push.

What does Guardian check Bedrock prompts and responses for?

The signals your profile enables, including PII, PHI and PCI, secrets, jailbreaking, instruction override, prompt leaking, role impersonation and toxicity. Every verdict comes from deterministic, purpose-built classifiers and is explained in Trace.