PAGES
← all tools
◆ Data Security & DLP

Bedrock Security

commercial

Summary

Bedrock Security is a commercial data-security platform that unifies data, identity, and AI context to show teams real risk without moving data. It is available as a SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. service and is built for teams interested in data-discovery, AI-data-governance, and DSPMDSPMData security posture management, locating sensitive data and checking how it is protected and who can reach it. It helps teams prioritize risks around their data stores.. The platform sits within the data-security category. It was launched in 2022.

How Bedrock Security helps

Which of my data stores actually hold sensitive information nobody is watching?

scans data across environments in place, without moving or copying it, and classifies what it finds so sensitive stores are surfaced by content rather than by name or location

Which identities can reach data they have no business touching?

correlates identity and access records against the data each account can reach, naming the accounts whose permissions exceed what their role or usage pattern justifies

Where is my sensitive data exposed to AI models or agents I never approved for it?

maps the flow between data stores and the AI tools and pipelines consuming them, flagging sensitive data reachable by models or agents outside the intended boundary

Which of the risks flagged today are the ones that actually matter?

combines data sensitivity, identity exposure, and AI context into a single risk view, ranking findings so the ones combining real access with real sensitivity surface above noise

Has a change in access or AI usage quietly increased risk to a data store I already reviewed?

reassesses stores continuously against current identity and AI context, rather than a point-in-time snapshot, so a shift in exposure since the last review shows up on its own

all 17 features, with the evidence for each →

Languages

Not documented

Features

17 capabilities across 4 capability groups

Built from Bedrock Security's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Bedrock Security covers 4 of the 8 data discovery and protection capabilities we track.

What Bedrock Security offers you

  • Natural-language query3
  • Administrative audit log1
  • Built-in AI assistant1
  • MCP server1
Data loss prevention 3 features Data discovery and protection since 2026
Agent DLP integrations shipped Extends Agent DLP to third-party agent runtimes including NVIDIA OpenShell (via Supervisor Middleware), AWS AgentCore, and LiteLLM, enforcing enterprise data policies at each platform's control point. 2 releases · first seen Sep 2026

Shared capability: Data loss prevention

release

  • Adds Agent DLP to ArgusAI with native hooks for AWS AgentCore and LiteLLM, sitting inline at the agent gateway to inspect every tool call in both directions without acting as a proxy.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history
  • Extends Agent DLP to NVIDIA OpenShell via OpenShell's Supervisor Middleware, evaluating each agent action against enterprise data policies and returning an allow/block decision that OpenShell enforces at the sandbox boundary.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history
Agent DLP runtime enforcement shipped Sits inline at the agent gateway to inspect every tool call in both directions — including MCP tools, command-line invocations, and agent-written code — enforcing data access and regulatory policies by masking, redacting, or blocking sensitive data in real time. 2 releases · first seen Sep 2026

Shared capability: Data loss prevention

release

  • Inspects both outbound agent requests to MCP tools and inbound tool responses, enforcing data access and regulatory policies to mask, redact, or block sensitive data exposure in real time. announced · Sep 2026 · source · release history
  • Applies the same data policies across every tool invocation path an agent may use — MCP tools, command-line invocations, and code the agent writes itself — from a single OpenShell control point. announced · Sep 2026 · source · release history
Observe mode shipped Records policy decisions and agent actions — such as returning customer emails — without enforcing blocks, letting teams validate coverage before enabling enforcement. 2 releases · first seen Sep 2026

Shared capability: Data loss prevention

release

  • Supports an observe mode that logs agent actions — such as a marketing agent returning customer emails — without blocking, for low-risk or monitoring-only enforcement scenarios. announced · Sep 2026 · source · release history
  • Supports an observe-only mode that records policy decisions without enforcing them, letting teams validate coverage before turning on enforcement. announced · Sep 2026 · source · release history
Data access governance 3 features Data discovery and protection since 2026
AI agent posture and blast-radius analysis shipped At design time, maps what data an agent's permissions can reach, what combinations that data forms, and where policy would be violated, giving teams pre-deployment visibility into agent risk. 2 releases · first seen Sep 2026

Shared capability: Data access governance

release

  • Extends ArgusAI posture coverage (data store inventory, identity mapping, natural-language access policies) to runtime enforcement, closing the gap between declared policy and actual agent behavior. announced · Sep 2026 · source · release history
  • At design time, exposes an agent's blast radius — what data its permissions can reach, what combinations that data forms, and where policy would be violated — giving security teams pre-deployment visibility. announced · Sep 2026 · source · release history
Natural Language Policy and Investigation shipped Lets teams express data controls and governance queries in plain English and translates them into enforceable controls or investigative answers — including questions about AI model access to PHI or PII — derived from the Metadata Lake. 2 releases · first seen Sep 2026

Shared capability: Data access governance

Also counts toward: Natural-language query

release

  • Extends Natural Language Policy over the DBOM and guardrail context so investigators can query AI governance in plain English — for example, 'Which models can access PHI data?' or 'Which identities interacted with customer PII through an agent?' — with answers derived from the Metadata Lake including lineage and… announced · Sep 2026 · source · release history
  • Adds Natural Language Policy and Investigation, enabling teams to articulate data controls in plain English (e.g., 'Only members of HR may view employment data' or 'EU personal data must remain within EU regions') and have them translated into enforceable controls across connected systems. announced · Sep 2026 · source · release history
Plain-English AI governance investigation shipped Enables investigators to query AI governance questions in plain English — such as which models can access PHI or which identities interacted with customer PII through an agent — with answers derived from the Metadata Lake including lineage context. 1 other source · first seen Sep 2026

Shared capability: Data access governance

Also counts toward: Natural-language query

example

  • Investigate which AI models in your Amazon Bedrock environment can access protected health information, using plain-English natural language queries. In the Bedrock Data Platform, navigate to ArgusAI > Natural Language Investigation and enter: 'Which models can access PHI data?' — the system returns results with lineage and access evidence from… announced · Sep 2026 · source
Sensitive data discovery 1 feature Data discovery and protection since 2026
Metadata Lake Copilot shipped A natural-language interface for querying the metadata lake to identify sensitive assets, riskiest users, and answers to data-risk questions, including in agentic and automated workflow contexts. 2 releases · first seen Sep 2026

Shared capability: Sensitive data discovery

Also counts toward: Built-in AI assistant, Natural-language query

release

  • Launches Bedrock Metadata Lake Copilot, a natural-language interface for querying the metadata lake to identify sensitive assets, riskiest users, and other data-risk questions. announced · Sep 2026 · source · release history
  • Builds on the existing Bedrock Metadata Lake Copilot, extending its natural-language metadata querying to agentic and automated workflow contexts. announced · Sep 2026 · source · release history
Data lineage 1 feature Data discovery and protection since 2026
AI Data Bill of Materials (DBOM) shipped Automatically generates a data bill of materials for AI systems by linking Amazon Bedrock Custom Models, Knowledge Bases, and Agents to the datasets used during training and inference. 1 release · first seen Sep 2026

Shared capability: Data lineage

release

  • Adds ArgusAI, a new product that automatically generates an AI Data Bill of Materials (DBOM) by linking Amazon Bedrock Custom Models, Knowledge Bases (RAG), and Agents to the datasets used during training and inference.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history
Other / not yet classified 9 features Features we have not matched to a capability yet. A suggested match is marked.
Agent activity audit log shipped suggested Logs every tool call decision with its target, action, data types involved, and verdict — blocked, modified, redacted, or observed — producing a continuous audit-ready record of agent activity. 2 releases · first seen Sep 2026

Suggested capability: Data access governance. This is our guess, not confirmed.

Also counts toward: Administrative audit log

release

  • Logs every tool call decision with its target, action, data types involved, and verdict (blocked, modified, redacted, or observed), producing a continuous audit-ready record of agent activity. announced · Sep 2026 · source · release history
  • Audits AI model interactions with enterprise data through the MCP Server to support traceability and policy alignment in agentic workflows. announced · Sep 2026 · source · release history
API and SIEM/CNAPP/DLP integration shipped Exposes an API-first architecture that lets teams implement uniform data-security policies across heterogeneous infrastructure and integrate the metadata lake with SIEMs, CNAPPs, and DLP tools. 2 releases · first seen Sep 2026

release

  • Exposes an API-first architecture enabling teams to implement and enforce uniform data-security policies across heterogeneous enterprise infrastructure and integrate the metadata lake with SIEMs, CNAPPs, and DLPs. announced · Sep 2026 · source · release history
  • Enables AI agents and external applications to query the metadata lake without custom point-to-point integrations, allowing teams such as legal and compliance to run data investigations without engineering bottlenecks. announced · Sep 2026 · source · release history
Metadata Lake shipped suggested A graph-backed centralized repository that continuously catalogs enterprise data stores across SaaS, PaaS, and IaaS, capturing location, sensitivity, entitlements, lineage, usage, risk, and more than fifty additional metadata signals. 2 releases · first seen Sep 2026

Suggested capability: Sensitive data discovery. This is our guess, not confirmed.

release

  • Introduces the Bedrock Metadata Lake, a graph-backed centralized repository that continuously catalogs enterprise data stores across SaaS, PaaS, and IaaS, capturing location, sensitivity, entitlements, lineage, usage, risk, and more than fifty additional parameters.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history
  • Surfaces over 50 distinct metadata signals — including sensitivity classification, access patterns, and lineage — as queryable context for agentic AI workflows and automated governance pipelines. announced · Sep 2026 · source · release history
Sensitive data discovery and classification shipped suggested Automatically discovers and classifies sensitive data — including data used in AI initiatives, plain-text secrets, and externally shared assets — across connected enterprise environments. 2 releases · first seen Sep 2026

Suggested capability: Sensitive data discovery. This is our guess, not confirmed.

release

  • Launches Bedrock Free for Snowflake, a free tier that delivers automated sensitive-data discovery and classification for Snowflake environments, including access to Metadata Lake Copilot, with upgrade paths to entitlement chain and usage analysis and automated policy capabilities. announced · Sep 2026 · source · release history
  • Supports detection of sensitive data used in AI initiatives and plain-text secrets, and provides external sharing discovery, through the metadata lake platform. announced · Sep 2026 · source · release history
Data residency policy enforcement shipped suggested Enforces data residency requirements — such as keeping EU personal data within EU regions — across AI systems without requiring custom control-plane code. 1 other source · first seen Sep 2026

Suggested capability: Data loss prevention. This is our guess, not confirmed.

example

  • Enforce a data residency policy across AI systems without writing control-plane code — useful for EU compliance requirements. In the Bedrock Data Platform, go to Natural Language Policy and enter: 'EU personal data must remain within EU regions.' — Bedrock Data translates the invariant into enforceable controls across… announced · Sep 2026 · source
DSPM AI agents shipped Proactive AI agents that analyze the metadata lake for policy violations and new risks, gather context automatically, suggest next steps, and guide users through incident-response resolution workflows. 1 release · first seen Sep 2026

release

  • Introduces Bedrock AI Agents for DSPM, which proactively analyze the metadata lake for policy violations and new risks, gather context automatically, suggest next steps, and guide users through incident-response resolution workflows. announced · Sep 2026 · source · release history
Guardrail gap analysis shipped suggested Compares policy intent against actual model data exposure drawn from the Metadata Lake and generates targeted remediations to suppress or mask sensitive data at the source or agent runtime. 1 release · first seen Sep 2026

Suggested capability: Data loss prevention. This is our guess, not confirmed.

release

  • Adds Guardrail Gap Analysis that compares policy intent against model data exposure — drawn from the Metadata Lake — and generates targeted remediations to suppress or mask sensitive data at the source or agent runtime. announced · Sep 2026 · source · release history
MCP Server for metadata lake access shipped A standardized MCP Server gateway that exposes metadata lake signals — sensitivity, risk, lineage, access, and usage — to AI agents and external applications, supporting traceability and policy alignment in agentic workflows. 1 release · first seen Sep 2026

Also counts toward: MCP server

release

  • Adds an MCP (Model Context Protocol) Server as a standardized gateway between AI agents and Bedrock's metadata lake, exposing data sensitivity, risk, lineage, access, and usage signals via the open MCP protocol.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ announced · Sep 2026 · source · release history
Metadata-aware data restriction propagation shipped suggested Carries data restrictions across table writes, tool handoffs, and agent-to-agent transfers using the Metadata Lake knowledge graph rather than payload pattern matching, so restrictions travel with the data as it moves. 1 release · first seen Sep 2026

Suggested capability: Data loss prevention. This is our guess, not confirmed.

release

  • Carries data restrictions across table writes, tool handoffs, and agent-to-agent transfers based on the Metadata Lake knowledge graph rather than payload pattern matching, so restrictions travel with the data as it moves. announced · Sep 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface

Five scores for Bedrock Security, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Bedrock Security puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

10 entries

  1. September 202610

    10 entries

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →