CLI 6.45.0
September 9th, 2026
[6.45.0] - 2026-09-09
Added
- Configurable console log format via
logFormat/logDateFormatin init.yaml, orREGSCALE_LOG_FORMAT/REGSCALE_LOG_DATEFORMATenvironment variables (environment takes precedence)
Changed
jcam --helpno longer lists the pre-rename spellingscheck_custom_fieldsandtest_jcam; both still run, so existing runbooks keep workingjcam check_confignow checks for a required custom field across the whole module rather than on one tab, and reports fields that resolved somewhere else as a note rather than a failure- CLI console logs now include a timestamp on each line by default
Fixed
- QRadar sync now rejects fractional time windows instead of silently truncating them and consistently applies the configured API version
- S3 file access no longer crashes on a default configuration and now honors documented AWS credential settings
- JCAM readiness check now calls out a missing system-id custom field as a blocker instead of omitting it
- JCAM test_connection now checks the systems, system detail, controls, and POA&M endpoints imports actually use, reporting each endpoint's status separately instead of one pass/fail
- JCAM import and export commands now surface configuration and connection failures instead of silently treating them as an empty or unchanged result
- JCAM system-to-plan lookups no longer drop plans beyond the first page of results
- JCAM configuration defaults in init.yaml.example that made every JCAM run exit with "No results match filter in JCAM"
- Wiz vulnerabilities and issues now capture the CVE when it appears alongside other text in the finding name
- JCAM control import now writes implementation status and control origin values allowed by the plan's compliance settings, and reports when it substitutes an equivalent label or when a plan offers no labels to constrain a field
- Axonius dry-run syncs no longer advance the incremental sync watermark
- Credentials named with the platform's own camelCase config keys are now redacted from log output instead of being written in the clear
jcam check_configon a tenant whose mapping profile does not fully resolve now reports that once instead of three times, and reads the tenant's fields once instead of three times- Corrected the JCAM mapping documentation and
init.yaml.example, which still described the oldTab/Fielddestination syntax that the CLI now refuses - A custom field the tenant put on a different tab than the mapping profile names now resolves instead of being reported missing, so renaming or rearranging a Form Builder tab no longer needs a
jcamFieldMappingline for every field on it - FedRAMP POA&M import now resolves asset lists pointed at a POAM Assets sheet and flags truncated Asset Identifier cells instead of importing partial data
- Integrations now stop with the field named when a module requires a custom field they cannot supply, instead of failing with an unclear server error
- Axonius saved-query sync now actually queries the configured saved query and raises a clear error instead of silently syncing zero records when it cannot be found
- Corrected the seconds separator in the CLI log file timestamp format
