CLI 7.2.0

Added

  • regscale client_runs commands: list shows the sync runs this machine left open, status shows one run, find names the run that holds a plan and source, and close closes a stuck run without mop-up
  • Every command that loads configuration now logs at INFO where its configuration came from and why (the working directory default, REGSCALE_CONFIG_FILE or --config), followed by a second line naming the environment variables that override it and how many secret-store references it holds. Values are never logged.
  • The compliance settings model now reads the vulnerability SLA mode and multi-agency flag from the platform.
  • Microsoft Defender and Defender for Cloud recommendations are now also reported as vulnerabilities, so they appear on the Vulnerability Status Board and in the FedRAMP VDR report, linked to their existing issues; this needs RegScale platform 6.36.2.0 or later, and older platforms keep creating issues only
  • Curated RSA Archer, Splunk, Microsoft Intune, ServiceNow, GitHub, GitLab, Sicura and Microsoft Sentinel commands in the Orchestration Hub command set (roh)

Changed

  • Trivy and Grype import_scans send each vulnerability once, with every asset that carries it, instead of once in every request that holds one of its findings, so a 750,000-finding import sends 20,000 vulnerability items (87 MiB) instead of 677,000 (1.2 GiB); --dry-run, --offset and --limit then count vulnerabilities, the closing log lines count them too and name the findings they cover, and groupScanFindings: false sends one item for each finding as before
  • A sync that finds another run of the same source still open for its plan now asks in a terminal whether to close that run and continue; answering y closes it without mop-up, which closes no records
  • Trivy and Grype import_scans send a folder's findings straight from the scan files instead of copying them into a multi-gigabyte staging file first, so a month of scans needs no large file on disk and no read of one from a slow shared drive; set stageScanFindings: true to stage them as before
  • Faster preparation of large flat-file scan imports (CSV, XLSX, JSON and XML), with no change to the data they create
  • A new init.yaml no longer carries issues blocks for aqua, defenderFile, ecr, nexpose, snyk, sonarcloud, veracode and xray, because the CLI never read them and RegScale takes issue due dates and status from the plan's compliance settings; blocks already in an existing init.yaml are ignored without a warning
  • The Nessus file import and the Tenable.sc sync now record one vulnerability per Tenable plugin, mapped to every affected asset, instead of one vulnerability per CVE. This follows Tenable's own definition of a finding (plugin, host, port and protocol), where the CVEs belong to the plugin and share one fix. The vulnerability's CVE field holds the plugin's first CVE, and its description lists every CVE of a multi-CVE plugin. On the first import after upgrading, the earlier per-CVE vulnerabilities, and the issues paired with them, close, and one vulnerability per plugin opens in their place.
  • The Trivy and Grype importers now stage their findings in small files that are removed when the import ends, instead of one file of up to several GB that stayed on disk, and they stage faster
  • AWS command help and the AWS docs now call the service the CLI reads "AWS Security Hub CSPM", matching the AWS rename; command names, options and IAM actions are unchanged
  • Warn at WARNING level when an SSP import falls back to a default impact level or categorization.
  • Scanner syncs now link a vulnerability to up to 50,000 affected assets by default instead of 10,000; an init.yaml that already sets maxAssetIdentifiersPerVulnerability keeps its value
  • Since 7.1.0, the Qualys VM scan import keys a host whose QG Host ID is a placeholder (0, none or unknown) on its IP address, so a host imported earlier under a placeholder ID gets a new asset keyed on its IP and its old asset stops receiving the host's findings
  • Every flat-file import in one import_all run stores Flat File Integration as the asset scanning tool, not the name of an import that ran before it
  • When Jira refuses an attachment upload, or a new ticket's attachment step fails in the ticketing sync, the log shows one error line and no stack trace
  • FedRAMP import-drf clears the saved operational requirement attachments of an OR deviation for an empty cell
  • regscale fedramp import-drf no longer sets a deviation's CVE from the Vulnerability Name column when the workbook has no CVE column
  • regscale tenable io sync_assets sends each MAC address in upper case split by :, so it rewrites a stored MAC Address that uses -
  • AWS findings sync no longer writes a Lambda console link that does not open the function, such as one for an AWS ISO region or for a function name that is not readable
  • AWS asset sync keeps an EFS file system's stored Disk Storage when AWS reports no usable size, instead of sending 0 or a negative or dropping the asset, and logs a warning for a reported size it cannot use
  • The next Wiz inventory sync moves images stored as Hardware to Software and keeps their stored OS version, and to keep images as Hardware you list VIRTUAL_MACHINE_IMAGE in wizHardwareAssetTypes with useWizHardwareAssetTypes on, which applies that whole list
  • Tenable and Qualys CIS results, Tenable STIG results, AWS Config failures, AWS Security Hub controls, Google Cloud misconfiguration findings and Wiz cloud configuration issues now show as misconfigurations, and AWS Inspector, Google Cloud vulnerability and Prisma Cloud advisory findings show as software vulnerabilities even without a CVE

Fixed

  • A JCAM profile value that cannot be mapped now fails and skips only that plan, in plan creation, front matter, agency-defined data and the dry run, and the import continues.
  • Failed file uploads now log a truncated, escaped response body instead of the raw text.
  • The TUI console runner now streams output lines longer than 64 KiB to completion and terminates the command if reading its output fails.
  • regscale jcam test_connection now exits 1 with a configuration message when jcamToken or jcamURL is unset or a placeholder, instead of reporting success without making a request.
  • JCAM import_parameters --learn-from now requires --crosswalk, so a learned mapping is never written into the installed package where an upgrade would discard it.
  • Corrected stale SORN/JOIN clearing so an empty value is no longer written to a required field, which stops the platform refusing the whole privacy save.
  • regscale jcam export_ssp now sends each authorization and front-matter value as plain text read from the field the mapping profile uses, so drift detection no longer flags identical values and --force no longer fails with a serialization error.
  • Fixed the JCAM SDK so it no longer retries POST or PATCH requests on 5xx responses or read timeouts, which could create duplicate POA&Ms; they now retry only on connect and pool errors and on 429.
  • A partly filled jcamSystemRoles block now stops regscale jcam import_ssp with exit code 1 and a clear message before any plan is written, instead of ending in a traceback part-way through.
  • JCAM export_poams now sends each POA&M's stored severity as the matching JCAM criticality instead of No Selection, and no longer writes that value into JCAM's severity weakness-type field.
  • JCAM exports now treat an unreadable drift-check response as drift and any accepted 2xx write, including an empty 204, as a success.
  • The JCAM POA&M export now skips a POA&M and counts it as failed when its milestones cannot be read, instead of sending it without them.
  • regscale jcam check_config now reports an unset jcamFrameworkCatalog 800-53r5 catalogue id, which import_controls needs, instead of passing on the shipped catalogue fallback.
  • The FedRAMP inventory workbook importer now checks the "Asset Type" column against the allowed asset types and stores "Other" with a warning for any other value, such as a hostname.
  • Wiz and Defender syncs, and the DevSecOps orchestrator, no longer swallow SIGTERM during best-effort fetches, so a stopped sync ends through its cleanup and closes its run.
  • GitHub repository sync now records a repository on its first run instead of failing until the second run.
  • Synqly asset syncs run with --filter no longer mark the assets the filter left out as Inactive.
  • Stop the FedRAMP POAM import from closing outdated findings when close_outdated_findings=False is passed.
  • Scanner and compliance syncs now log throttled progress lines when no terminal is attached (cron, jobs run-due, redirected output) instead of running silent.
  • A batch the server refuses is now logged once as a single line with its counts, and the traceback is kept at DEBUG, instead of printing full tracebacks (twice for vulnerabilities) for refused or retried batches.
  • A vulnerability that fails to queue is now recorded as a failed item in the run, so the run exits 3 under REGSCALE_STRICT_EXIT_CODES=1.
  • The FedRAMP POA&M import now exits non-zero under strict exit codes when rows fail to parse or issues are rejected, and one finding that raises no longer ends the import.
  • A compliance sync that cannot process one of its items now skips control assessments, issue mop-up and asset mop-up for that run instead of judging controls from the remaining items and closing the failed item's issue.
  • Flat-file imports now skip a row whose builder raises, log the file and row, withhold mop-up, and carry on with the rest of the file and folder.
  • A flat-file import with a missing security plan or component now logs one ERROR line and exits 1 before any file is fetched or imported, instead of logging a warning and exiting 0.
  • Synqly ticketing commands now record a failed ticket create, ticket link save or attachment upload in the exit code and log the RegScale issue and ticket involved.
  • Synqly ticketing sync now creates tickets by sending only the issue and its ticket fields, instead of every command option and the query filter.
  • Sentinel incremental syncs no longer close open issues and mark assets Inactive for incidents and alerts that did not change since the last run.
  • The AWS Inspector sync no longer closes findings through mop-up when a findings bucket failed partway through the pull, and the run is now recorded as a partial failure.
  • QRadar sync-events now disables mop-up when a pull reaches max_events, so findings cut off by the cap are no longer closed.
  • Jira issue creation: one refused create no longer ends the run, so the keys of the other created issues are still saved to RegScale and a failed create is counted as a partial failure.
  • Burp and Acunetix folder imports now run as one import, so a later file no longer closes the findings an earlier file reported.
  • Fixed regscale defender sync_acr_containers marking other registries' container images Inactive when it syncs one registry or cannot read one.
  • Incident sync to ServiceNow no longer creates a duplicate incident when the lookup of the linked incident fails, and the run now exits 1 when a lookup or the link write-back fails.
  • The sonarcloud sync_alerts command now closes RegScale issues that SonarCloud has resolved, and a run without --regscale_id reuses one assessment per project instead of copying every issue each run.
  • Made regscale aws sync_config_compliance record a failure, log a warning naming the API action, and skip the success message when AWS Config refuses access to a read the run needs.
  • Fixed regscale azure sync_intune --dry-run no longer creates or overwrites SBOM records.
  • Fixed regscale salesforce sync so one refused Salesforce case no longer stops the run or loses the case numbers of the cases already created, which caused duplicate cases on the next run
  • Hold Qualys server-side mop-up for a sync_qualys run whenever any reported finding is updated or skipped client-side, so findings Qualys still reports are no longer closed; because most re-syncs update or skip some findings, a finding Qualys has stopped reporting stays open until a run in which none is held back
  • A failed Tenable WAS export no longer leaves a partial cache that a rerun in the same hour syncs as a complete export.
  • A Client API batch request that fails with a timeout or a server error is now sent again as the same request, after waits of 5, 15 and 45 seconds, instead of falling back to sending its items one at a time, which was too slow to finish; when every send fails the sync stops and says to run it again
  • Trivy and Grype imports of large scan folders no longer hold every finding in memory until the run ends, so an import of 750,000 findings peaked near 600 MiB instead of 8.3 GiB in our tests
  • Trivy and Grype import_scans no longer stop with TypeError: 'digest_size' is an invalid keyword argument for openssl_blake2b() on hosts whose Python has no built-in blake2b module, such as some RHEL and UBI images
  • Databricks sync_assets and sync_findings no longer fail with "affected_hosts is ndarray, not a list" when reading findings straight from a query with --query
  • S3 prefixes for the Trivy and Grype imports now accept the wildcards , ? and [abc], so a prefix like trivy-scan finds its files again
  • Updated the container images to the patched Kerberos libraries
  • Updated a dependency of the HTML parser to clear a high severity finding in the container image scan
  • Logging calls in the FedRAMP import and config loading no longer raise logging errors, so the upload status code and stakeholder debug output are now logged.
  • A catalog update now names the control in the justification it records when it archives a control. It previously recorded the literal text {control_id}.
  • Group user lookup no longer fails with an AttributeError for groups that have users, and it adds each user's delegates once without repeating or looping on delegation cycles.
  • AWS inventory now logs a warning, not an error, when QLDB is enabled but the installed boto3 no longer includes the retired qldb service
  • jcam list_fields now sorts the fields in each tab by name.
  • jcam check_config now lists the destinations a tenant excluded with @drop, under a heading that marks them as chosen.
  • OSCAL profile import now reads the controls of every imports entry and every include-controls block instead of only the first.
  • OSCAL profile import now matches control ids regardless of case, zero padding and enhancement notation, and the log names each control it cannot find.
  • OSCAL catalog import now keeps the text of every guidance and overview part of a control instead of only the last one.
  • ControlObjective.from_dict no longer raises a TypeError and no longer turns missing values into the text "None".
  • A Qualys CIS benchmark row with no host IP no longer stops issue creation; the row adds no host and the control still gets its issue.
  • Queue a record created and then edited in the same run as a single create, so no id 0 update is sent that could fail a whole update batch.
  • The JCAM controls import now reports a value the plan's compliance settings do not offer once per run with a control count, instead of one warning per control that reprinted the plan's whole allowed-value list.
  • jcam check_config now ends with a one-line ready or not-ready verdict that lists only the items that block the import.
  • Fixed the GitLab findings sync failing on a group whose projects have no successful pipeline or security scan job yet; it now logs that no scan results are available and exits cleanly.
  • Fixed STIG checklist import so the comments and finding details from a checklist file are saved instead of always being empty; re-importing a checklist whose comments or details changed now updates the stored checklist, and a checklist action that raised a recursion error when an item was deleted now reports that it is not supported.
  • Qualys asset de-duplication no longer relies on a pluginId value that the Asset model silently dropped; existing assets are matched by their Qualys asset ID.
  • FedRAMP SSP import no longer crashes on objective and parameter ids in OSCAL control implementations.
  • Fixed a crash when mapping Synqly security findings that have no vulnerabilities, and DuroSuite group template variables that were silently dropped on group creation.
  • Refreshed the vendored platform schema snapshot and the generated model fields.
  • Creating the shared moka cache from several threads at once no longer builds more than one cache.
  • AWS, Microsoft Defender, Azure Container Registry and flat-file asset imports now leave an asset's public-facing flag unset when the vendor gave no exposure signal, instead of recording it as not public-facing.
  • Qualys container findings now send the real CVSS v3 vector and report every vulnerability in a container instead of only the first, so container vulnerability counts will rise.
  • Prisma Cloud, Microsoft Defender for Cloud, Qualys Total Cloud, Qualys CIS and Tanium now read their shipped issues.<integration> block from init.yaml (including noPastDueDates), and a fresh init.yaml now includes issues.noPastDueDates.
  • Import now keeps the original detection date and False Positive value (a No in that column is no longer read as a false positive) and restores the scheduled completion date the export shifted by one day (the import adds that day to the Scheduled Completion Date of every workbook, including one RegScale did not export, but leaves an unparseable date unshifted), and the Rev5 export lists every non-Closed POA&M on the Open sheet with its status shown as Status: <status> in the Comments column
  • Records the server rejects, and still rejects after the one retry, now count as failures, so REGSCALE_STRICT_EXIT_CODES=1 exits 3 when assets, vulnerabilities or issues fail to save.
  • regscale tenable io sync_compliance_controls no longer says that RegScale saved no control implementation when RegScale saved them and only reading them back failed; the run still exits 1 and says how many saved records got no assessment
  • The help for aws sync_iam and aws sync_kms now describes the assets each command writes: one AWS account asset for sync_iam, not one per user or role, and one asset per KMS key for sync_kms, both stored with asset type Other
  • When the batch request for an asset fails while another import saves the same plan, an asset import now tries the platform's single asset create or update, which never adds a second copy, and reports the asset as not saved if the platform does not have it or the other import holds the plan longer than the request can wait
  • Flat-file imports stop with a usage error, and leave the mapping file unchanged, when its mapping entry is 0, false, an empty string or an empty list instead of silently replacing it with the scan file's headers
  • The Qualys VM scan import now names each skipped host by its DNS name, then its NetBIOS name (the same order as asset names), then its FQDN, quoted and escaped in the skip warning, instead of reporting every host with only a NetBIOS name as one unnamed host
  • An Axonius v2 incremental sync that fails to write some records no longer moves its watermark past them, so the next sync retries them instead of reporting success with 0 records
  • If a component's protocol name, type or interconnection information value is empty, FedRAMP OSCAL SSP imports now store its port record, which RegScale rejected before
  • If a component port value or port range is missing or not valid, FedRAMP OSCAL SSP imports now log a warning and continue
  • FedRAMP OSCAL SSP imports now store every port range of a component protocol, not only the first one
  • If a Services, Used By or protocol cell is empty in a FedRAMP SSP Word document, the import now sends "Unknown"
  • Burp and Acunetix imports of a folder with two or more files no longer stop at the second file because another sync is still open
  • An AWS asset sync that retires a region's deleted assets itself (on a plan with assets of several regions, or when an inventory section could not be read) now takes a deleted "Off-Network" or "Decommissioned" asset out of the latest scan without changing its status, so the FedRAMP inventory export reads "No" for it in "In Latest Scan"
  • A line break or control character in an attachment name no longer starts a new line in the Jira or ticketing sync log
  • FedRAMP import-drf saves the operational requirement attachments of an OR deviation in their own field
  • regscale fedramp import-drf reads a deviation's CVE from the CVE column, so re-importing an exported Deviation Request workbook no longer replaces each CVE with its issue title
  • Fixed Wiz vulnerabilities sync keeping a resource's asset link Open after Wiz resolved the rule on that resource while the rule stayed open on another: the link now closes at the date Wiz resolved it there
  • regscale jira issues and regscale jira tasks (including --to-evidence) now work against Jira Data Center / Server: when Jira reports a Server or DataCenter deployment the issue search goes to /rest/api/2/search, paged on startAt, instead of Jira Cloud's /rest/api/3/search/jql, which Data Center rejects. A server that reports no deployment type is tried on v3 first and on v2 when it answers 404, 405 or 410. A failed search now ends with one line naming the HTTP status and the endpoint, without the query string, and for Data Center points at regscale jira_dc.
  • regscale axonius_v2 sync_saved_queries no longer prints a doubled period in the missing security plan error
  • regscale tenable io sync_assets now stores an asset that reports two or more MAC addresses. MAC Address holds one real address, the first in sorted order, so a new interface order does not change it. The command uses an all-zero or broadcast placeholder only for an asset with no other address. The asset's notes list the other addresses. If RegScale refuses an asset, the command now exits 1 instead of reporting success.
  • If Tenable.io reports an address as 0050.56a1.0f22 or 005056a10f22, regscale tenable io sync_assets now puts it in MAC Address
  • regscale tenable io sync_assets keeps an asset's MAC Address and notes the same when Tenable.io changes the letter case or separators of an address
  • Wiz compliance report issues for a failing control now count, list and name in their Asset Identifier only the resources that fail the control, and take their severity from the failing checks only
  • GCP findings now give their issues the Security Command Center recommendation as Recommended Actions instead of the generic sentence on RegScale 6.36.2.0 or later, including existing issues that still hold the generic sentence; a finding on the CISA KEV list can keep the KEV sentence, and an earlier platform ignores the recommendation
  • AWS Security Hub findings now count First Seen and the issue Due Date from the date the finding was first observed, with First Seen never later than Last Seen and the created or updated date used when a date is blank or not between 2000 and today. A consolidated vulnerability now takes the earliest First Seen and the earliest Date Created across the findings in its group, and the latest Last Seen, and counts its Due Date at the group's highest severity from that earliest First Seen, so an open issue Due Date can move earlier or later on the next sync and an issue whose new Due Date has passed becomes a POA&M
  • regscale aws sync_cloudtrail and regscale aws sync_s3 evidence records now list each control as passed or failed by the same rule as the run's control assessments, and name how many trails or buckets fail each control
  • AWS asset and findings sync now take a Lambda function asset's location from the region in its ARN, so a finding with no region no longer places a function in us-east-1 when its ARN names another region
  • AWS asset sync now fills in the URI of a Lambda function asset with its AWS console link, as AWS findings sync does
  • import_all run names each file it cannot read on one error line and stops with exit 1, where a traceback named only the first such file
  • AWS asset sync stores a DynamoDB table's Disk Storage in whole GiB instead of bytes, so a table of 2 GiB or more no longer fails the asset request; a table under 1 GiB shows 0
  • The AWS GuardDuty evidence record now says when the detector or findings read was incomplete, gives those counts as unknown instead of 0, and lists a control the read could not settle as not assessed instead of passed or failed
  • AWS GuardDuty sync logs each "not assessed" control warning and the malware findings warning once per run instead of repeating them
  • GCP sync_compliance and collect_evidence now log how many findings mapped to a control and how many had none
  • A list setting given as an environment variable, such as wizHardwareAssetTypes, now reads a JSON or comma-separated list instead of single characters, and a blank value falls back to the default
  • Wiz inventory and Wiz compliance and STIG asset stubs record a virtual machine image as Software, as the default hardware type list intends
  • A Wiz vulnerabilities sync no longer opens issues titled with the CVE twice ("CVE-2016-9267: CVE-2016-9267") for findings Wiz names by their CVE alone: the title now reads the CVE once, followed by the start of the description or, without one, the affected package; the next sync also retitles existing issues of this kind and updates their Security Checks text to match
  • The AWS command help and integration guide now match what sync_findings, the Audit Manager and AWS Config syncs and the asset sync do
  • regscale aws sync_assets no longer adds an Athena workgroup asset with no account number when AWS STS refuses the call and the security plan holds that workgroup for more than one account
  • The child jobs of a split Wiz inventory sync now read Wiz at the same time, so a later child waits only for the first child's remaining read and the writes ahead of it instead of every other child's full read
  • regscale aws sync_assets no longer marks Inactive an asset that regscale aws sync_findings_and_assets created for a resource the inventory does not list
  • regscale aws sync_assets --account_id now skips Athena workgroups, with a warning, when the AWS credentials belong to a different account, instead of saving that account's workgroups under the scoped account
  • aws sync_findings and aws sync_findings_and_assets with --account_id or --tags now close no vulnerabilities, and a run without these options closes the ones no longer reported
  • regscale aws sync_config_compliance no longer fails its compliance lookup or evidence collection when AWS Config returns a rule with no name, and its warning shows such a rule by its ID or ARN
  • regscale aws sync_config_compliance no longer closes the vulnerabilities and issues of passing controls when AWS Config returns a rule with no ARN or no name. The run names the rule in a warning. When the run checks that rule, it also leaves mop-up off and does not update control assessments. Fix or delete the rule in AWS Config to close records again
  • When AWS refuses part of the S3 bucket listing, regscale aws sync_s3 now warns and does not cache the partial list
  • regscale aws inventory collect now warns about each resource type that AWS refused to list
  • If AWS refuses the GuardDuty detector listing or a detector's details, regscale aws sync_assets now keeps the GuardDuty detector assets Active instead of marking them Inactive
  • When regscale aws sync_assets cannot read a resource listing, it now keeps those assets Active and names the type in a warning
  • regscale aws sync_s3 keeps its earlier evidence file when AWS refuses to return one of a bucket's settings or a bucket cannot be read
  • regscale aws sync_s3 now replaces the evidence file it attached earlier for the same AWS account instead of adding one more every run, and keeps files others added, files in an approval and files from a narrowed or partial run
  • regscale gcp sync_assets with --asset-types or --labels no longer sets the plan's other GCP assets Inactive
  • regscale gcp collect_evidence (and regscale gcp sync_findings --generate-evidence) now replaces the evidence file on each evidence record instead of adding one more file every run, and keeps files a person or another account added, files in an approval and files in an earlier version of the record
  • The gcp sync_compliance, collect_evidence and sync_findings --generate-evidence commands no longer set the plan's other compliance assets Inactive
  • The gcp sync_compliance command now closes its own earlier Fail of a control once no active finding fails it, and keeps any other Fail
  • Fixed gcp sync_findings with --sources or --severity-filter closing the plan's GCP findings that the filter left out; only an unfiltered run closes findings that are no longer in SCC
  • Fixed GCP findings sync keeping a vulnerability linked to an asset its finding no longer names: when a finding moves to another asset, the sync now maps the vulnerability to the new asset and closes its link to the old one, unless the vulnerability is not Open, when the old link stays Open
  • gcp sync_compliance and gcp collect_evidence now fail with exit 6 (4 when GCP refuses the credentials, 1 when the findings cannot be read) instead of ending successfully with nothing assessed when Security Command Center cannot be reached or its findings cannot be read
  • regscale jira issues no longer changes the "Due Date:" line of an issue description to ISO form (2027-02-04T07:19:41Z) on a re-sync; the line keeps 2027-02-04 07:19:41, or 2027-02-04 for a Jira due date
  • jira tasks now applies Jira's title, description and due date to a task in the same run that closes it; before, a task edited and moved to Done in Jira closed with its old values until a later run fetched the issue again
  • regscale jira issues no longer changes an issue that a scanner integration wrote, so a closed AWS or GCP issue stays closed
  • regscale wiz compliance_report now replaces the report file on the project's evidence record instead of adding one more file every run, and keeps files a person or another account added, reports in an approval and reports in an earlier version of the record
  • regscale wiz compliance_report and the deprecated regscale wiz sync_compliance now close the issue of a control that the latest report passes
  • A Wiz vulnerabilities sync now updates an end-of-life finding's vulnerability in place when Wiz renames the finding, instead of adding a second vulnerability for the same finding
  • A repeat OCSF ingest no longer creates a second asset for a named resource that has no uid, and it updates only a same-named asset whose notes hold that resource
  • A repeat OCSF ingest keeps the asset status and other asset values a person set
  • Wiz commands that get a query answer with errors and no data now print one error line that names the query and the errors Wiz reported, instead of several tracebacks, and optional steps that skip on such an answer (asset enrichment, the representative-asset collapse) say what they skipped without a traceback
  • Vulnerabilities that an integration builds itself (the Qualys VM report and CIS imports) now carry a finding type like the rest: software vulnerability when there is a CVE, otherwise other.
  • SARIF, Qualys Total Cloud, OpenText WebInspect and DevSecOps SARIF and Wiz CLI imports, and Trivy or Grype imports whose files share no scan day, no longer send the CLI machine's local date as the scan history date when none was given, so RegScale dates the scan history by the import time
  • regscale gcp sync_compliance with CIS_GCP, PCI-DSS or SOC2 no longer fails controls from Security Command Center tags of another standard or version (CIS Controls, CIS benchmarks other than 2.0, PCI DSS 4.0, SOC 1)
  • The FedRAMP inventory workbook importer now stores a common "Asset Type" such as "Server" as "Physical Server" (the shared asset type aliases) instead of "Other", or as "Virtual Machine (VM)" when the row's Virtual column is Yes; values that match nothing are still stored as "Other" with a warning.
  • Microsoft Defender asset sync now marks public IP address resources as public-facing, as PS-929 specifies, instead of leaving the flag unset.
  • A Nessus or Tenable.sc plugin that lists several CVEs now takes its KEV-listed CVE (the one with the earliest KEV due date) as the vulnerability's CVE, so the issue's KEV list, the KEV due date and the VDR KEV clock still apply when the KEV CVE is not the plugin's first. A plugin with no KEV CVE keeps its first CVE, and the description still lists every CVE. The vulnerability is still keyed on the plugin ID, and the issue's identity stays on the plugin's first CVE when the primary CVE is swapped, so a CVE joining the KEV catalog does not reopen the issue.