Acunetix 360 On-Demand

The internal agent’s current version is 2.0.2.128.

IMPROVEMENTS

• Added a behavior that the system sets the default policies of a website group to a website for the Scheduled Group Scans and Group Scans. The system sets the default policies only if users select the default policies on the General Settings page and then assign these policies to a website group on the policies page.
• Added an information message for updating the agent’s status.

FIXES

• Fixed an issue that set the wrong default scan and report for the Scheduled Group Scan and Group Scan if there is a scan profile.
• Fixed an issue that prevented a user from editing the default scan policy.
• Fixed an issue that removes the client certificate from the Form Authentication page if the related scan profile is updated.
• Fixed an issue that occured when the same vulnerability was sent to Jira’s endpoint more than once.
• Fixed a mismatching type issue on /scanprofiles/list API response model.

FEATURES

• Introduced the default scan and report policy, so you can set default policies for your team.

IMPROVEMENTS

• Added the tagging filtering to the Scan Profiles.
• Added the license error to the scans that were scheduled by users whose licenses are expired.
• Added the fixed confirmation date to the issues API endpoint so that you can better track your team’s remediation efforts.
• Added null check for application names during comparison with the vulnerability database.

FIXES

• Fixed the first seen date issue that appeared differently on the user interface and the scan report.
• Fixed the Url Rewrite Excluded Links API call by adding null response back to that call’s responses.
• Fixed a bug that prevents serialized integration information from being decrypted in some issues.
• Fixed an issue that displays the mistaken path in the trend matrix reports when different paths are scanned.
• Fixed a bug returning the 500 Error when an issue is updated.

This update includes changes to Internal Agents. The internal agent’s current version is 2.0.2.125.

IMPROVEMENTS

• Improved the Login Banner Warning feature so that users cannot access any resources on Acunetix 360 until they select the Accept, Continue button.
• Add the Environment field to the DefectDojo integration.
• Added the Export to CSV button on the Manage Members page so that you can download all your team members to your environment.

FIXES

• Fixed a bug that prevented the scan profile of a deleted website from being removed. Now, when users delete a website, the related scans, including scan profile, are also deleted.
• Fixed an issue that prevent the scan from being canceled.
• Fixed the missing ScanTaskProfile field by adding it back to scan API call responses.
• Fixed a bug that prevents members and teams from being deleted if they have been assigned to website groups.
• Fixed a bug that allows the API member edit endpoint which accepts less than 15 characters for the administrator’s password.
• Changed the permission to view reports from Add/Edit Scan to the View Report.
• [INTERNAL AGENTS] Changed Agent request time interval to 60 seconds.
• [INTERNAL AGENTS] Fixed a bug that prevents an agent from scanning a new website if the previous scan was canceled.

This update includes changes to Internal Agents. The internal agent’s current version is 2.0.2.123.

FEATURES

• Introduced a login banner warning. The banner displays security and legal notices to users accessing the system.
• Added pre-scan validations so that Acunetix 360 can automatically choose TLS protocol.

IMPROVEMENTS

• Added the tag filtering to the Recent Scans page.
• Added the tag limitation. Users cannot add more than 20 tags.
• Added the date range filter to the global dashboard. Thanks to this improvement, users can filter scan data according to the selected time range.
• Added website and website groups information to Jira integration. When users send an issue to Jira via Acunetix 360, website and website groups information, if any, appears in that ticket.
• Added a check for the Trend Matrix Report to ignore null records in the database.
• Improved the method to query known vulnerabilities in Acunetix 360.
• Changed SCIM response status code from 400 to 409 when the same email address is submitted twice.
• Added a 400 Error message in the SCIM response status code when a user tries to change its email to a username.
• Updated the error message when deleting the website during a PCI scan.
• Added the severity level icons to the websites listed on the Websites’ page.

FIXES

• Fixed the retest retry limit if the base scan is not loaded.
• Fixed an email notification error sent to guest users which showed a “Failed – Unable to load scan session” error in the scheduled scans although the scan was successful.
• Fixed a NullReferenceException thrown while checking target URL in the New Scan page.
• Fixed password autocomplete issue in the form authentication saved in a scan profile.
• Fixed an error that prevents the URL Rewrite rule from being updated in the saved scan profile.
• Fixed an error that prevents scan tags from being shown while creating a scheduling scan.
• [INTERNAL AGENT] Fixed the Ignore SSL Certificate issue that prevents internal agents from being auto-updated.
• [INTERNAL AGENT] Improved the performance of security check on cases when multiple checks are running concurrently.

This update includes changes to Internal Agents.

IMPROVEMENTS

• Added the missing information that was not exported to YouTrack, Asana, and Github in the case of Frame Injection vulnerability.
• Added new property to /scans/list API endpoint to distinguish between scans.
• Added paging to auditlogs/export API endpoint.
• Added the group by parameter to the Technology dashboard.
• [INTERNAL AGENT] Increased the agent’s polling time to 30 seconds.

FIXES

• Fixed a bug that prevents updated scan profiles of the Scheduled Scans from being synchronized with these scheduled scans.
• Fixed a space issue in GitLab integration that prevents integration to be completed successfully.
• Fixed the deserialization issue that threw bad requests in some scans.
• Fixed the issue of returning null response by removing WebsiteGroupId requirement from UserRoleWebsiteGroupMapping API endpoint.