Palo Alto SD-WAN

nav.hidden, nav ul [x-cloak], nav ul li ul { display: block !important; } This website requires Javascript for some parts to function properly. Your experience may vary.

Cookie Settings

This site uses cookies that need consent.

Functional First party cookies are needed for the website to function. These can't be turned off.

Products / Palo Alto SD-WAN

Palo Alto Networks' Prisma SD-WAN is a cloud-delivered service that implements app-defined, autonomous SD-WAN to help you secure and connect your branch offices, data centers and large campus sites.

The CI Sync Palo Alto SD-LAN connector elicits multiple virtual SD-WAN objects from your Palo Alto SD-WAN environment to create and maintain corresponding configuration item records in your Configuration Management Database (CMDB).

Simple setup, simple synchronization

The CI Sync Palo Alto SD-WAN connector is simple to setup via the CI Sync multi-source agent. Once the source connection is defined synchronization is nothing more than a few clicks in the CI Sync UI. The complexity of your SD-WAN environment is entirely obfuscated by the CI Sync integration logic which results in automated CI creation and update when the SD-WAN resources change.

Dynamically Generates CI-to-CI Relationships

CI Sync derives multiple virtual relationships from the underlying virtual records held within your Palo Alto SD-LAN configuration.

Delta synchronization

CI Sync’s delta synchronization features work with the Palo Alto SD-WAN connector creating a highly efficient method of keeping your SD-LAN resources aligned to the CIs in your CMDB.

SD-WAN Topology and Objects

The CI Sync engine natively understands the Palo Alto SD-WAN objects including tenants, sites and elements. This allows CI Sync to intelligently generate CIs and CI relationships which can be leveraged by your ITIL processes based on the SD-WAN data held in the CMDB.

Relationships

Roadmap Connectors

AirWatch (Workspace ONE)

Lansweeper Cloud (Native)

Meraki

Microsoft Defender

SentinelOne

Tanium

Frequently Asked Questions

CI Synchronizer Professional Edition provides a streamlined, out-of-the-box solution for businesses looking for efficient, hassle-free CMDB synchronisation without the need for extensive customisation.

CI Synchronizer Enterprise Edition offers advanced customisation and high-volume data handling capabilities, perfect for organisations with complex synchronisation needs and custom configuration requirements.

Compare CI Synchronizer editions

Many! Check out each source connector page for details of the supported assets and other records.

Yes. CI Synchronizer can detect which source records have changed since the previous synchronisation job and only sync the newly changed source data.

Throughput is affected by factors outside of the control of CI Synchronizer, however we see a typical throughput of between 200,000 and 400,000 records per hour (and even higher rates are possible).

Yes. CI Synchronizer has a highly customisable rules engine. Amendment of some Standard (simple) default Data Sync Rules can be performed via the CI Sync Web User Interface and supported with Knowledge Base articles. Amendment of Advanced Data Sync Rules or creation of Custom Data Sync Rules requires an “Extended Implementation and Ongoing Support Plan” available at an additional cost to your CI Sync Subscription Plan.

Visit the Support page for details on amending the Default CI Sync Data Sync Rules relative to the support plan (including no plan) offered by Syncfish.

Yes. Please fill and submit the Book a Demo form to set up a time to meet with one of the Syncfish team.

No. Each customer is provisioned with a dedicated CI Synchronizer instance.

Ultimately the customer decides, however Syncfish recommends hosting each customer instance physically close to the location of their ServiceNow instance (for best performance). It can be hosted in most/all Azure Regions globally (it is still hosted/managed/maintained by Syncfish, but the customer decides which geography it is physically located in).

No. The source asset data (read from the relevant source system by one of the CI Synchronizer connectors) is transited through your dedicated CI Synchronizer instance then deleted after it’s been processed into ServiceNow.