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.

Connector Overview: Broadcom (Symantec) Email Security.cloud

               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 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.

   

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.

   This field does not accept multibyte characters.

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 .

   • Certain connectors can be run on either a Sensor or a Data Processor. The available devices are displayed in the Run On menu. If you want to associate your collector with a sensor, you must have configured that sensor prior to configuring the connector or you will not be able to select it during initial configuration. If you select Data Processor, you will need to associate the connector with a Data Analyzer profile as a separate step. That step is not required for a sensor, which is configured with only one possible profile.

   • If the device you're connecting to is on premises, we recommend you run on the local sensor. If you're connecting to a cloud service, we recommend you run on the DP.

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

11. Click Next. The Configuration tab appears.

    

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.

18. If you are adding rather than editing a connector with the Collect function enabled and you specified for it to run on a Data Processor, a dialog box now prompts you to add the connector to the default Data Analyzer profile. Click Cancel to leave it out of the default profile or click OK to add it to the default profile.

    • This prompt only occurs during the initial create connector process when Collect is enabled.

    • Certain connectors can be run on either a Sensor or a Data Processor, and some are best run on one versus the other. In any case, when the connector is run on a Data Processor, that connector must be included in a Data Analyzer profile. If you leave it out of the default profile, you must add it to another profile. You need the Administrator Root scope to add the connector to the Data Analyzer profile. If you do not have privileges to configure Data Analyzer profiles, a dialog displays recommending you ask your administrator to add it for you.

    • The first time you add a Collect connector to a profile, it pulls data immediately and then not again until the scheduled interval has elapsed. If the connector configuration dialog did not offer an option to set a specific interval, it is run every five minutes. Exceptions to this default interval are the Proofpoint on Demand (pulls data every 1 hour) and Azure Event Hub (continuously pulls data) connectors. The intervals for each connector are listed in the Connector Types & Functions topic.

    The Connector Overview appears.

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).

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.

Display sample messages...

Success !

Failure with summary of issue: Show More example detail:

 

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.