Skip to main content

Cisco AMP Source


The Cisco AMP Source provides a secure endpoint to receive data from the Cisco Amp System Log API. It securely stores the required authentication, scheduling, and state tracking information.

Data collected

Polling IntervalData
5 minsSystem Log data


Vendor configuration

The integration requires an Cisco Amp Client ID and API key.

Source configuration

When you create a Cisco AMP Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Configure a Hosted Collector.

To configure a Cisco AMP Source:

  1. In the main Sumo Logic menu, select Manage Data > Collection > Collection.
  2. On the Collectors page, click Add Source next to a HostedCollector.
  3. Search for and select Cisco AMP.
  4. Enter a Name to display for the Source in the Sumo web application. The description is optional.
  5. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
  6. Forward to SIEM. Check the checkbox to forward your data to Cloud SIEM.

    Select Forward to SIEM only if you have Cloud SIEM installed.

  7. (Optional) Fields. Click the +Add Field link to define the fields you want to associate, each field needs a name (key) and value.
    • green check circle.png A green circle with a check mark is shown when the field exists in the Fields table schema.
    • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema it is ignored, known as dropped.
  8. Client ID. Provide the Client ID you want to use to authenticate collection requests.
  9. API Region (Optional). Select the appropriate region of your API Key. The default is
  10. API Key. Provide the API Key you want to use to authenticate collection requests. 
  11. (Optional) The Polling Interval is set for 300 seconds by default, you can adjust it based on your needs. This sets how often the Source checks for new data.
  12. When you are finished configuring the Source, click Submit.

Metadata fields

_siemVendorCiscoSet when Forward To SIEM is checked.
_siemProductAMPSet when Forward To SIEM is checked.
_siemFormatJSONSet when Forward To SIEM is checked.
_siemEventID<eventType>}Where <eventType> is the value of the field from the JSON event, such as Threat Detected. A list of possible event types can be found here.

JSON schema

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details. 

schemaRefJSON Object{"type":"Cisco AMP"}YesDefine the specific schema type.
sourceTypeString"Universal"YesType of source.
configJSON ObjectConfiguration objectYesSource type specific values.

Configuration Object

nameStringYesnullType a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source."mySource"
descriptionStringNonullType a description of the source."Testing source"
categoryStringNonullType a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details."mySource/test"
fieldsJSON ObjectNonullJSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.{"_siemForward": false, "fieldA": "valueA"}
clientIdStringYesnullProvide the Client ID you want to use to authenticate collection requests.
apiRegionStringNonullSelect the appropriate region of your API Key.
apiKeyStringYesnullProvide the API Key you want to use to authenticate collection requests.
pollingIntervalIntegerNo300This sets how often the Source checks for new data.

JSON example

"type":"Cisco AMP"
"description":"East field",
Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "cisco_AMP_source" {
collector_id =
schema_ref = {
type = "Cisco AMP"
config = jsonencode({
"description":"East field",
resource "sumologic_collector" "collector" {
name = "my-collector"
description = "Just testing this"
Download example



Click here for more information about Cloud-to-Cloud sources.

Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.