What's New in Release 3.12.0

C1Risk Version 3.12.0 delivers major enhancements to our Business Continuity Management (BCM) suite, introduces our secure Model Context Protocol (MCP) AI framework, and expands our change auditing history logs across key administrative, asset, vendor, and incident management modules.

1. Advanced Business Continuity Management (BCM) Updates

This release significantly advances our BCM capabilities by streamlining criticality configurations, shared record visibility, and detail page layouts.

• BIA Criticality Configuration: Administrators can now configure BIA criticality directly under Administration > Risk Policy> Criticality. You can select a single determining factor—Impact Score, MTD (Maximum Tolerable Downtime), or RTO (Recovery Time Objective)—to map custom dropdown values to Rating Levels 1–5. Criticality remains read-only on BIA records and recalculates automatically on save.

• BCM BIA Shared Access: A new default-enabled Shared Access attribute automatically grants read-only BIA Record Viewer access to contacts on related Asset and BCM Plan records. BIA list views now support Shared Access columns, filters, and bulk modification controls.

• Dynamic Asset and Vendor Layouts: Floating tables on Enterprise Asset and Vendor detail sheets now display read-only, non-archived BIAs, while related BCM dependencies are displayed as neat chips for immediate, at-a-glance visibility.

2. Secure AI Model Context Protocol (MCP) Integration

To securely empower compliance teams to interact with their GRC data using natural language, we have established our secure Phase 1 AI assistant architecture.

• Python fastMCP Server: Launches a containerized Python fastMCP server mapped via ArgoCD GitOps, allowing secure external AI clients (such as Claude Code, ChatGPT, and GitHub Copilot) to safely query and manage C1Risk records.

• Enterprise Authentication & Security: Every request is strictly authenticated using API keys AES-encrypted at rest in the database and validated directly by our Spring Boot authorization server.

3. Compliance and Test Procedure Enhancements

We have introduced key usability upgrades for testing coordinators to easily navigate, link, and detail procedures.

• Test Result Subtabs: Test Procedure detail pages now feature a dedicated Test Results subtab. Creating a new test result from this subtab auto-associates and pre-populates the Source Type, Source ID, and parent Test Procedure fields, streamlining your testing workflows.

4. Post-Approval Entity Status Standardization

To ensure operational clarity and data consistency across all modules, C1Risk has standardized how record statuses behave upon completing an approval workflow. This update removes the "Approved" state from several operational status dropdowns, automatically transitioning approved records to their correct operational lifecycle stages.

User Manual: https://c1risk.freshdesk.com/support/solutions/articles/73000672900-c1risk-user-manual-post-approval-entity-status-standardization

Announcement: Mandatory TLS 1.3 Upgrade

C1Risk connection security is upgraded exclusively to TLS 1.3, retiring support for TLS 1.2 and legacy browsers to ensure your data is protected by the most modern encryption standards.

• Timeline: This is active in Dev and Staging environments for Release 3.12.0, with Production deployment scheduled for Release 3.13.0.
• Action Required: For most users, no action is required. If you use an older or legacy browser, please upgrade to a native TLS 1.3 supported version (such as Google Chrome 70+, Microsoft Edge 79+, Mozilla Firefox 63+, or Apple Safari 12.1+) to retain uninterrupted access.

Please refer to our support article for details on browser compatibility and necessary upgrades on your end: Browser Support & Mandatory Security Upgrade to TLS 1.3