Discover · databricks.com

No picture published by databricks.com

Block or redact sensitive data in requests and responses

docs.databricks.com databricks.com

This is what was read here when it was published. databricks.com no longer carries it in what it publishes now.

The Sensitive Data Detection guardrail (Beta) detects structured sensitive data (such as Social Security numbers, credit card numbers, IBANs, and phone numbers) and either denies the interaction or masks the matched values in place. Detection is deterministic (regular expressions plus checksums and context keywords, with no evaluator model), so it adds under 50 ms and returns the same result every time. To use it, turn on the Unity Gateway Service Policies preview on the Previews page in your workspace.

For chat-style APIs, blocked interactions now return a standard HTTP 200 response with the block reason, instead of a 4xx error, so coding agents that resend history don't re-trigger the same block every turn.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Also from docs.databricks.com

  1. Genie Code analysis for alerts is in Betadatabricks.com
  2. MCP tools in Genie Agents are generally availabledatabricks.com
  3. Lakebase now available in three additional regionsdatabricks.com
  4. Warehouse-level statement timeouts are now generally availabledatabricks.com
  5. OAuth authentication for webhook destinations will soon be available by default for workspaces with the compliance security profile enableddatabricks.com
  6. The Databricks GitHub app will request permission to create and manage pull requestsdatabricks.com