Skip to main content

Symantec Endpoint Security Source

icon

Symantec Endpoint Protection is a client-server solution that protects laptops, desktops, and servers in networks against malware, risks, and vulnerabilities. Symantec Endpoint Protection combines virus protection with advanced threat protection to proactively secure client computers against known and unknown threats. This integration collects this information using the Symantec Incidents API and ingests it into Sumo Logic.

Data collected

Polling IntervalData SourceDescription
5 minIncidentsUsed to retrieve incidents and incident events.
5 minIncident EventsUsed to retrieve incident related events based on time range filter.

Setup

Vendor configuration

The Symantec Endpoint Security source requires you to provide credentials. To obtain the client secret, follow the steps below.

  1. Sign in to the Symantec Endpoint Security platform.
  2. Go to Integration and select Client Applications.
  3. Click on Add Client Application.
  4. Enter any name for the application and press the Add button. The client application details screen appears.
  5. Select required privileges for the client application and click Save.
  6. Click the More Options icon and select Client Secret.

Source configuration

When you create a Symantec Endpoint Security 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 Symantec Endpoint Security Source, follow the steps below:

  1. In the main Sumo Logic menu, select Manage Data > Collection > Collection.
  2. On the Collection page, click Add Source next to a Hosted Collector.
  3. Search for and select Symantec Endpoint Security.
  4. Enter a Name for the Source. 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. (Optional) Fields. Click the +Add button 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 Logic that does not exist in the Fields schema, it is ignored, also known as dropped.
  7. In Client ID, enter the Client ID you generated from the Symantec Endpoint Security platform.
  8. In Client Secret, enter the Client Secret you generated from the Symantec Endpoint Security platform.
  9. (Optional) In Initial LookBack, enter the first collection start time. Default is 1 day and maximum is 30 days.
  10. Include Events. Select this checkbox if you want to collect events from incidents.
  11. (Optional) The Polling Interval is set for 24 hours by default. You can adjust it based on your needs.
  12. (Optional) Processing Rules for Logs. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
  13. When you are finished configuring the Source, click Save.

JSON schema

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

ParameterTypeValueRequiredDescription
schemaRefJSON Object{"type":"Symantec Endpoint Security"}YesDefine the specific schema type.
sourceTypeString"Universal"YesType of source.
configJSON ObjectConfiguration objectYesSource type specific values.

Configuration Object

ParameterTypeRequiredDefaultDescriptionExample
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"}
clientIDStringNonullClient ID generated from the Symantec Endpoint Security platform.
clientSecretStringNonullClient Secret generated from the Symantec Endpoint Security platform.
incidentsIncludeEventsStringNofalseSelect the checkbox to include the incident events.5 minutes
incidentsInitialLookbackIntegerNo1 dayFirst collection start time.
pollingIntervalStringNo5 minutesThis sets how often the Source checks for data.5 minutes

JSON example

{
"api.version":"v1",
"source":{
"config":{
"name":"Symantec Endpoint Security Test",
"clientID":"********",
"incidentsIncludeEvents":true,
"incidentsInitialLookback":"1d",
"fields":{
"_siemForward":false
},
"clientSecret":"********",
"pollingInterval":"5m"
},
"schemaRef":{
"type":"Symantec Endpoint Security"
},
"state":{
"state":"Collecting"
},
"sourceType":"Universal"
}
}
Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "symantec-endpoint-security-source" {
collector_id = sumologic_collector.collector.id
schema_ref = {
type = "Symantec Endpoint Security"
}
config = jsonencode({
"name":"Symantec Endpoint Security Test",
"clientID":"********",
"incidentsIncludeEvents":true,
"incidentsInitialLookback":"1d",
"fields":{
"_siemForward":false
},
"clientSecret":"********",
"pollingInterval":"5m"
})
}
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.

Status
Legal
Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.