2019.09 Release Notes¶

The Managed Services Platform 2019.09 release introduces new features. In addition, two report formats are in transition.

What’s New¶

These are the highlights of this release:

Validation of scan targets

When scheduling a test for a Web application, the administrator can now verify that the target URL is accessible. This helps to minimize the chance of a scan not taking place when it is expected to.
IP address restrictions and expiration for API keys

A client now has the ability to create API keys that are limited in duration and scope. This helps to minimize the chance of keys being misused in the event that they are stolen.
IP address ranges for API keys

If a client specifies an IP address range, the generated API key can only be used from within that IP address range. Attempts to use the API key from other IP addresses will be rejected. Like address restrictions and expiration for API keys, this feature also improves security.
Common Vulnerability Scoring System (CVSS v2) now applied to Mobile scans

CVSS is a framework for communicating the characteristics and impacts of security vulnerabilities in mobile applications. This information lets customers assess where their Mobile vulnerabilities fall, within the industry-standard classification of software weaknesses.

Report format transition

The formats for XML reports was updated in the 2019.05 release, and the format for CSV (comma-separated) reports was updated in 2019.06. The updated formats are not backward compatible with the old reports.

To ease the transition to the new reports, the old XML and CSV reports are still published and will be published in the 2019.10 release under the “Additional” section, as xml_report (deprecated).xml and csv_report (deprecated).csv.

Following the 2019.10 release, only the new reports will be published.
Deprecation of v1 and v2 APIs

As a part of our public API versioning strategy, and to ease the transition into using only the v3 API, the requests that are currently supported in version 1 and version 2 will continue to be supported until the 2020.01 release.

Following version 2020.01, requests to the v1 and v2 versions of the API will no longer be supported.