Cisco Identity Services Engine

Applies an Adaptive Network Control (ANC) policy to an endpoint in Cisco Identity Services Engine (ISE). This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node (PAN)

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Build the request payload
[] Request the ANC policy be applied
[] Check if the request was successful:
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!anc-endpoint/apply

Cisco ISE - ERS - ANC Policy - Apply to Endpoint

prod-nam

prod-eu

prod-apjc

Clears all Adaptive Network Control (ANC) policies from an endpoint in Cisco Identity Services Engine (ISE). This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node (PAN)

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Build the request payload
[] Request the ANC policies be cleared
[] Check if the request was successful:
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!anc-endpoint/clear

Cisco ISE - ERS - ANC Policy - Clear from Endpoint

Fetches an Adaptive Network Control (ANC) policy from Cisco Identity Services Engine (ISE) using its name. This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Request matching ANC policies
[] Check if the request was successful:
[]> If it was, extract the ANC policy and set the output variables
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!anc-policy/Get-By-Name

Cisco ISE - ERS - ANC Policy - Get by Name

Creates a new endpoint in Cisco Identity Services Engine (ISE). This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node (PAN)

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Request the endpoint be created
[] Check if the request was successful:
[]> If it was, add the change list to the workflow output
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!end-point/create

Cisco ISE - ERS - Endpoint - Create Endpoint

Fetches an endpoint from Cisco Identity Services Engine (ISE) using its unique ID. This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node (PAN)

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Request the endpoint
[] Check if the request was successful:
[]> If it was, extract the endpoint and set output variables
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!end-point/get-by-id

Cisco ISE - ERS - Endpoint - Get by ID

Searches Cisco Identity Services Engine (ISE) for endpoints based on MAC address, identity group, profiler policy, or portal user. Note that only one search criteria should be provided. This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node (PAN)

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Build the search string based on the field value provided
[] Request a list of matching endpoints
[] Check if the request was successful:
[]> If it was, extract the result count and set output variables
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!end-point/get-all

Cisco ISE - ERS - Endpoint - Search

Updates an endpoint's identity group assignment in Cisco Identity Services Engine (ISE). If you set a static assignment, the endpoint will stay in the group regardless of profiling events. If static assignment is false, the endpoint may leave the group depending on how it's profiled. This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node (PAN)

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Request the endpoint be updated
[] Check if the request was successful:
[]> If it was, add the change list to the workflow output
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!end-point/update

Cisco ISE - ERS - Endpoint - Update Identity Group

Updates an endpoint's profiler policy assignment in Cisco Identity Services Engine (ISE). If you set a static assignment, the endpoint will stay in the profile regardless of profiling events. If static assignment is false, the endpoint may leave the profile depending on how it's profiled. This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node (PAN)

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Request the endpoint be updated
[] Check if the request was successful:
[]> If it was, add the change list to the workflow output
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!end-point/update

Cisco ISE - ERS - Endpoint - Update Profiler Policy

Fetches an endpoint identity group from Cisco Identity Services Engine (ISE) using its name. This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Request matching identity groups
[] Check if the request was successful:
[]> If it was, extract the identity group and set output variables
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!endpoints-identity-group/get-by-name

Cisco ISE - ERS - Endpoint Identity Group - Get by Name

Fetches a profiler policy from Cisco Identity Services Engine (ISE) using its name. This atomic is designed for use with ISE version 2.4 or newer.

Note: You may need to use an XDR automation remote to communicate with ISE if it's on-premises. See the XDR automation documentation for more information about remotes.

Target: HTTP Endpoint for your ISE cluster's primary admin node

Account Key: HTTP Basic Authentication for your ISE target

Steps:
[] Request matching profiler policies
[] Check if the request was successful:
[]> If it was, extract the first profiler policy and set the output variables
[]> If it wasn't, return an error

More information about this API: https://developer.cisco.com/docs/identity-services-engine/3.0/#!profiler-profile/get-all