Security Cloud Control Endpoint Target

Last updated
Save as PDF

A Security Cloud Control Endpoint target connects Cisco Workflows to Security Cloud Control (SCC) and Cloud-Delivered Firewall Management Center (Cloud-Delivered FMC) APIs exposed through SCC. The target stores endpoint details referenced by Generic SCC API Request and the generated SCC and Cloud-Delivered FMC workflows.

Before You Begin

Make sure you have:

Access to Security Cloud Control and the APIs needed by your workflows.
The hostname and Base API pairing for your SCC environment.
A saved Security Cloud Control Credentials account key.

Creating Security Cloud Control Targets

In Workflows, go to Automation > Targets.
Select New Target.
Select Security Cloud Control Endpoint.
Enter a display name and description.
Select a saved Security Cloud Control Credentials account key.
In Connection, enter the Protocol, Host, Port, and Base API.
Select Save.

Target Fields

Field	Required	Description
Protocol	Yes	HTTPS only.
Host	Yes	Enter only the SCC hostname, without a protocol, port, or path. Most commercial environments use `api.<region>.security.cisco.com`; the default is `api.us.security.cisco.com`. SCC management or FedRAMP environments use `manage.secure.cisco`.
Port	Yes	HTTPS port `443`.
Base API	Yes	Enter the path between Host and the versioned `/v1` route. Use `/firewall` with `api.<region>.security.cisco.com`, or `/api/rest` with `manage.secure.cisco`. The adapter normalizes a trailing slash.

The Host and Base API values must be changed together when switching between the commercial and management or FedRAMP endpoint formats.

For Generic SCC API Request, enter the complete versioned route after Base API, such as /v1/inventory/devices. Do not repeat the protocol, host, port, or Base API.