Loading

Cato Networks Integration for Elastic

Version 0.1.0 (View all)
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) API
Minimum Kibana version(s) 9.1.0
8.19.0
The Cato Networks integration v0.1.0 is in technical preview

To use pre-release integrations, go to the Integrations page in Kibana, scroll down, and toggle on the Display beta integrations option.

Cato Networks is a cloud-native, global SD-WAN provider that delivers a secure, optimized, and agile global network for businesses of all sizes. Cato's cloud-based platform converges multiple network and security functions into a unified solution that includes SD-WAN, network security, cloud security, and secure access service edge (SASE) capabilities.

The Cato Networks integration for Elastic collects Events Feed and Audit Feed from the API and visualizes them in Kibana.

The Cato Networks integration is compatible with graphQL API version v1.

This integration periodically queries the Cato Networks GraphQL API to retrieve logs.

This integration collects log messages of the following type:

  • Events Feed: Collects Events Feed logs from the Cato Networks API (endpoint: /api/v1/graphql2).

  • Audit Feed: Collects Audit Feed logs from the Cato Networks API (endpoint: /api/v1/graphql2).

Audit data stream: The audit dataset contains administrative and configuration activities from the Cato Management Application (CMA), which manages the broader Cato SASE Cloud Platform.

Integrating Cato Networks with Elastic SIEM provides centralized visibility into both administrative activities and security events through the Audit and Event data streams, enabling efficient monitoring, investigation, and compliance tracking within Kibana dashboards.

The Audit data stream delivers insights into configuration changes, administrative actions, and policy modifications. Dashboards highlight metrics such as Audit by Event Type over Time and Top Admins, helping administrators monitor operational changes, track privileged activity, and support governance requirements.

The Event data stream focuses on security monitoring and threat investigation. Dashboards provide views such as Top Hosts and Events over Time, enabling analysts to detect activity spikes, identify suspicious behavior, and monitor evolving threat patterns across the environment.

Interactive filtering controls allow users to drill down across dimensions such as event type, affected models, geographic location, traffic direction, threat type, and authentication type. This supports streamlined compliance auditing, faster investigations, and a unified operational view across administrative and security data.

To collect data through the Cato Networks API, you need to provide an API Key and Account ID. Authentication is handled using the API Key, which serves as the required credential.

  1. Log in to the Cato Management Application.
  2. In the navigation menu, click ResourcesAdmin API Keys.
  3. Click New. The Create API Key panel opens.
  4. Provide a descriptive name for the API key (for example, "Elastic Integration").
  5. Select the appropriate permissions for the API key.
  6. Click the button to copy the API Key that is generated by the CMA and save it to a secure location.
  7. Note your Cato Networks Account ID, which can be found in the Cato Management Application under AdministrationAccountGeneral Info.
Note

For more information on generating API keys, refer to the Generating API Keys for the Cato API.

This integration supports both Elastic Agentless-based and Agent-based installations.

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to Agentless integrations and the Agentless integrations FAQ.

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

  1. In the top search bar in Kibana, search for Integrations.

  2. In the search bar, type Cato Networks.

  3. Select the Cato Networks integration from the search results.

  4. Select Add Cato Networks to add the integration.

  5. Enable and configure only the collection methods which you will use.

    • To Collect Cato Networks logs via API, you'll need to:

      • Configure URL (the base URL of the Cato Networks API, for example, https://api.catonetworks.com).
      • Configure Account IDs.
      • Configure API Key.
      • Adjust the integration configuration parameters if required, including the Interval, Preserve original event etc. to enable data collection.
  6. Select Save and continue to save the integration.

  1. In the top search bar in Kibana, search for Dashboards.
  2. In the search bar, type Cato Networks.
  3. Select a dashboard for the dataset you are collecting, and verify the dashboard information is populated.

For help with Elastic ingest tools, check Common problems.

  • The Cato Networks EventsFeed API enforces rate limiting of 100 requests per minute (approximately 1.66 requests per second). For detailed information, refer to the official documentation.

  • The Cato Networks AuditFeed API enforces rate limiting of 5 requests per minute (approximately 0.083 requests per second). For detailed information, refer to the official documentation.

  • If you encounter rate limiting errors, consider decreasing the Resource Rate Limit parameter or increasing the Interval value.

  • The EventsFeed API operates with a time-based data retrieval mechanism. On the initial API call, no data will be returned as it establishes a baseline marker. Subsequent requests will retrieve events that occurred between the current request and the previous one. Due to this behavior, data ingestion begins only after the first interval has elapsed, so it is expected to have a delay equal to the configured interval before seeing the first events in Elasticsearch.

  • The Cato Networks EventsFeed API uses a marker-based pagination with a 3-day expiration period. If the Elastic Agent or Elasticsearch instance experiences downtime exceeding 3 days, the marker becomes invalid and any events generated during this outage will be permanently lost and cannot be recovered.

  • The Cato Networks API rate limit quota is shared across all integration instances that use the same API credentials, which can impact data collection when running multiple instances simultaneously.

  • The Cato Networks AuditFeed API contains certain fields with inconsistent data types across different events. These type conflicts can cause indexing failures in Elasticsearch, resulting in discrepancies between the document count stored in Elasticsearch and the total number of events returned by the API. Users can observe that not all events from the API response are successfully indexed due to these type mapping conflicts.

For more information on architectures that can be used for scaling this integration, check the Ingest Architectures documentation.

This input is used in the integration:

This integration uses the following Cato Networks API:

Events Feed: Cato Networks Events Feed API documentation. Audit Feed: Cato Networks Audit Feed API documentation.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.