Configuring Cato Networks Connectors

Connectors allow Stellar Cyber to collect data from external sources and add it to the data lake. You create one instance of this connector for each Cato Networks account you want to monitor.

Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the collector is exceeded.

Connector Overview: Cato Networks

Capabilities

  • Collect: Yes

  • Respond: No

  • Native Alerts Mapped: No

  • Runs on: DP

  • Interval: Configurable

Collected Data

Content Type

Index

API
Security  Syslog

This connector uses a single API call to retrieve records that are then parsed for the event_type field to identify the content type. For the content types configured in the connector, the records are saved and tagged with the appropriate msg_class (see Locating Records, below).

https://api.catonetworks.com/api/v1/graphql2

using these parameters:

  • timeframe: Duration of data to collect

  • marker: Used to ensure only new events are retrieved each time.

 

 

 
Connectivity
Sockets Management
Routing
System
Audit

Domain

https://api.catonetworks.com/

Response Actions

N/A

Third Party Native Alert Integration Details

N/A

Required Credentials

Collection requires a Cato Networks Account ID with an Editor role, an API key, and the account must also be enabled to Allow use Cato-Events API.

Locating Records

Use the following fields as a guide to query for records:

  • msg_origin.source: cato_networks

  • msg_origin.vendor: cato_networks

  • msg_origin.category: sase

  • msg_class: cato_security, cato_connectivity, cato_sockets_management, cato_routing, cato_system, cato_audit

               Let us know if you find the above overview useful.

Adding a Cato Networks Connector

To add a Cato Networks connector:

  1. Enable Cato API access
  2. Add the connector in Stellar Cyber
  3. Test the connector
  4. Verify ingestion

Enabling Cato API Access

As part of this procedure, you specify the credentials of an account on the Cato server that will be used to retrieve data.

  1. Log in to your Cato Networks account as the user you want to monitor.

  2. Display the user's profile to verify the account type. Click the user button at the top right of the console, and then clicking My Profile. The user role must be Editor.

  3. Obtain the Account ID by noting the URL that displays when the console loads.

  4. Navigate to Administration > API Management.

  5. Click the button for a New key.

  6. In the dialog that displays, enter an identifying Name for the key, then click Apply.

  7. When the key is created, a dialog with the value displays. Click the Copy button to copy your API key and ensure you save it to a secure location.

    After you close the dialog you can no longer access the value of the API key.

  8. Click OK to close the API key dialog.

  9. When the list of keys re-displays, locate the toggle for Use Cato-Events API is Enabled.

Adding the Connector in Stellar Cyber

To add the Cato Networks connector in Stellar Cyber:

  1. Log in to Stellar Cyber.

  2. Click System | Integration | Connectors. The Connector Overview appears.

  3. Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

    The asterisk (*) indicates a required field.

  4. Choose SASE from the Category drop-down.

  5. Choose Cato Networks from the Type drop-down.

  6. For this connector, the supported Function is Collect, which is enabled already.

  7. Enter a Name.

    This field does not accept multibyte characters.

  8. Choose a Tenant Name to specify which tenant is permitted to use this connector on Stellar Cyber.

  9. Choose the device on which to run the connector .

  10. (Optional) When the Function is Collect, you can create Log Filters. For information, see Managing Log Filters.

  11. Click Next. The Configuration tab appears.

    The asterisk (*) indicates a required field.

  12. Enter the Account ID you obtained from the Cato Networks login, above.

  13. In the API Key field, enter the value you saved above.

  14. Enter the Interval (min).This is how often the logs are collected.

  15. Select the Content Type:

    • Audit Log
    • Connectivity
    • Routing
    • Security
    • Sockets Management
    • System

  16. (Optional) This Initial Marker field is used to adjust the ingestion start point in cases where the volume of Event data to retrieve is extremely large. (The default duration Cato Network’s API retrieves is 7 days of Event data.) The API supporting this field requires an encoded base64 string (combining topic, partition, and offset) that is unique to your active events queue. Stellar Cyber has provided this field for use only by advanced API users of Cato Networks who are already familiar with retrieving this marker value in their environment. (This marker does not apply to Audit type data.)

  17. Click Next. The final confirmation tab appears.

  18. Click Submit.

    To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.

The new connector is immediately active.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).

For connectors running on a sensor, Stellar Cyber recommends that you allow 30-60 seconds for new or modified configuration details to be propagated to the sensor before performing a test.

  1. Click System | Integrations | Connectors. The Connector Overview appears.

  2. Locate the connector that you added, or modified, or that you want to test.

  3. Click Test at the right side of that row. The test runs immediately.

    Note that you may run only one test at a time.

Stellar Cyber conducts a basic connectivity test for the connector and reports a success or failure result. A successful test indicates that you entered all of the connector information correctly.

To aid troubleshooting your connector, the dialog remains open until you explicitly close it by using the X button. If the test fails, you can select the  button from the same row to review and correct issues.

The connector status is updated every five (5) minutes. A successful test clears the connector status, but if issues persist, the status reverts to failed after a minute.

Repeat the test as needed.

ClosedDisplay sample messages...

Success !

Failure with summary of issue:

Show More example detail:

 

Verifying Ingestion

To verify ingestion:

  1. Click Investigate | Threat Hunting. The Interflow Search tab appears.

  2. Change the Indices to Syslog.

  3. Search for msg_origin.source: cato_networks.