ZeroNetworksSegmentEventCollector
Integrates with Zero Networks Segment API to fetch and process audit and network events.
Network Security · Zero Networks Segment
Details
| ID | ZeroNetworksSegmentEventCollector |
|---|---|
| Provider | Zero Networks |
| Category | Network Security |
| From Version | 6.10.0 |
| Docker Image | demisto/python3:3.12.13.10116658 |
| Supported Modules | XSIAM |
README
This is the Zero Networks event collector integration for Cortex XSIAM.
Configure Zero Networks Segment Event Collector in Cortex
| Parameter | Description | Required |
|---|---|---|
| Server URL | True | |
| API Key | The API key to use for connection. | True |
| Fetch network events | False | |
| Network Activity Filters | Use filters to reduce the amount of events. | False |
| Maximum audit events to fetch | Maximum number of audit events per fetch. The default value is 10000. | False |
| Maximum network activities events to fetch | Maximum number of network activities events per fetch. The default value is 2000. | False |
| Trust any certificate (not secure) | False | |
| Use system proxy settings | False |
Commands
You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.
zero-networks-segment-get-events
Gets events from Zero Networks Segment.
Base Command
zero-networks-segment-get-events
Input
| Argument Name | Description | Required |
|---|---|---|
| should_push_events | If true, the command will create events, otherwise it will only display them. Warning: Using this argument may lead to duplicate events. Possible values are: true, false. Default is false. | Required |
| from_date | Date from which to get events. | Optional |
Context Output
There is no context output for this command.
Command Example
!zero-networks-segment-get-events from_date="2024-08-29T12:00:15.000Z"
Human Readable Output
Audit Events
| timestamp | auditType | destinationEntitiesList | details | enforcementSource | isoTimestamp |
|---|---|---|---|---|---|
| 1724928222479 | 1 | {“id”: “fake_id”} | {“rule”:”fake_rule”, “id”:”fake_id”} | 1 | 2024-08-29T10:43:42.479Z |
Network Activities Events
| timestamp | protocol | state | trafficType | dst | src |
|---|---|---|---|---|---|
| 1724924207581 | 6 | 2 | 1 | {“assetId”:”fake_dst”, “ip”:”1.2.3.4”} | {“assetId”:”fake_src”, “ip”:”1.1.1.1”} |
Configuration parameters
url— Server URL (required)credentials— (required)event_types_to_fetch— Event Types To Fetchnetwork_activity_filters— Network Activity Filtersmax_fetch_audit— Maximum audit events to fetchmax_fetch_network— Maximum network activities events to fetchinsecure— Trust any certificate (not secure)proxy— Use system proxy settings
Commands (1)
-
zero-networks-segment-get-eventsGets events from Zero Networks Segment.
### Zero Networks Segment Event Collector To interact with the Zero Networks API, you need to generate an API key. Follow the steps below to create and configure your API token. ### Generate an API Key #### 1. **Log in to the Zero Networks Portal** 1. Go to [portal.zeronetworks.com](https://portal.zeronetworks.com). 2. Log in using your email address. 3. Authenticate using the code sent to your email. #### 2. **Navigate to API Key Settings** 1. Go to `Settings` > `System` > `Integrations` > `API`. 2. Click on `Add new token`. #### 3. **Fill in the Required Fields** - **Token Name:** Provide a name for your token. - **Access Type:** - ***Read only:*** Allows only GET API requests. - **Expiry:** Set the token expiration period (1-36 months). #### 4. **Create and Copy the Token** 1. Click `Add` to create the token. 2. Copy the token immediately. **Note:** The token will not be displayed again after this step. If needed, the token can be regenerated at any time.