Note: These features, updates, and addressed issues are released first in Hyperproof US and Hyperproof EU on the date noted in the title. They are released in Hyperproof Gov one week later unless otherwise noted.
Added / Improved
Hyperproof MCP server - Read access
Note: This feature is not supported in Hyperproof Gov.
You can now connect compatible AI clients directly to your Hyperproof organization using the Hyperproof MCP server. This allows you to query your live compliance data in plain language without exporting reports or switching contexts.
Supported Data (Read-Only Access)
The Hyperproof MCP server currently supports read access for the following objects:
Assessments
Audits
Controls
Custom Fields
Evaluations
Groups
Issues
Labels
Policies
Programs
Proof
Requests
Risks
Tasks
Users
Permissions and security
All MCP connections authenticate using the individual user's Hyperproof credentials. Data visibility mirrors the user's existing Hyperproof permissions and is further restricted by the MCP scopes configured by your organization's administrator.
Setup
Contact your Customer Success Manager (CSM) to enable MCP for your Hyperproof organization.
Once enabled, follow the setup guide in Setting up your Hyperproof MCP server.
Note: You must be logged in to Hyperproof to access the MCP server documentation.
MCP access for self-service reporting
Note: Self-service reporting is not supported for Hyperproof Gov.
You can now enable access to a Snowflake-managed MCP server, allowing Claude and other MCP clients to query your Hyperproof self-service reporting data warehouse. See the Hyperproof Self-service reporting data model.
Instead of manually building reports in a BI tool, you can ask questions in plain language, such as "How has the share of healthy controls changed month over month for each program?" Your AI client will generate and run the SQL commands against your Hyperproof data in Snowflake. You can use the returned data to draft summaries, compare programs, identify trends, or create ad-hoc reports.
Setup and authentication
Provisioning: Enabling MCP access in Hyperproof automatically creates a Snowflake-managed MCP server for your organization's data warehouse, along with a dedicated sign-in client for your MCP tool. See Connecting an MCP client to your self-service reporting data.
Permissions: Users authenticate using their individual Snowflake Person accounts, ensuring the AI client only accesses data the user is already authorized to view in Snowsight or a BI tool. assistant sees the same data that person sees in Snowsight or a BI tool.
Self-service reporting
Added RATIONALE to the CONTROL_RISK table. This addition supports reporting on the rationale for the mitigating controls' likelihood and impact.
Hierarchical Scopes - Improved control identifiers
Hierarchical scopes support up to 10 levels, making control scope identifiers much longer. Previously, the full path shown on Hyperproof windows was combined into a single name (for example,
CloudProduct>Europe>Germany_Berlin). Long names were cut off at the end, hiding the most specific part.Identifiers now contain the first and last levels and shorten the middle when displayed in Hyperproof windows, for example, Cloud Product > … > Berlin. You can see the exact scope at a glance, no matter how deep your hierarchy goes.
Customers using the API have been sent a personalized message from support asking them to reach out if they are affected by this change and need assistance.
Policy AI section-level linking
Note: This is an additional feature available for purchase.
You can now use Policy AI to review your policies, get suggestions for which controls and requirements to link to each section, and see a score based on framework alignment, control health, and policy adherence.
Moving to a new effective policy now carries over previous links. Policy AI labels each edited section as a major or minor change and recommends whether to keep, remove, or add links.
See Policy section linking for more information.
ServiceNow task integrations status mapping
Previously, a single status mapping handled both directions, and closing a task in Hyperproof didn't close its corresponding ticket in ServiceNow. Status mapping is now bi-directional, split into inbound and outbound rules:
Closing or canceling a task in Hyperproof now also closes its ServiceNow ticket, with no additional manual step.
A ticket closed in ServiceNow moves the task to "Submitted" in Hyperproof, not "Closed", so the compliance reviewer still reviews it before it closes.
Note: Status mappings saved before inbound and outbound mapping became available were converted automatically. In a converted mapping, Closed and Cancelled send the same ServiceNow status as Submitted, so closing or cancelling a task doesn't close the ServiceNow ticket. To close or cancel tickets in Hyperproof, choose the ServiceNow status Closed or Cancelled.
Proof linked objects
The proof window and the proof preview now include links and totals for policies and tasks.
For Policies, proof links to a specific policy version, so you can see exactly which version of a policy it supports.
Hypersyncs and integrations
Updated the Hypersync for Google Workspace Platform - Refined the permission set required to collect proof from Google Workspace Platform. See Google Workspace Platform proof types and permissions for more details on permissions.
Updated the Hypersync for GitHub - Refined the permission set required to collect proof from GitHub. See GitHub proof types and permissions for more details on permissions.
The new Hyperproof Community is officially live!
Customers can now access the Community directly in Hyperproof, either from the Support agent help widget in the bottom left (Go to Community) or from the Help dropdown in the upper right (Hyperproof Community).
Note: You may need to log out and back in to Hyperproof if you don’t see it.
Support system updates
Our support system will be offline from November 20, 5:00 PM Pacific time until November 23, 12:00 AM Pacific time while we transition our support ticketing system from Salesforce to Intercom. Read more about the transition in this article: Ticketing system change
Addressed issues
Fixed an issue in the Policies module where the External link for editing field was cleared and locked in read-only mode for a cloud-sourced policy document, preventing users from accessing the external editing link once a policy moved into Approval or Effective status. (Case # 00012703)
Fixed an issue where tasks generated from a repeating task failed to start approvals or automatically close after final approval if the repeating task's original organizer was deactivated, leaving approved tasks stuck in Submitted status. (Case # 00012829)
Fixed an issue where sender headshots in email notifications appeared cropped as narrow rectangular strips instead of circular icons in classic Outlook desktop clients. (Case # 00012871)
Fixed an issue in Policy imports where updating existing policies with linked controls failed to link the effective policy document to those linked controls. (Case # 00012893)
Fixed an issue in the automated test builder where the field dropdown displayed blank labels for the state, usersIncluded, and usersExcluded fields when configuring tests for the Hypersync for Microsoft Entra ID Conditional Access Policies proof type. (Case # 00012968)
Fixed an issue on tasks and task templates integrated with ServiceNow where the Assignee picker displayed all ServiceNow users instead of filtering the list to active members of the selected Assignment Group. (Case # 00012967)
Fixed an issue in the Hypersync for Microsoft Intune List of Configuration Policies proof type where the Assigned column, Platform, and Policy Type fields were left blank, built-in Microsoft templates were included alongside organization policies, and policy lists were truncated after the first page. (Case # 00012990)
Fixed an issue in the Approvals workflow where sequential approvals failed to generate when a task created using an API service account without an assignee was submitted. (Case # 00012836)
Fixed an issue in Automated Tests where CSV-based tests linked to a control through a label failed to automatically run when a new version of the CSV proof was uploaded. (Case # 00013022, 00013035, 00013036, 00013038, 00013039)
.. plus other fit and finish, performance, stability, and security issues — as always!
