Skip to main content

Symantec Web Security Service Source

icon

The Symantec Web Security Service Source provides a secure endpoint to receive WSS Access logs from the Symantec WSS API. It securely stores the required authentication, scheduling, and state tracking information.

  • See the Access Log Format for reference.
  • Logs are ingested in batches of 1,000.
  • Logs are polled every five minutes.
note

This source is not available in the Fed deployment.

Data collected

Polling IntervalData
5 minWSS Access logs

Setup

Vendor configuration

note

You need to configure a WSS agent on the machine you want to collect data from. The WSS agent will collect your access data and the Symantec Web Security Service Source will receive that data using the Symantec WSS API. To configure and install the agent, follow the instructions in the Web Security Service documentation.

You need to have a Symantec Web Security Service username and password. To create a User API Key that serves as the username and password in the Sync API syntax follow these steps:

  1. Navigate to Account Configuration > API Credentials.
  2. Click Add API Credentials.
  3. WSS displays the Add API Credential dialog, which contains the random characters Username and Password.
    Symantec generate api creds.png
    1. Copy the Username and Password keys into a text file.
    2. Select the API Expiry you'd like to set.
      • Time-based—You define the date and time when this token expires.
      • Never expires.
    3. For the Access option, select Reporting Access Logs.
  4. Click Save.

See Symantec Security Software documentation for further details on generating API credentials.

Source configuration

When you create a Symantec Web Security Service 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 Web Security Service Source:

  1. In Sumo Logic, select Manage Data > Collection > Collection
  2. On the Collectors page, click Add Source next to a Hosted Collector.
  3. Select Symantec Web Security Service.
    symantec source icon.png
  4. Enter a Name to display for the Source in the Sumo web application. The description is optional.
    Symantec WSS version 1.2.3.png
  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.
    • 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. API Username and Password. Provide the Symantec Web Security Service user credentials you want to use to authenticate collection requests. This was copied during the Vendor configuration steps above.
  9. When you are finished configuring the Source, click Submit.

Metadata fields

FieldValueDescription
_siemVendorSymantecSet when Forward To SIEM is checked.
_siemProductWeb Security ServiceSet when Forward To SIEM is checked.
_siemFormatJSONSet when Forward To SIEM is checked.
_siemEventIDproxy-messagesSet when Forward To SIEM is checked and specific to the API collected.

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. 

ParameterTypeValueRequiredDescription
schemaRefJSON Object{"type":"Symantec Web Security Service"}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"}
apiUsernameStringYesnullProvide the username you want to use to authenticate collection requests.
apiPasswordStringYesnullProvide the password for the username that you want to use to authenticate collection requests.

JSON example

{
"api.version":"v1",
"source":{
"schemaRef":{
"type":"Symantec Web Security Service"
},
"config":{
"name":"Symantec WSS",
"apiUsername":"********",
"fields":{
"_siemForward":false
},
"category":"c2c/sym",
"apiPassword":"********"
},
"state":{
"state":"Collecting"
},
"sourceType":"Universal"
}
}

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "symantec_web_security_service_source" {
collector_id = sumologic_collector.collector.id
schema_ref = {
type = "Symantec Web Security Service"
}
config = jsonencode({
"name":"Symantec WSS",
"apiUsername":"********",
"fields":{
"_siemForward":false
},
"category":"c2c/sym",
"apiPassword":"********"
})
}
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.

Legal
Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.