Configuring Broadcom (Symantec) Email Security.cloud Connectors

The Broadcom (Symantec) Email Security.cloud connector allows you to ingest email related log reports to the Stellar Cyber data lake.

Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the collector is exceeded.

Connector Overview: Broadcom (Symantec) Email Security.cloud

Capabilities

  • Collect: Yes

  • Respond: No

  • Native Alerts Mapped: No

  • Runs on: DP

  • Interval: Configurable

Collected Data

Content Type

Index

Locating Records

Clicktime

Delivery

EC Reports

Isolation

Malware

Spam

Syslog

msg_class:

symantec_email_clicktime

symantec_email_delivery_data

symantec_email_threat_analytics

symantec_email_threat_isolation

symantec_email_malware

symantec_email_anti_spam

msg_origin.source:

symantec_email_security_cloud

msg_origin.vendor:

symantec

msg_origin.category:

email

Domain

https://datafeeds.emailsecurity.symantec.com

Response Actions

N/A

Third Party Native Alert Integration Details

N/A

Required Credentials

  • Username and Password

               Let us know if you find the above overview useful.

Adding a Broadcom (Symantec) Email Security.cloud Connector

To add the Broadcom (Symantec) Email Security.cloud connector:

  1. Obtain the required credentials
  2. Add the connector in Stellar Cyber
  3. Test the connector

Obtaining the Required Credentials

To configure this connector in Stellar Cyber, you will need the following information from your Broadcom (Symantec) Email Security.cloud deployment:

  • Username and password for an account with View Statistics permissions.

    The password should not include non-ASCII special characters.

  • The type of data feed to collect:

    • clicktime: Contains metadata from events generated by end-user clicks in URLs that were rewritten by the Click-time URL Protection.

    • delivery: Contains metadata that describes both inbound and outbound email delivery to provide visibility into email tracing, TLS compliance, and routing.

    • ec_reports: Contains contextual information about all emails blocked by the Email Security.cloud’s Anti-Malware service, as well as emails blocked because their attachments are determined to be malicious.

    • isolation: Contains data from events logged by the URL and Attachment Isolation features, which ensure threats are executed in an isolation platform.

    • malware: Contains data about malware-containing email only.

    • spam: Contains metadata about email that the Anti-Spam service has detected as spam, as well as the action taken as a result of that detection.

    More details on the requirements for users and the nature of the feeds are described in Symantec's Data Feeds API Guide for Email Security.cloud.

Adding the Connector in Stellar Cyber

With the configuration information handy, you can add the Broadcom (Symantec) Email Security.cloud connector in Stellar Cyber:

  1. Log in to Stellar Cyber.

  2. Click System | Integration | Connectors. The Connector Overview appears.

  3. Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

    The asterisk (*) indicates a required field.

  4. Choose Email from the Category drop-down.

  5. Choose Symantec Email Security.cloud from the Type drop-down.

  6. For this connector, the supported Function is Collect, which is enabled already.

  7. Enter a Name.

    Notes:
    • This field does not accept multibyte characters.
    • It is recommended that you follow a naming convention such as tenantname-connectortype.
  8. Choose a Tenant Name. The Interflow records created by this connector include this tenant name.

  9. Choose the device on which to run the connector .

  10. (Optional) When the Function is Collect, you can apply Log Filters. For information, see Managing Log Filters.

  11. Click Next. The Configuration tab appears.

    The asterisk (*) indicates a required field.

  12. Enter the Username you copied earlier.

  13. Enter the Password you copied earlier.

  14. Choose the Interval (min). This is how often the logs are collected.

  15. Select the Content Type you want to collect:

    • Clicktime: Contains metadata from events generated by end-user clicks in URLs that were rewritten by the Click-time URL Protection.

    • Delivery: Contains metadata that describes both inbound and outbound email delivery to provide visibility into email tracing, TLS compliance, and routing.

    • EC Reports: Contains contextual information about all emails blocked by Email Security.cloud’s Anti-Malware service, as well as emails blocked because their attachments are determined to be malicious.

    • Isolation: Contains data from events logged by the URL and Attachment Isolation features, which ensure threats are executed in an isolation platform.

    • Malware: Contains data about malware-containing email only.

    • Spam: Contains metadata about email that the Anti-Spam service has detected as spam, as well as the action taken as a result of that detection.

    Descriptions of this content type (the data feeds) and requirements for those to be available in your deployment are provided in Symantec's Data Feeds API Guide for Email Security.cloud.

  16. Click Next. The final confirmation tab appears.

  17. Click Submit.

    To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.

The new connector is immediately active.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).

For connectors running on a sensor, Stellar Cyber recommends that you allow 30-60 seconds for new or modified configuration details to be propagated to the sensor before performing a test.

  1. Click System | Integrations | Connectors. The Connector Overview appears.

  2. Locate the connector that you added, or modified, or that you want to test.

  3. Click Test at the right side of that row. The test runs immediately.

    Note that you may run only one test at a time.

Stellar Cyber conducts a basic connectivity test for the connector and reports a success or failure result. A successful test indicates that you entered all of the connector information correctly.

To aid troubleshooting your connector, the dialog remains open until you explicitly close it by using the X button. If the test fails, you can select the  button from the same row to review and correct issues.

The connector status is updated every five (5) minutes. A successful test clears the connector status, but if issues persist, the status reverts to failed after a minute.

Repeat the test as needed.

ClosedDisplay sample messages...

Success !

Failure with summary of issue:

Show More example detail:

If the test fails, the common HTTP status error codes are as follows:

HTTP Error Code HTTP Standard Error Name Explanation Recommendation
400 Bad Request This error occurs when there is an error in the connector configuration.

Did you configure the connector correctly?

401 Unauthorized

This error occurs when an authentication credential is invalid or when a user does not have sufficient privileges to access a specific API.

Did you enter your credentials correctly?

Are your credentials expired?

Are your credentials entitled or licensed for that specific resource?

403 Forbidden This error occurs when the permission or scope is not correct in a valid credential.

Did you enter your credentials correctly?

Do you have the required role or permissions for that credential?

404 Not Found This error occurs when a URL path does not resolve to an entity. Did you enter your API URL correctly?
429 Too Many Requests

This error occurs when the API server receives too much traffic or if a user’s license or entitlement quota is exceeded.

The server or user license/quota will eventually recover. The connector will periodically retry the query.

If this occurs unexpectedly or too often, work with your API provider to investigate the server limits, user licensing, or quotas.

For a full list of codes, refer to HTTP response status codes.

Verifying Ingestion

To verify ingestion:

  1. Click Investigate | Threat Hunting. The Interflow Search tab appears.
  2. Change the Indices to Syslog. The table immediately updates to show ingested Interflow records.