# Integrate Cisco Secure Network Analytics with
Google SecOps

This document explains how to integrate Cisco Secure Network Analytics (formerly
Stealthwatch) with Google Security Operations (Google SecOps).

> [!IMPORTANT]
> **Important:** Cisco acquired Stealthwatch and rebranded it as *Cisco Secure Network Analytics* . However, the integration for Cisco Secure Network Analytics in the Google SecOps platform uses the name *Stealthwatch*.

## Use cases

The **Cisco Secure Network Analytics** integration can address the following use
cases:

- **Retrieve security events**: Use Google SecOps capabilities to
  search and retrieve host security events from the Cisco Secure Network Analytics
  server during incident investigation.

- **Search for network flow data**: Use Google SecOps
  capabilities to search for network flows by IP address within a specified
  timeframe to understand host communication patterns.

## Integration parameters

The **Cisco Secure Network Analytics** integration requires the following
parameters:

| Parameter | Description |
|---|---|
| `API Root` | Required. The base URL of the Cisco Secure Network Analytics instance. The default value is `https://x.x.x.x`. |
| `Username` | Required. The username used to sign in to Cisco Secure Network Analytics. |
| `Password` | Required. The password used to sign in to Cisco Secure Network Analytics. |
| `Verify SSL` | Optional. If selected, the integration validates the SSL certificate when connecting to the Cisco Secure Network Analytics server. Disabled by default. |


For instructions about how to configure an integration in
Google SecOps, see [Configure
integrations](https://docs.cloud.google.com/chronicle/docs/soar/respond/integrations-setup/configure-integrations).

You can make changes at a later stage, if needed. After you configure an
integration instance, you can use it in playbooks. For more information about
how to configure and support multiple instances, see [Supporting
multiple instances](https://docs.cloud.google.com/chronicle/docs/soar/respond/integrations-setup/supporting-multiple-instances).

<br />

## Actions


For more information about actions, see [Respond to pending actions from your workdesk](https://docs.cloud.google.com/chronicle/docs/soar/overview-and-introduction/your-workdesk/respond-to-pending-actions-from-workdesk) and [Run a
manual action in your case](https://docs.cloud.google.com/chronicle/docs/soar/investigate/working-with-cases/what-actions-can-you-take-on-a-case#run-manual-action).

### Ping

Use the **Ping** action to test connectivity to Cisco Secure Network Analytics.


This action doesn't run on Google SecOps entities.

#### Action inputs

None.

#### Action outputs

The **Ping** action provides the following outputs:

| Action output type | Availability |
|---|---|
| Case wall attachment | Not available |
| Case wall link | Not available |
| Case wall table | Not available |
| Enrichment table | Not available |
| JSON result | Not available |
| Output messages | Available |
| Script result | Available |

##### Output messages

The **Ping** action can return the following output messages:

| Output message | Message description |
|---|---|
| `Successfully connected to the Stealthwatch with the provided connection parameters!` | The action succeeded. |
| `Error executing action "Ping". Reason: ERROR_REASON` | The action failed. Check the connection to the server, input parameters, or credentials. |

##### Script result

The following table lists the value for the script result output when using
the Ping action:

| Script result name | Value |
|---|---|
| `is_success` | `True` or `False` |

<br />

### Search Events

Use the **Search Events** action to retrieve a host's security events from Cisco
Secure Network Analytics for a given timeframe.

This action runs on the following Google SecOps entities:

- `IP Address`

#### Action inputs

The **Search Events** action requires the following parameters:

| Parameter | Description |
|---|---|
| `Time Frame` | Required. The number of hours, measured backward from the current time, to include in the search window for security events. |

#### Action outputs

The **Search Events** action provides the following outputs:

| Action output type | Availability |
|---|---|
| Case wall attachment | Not available |
| Case wall link | Not available |
| Case wall table | Not available |
| Enrichment table | Not available |
| JSON result | Available |
| Output messages | Available |
| Script result | Available |

### Search Flows

Use the **Search Flows** action to retrieve network flow data from Cisco Secure
Network Analytics for a given IP address and timeframe.

This action runs on the following Google SecOps entities:

- `IP Address`

#### Action inputs

The **Search Flows** action requires the following parameters:

| Parameter | Description |
|---|---|
| `Time Frame` | Required. The number of hours, measured backward from the current time, to include in the flow search. |
| `Limit` | Required. The maximum number of flow records to retrieve from Cisco Secure Network Analytics. |

#### Action outputs

The **Search Flows** action provides the following outputs:

| Action output type | Availability |
|---|---|
| Case wall attachment | Not available |
| Case wall link | Not available |
| Case wall table | Not available |
| Enrichment table | Not available |
| JSON result | Available |
| Output messages | Available |
| Script result | Available |

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)