Your questions, answered

The end-user continues working with ServiceNow, while ebridge works behind the scenes to collate information from all your enterprise applications. Your style of work doesn’t change – you just have more information at your disposal.

See our list of integrations to see which applications ebridge can pull in data from.

We need one of your IT resources for a short period of time, and ebridge will then get your application deployed to ServiceNow within 72 hours.

ebridge has custom integrations, so no matter which application your business uses, you can connect it to ebridge and ServiceNow.

Of course! Schedule a demo or get in touch to see how to implement ebridge into your ServiceNow environment and the areas it can save you time and money.

ebridge is a product from Champions Solutions Group, a professional services provider who has created innovative IT solutions for over 35 years. Visit the Champions Solutions Group website to learn more.

No. ebridge utilizes the ServiceNow MID Server as the secure connection into the client’s environment.

We do not change the base tables/CI’s in ServiceNow. We use custom tables to relate data to the base CI data in ServiceNow.

With the BigFix girder, much of your day-to-day BigFix workflow can be performed in ServiceNow. High level, complex tasks and configuration will likely be performed within the BigFix console.

We’d love to hear about your tools and how your organization utilizes them. Our rapid deployment methodology allows us to develop new integrations in 30 days or less in many cases.

We’re able to analyze your data and determine which integration dataset is the most comprehensive and accurate for your environment.

We enhance ServiceNow’s Discovery module. CORE’s base detection functionality meets and exceeds the level of data provided by ServiceNow Discovery.

ebridge can populate the ServiceNow (or equivalent) CMDB in the same manner as Forescout eyeExtend. In addition, ebridge intelligently communicates with other 3rd party girder integrations (SIEM, Monitoring, Lifecycle Management) to provide the ultimate in environmental awareness and single pane of glass management.

Yes, but we do not overwrite any of the base CI’s in ServiceNow.

Javascript/Python/PowerShell – Depending on the application girders deployed.

Scheduled and configurable depending on use case and compliance requirements.

ebridge utilizes the MID Server as the connection into the organization’s environment.

Yes, in multiple formats.

No. All ebridge tables are custom and provide relational data.

Yes, in the ServiceNow System Logs. Logs are archived weekly and archived data is purged every 21 days.

All ebridge data uses a custom message prefix within the log for quick and efficient troubleshooting.

Yes. Our CORE girder is able to ingest software installed on endpoints.

We coalesce (via scripting and ServiceNow settings) much of our data ingestion for de-duplication.

With the appropriate girders and configuration yes. Tell us how you monitor today and we’ll develop a solution to bring that information into ServiceNow!

Absolutely. And ebridge’s extensive datapoints allow you to create more meaningful and granular data than you may have previously thought possible.

This is optional and can be configured to meet your business case.

ebridge applications are able to identify and therefore classify the unique Cis associated with virtual machines. ebridge utilizes vCenter and UUIDs to ensure correctness of the VM.

The relationships are ready-built and are tagged as an “ebridge source” should you need to investigate the additional Cis that we discover.

Absolutely. All ebridge applications are built to adhere to this standard and utilize ServiceNow’s IRE (Identification and reconciliation engine.)

Our ebridge integration is tight. With the CMDB health tools in ServiceNow you have visibility into this data and can tune your ebridge application to address how stale Cis discovered by ebridge are addressed.