Akamai CPC Source

Akamai Client-Side Protection and Compliance (CPC) is a security solution designed to monitor and protect against client-side threats such as JavaScript-based data skimming and formjacking. It provides visibility into third-party script behavior and enforces security policies to ensure compliance with data protection standards.

Data collected

Polling Interval	Data
12 hours	CPC-Configs
5 minutes	CPC-Alerts

Setup

Vendor configuration

You'll need a Host Name, Client Token, Client Secret, and Access Token. To generate these, follow these steps:

• Host Name. The Akamai API base URL used to sending authenticated requests.
• Refer to the Akamai Documentation to generate Client Token, Client Secret, and Access Token.

Source configuration

When you create an Akamai CPC 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 an Akamai CPC Source:

1. Classic UI. In the main Sumo Logic menu, select Manage Data > Collection > Collection.
   New UI. In the Sumo Logic top menu select Configuration, and then under Data Collection select Collection. You can also click the Go To... menu at the top of the screen and select Collection.
2. On the Collection page, click Add Source next to a Hosted Collector.
3. Search for and select Akamai CPC.
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 Field link to define the fields you want to associate. Each field needs a name (key) and value.
   •  A green circle with a checkmark is shown when the field exists in the Fields table schema.
   •  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 (that is, dropped).
7. Client Token. Enter the Client token value collected from the Akamai platform.
8. Client Secret. Enter the Client secret value collected from the Akamai platform.
9. Access Token. Enter the Access token value collected from the Akamai platform.
10. API Host Name. Enter the API Host Name value collected from the Akamai platform.
11. (Optional) Collect Alert Logs. Select this checkbox to collect the alert logs from the Akamai platform.
    1. (Optional) Supported Severity Level. Select the severity of the alert logs from the dropdown.
    2. (Optional) Supported Alert Type. Select the type of alerts from the dropdown.
    3. (Optional) Supported Alert Status. Select the status of the alerts from the dropdown.
12. (Optional) Collect Alert Details. Select this checkbox to collect the alert details from the Akamai platform.
13. The CPC Configs Polling Interval is set to 12 hours by default, you can adjust it based on your needs.
14. (Optional) Processing Rules for Logs. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
15. When you are finished configuring the Source, click Save.

JSON configuration

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

Parameter	Type	Value	Required	Description
schemaRef	JSON Object	{"type":"Akamai CPC"}	Yes	Define the specific schema type.
sourceType	String	"Universal"	Yes	Type of source.
config	JSON Object	Configuration object	Yes	Source type specific values.

Configuration Object

Parameter	Type	Required	Default	Description	Example
name	String	Yes	null	Type a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source.	"mySource"
description	String	No	null	Type a description of the source.	"Testing source"
category	String	No	null	Type a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details.	"mySource/test"
fields	JSON Object	No	null	JSON 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"}
clientToken	String	Yes	null	A unique identifier used to authenticate API requests.
clientSecret	String	Yes	null	User account secret which will be used in authentication.
accessToken	String	Yes	null	Token granting access to the Akamai CPC API on behalf of a client.
akamaiHostName	String	Yes	null	The base URL of the Akamai API endpoint used to interact with CPC services.
collectAlertsLogs	Boolean	No	null	Specify if we need to collect the alert logs.
severityLevel	String Array	No	null	Specify the alert logs severity
alertType	String Array	No	null	Specify the type of alerts.
alertStatus	String Array	No	null	Specify the status of the alerts.
pollingIntervalAlertsMin	Integer	No	5 minutes	Time interval (in minutes) after which the source will check for new data. Minimum: 5 minutes Maximum: 60 minutes
collectAlertDetails	Boolean	No	false	Specify if we need to collect the alert details.
pollingIntervalCPCConfigsHrs	Integer	Yes	12 hours	Time interval (in minutes) after which the source will check for new data. Minimum: 1 hour Maximum: 24 hours

JSON example

{
	"api.version": "v1",
	"source": {
		"config": {
  "name": "c2c-Akamai CPC",
  "clientToken":"akab-ctfkqxxxxxxa3quph-xxxxxx",
  "clientSecret":"IyVVIdYgBfxxxxxbToZMGGaxxxxxxxxxxM",
  "accessToken":"akabxxxxxx4ke52-xxxxxxxx5efol",
           "hostName":"abcde-efgx-xxxxxx.net",
		"collectAlertsLogs": true,
		"pollingIntervalAlertsMin": 5,
            "collectAlertDetails": true,
 "severityLevel": [
    "HIGH",
    "MEDIUM"
  ],
"alertType": [
    "SUSPICIOUS_SCRIPT_ACTIVITY_EG_CPC_ALERT"
  ],
  "alertStatus": [
    "OPEN"
  ],
  "pollingIntervalCPCConfigsHrs":12
  },
		"schemaRef": {
            		"type": "Akamai CPC"
        	},
        	"sourceType": "Universal"
	}
}

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "akamai-cpc-source" {
  collector_id = sumologic_collector.collector.id
  schema_ref = {
    type = "Akamai CPC"
  }
  config = jsonencode({
            "name": "c2c-Akamai CPC",
            "clientToken":"akab-ctfkqxxxxxxa3quph-xxxxxx",
            "clientSecret":"IyVVIdYgBfxxxxxbToZMGGaxxxxxxxxxxM",
            "accessToken":"akabxxxxxx4ke52-xxxxxxxx5efol",
                    "hostName":"abcde-efgx-xxxxxx.net",
                    "collectAlertsLogs": true,
                    "pollingIntervalAlertsMin": 5,
                        "collectAlertDetails": true,
            "severityLevel": [
                "HIGH",
                "MEDIUM"
            ],
            "alertType": [
                "SUSPICIOUS_SCRIPT_ACTIVITY_EG_CPC_ALERT"
            ],
            "alertStatus": [
                "OPEN"
            ],
            "pollingIntervalCPCConfigsHrs":12
  })
}
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.