Configuring Akamai Connectors

Connectors allow Stellar Cyber to collect

data from external sources and add it to the data lake.
To add an Akamai connector:
1. Obtain credentials.
2. Add the connector in Stellar Cyber.
3. Test the connector.
4. Verify ingestion.

Obtain Credentials
To create the Akamai API credentials:

 Use our example as a guideline, as you might be using a different software version.

1. Log in to your Akamai Control Center account (https://control.akamai.com).

2. Navigate to Identity & Access > New API Client for Me.
3. Select which roles, contracts, and groups you are using with the Stellar Cyber API client. You will need to note the Contract ID for use with
the connector.
4. Select HTTPie for the tool you will use for the API requests.
5. Select the permissions as read-only.
Click Submit.
6. When displayed, copy the base URL.
7. Click on the New Credential button and copy or download your Access Token, Client Token, and Client Secret.
8. Save all of the above information before proceeding to the next section.

Adding an Akamai Connector

After completing the previous section, with the required credentials noted, you can add the Akamai 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 Endpoint Security from the Category drop-down.

5. Choose Akamai from the Type drop-down.
6. For Function, the setting of Collect is pre-selected. Respond is not an option for Akamai.
7. Enter a Name. This field is required, and 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 to run the connector on.
10. Click Next. The Configuration tab appears.

Enter the Host URL.

  Ensure the URL does not include a trailing "/" symbol.

Enter the Access Token.

Enter the Client Token.
Enter the Client Secret.
Enter the Contract ID.
Enter the Interval (min). This is how often Stellar Cyber collects the logs.
Choose the Content Type you want to collect. The available current content types are:
Admin Events Reports
Audit Logs Reports
Connectors
Users
11. Click Next. The final confirmation tab appears.

12. Click Submit.

13. 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 OK to add it, or Cancel to leave it out of 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 where 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. 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, and it is it runs
every five minutes. Exceptions to this default, internal interval are the Proofpoint (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

To test the connector:
1. Click System | Integration | Connectors. The Connector Overview appears.

2. Click Test for the connector you want to test. The test runs immediately.
Stellar Cyber conducts a basic connectivity test for the connector. A successful test indicates that you entered all of the connector information
correctly.

Verifying Ingestion
To verify ingestion:
1. Click Investigate | Threat Hunting. The Interflow Search tab appears.
2. Change the Index to Syslog. The table immediately updates to show ingested Interflow records.

Stellar Cyber version 4.3.3 © 2022 Stellar Cyber . All rights reserved.

Support   | 
Contact Us  |  
   
  
