Microsoft Defender for Cloud Apps

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 / Microsoft Defender for Cloud Apps

Microsoft Defender for Cloud Apps

Microsoft Defender for Cloud Apps delivers protection for SaaS applications, helping customers monitor and protect their cloud apps and cloud app data. Defender for Cloud Apps also shows risks to your environment from SaaS app usage and resources and gives control of what’s being used and when.

The CI Synchronizer connector for Defender for Cloud Apps allows organisations to manage Cloud Applications in their ServiceNow CMDB by synchronising Cloud Apps as Business Application CIs. Optionally, CI Synchronizer can also create relationships between User records (in the ServiceNow User Table) and the Business Application CIs.

This connector allows organisations to rapidly implement Service Management practices for their automatically discovered and maintained Cloud Applications and reduces operational risks by visualising which users are actively using which applications.

Generate Business Applications from Defender Cloud Applications

CI Synchronizer automatically creates new CIs, or correlates to existing CIs, for each Cloud Application registered in Microsoft Defender for Cloud Apps.

Understand Which Users Actively Use Which Business Applications

CI Synchronizer can also automatically create CI-to-CI relationships (dependency records) between User records in ServiceNow User Table) and the Business Application CIs. This allows organisations to visualise which users are actively using which Business Applications using dependency maps within ServiceNow .

Relationships

Roadmap Connectors

Meraki

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.