[6.31.1.3] 06-25-2026

Enhancements

Added support for importing XCCDF TestResults into the assessment pipeline, enabling organizations to leverage additional security assessment data sources within RegScale.
Enhanced CKL/CKLB import capabilities to capture and store additional assessment metadata, providing greater fidelity and traceability for imported checklist data.
Updated vulnerability processing to automatically associate vulnerability-derived issues with affected assets, improving reporting accuracy and remediation tracking.
Enhanced vulnerability mappings and processing performance through optimized bulk operations, significantly improving import efficiency for large environments.
Added support for populating affected controls and control parts during vulnerability processing, improving control-level visibility and remediation workflows.
Expanded the CKL data model and import services to support additional checklist information and future assessment use cases.

Added support for SLCM exports, expanding available compliance reporting options.
Updated import, export, and form mappings to improve alignment with eMASS data structures and workflows.
Added export pre-flight validation checks to identify potential issues before export generation.
Updated Framwwork Importer manifest support to align with current requirements.
Enhanced asset mapping capabilities during imports to improve asset identification and correlation accuracy.

Modernized CKL and CKLB user interface views for a more streamlined assessment experience.
Removed unnecessary visual indicators from submodule input fields to improve form usability and reduce user confusion.
Added new form enhancements and field updates across the platform.
Updated Result Severity field handling to provide more accurate assessment data representation.
Improved inventory scorecard reporting by reducing noise from assets that do not contain vulnerabilities or issues.

Removed legacy eMASS Rev 4 export options that are no longer supported.
Streamlined export option management and cleanup processes.
Removed deprecated SDK dependencies from the core application, reducing platform complexity and improving maintainability.
Added data consistency safeguards to ensure system-defined fields are correctly identified and managed.
Enhanced custom field handling and validation to improve platform stability and configuration integrity.

Fixed an issue where repeated Wiz vulnerability imports could create duplicate issues when no changes existed in the source data.
Fixed an issue that prevented customized default issue statuses from being honored when creating vulnerability-derived issues.
Corrected vulnerability processing behavior that could overwrite customer-defined issue values with system-generated values.
Fixed an issue causing vulnerability rollup API requests to fail when no vulnerable assets existed in the environment.
Resolved an issue affecting vulnerability status board reporting when viewing data by asset.

Fixed an issue where questionnaire review assignments were not appearing in Notifications or Workbench views.
Fixed an issue preventing workflows from being added to Continuous Monitoring and Master Assessment configurations.
Corrected checklist import behavior so failed control implementations are properly transitioned to an "In Remediation" state when appropriate.
Added validation to ensure imported SCAP benchmark files are recognized and processed correctly.

Fixed an issue where conditional rules for Cyber Reportable POA&Ms did not correctly disable editing when records were no longer in Draft status.
Fixed a classification selection interface issue that could impact user interaction with classification fields.
Resolved a conditional visibility issue where Special Type Description fields did not display correctly for multi-select values.

Fixed a framework import edge case that could cause import failures under specific blob storage conditions.
Corrected eMASS HW/SW Rev. 5 export behavior to properly support numeric values in software licensing cost fields.
Improved export reliability and consistency through additional validation and cleanup updates.

Fixed data migration behavior to ensure system fields are correctly identified as non-custom fields.
Improved issue and vulnerability correlation accuracy by ensuring asset mappings are created consistently during automated processing.
Fix TDS packet size exceeding TLS record limit on encrypted SQL connections.

RE: TDS packet size exceeding TLS record limit on encrypted SQL connections.

On a TLS-encrypted connection, each TDS packet must fit inside a single TLS record (max plaintext fragment 16,384 bytes / 2^14). A 32 KB packet size negotiates to 16,442 bytes, which is over the limit.
TDS PacketSize is now configurable and default it to the largest value that is provably safe on an encrypted connection: 16,368 bytes.