Configuring Context Integrations
About Context Integrations
Context integrations provide enriched asset context to Netography Fusion from third-party products. This is done by reading asset information from the external product (generally via an API) and then adding asset information as context Labels associated with the asset's IP address.
Types of context integrations
- SaaS - Directly integrated into Netography Fusion - can only be configured and deployed in the Netography Fusion SaaS.
- NetoFuse - NetoFuse modules can be deployed as a context integration in the Netography Fusion Portal or deployed locally (as a container or software package) in your environment. Local deployments are useful for on-prem integrations or to maintain control of the configuration, connection, and credentials to a third-party data source locally.
- Cloud Function - AWS, Azure, and GCP also support deploying a cloud function via Terraform as part of the Netography cloud onboarding automation. In this case, context enrichment information is gathered from within your cloud environment, and the function then uses a Fusion API key to make an outbound connection to Fusion to send it to the API. No inbound access to your cloud accounts is used for context enrichment when using a Cloud Function.
To understand more about the difference between Context Integrations and NetoFuse modules, see About NetoFuse.
Available Context Integrations
Cloud Providers
| Vendor | Product | Type |
|---|---|---|
| Amazon | Amazon Web Services | SaaS, Cloud Function |
| Google Cloud Platform | Google Cloud Platform | SaaS, Cloud Function |
| IBM | IBM Cloud | SaaS |
| Microsoft | Microsoft Azure | SaaS, Cloud Function |
| Oracle | Oracle Cloud Infrastructure | SaaS |
Asset Management / Device Inventory
| Vendor | Product(s) | Type |
|---|---|---|
| Axonius | Axonius Platform | NetoFuse |
| Device42 | Device42 | NetoFuse |
| RunZero | RunZero | NetoFuse |
| Tanium | Tanium | NetoFuse |
Cloud Security
| Vendor | Product | Type |
|---|---|---|
| Wiz | Wiz | NetoFuse |
Endpoint Protection Platforms
| Vendor | Product | Type |
|---|---|---|
| Crowdstrike | CrowdStrike Falcon Discover CrowdStrike Falcon Protect | SaaS |
| Microsoft | Microsoft Defender for Endpoint Microsoft Defender XDR | NetoFuse |
| SentinelOne | SentinelOne | SaaS |
Industrial Cybersecurity (OT) Security Platforms
| Vendor | Product | Type |
|---|---|---|
| Claroty | Claroty CTD Claroty EMC | NetoFuse |
Vulnerability Management
| Vendor | Product | Type |
|---|---|---|
| Tenable | Tenable Vulnerability Management | NetoFuse |
Generic Integration Capabilities
These options provide additional methods to integrate asset context from any data source.
| Method | Formats Supported | Type |
|---|---|---|
| Amazon S3 | CSV files in Netography label format | SaaS |
| Custom NetoFuse Module | All Formats | NetoFuse |
| Local File NetoFuse Module | CSV files in any format CSV files in Netography label format JSON | NetoFuse |
| NetoFuse upload command | CSV files in any format CSV files in Netography label format JSON | NetoFuse |
| Netography Fusion API Reference | CSV files in Netography label format JSON | REST API |
Adding a Context Integration
In the Netography Fusion Portal:
- Select Settings at the bottom of the left-hand navigation menu
- Select Context Integrations in the Data Management section.
- Select the Add Integration button.
- Select a context integration from the list provided.
- Follow the configuration steps in the documentation for the context integration you selected.
Updated 4 months ago