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.

note

This source is available in all deployments, including the Fed deployment.

Data collected

Polling Interval	Data
5 mins	System Log data

Setup

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 Sumo Logic, 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.
7. (Optional) Fields. Click the +Add Field link to define the fields you want to associate, each field needs a name (key) and value.
   •  A green circle with a check mark is shown when the field exists in the Fields table schema.
   •  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 api.amp.cisco.com.
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

Field	Value	Description
_siemVendor	Cisco	Set when Forward To SIEM is checked.
_siemProduct	AMP	Set when Forward To SIEM is checked.
_siemFormat	JSON	Set 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. 

Parameter	Type	Value	Required	Description
schemaRef	JSON Object	{"type":"Cisco AMP"}	Yes	Define the specific schema type.
sourceType	String	"Universal"	Yes	Type of source.
config	JSON Object	Configuration object	Yes	Source type specific values.

Configuration Object

Parameter	Type	Required	Default	Description	Example
name	String	Yes	null	Type a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source.	"mySource"
description	String	No	null	Type a description of the source.	"Testing source"
category	String	No	null	Type a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details.	"mySource/test"
fields	JSON Object	No	null	JSON 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"}
clientId	String	Yes	null	Provide the Client ID you want to use to authenticate collection requests.
apiRegion	String	No	null	Select the appropriate region of your API Key.
apiKey	String	Yes	null	Provide the API Key you want to use to authenticate collection requests.
pollingInterval	Integer	No	300	This sets how often the Source checks for new data.

JSON example

{
    "api.version":"v1",
    "source":{
      "schemaRef":{
        "type":"Cisco AMP"
      },
      "config":{
        "name":"Cisco",
        "description":"East field",
        "clientId":"********",
        "apiKey":"********",
        "fields":{
          "_siemForward":false
        },
        "category":"eastTeamF",
        "pollingInterval":300
      },
      "sourceType":"Universal"
    }
  }

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "cisco_AMP_source" {
  collector_id = sumologic_collector.collector.id
  schema_ref = {
    type = "Cisco AMP"
  }
  config = jsonencode({
      "name":"Cisco",
      "description":"East field",
      "clientId":"********",
      "apiKey":"********",
      "fields":{
        "_siemForward":false
      },
      "category":"eastTeamF",
      "pollingInterval":300
  })
}
resource "sumologic_collector" "collector" {
  name        = "my-collector"
  description = "Just testing this"
}

Download example

FAQ

info

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