Skip to content

Commit cfe352c

Browse files
[SAASINT-5085] DDS: Cato Networks: Crawler Integration v1.0.0 (DataDog#22152)
* Add Cato Networks crawler integration without assets * Add Cato Networks integration with assets * Resolve CI Failures * Added dashboard screenshots * Address review comments * Update log pipeline * Update the README related to AWS configuration * Rename panel name
1 parent 188dcce commit cfe352c

16 files changed

Lines changed: 6663 additions & 18 deletions

cato_networks/README.md

Lines changed: 54 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,75 @@
1-
# Agent Check: cato-networks
2-
31
## Overview
42

5-
This check monitors [cato-networks][1].
3+
[Cato Networks][1] provides a single-vendor Secure Access Service Edge (SASE) platform that converges SD-WAN, global private networking, and a full network security stack into a cloud-based service.
4+
5+
This integration ingests the following logs:
6+
7+
- **Audit Logs**: These logs provide detailed information on admin actions performed within the system.
8+
- **Events**: These logs provide detailed insights into security, detection and response, connectivity, and system events within the Cato Networks platform.
9+
10+
Integrate Cato Networks with Datadog to gain insights into audit logs and events using pre-built dashboard visualizations. Datadog uses its built-in log pipelines to parse and enrich these logs, facilitating easy search and detailed insights. Additionally, the integration can be used for Cloud SIEM detection rules for enhanced monitoring and security.
611

712
## Setup
813

9-
### Installation
14+
### Audit Log Collection
15+
16+
#### Obtaining Client Credentials
17+
1. Log in to Cato Networks platform and navigate to **Resources** > **Service API Keys**.
18+
2. In the **Service API Keys** tab, click **New** and provide the following details:
19+
- Select the **Service Principal**.
20+
- Enter the **Key Name**.
21+
- Set the **API Permission** as **Downgrade to View**.
22+
- Set **Any IP** under the **Allow access from IPs** section.
23+
3. Click **Apply** button and copy the **Token**.
24+
4. Navigate to **Account** > **Account Info** and copy the **Account ID**.
25+
5. Identify your Cato Networks Region by checking the prefix of your URL:
26+
- `cc.us1.catonetworks.com` - us1
27+
- `cc.catonetworks.com` - Keep region as empty
28+
29+
#### Connect your Cato Networks Account to Datadog
30+
31+
1. Add your `Cato Account ID`, `API Token` and `Region`.
32+
| Parameters | Description |
33+
| ---------- | ---------------------------------------------- |
34+
| Cato Account ID | The account ID from your Cato Networks platform URL |
35+
| API Token | The API Token of your Cato Networks platform |
36+
| Region | The prefix from your Cato Networks platform URL |
37+
2. Click **Save**.
38+
39+
40+
### Event Log collection
41+
42+
#### Configure AWS S3 Bucket
43+
When configuring the AWS bucket, use **cato-networks** as the **S3 prefix**.
44+
For more information, see [Configuring the AWS S3 Bucket][2].
1045

11-
The cato-networks check is included in the [Datadog Agent][2] package.
12-
No additional installation is needed on your server.
46+
#### Set up event integration in CATO networks
47+
For more information on configuring the event integration in a CATO network, see [Adding Amazon S3 Integration for Events][3].
1348

14-
### Configuration
49+
#### Configure Datadog Forwarder
50+
See information on configuring the [Datadog Forwarder][4]. When configuring the Lambda Forwarder, set the environment variable **DD_SOURCE** to **cato-networks**.
1551

16-
!!! Add list of steps to set up this integration !!!
1752

18-
### Validation
53+
## Data collected
1954

20-
!!! Add steps to validate integration is functioning as expected !!!
55+
### Logs
2156

22-
## Data Collected
57+
The Cato Networks integration collects and forwards audit logs and events to Datadog.
2358

2459
### Metrics
2560

26-
cato-networks does not include any metrics.
61+
The Cato Networks integration does not include any metrics.
2762

2863
### Events
2964

30-
cato-networks does not include any events.
65+
The Cato Networks integration does not include any events.
3166

3267
## Troubleshooting
3368

34-
Need help? Contact [Datadog support][3].
69+
Need help? Contact [Datadog support][5].
3570

36-
[1]: **LINK_TO_INTEGRATION_SITE**
37-
[2]: https://app.datadoghq.com/account/settings/agent/latest
38-
[3]: https://docs.datadoghq.com/help/
71+
[1]: https://www.catonetworks.com/
72+
[2]: https://support.catonetworks.com/hc/en-us/articles/9726441847965-Integrating-Cato-Events-with-AWS-S3#h_01K06PD8YPXBZJH5P0BP625BB1
73+
[3]: https://support.catonetworks.com/hc/en-us/articles/9726441847965-Integrating-Cato-Events-with-AWS-S3#h_01K06PD8YP6JCM5618J4YYDFAS
74+
[4]: https://docs.datadoghq.com/logs/guide/forwarder/?tab=cloudformation
75+
[5]: https://docs.datadoghq.com/help/
Lines changed: 14 additions & 0 deletions
Loading

0 commit comments

Comments
 (0)