Integrations

Understand what each technology connects.

Inventory, reputation and logs bring different information to the team’s work. To choose the right connection, we start with the data and functions you need.

Three capabilities to assess separately

Receiving logs, synchronizing inventory and executing response actions are distinct capabilities. A connection for one function does not imply that the others are available.

The matrix describes the scope identified in the technical review. Activation in your environment and commercial availability are confirmed with OpenConnexio before adoption.

Sources and inventory connectors

On smaller screens, scroll the table horizontally to read all columns. With a keyboard, use Tab and the arrow keys.

Sources and inventory connectors
TechnologyCollected data or roleEnabled functionsPrerequisitesVerified availability
Microsoft Defender / IntuneDevices, software and vulnerabilities → ShadowThreat inventory.System and vulnerability context for analysis.Authorized access to service data and connection configuration.Inventory adapter identified. This does not automatically include other Microsoft services or Entra ID identity events.
AcronisResource inventory and status → ShadowThreat.View resources and their status in the operational context.Authorized service access and adapter configuration.Inventory adapter identified. Additional capabilities require separate verification.
UbiquitiEvents already collected in the Data Plane → inventory.Build inventory from available events.Compatible events available in the environment’s Data Plane.Event-derived inventory identified; this is not full network discovery.
Integrations are continually updated. If the technology you use is not listed, we also assess custom integrations based on your needs.

Reputation services

On smaller screens, scroll the table horizontally to read all columns. With a keyboard, use Tab and the arrow keys.

Reputation services
TechnologyCollected data or roleEnabled functionsPrerequisitesVerified availability
Editorial sourcesIndicators of compromise (IOCs) drawn from accredited editorial sources.Threat context to support the analyst’s assessment.Access to editorial sources and availability of IOCs.Coverage depends on the editorial sources and IOCs available.
APIVoidReputation request → service; result → analyst.Reputation context for IP addresses and domains, according to the configured service.Credentials, service quota and configured connection.Reputation role identified, separate from alert ingestion.
AbuseIPDBIP reputation request → service; result → analyst.Reputation information for queried IP addresses.Credentials, service quota and configured connection.Reputation role identified; this does not imply alert ingestion or IP blocking.

Ingestion protocols and channels

On smaller screens, scroll the table horizontally to read all columns. With a keyboard, use Tab and the arrow keys.

Ingestion protocols and channels
TechnologyCollected data or roleEnabled functionsPrerequisitesVerified availability
WatchGuardFirebox traffic, event and alarm logs forwarded to the Data Plane via Syslog.Firebox log ingestion for searches and analyst review.Syslog forwarding enabled, a reachable collector and a parser compatible with Fireware messages.Fireboxes support Syslog forwarding; reception and parsing in ShadowThreat require validation for the device model and Fireware version.
FortinetFortiGate firewall logs forwarded to the Data Plane via Syslog.FortiGate log ingestion for searches and analyst review.A configured Syslog destination, logging enabled and a parser compatible with the FortiOS version.Channel configuration identified; reception and parsing require validation for the device model and FortiOS version.
SyslogProtocol for sending logs from compatible firewalls, servers and devices to the Data Plane.Centralized log collection and searches across enabled sources.A configured source, collector address and port, agreed transport and format, and a validated parser.Channel configuration identified; reception and compatibility require validation for each source and format.
Integrations are continually updated. If the technology you use is not listed, we also assess custom integrations based on your needs.

Multi-customer organization

A clear context for every piece of information.

Partner, customer and environment identify the working scope. Roles and permissions determine which data and activities each person can access.

Technical detail: Control Plane and Data Plane

Control Plane: console, access and case management

Includes operational coordination, roles, configuration and case metadata. Incident and task management extends beyond source configuration.

Data Plane: log collection, processing and search

Handles log flows and searches within the intended scope. Component deployment and actual connections depend on the installation.

FAQ

How do we connect your tools?

Our firewall isn’t on the list. How can I find out if we can connect it?

Tell us the make and model and which events you’d like to see in ShadowThreat. You might be interested in sign-in attempts or blocked connections. We’ll check what your firewall can send and whether we can read it using Syslog, an existing connector or a custom integration.

Our IT team can already forward logs over Syslog. How do we check they’re coming through correctly?

We’ll check the log destination and the device’s log format with your team. Then we’ll look up a test event in ShadowThreat. For example, if the firewall logs a blocked connection, we’ll find that event and check its timestamp and addresses against the original log.

If I connect our firewall to ShadowThreat to read its logs, can I also block an IP address from there?

With Syslog, your firewall sends events to ShadowThreat for you to review. To block an IP address from ShadowThreat, you need a connection that can also send commands to the firewall. Tell us the make and model and we’ll check which actions your setup supports and what permissions they require.

An alert mentions an IP address I don’t recognise. Can I check its reputation?

Yes, if a reputation service such as AbuseIPDB is configured in your environment. The analyst can check the available reports on that address and compare them with what happened on your network before deciding what to do next.

See ShadowThreat in your environment

Want to know which tools we can connect?

Tell us briefly about your environment. You do not need to prepare data or technical documentation—we will start with the information you already have.