The supplied Checkmarx SAST 9.8.0 release-note source contains no feature, fix, compatibility, or known-issue detail, which matters because a release owner cannot approve production rollout without verifiable scope.
The source provided is a documentation-site security-verification page. It confirms that the release-note content was not available for review; it does not confirm what changed in version 9.8.0. Treating an inaccessible page as release evidence creates avoidable delivery and audit risk.
What is currently verifiable
No 9.8.0 capabilities, defect resolutions, deprecated behavior, platform prerequisites, or limitations can be substantiated from the supplied material.
That distinction matters in enterprise delivery. Security-tool changes can affect:
- Finding volumes and severity distributions
- CI/CD pipeline duration and failure behavior
- Custom query and policy outcomes
- Integration behavior with issue trackers and identity systems
- Reporting baselines used by security leadership
- Exception decisions and application release gates
Until the authenticated release notes are reviewed, do not represent any of these areas as changed or unchanged in 9.8.0.
Release governance actions before approval
Request the official 9.8.0 release notes through an authenticated Checkmarx documentation session or the organization's vendor-support channel. Preserve the retrieved version with the change record, including its publication date and source location.
Then require owners to document the following before deployment:
