SaaS Detection and Response Release 1.16.0 

August 20, 2026

Claude Connector Support

SaaSDR now supports a SaaS connector for Claude. The connector collects and monitors information from your Claude environment, including users, groups, files, and activity.

To set up the connector, you only need a Claude API key. Administrator access is required only to generate the API key and is not required afterward to use or maintain the connector.

After the connector is configured, SaaSDR automatically discovers and regularly updates information about your organizations, users, groups, projects, and files.

claude support

  • Users and files discovered through the connector are classified as Internal.
  • Files are available on the Resources tab.
  • File-related activity is available on the Events tab.
  • Events are categorized by severity (High, Medium, or Low) and grouped by activity type, such as login and compliance-related activities, making it easier to review and filter events.

Introduced Resource Inventory Reports

SaaSDR now provides enhanced reporting capabilities. The new Resource Inventory Report is now available, which lets you generate reports for Groups, Documents, Applications, and Users.

When generating a report, you can select:

  • The SaaS application

  • One or more connectors

  • The type of data to include

  • The required file format

The report supports large volumes of data in a single report. While the report is being generated, its status is shown as 'Processing'. The status changes to 'Completed' when the report is ready for download.

Introduced Clone Control Option to Create Custom Controls on Controls Page

SaaSDR now lets you create custom controls directly from the Controls page. You can create a custom control by cloning an existing predefined control and modifying it to meet your requirements, such as changing its criticality or evaluation condition.

Clone Control

  • Custom controls are supported for all SaaS applications, including the Claude connector.

  • You can create custom controls without assigning them to a policy. You can add them to a policy later when needed.

  • Custom controls appear alongside predefined controls in the control list and are clearly labeled, making them easy to distinguish.