Skip to content
  • There are no suggestions because the search field is empty.

Release Notes - CRT v6.12.330, TPRM v3.1.52, & SGA v3.1.33

The above versions were released on 4/11/2025. This article contains information about what was included in those releases.

BUG FIXES

  • #2850 - Users > User Editor / My Profile - It was found that in certain areas we were collecting a users Job Title, but no where was it appearing on the user editor except for one single location. This has been corrected and been made consistent across the user editors.

  • #2882 - Compliance Management > Assessment - It was found that some fields were editable like : Risks, Policies, Affiliated Documents even though the Assessment is closed. This is been resolved so that once an assessment is closed nothing can be changed.

  • #2924 - Maturity Management > Managed Finding - Users reported that they were unable to delete an inactive managed practice. This was reviewed and resolved in this version.

  • #3128 - Compliance Management > Assessment Management - It was discovered that internal notes and remediation notes were no longer showing on the C2MA report template. This was adjusted and fixed in this release.

  • #3188 - Compliance Management & User Security - Users reported that although a specific user has been updated to have the "Evidence Owner" entitlement, their name was still not displayed in the associated evidence screens. This has been resolved.

  • #3236 - Risk Register > Add/Edit Risk - It was found that the "Third-Party" field  would disappear when a risk was saved. This was reviewed by the UI/UX team, and resolved.

  • #3238 - TPRM Portal > Manage Users - Vendor users reported that they were unable to mark an inactive user as active from within the users list. An investigation of the user security code took place and consistency was brought between the CRT and TPRM applications.

  • #3240 - Admin > Manage Clients - Users reported that they were unable to delete a Client record. This has been resolved.

  • #3241 - Compliance Management > Assessment Management > Assessment Practices - The ability to include/exclude practices was not functioning as the checkboxes were not saved. This has been resolved in this release.

  • #3247 - Third Party Risk Management - Issues between the data shown on a Third Party profile and what displayed in the list were inconsistent. Data was normalized so now the views are the same.

  • #3250 - Administration > Attribute Management > Manage Lists - Functionality that allows the limitation of specific drop list items to be limited to a single Client or Organization was not working correctly. This was reviewed, and necessary changes made to ensure functionality.

  • #3263 - Administration > Report Builder - An issue was found where when a user would attempt to clone a report they would receive an error. This is been reviewed and resolved in this version.

  • #3269 - Administration > Assessment Management > Framework ingestion/Assessment Editor - When users were importing frameworks it was found that classes are not displayed for the practices. The import functionality was reviewed and updated.

  • #3281 - Risk Register > Notifications - Users were receiving 403 errors when clicking links in notifications. This was resolved in this release.

  • #3282 - Compliance Management > Assessment Management > Data Ingestion - Users found that when attempting an ingestion that the results were incomplete. This was tested with multiple import types and issues were resolved along the way. 

  • #3287 - Risk Register > Add New Risk - Users found that they weren't being notified when a new risk was created. An issue was found and corrected in this release. Notifications should now be delivered as expected.

  • #3291 - Risk Register > Add New Risk - It was found that certain required fields  were not appearing as expected  when attempting to create a risk, or there was an inability to mark certain fields as required. Data validation was reviewed and updated as to resolve this issue in this release.

  • #3292 - Risk Register > Lines of Business - Users discovered in certain situations that they were unable to create a new Line of Business record. This was reviewed and resolved.

  • #3303 - Compliance Management > Assessment Management - Through testing it was found that evidence was not copying forward when a new iteration was being created. The business logic was reviewed and updated so evidence is copying forward once again as expected.

  • #3304 - Administration > Notification Manager - Related to #3303 it was found that the configured notification triggers that were responsible for sending evidence expiration notifications were not seeming to work as expected. This was resolved along with #3303.

ENHANCEMENTS/FEATURES

  • #2731 - SGA Portal - To eliminate some confusion in setting up a repository we've updated some of the language used while going through the setup steps.
  • #2870 - OSCAL: Open Security Controls Assessment Language - Cyturus has incorporated functionality to utilize OSCAL throughout the product. 
  • #3131 - Administration > Manage Client > Repository Setup - We have added a new repository type: S3. This allows users to utilize an S3 storage container as a repository location.
  • #3180 - DCMS - It had been suggested that the document naming convention should be based off a Category/Subcategory combination. Functionality has been added in this release that allows for this.
  • #3283 - Administration > Campaign Management - In this version we have updated the "Add New Campaign" form that allows users more options for managing their campaign.