Akamai CPC

The Sumo Logic app for Akamai Client-Side Protection (CPC) helps organizations monitor and secure their client-side web applications. It provides real-time visibility into alerts, threat indicators, and data exposure risks from client-side scripts, enabling fast and accurate threat detection. Using Akamai’s data, the app identifies threats like data exfiltration, script-based attacks, policy violations, and insecure handling of sensitive data. Pre-configured dashboards show alert trends, risk levels, and anomalies, helping analysts investigate incidents and respond efficiently. With clear visualizations and detailed event insights, the app supports compliance (e.g., PCI) and strengthens the security of client-facing digital assets.

info

This app includes built-in monitors. For details on creating custom monitors, refer to the Create monitors for Akamai CPC app.

Log types

This app uses Sumo Logic’s Akamai CPC Source to collect the alerts and their details from the Akamai CPC platform.

Sample log messages

Alerts

{
  "cpcConfigId": 10286,
  "cpcAlertId": "e1-b10064e2",
  "cpcAlertLink": "/client-side-protection-and-compliance/v2/cpc-configs/10286/cpc-alerts/e1-b10064e2",
  "cpcAlertType": "SENSITIVE_DATA_EXFILTRATION_E1_CPC_ALERT",
  "severityLevel": "INFO",
  "cpcAlertStatus": "OPEN",
  "cpcAlertFlags": [],
  "alertTime": "2025-06-09T13:49:16.071+0000",
  "firstSeenTime": "2025-06-05T18:41:03.603+0000",
  "lastSeenTime": "2025-06-09T13:48:42.792+0000"
}

Alert Details

{
  "cpcConfigId": 10286,
  "cpcAlertId": "e1-b10064e2",
  "cpcAlertLink": "/client-side-protection-and-compliance/v2/cpc-configs/10286/cpc-alerts/e1-b10064e2",
  "cpcAlertType": "SENSITIVE_DATA_EXFILTRATION_E1_CPC_ALERT",
  "severityLevel": "INFO",
  "cpcAlertStatus": "OPEN",
  "cpcAlertFlags": [],
  "alertTime": "2025-06-09T13:49:16.071+0000",
  "firstSeenTime": "2025-06-05T18:41:03.603+0000",
  "lastSeenTime": "2025-06-09T13:48:42.792+0000",
  "links": [
    {
      "rel": "self",
      "href": "/client-side-protection-and-compliance/v2/cpc-configs/10286/cpc-alerts/e1-b10064e2"
    },
    {
      "rel": "control-center",
      "href": "https://control.akamai.com/apps/securitycenter/#/page-integrity-console?view=incident-details&incidentId=b10064e2&configId=10286&scConfigId=10286"
    },
    {
      "rel": "cpc-alerts",
      "href": "/client-side-protection-and-compliance/v2/cpc-configs/10286/cpc-alerts"
    },
    {
      "rel": "cpc-config",
      "href": "/client-side-protection-and-compliance/v2/cpc-configs/10286"
    }
  ],
  "details": {
    "affectedSessionCount": 4288,
    "scriptSource": {
      "scriptHostname": "www.ihg.com",
      "scriptUrls": [
        "https://www.ihg.com/resources/gb/en/customer-care/forms/v14.118.0/chunk-L6HJ7Y67.js"
      ],
      "scriptOrigin": "FIRST_PARTY",
      "hostnameRiskScore": "LOW_RISK",
      "vendor": null
    },
    "destination": {
      "destinationHostname": "apis.ihg.com",
      "destinationUrls": [
        "https://apis.ihg.com/members/v3/resetPassword"
      ],
      "hostnameRiskScore": "LOW_RISK",
      "vendor": null
    },
    "pages": null,
    "dataType": null,
    "dataSubtypes": [
      {
        "dataSubtype": "EMAIL",
        "dataOperations": [
          "VALUES_READ",
          "VALUES_SENT_OVER_NETWORK"
        ],
        "selectors": [
          "#gigya-loginID-62290586448469890, :nth-child(2) > :nth-child(1) > :nth-child(1) > :nth-child(2) > :nth-child(1) > :nth-child(2)"
        ]
      },
      {
        "dataSubtype": "CREDENTIALS_PASSWORD",
        "dataOperations": [
          "VALUES_READ",
          "VALUES_SENT_OVER_NETWORK"
        ],
        "selectors": [
          ""
        ]
      },
      {
        "dataSubtype": "CREDIT_CARD_NUMBER",
        "dataOperations": [
          "VALUES_READ"
        ],
        "selectors": [
          ":nth-child(2) > :nth-child(1) > :nth-child(1) > :nth-child(3) > :nth-child(1) > :nth-child(2) > :nth-child(1)"
        ]
      },
      {
        "dataSubtype": "EMAIL",
        "dataOperations": [
          "VALUES_READ"
        ],
        "selectors": [
          "#email"
        ]
      },
      {
        "dataSubtype": "PII_LAST_NAME",
        "dataOperations": [
          "VALUES_READ",
          "VALUES_SENT_OVER_NETWORK"
        ],
        "selectors": [
          "#lastName"
        ]
      },
      {
        "dataSubtype": "PII_ADDRESS",
        "dataOperations": [
          "VALUES_READ"
        ],
        "selectors": [
          "#address1, #city"
        ]
      },
      {
        "dataSubtype": "PII_ZIP_CODE",
        "dataOperations": [
          "VALUES_READ"
        ],
        "selectors": [
          "#zipCode"
        ]
      },
      {
        "dataSubtype": "PII_FIRST_NAME",
        "dataOperations": [
          "VALUES_READ",
          "VALUES_SENT_OVER_NETWORK"
        ],
        "selectors": [
          "#firstName"
        ]
      },
      {
        "dataSubtype": "CREDIT_CARD_EXPIRATION_DATE",
        "dataOperations": [
          "VALUES_READ"
        ],
        "selectors": [
          "#checkInDate, #checkOutDate"
        ]
      },
      {
        "dataSubtype": "CREDENTIALS_USERNAME",
        "dataOperations": [
          "VALUES_READ",
          "VALUES_SENT_OVER_NETWORK"
        ],
        "selectors": [
          ":nth-child(1) > :nth-child(1) > :nth-child(1) > :nth-child(2) > :nth-child(1) > :nth-child(2) > :nth-child(2)"
        ]
      }
    ],
    "threatIndicators": [
      "SENSITIVE_DATA_READ",
      "SENSITIVE_DATA_EXFILTRATION"
    ]
  }
}

Sample queries

Total Alerts
_sourceCategory="Labs/AkamaiCPC"
| json "cpcConfigId", "cpcAlertId", "cpcAlertLink", "cpcAlertType", "severityLevel", "cpcAlertStatus", "cpcAlertFlags", "alertTime", "firstSeenTime", "lastSeenTime","details.dataSubtypes[*].dataSubtype","details.threatIndicators","details.destination.destinationHostname","details.destination.vendor","details.destination.hostnameRiskScore","details.destination.destinationUrls","details.scriptSource.vendor","details.scriptSource.hostnameRiskScore","details.scriptSource.scriptOrigin","details.scriptSource.scriptUrls","details.scriptSource.scriptHostname","details.affectedSessionCount","details.dataSubtypes[*].dataOperations[*]" as cpc_config_id, cpc_alert_id, cpc_alert_link, cpc_alert_type, severity_level, cpc_alert_status, cpc_alert_flags, alert_time, first_seen_time, last_seen_time,data_sub_type, threat_indicators,destination_hostname,destination_vendor,destination_hostname_risk_score,destination_urls, source_script_vendor, source_hostname_risk_score, source_script_origin, source_script_urls,source_hostname,affected_session_count,data_operations nodrop

// global filters
| where cpc_config_id matches "{{cpc_config_id}}"
| where severity_level matches "{{alert_severity}}"
| where cpc_alert_status matches "{{alert_status}}"
| where cpc_alert_type matches "{{alert_type}}"

// panel specific
| count by cpc_alert_id
| count

Collection configuration and app installation

Depending on the set up collection method, you can configure and install the app in three ways:

Create a new collector and install the app. Create a new Sumo Logic Cloud-to-Cloud (C2C) source under a new Sumo Logic Collector and later install the app, or
Use an existing collector and install the app. Create a new Sumo Logic Cloud-to-Cloud (C2C) source under an existing Sumo Logic Collector and later install the app, or
Use existing source and install the app. Use your existing configured Sumo Logic Cloud-to-Cloud (C2C) source and install the app.

info

Use the Cloud-to-Cloud Integration for Akamai CPC to create the source and use the same source category while installing the app. By following these steps, you can ensure that your Akamai CPC app is properly integrated and configured to collect and analyze your Akamai CPC data.

Create a new collector and install the app

To set up collection and install the app, do the following:

note

Next-Gen App: To install or update the app, you must be an account administrator or a user with Manage Apps, Manage Monitors, Manage Fields, Manage Metric Rules, and Manage Collectors capabilities depending upon the different content types part of the app.

Select App Catalog.
In the 🔎 Search Apps field, run a search for your desired app, then select it.
Click Install App.
note
Sometimes this button says Add Integration.
In the Set Up Collection section of your respective app, select Create a new Collector.
1. Collector Name. Enter a Name to display the Source in the Sumo Logic web application. The description is optional.
2. Timezone. Set the default time zone when it is not extracted from the log timestamp. Time zone settings on Sources override a Collector time zone setting.
3. (Optional) Metadata. Click the +Add Metadata link to add a custom log Metadata Fields. Define the fields you want to associate, each metadata field needs a name (key) and value.
  - A green circle with a checkmark is shown when the field exists and is enabled in the Fields table schema.
  - An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the Fields table schema. In this case, an option to automatically add or enable 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 or is disabled it is ignored, known as dropped.
4. Click Next.
Configure the source as specified in the Info box above, ensuring all required fields are included.
In the Configure section of your respective app, complete the following fields.
1. Field Name. If you already have collectors and sources set up, select the configured metadata field name (eg _sourcecategory) or specify other custom metadata (eg: _collector) along with its metadata Field Value.
Click Next. You will be redirected to the Preview & Done section.

Post-installation

Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.

Each panel slowly fills with data matching the time range query received since the panel was created. Results will not immediately be available but will be updated with full graphs and charts over time.

Use an existing collector and install the app

To set up the source in the existing collector and install the app, do the following:

note

Select App Catalog.
In the 🔎 Search Apps field, run a search for your desired app, then select it.
Click Install App.
note
Sometimes this button says Add Integration.
In the Set Up Collection section of your respective app, select Use an existing Collector.
From the Select Collector dropdown, select the collector that you want to set up your source with and click Next.
Configure the source as specified in the Info box above, ensuring all required fields are included.
In the Configure section of your respective app, complete the following fields.
1. Field Name. If you already have collectors and sources set up, select the configured metadata field name (eg _sourcecategory) or specify other custom metadata (eg: _collector) along with its metadata Field Value.
Click Next. You will be redirected to the Preview & Done section.

Post-installation

Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.

Use an existing source and install the app

To skip collection and only install the app, do the following:

note

Select App Catalog.
In the 🔎 Search Apps field, run a search for your desired app, then select it.
Click Install App.
note
Sometimes this button says Add Integration.
In the Set Up Collection section of your respective app, select Skip this step and use existing source and click Next.
In the Configure section of your respective app, complete the following fields.
1. Field Name. If you already have collectors and sources set up, select the configured metadata field name (eg _sourcecategory) or specify other custom metadata (eg: _collector) along with its metadata Field Value.
Click Next. You will be redirected to the Preview & Done section.

Post-installation

Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.

Viewing Akamai CPC dashboards

All dashboards have a set of filters that you can apply to the entire dashboard. Use these filters to drill down and examine the data to a granular level.

You can change the time range for a dashboard or panel by selecting a predefined interval from a drop-down list, choosing a recently used time range, or specifying custom dates and times. Learn more.
You can use template variables to drill down and examine the data on a granular level. For more information, see Filtering Dashboards with Template Variables.
Most Next-Gen apps allow you to provide the scope at the installation time and are comprised of a key (_sourceCategory by default) and a default value for this key. Based on your input, the app dashboards will be parameterized with a dashboard variable, allowing you to change the dataset queried by all panels. This eliminates the need to create multiple copies of the same dashboard with different queries.

Overview

The Akamai CPC - Overview dashboard provides a comprehensive snapshot of your client-side security posture and alert trends. It highlights alert volumes, severity levels, and configuration health over time, helping you quickly spot anomalies and areas needing attention. Security teams can monitor threat activity, identify impacted configurations, and understand common alert types. The dashboard also surfaces recurring risk indicators, such as compromised scripts, suspicious behavior, and sensitive data exposure, offering critical context for prioritizing incidents. By consolidating this information into one view, it enables faster threat response and more informed risk mitigation decisions.
Akamai-CPC-Overview

Security Overview

The Akamai CPC - Security Overview dashboard provides deep visibility into client-side security risks, enabling proactive detection of suspicious behavior and policy violations. It highlights critical indicators such as data exfiltration attempts, access to suspicious domains, abnormal script activity, and insecure data transmissions. With detailed event tracking and contextual insights, it helps security teams identify hidden threats, assess exposure, and ensure compliance. The dashboard supports investigations into high-risk scenarios, including compromised code, misconfigurations, and attempts to bypass protections—helping organizations safeguard user data, enforce security policies, and protect client-side environments.
Akamai-CPC-Security-Overview

Create monitors for Akamai CPC app

From your App Catalog:

From the Sumo Logic navigation, select App Catalog.
In the Search Apps field, search for and then select your app.
Make sure the app is installed.
Navigate to What's Included tab and scroll down to the Monitors section.
Click Create next to the pre-configured monitors. In the create monitors window, adjust the trigger conditions and notifications settings based on your requirements.
Scroll down to Monitor Details.
Under Location click on New Folder.
note
By default, monitor will be saved in the root folder. So to make the maintenance easier, create a new folder in the location of your choice.
Enter Folder Name. Folder Description is optional.
tip
Using app version in the folder name will be helpful to determine the versioning for future updates.
Click Create. Once the folder is created, click on Save.

Akamai CPC monitors

Name	Description	Trigger Type (Critical / Warning / MissingData)	Alert Condition
`Critical Severity Alerts`	This alert is triggered when client-side protection detects an event with critical severity. It indicates a high-impact threat that requires immediate investigation and remediation to prevent potential exploitation or data compromise.	Critical	Count > 0
`Credentials Sent Over Network Activities`	This alert is triggered when user credentials, such as passwords, are detected being transmitted over the network. It highlights potential security gaps or data leakage risks and helps enforce best practices around credential handling and data protection.	Critical	Count > 0

Upgrade/Downgrade the Akamai CPC app (Optional)

To update the app, do the following:

note

Select App Catalog.
In the Search Apps field, search for and then select your app.
Optionally, you can identify apps that can be upgraded in the Upgrade available section.
To upgrade the app, select Upgrade from the Manage dropdown.
1. If the upgrade does not have any configuration or property changes, you will be redirected to the Preview & Done section.
2. If the upgrade has any configuration or property changes, you will be redirected to the Setup Data page.
3. In the Configure section of your respective app, complete the following fields.
  1. Field Name. If you already have collectors and sources set up, select the configured metadata field name (eg _sourcecategory) or specify other custom metadata (eg: _collector) along with its metadata Field Value.
4. Click Next. You will be redirected to the Preview & Done section.

Post-update

Your upgraded app will be installed in the Installed Apps folder and dashboard panels will start to fill automatically.

note

See our Release Notes changelog for new updates in the app.

To revert the app to a previous version, do the following:

Select App Catalog.
In the Search Apps field, search for and then select your app.
To version down the app, select Revert to < previous version of your app > from the Manage dropdown.

Uninstalling the Akamai CPC app (Optional)

To uninstall the app, do the following:

Select App Catalog.
In the 🔎 Search Apps field, run a search for your desired app, then select it.
Click Uninstall.

Log types​

Sample log messages​

Sample queries​

Collection configuration and app installation​

Create a new collector and install the app​

Use an existing collector and install the app​

Use an existing source and install the app​

Viewing Akamai CPC dashboards​​

Overview​

Security Overview​

Create monitors for Akamai CPC app​

Akamai CPC monitors​

Upgrade/Downgrade the Akamai CPC app (Optional)​

Uninstalling the Akamai CPC app (Optional)​

Log types

Sample log messages

Sample queries

Collection configuration and app installation

Create a new collector and install the app

Use an existing collector and install the app

Use an existing source and install the app

Viewing Akamai CPC dashboards

Overview

Security Overview

Create monitors for Akamai CPC app

Akamai CPC monitors

Upgrade/Downgrade the Akamai CPC app (Optional)

Uninstalling the Akamai CPC app (Optional)