11.31.46 Platform Release

Released June 17, 2025

info

If you are using the NIST NVD connector, Brinqa recommends switching to Brinqa Risk Intelligence, as the NIST NVD connector is no longer supported in Brinqa Platform version 11.28 or later.

Announcements

• We implemented the ability to select specific findings and create tickets from the findings List views. These tickets are called ad hoc tickets.

  • There is a 1000 findings limit per ad hoc ticket.
  • The system validates inclusion of findings already in existing tickets.
  • An attribute was added to the Ticket data model for ad hoc identification.
  • You can remove selected findings from ad hoc tickets.

New features and enhancements

• Removed risk and compliance related attributes from cluster data models in CAASM. These attributes and relevant computations were moved to an optional add-on for better scalability. Migration scripts were updated accordingly.

• Reviewed and updated parquet file retention policies to improve storage management.

• Previously, users could not add custom names to Inputs on reports. We added support for customizing input titles in reports, allowing users to set and persist custom titles for basic inputs.

• Moved drill-down configuration for charts that use a data model as the Data Source type into the Setup tab to ensure consistent navigation.

• Updated ACLs to allow Remediation owners to add comments and attachments to remediation validation requests.

Addressed issues

• Fixed inconsistent refresh behavior between bulk and single record updates on custom attributes. Previously, single records would automatically refresh while bulk updating would not. These will refresh automatically.

• Fixed flow executions that caused an incorrect username to be populated. The fix clears the entire local store before reuse so that the appropriate username is now populated.

• Fixed an ACL issue that disallowed remediation owners from launching remediation validation requests. They now are able to launch these requests.

• Fixed an issue that caused 'Node already exists' errors when creating users from Person. Email lookup is now case-insensitive to prevent these exceptions.

• Fixed orchestration conflicts by ensuring Data Lifecycle steps and flows display consistent run statuses so that automations do not start prematurely.

• Fixed the incorrect condition in the 'Finding has no valid source status but data lifecycle is inactive' configuration by adding a migration script to delete the problematic clusters.

Known issues

• Manually setting a custome attribute in an ad hoc ticket results in an identifier mismatch error.