Change Automation and Orchestration

SecureChange Supports Provisioning to Cisco Nexus Devices

You can provision Cisco Nexus Access Request changes in SecureChange in a manual or auto step. This capability saves time, prevents misconfigurations, and enables end-to-end zero-touch automation.

Azure Firewalls in Access Requests and Verifier

You can now include Azure Firewall devices in Access Request tickets in topology mode, where they will be identified and suggested as targets. You can close the ticket automatically if the access already exists in the network. Additionally, Verifier can close the ticket once the policy change has been implemented correctly, saving the need to re-open the ticket and check manually. The result is increased agility and saving of operational time.

Automation Support for Check Point FQDN

Check Point users can now leverage SecureChange automation tools, such as target selection, Verifier, and Designer, to automate access requests that contain FQDNs. This change speeds processes and prevents errors.

Commit Tufin-only Changes for Panorama Devices

You can configure Designer to commit changes to Panorama devices made by the Tufin user without committing changes made by other Panorama users. This allows more granular auditing of the change process.

Designer Redesign API

A new API allows you to automate a redesign action in Designer, which is especially useful when a new revision has arrived and makes the designer suggestion obsolete. This can save time and shorten business SLAs for processing network changes.

Ticket Creation API for Multiple Devices/Policies

You can now use API POST to create tickets with rules from multiple devices or policies in Rule Modification, Rule Decommission, or Rule Recertification workflows.

Trigger Commit Now in SecureChange Ticket

You can now use an API to run Commit Now for a specific device in a SecureChange ticket. Script writers can use this API to automate retries of Commit Now, or to implement customized change windows for a given device.

Selective Devices Update API

It is now possible to schedule, trigger, or retry the provisioning process programmatically per device in the ticket, automating the provisioning step for all SecureChange workflows. This can increase efficiency and reduce the risk of human error.