Skip to content

Cross-source questions

Wiz and ServiceNow in one question

Ask questions that join Wiz issues and vulnerability findings with ServiceNow tickets and SLAs, with the query and lineage for each system in the answer.

Short answer

One question can span Wiz and ServiceNow, such as which critical Wiz issues have no open ServiceNow ticket. Nexatron queries each within the requesting user’s existing access, combines the results in an isolated step inside your workspace, and shows each source’s query. Wiz and ServiceNow are both available.

Example joined questions

Questions to ask. Each needs data from both systems; the answer depends on your own data and definitions.

  • Which critical Wiz issues older than 14 days have no open ServiceNow ticket?
  • How long did ServiceNow tickets raised for high and critical Wiz issues take to resolve last quarter, by assignment group?
  • Which assignment groups own the most open tickets for Wiz vulnerability findings with a fix available?
  • Which Wiz issues are resolved in Wiz while their ServiceNow ticket is still open?

Agree how a Wiz issue relates to a ServiceNow record before joining, such as the ticket that Wiz’s ServiceNow integration records on the issue, or the configuration item for the affected resource.

Check before you trust a joined answer

  • Both sides use user-level access: Nexatron inherits each user’s Wiz role and project scope and their ServiceNow ACLs, so two users can see different findings and tickets for the same issues.
  • One Wiz issue can have several tickets, and one ticket can cover several issues. Aggregate before comparing counts.
  • Resolved in Wiz and closed in ServiceNow are different events with different dates. Name the one the question means.

How a cross-source answer works

  1. Each system is queried within the person’s access

    Nexatron sends each part of the question to the system that holds it. Each system answers with user-level access: Nexatron inherits the requesting user’s existing permissions in that system.

  2. Results are joined inside your workspace

    Nexatron combines each system’s results in an isolated step inside your tenant when the question is asked. Nothing has to be consolidated into a warehouse first, and there is no pipeline to build.

  3. The queries come back with the answer

    The answer carries the generated query for each system and how many records matched, so a reviewer can check which system supplied which figure and repeat the check later.

  4. Joins follow links found at setup

    Nexatron joins on the links setup found between the systems, and says how many records matched. If no record matches, it says so and marks the figures as uncertain.

  5. Currencies are never added up as they are

    Amounts in different currencies are converted with one system’s own exchange rates where a usable rate source exists, and otherwise shown side by side with the reason.

  6. Longer than a single-source answer

    These answers take longer than single-source ones.

More on how it works and its limits: Cross-source analytics and the guide to cross-source analytics without a warehouse migration.