Changelog
Back to All

CLI 6.45.8

September 10th, 2026

[6.45.8] - 2026-09-10

Added

  • JCAM imports can now create the system roles a plan is missing. Declare them in the new jcamSystemRoles init.yaml key along with the five values RegScale requires and JCAM does not send; without that key nothing is created and behaviour is unchanged.

Changed

  • The recommended JCAM mapping profile now writes to spelled-out field names such as "Maximum Tolerable Downtime (MTD)" and "Authorization Status" rather than abbreviations, matching the names JCAM and RegScale tenants already use. The legacy profile is unchanged.
  • The recommended JCAM mapping profile no longer assumes what an agency calls its agency-defined items. A new jcamAgencyDefinedHandling setting names which of your attributes carry a High Value Asset flag or a cloud descriptor, so the built-in handling applies whatever your agency named them. The legacy profile is unchanged.
  • jcam check_config now reads every JCAM system in scope rather than the first one when reporting system roles, and names any position that no role covers.

Fixed

  • JCAM mapping no longer reports a false "RegScale has no module named 'milestones'" error, reads the module list once per run instead of once per module, stops rather than continuing when the module list cannot be read, and no longer describes unresolved destinations as a tab problem
  • A JCAM field mapping destination may contain a slash, so a RegScale field whose name contains one can now be mapped
  • JCAM imports no longer fail when a JCAM field holds a numeric value
  • JCAM POA&M severity is no longer filled from JCAM's computed criticality when no human-set value exists, since the two are different facts
  • JCAM POA&M import now reads the pre-rename criticality key, so tenants that predate the CSAM to JCAM rename populate the derived criticality field
  • jcam preview_poc_roles no longer refuses to run on a tenant whose mapping profile does not fully resolve. Building the import scope needs one destination, the JCAM system id, so it no longer demands the whole profile. Every importer and exporter still refuses a half-configured tenant on its own.