availability

Deployment: Invicti Platform on-demand, Invicti Platform on-premises

Acunetix on-premises upgrade reference

This document provides a breakdown of what's carried over and what isn't when moving from Acunetix on-premises to Invicti Platform.

For the step-by-step upgrade procedure, refer to the Moving from Acunetix on-premises to Invicti Platform document.

What's carried over

The following sections list what's carried over from Acunetix on-premises, grouped by area.

Users and access

• Root account and child users (including their passwords)
• User profile settings
• User notification settings
• User groups (teams)
• RBAC settings
• User access settings
• SSO settings - the redirect URL needs to be reconfigured in Invicti Platform and reactivated manually; SSO user permissions are retained

Scanning configuration

• Targets (including target settings, LSRs, BLRs, and import files)
• Target groups
• Recurring and future scans
• Discovery settings
• Scan profiles
• Excluded hours
• Internal scanning agent configuration

Integrations

• WAF settings
• GitLab, GitHub, Azure Boards
• Jira integration is carried over with the following limitations:
  • Only HTTP Basic Token authentication is supported. Integrations using other authentication methods need to be updated after the upgrade.
  • The fields in Invicti Platform and Acunetix aren't identical. Review the integration after the upgrade completes.

What isn't carried over

• Audit events
• Notification (bell) items
• Paused scan status
• Past scans (including HTTP request/response data and scan activity)
• Issue tracker integrations with Bugzilla, Mantis
• Vulnerabilities
• Reports

---

Need help?

Invicti Support team is ready to provide you with technical help. Go to Help Center