Cisco Secure Endpoint
Visualize Cisco Secure Endpoint protected devices, map agents to devices and their respective owners, and monitor changes through queries and alerts.
- Installation guide
- Cisco Secure Endpoint data model
Installation
This integration connects directly to Cisco Secure Endpoint REST API to obtain endpoint protection and configuration information.
Valid API Endpoints include:
api.amp.cisco.com
api.apjc.amp.cisco.com
api.eu.amp.cisco.com
You will need to create a new Client ID and API Key with read access in Cisco Secure Endpoint for this integration. See their documentation for more information.
To install the Cisco Secure Endpoint integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Cisco Secure Endpoint. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Cisco Secure Endpoint account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
toggle is enabled.Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.The API Endpoint Hostname associated with your Cisco Secure Endpoint account.
Your Cisco Secure Endpoint Client ID and API Key (configured for read access).
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Account | cisco_amp_account | Account |
Computer | cisco_amp_endpoint | HostAgent |
Finding | cisco_amp_finding | Finding |
Vulnerability | cve | Vulnerability |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
cisco_amp_account | HAS | cisco_amp_endpoint |
cisco_amp_endpoint | IDENTIFIED | cisco_amp_finding |
cisco_amp_finding | IS | cve |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
---|---|---|---|
cisco_amp_endpoint | PROTECTS | *user_endpoint* | FORWARD |