|
| 1 | +--- |
| 2 | +id: akamai-cpc-source |
| 3 | +title: Akamai CPC Source |
| 4 | +sidebar_label: Akamai CPC |
| 5 | +tags: |
| 6 | + - cloud-to-cloud |
| 7 | + - akamai-cpc |
| 8 | +description: Learn how to fetch CPC-Configs, CPC-Alerts, and CPC-Alert Details from the Akamai platform and send it to Sumo Logic. |
| 9 | +--- |
| 10 | + |
| 11 | +import CodeBlock from '@theme/CodeBlock'; |
| 12 | +import ExampleJSON from '/files/c2c/akamai-cpc/example.json'; |
| 13 | +import MyComponentSource from '!!raw-loader!/files/c2c/akamai-cpc/example.json'; |
| 14 | +import TerraformExample from '!!raw-loader!/files/c2c/akamai-cpc/example.tf'; |
| 15 | +import useBaseUrl from '@docusaurus/useBaseUrl'; |
| 16 | + |
| 17 | +<img src={useBaseUrl('img/integrations/saas-cloud/akamai.svg')} alt="Thumbnail icon" width="90"/> |
| 18 | + |
| 19 | +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. |
| 20 | + |
| 21 | +## Data collected |
| 22 | + |
| 23 | +| Polling Interval | Data | |
| 24 | +| :--- | :--- | |
| 25 | +| 12 hours | CPC-Configs | |
| 26 | +| 5 minutes | CPC-Alerts | |
| 27 | + |
| 28 | +## Setup |
| 29 | + |
| 30 | +### Vendor configuration |
| 31 | + |
| 32 | +You'll need a **Host Name**, **Client Token**, **Client Secret**, and **Access Token**. To generate these, follow these steps: |
| 33 | + |
| 34 | +- **Host Name**. The Akamai API base URL used to sending authenticated requests. |
| 35 | +- Refer to the [Akamai Documentation](https://techdocs.akamai.com/developer/docs/set-up-authentication-credentials) to generate **Client Token**, **Client Secret**, and **Access Token**. |
| 36 | + |
| 37 | +### Source configuration |
| 38 | + |
| 39 | +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](/docs/send-data/hosted-collectors/configure-hosted-collector). |
| 40 | + |
| 41 | +To configure an Akamai CPC Source: |
| 42 | +1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-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**. |
| 43 | +1. On the Collection page, click **Add Source** next to a Hosted Collector. |
| 44 | +1. Search for and select **Akamai CPC**. |
| 45 | +1. Enter a **Name** for the Source. The description is optional. |
| 46 | +1. (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`. |
| 47 | +1. (Optional) **Fields.** Click the **+Add Field** link to define the fields you want to associate. Each field needs a name (key) and value. |
| 48 | + *  A green circle with a checkmark is shown when the field exists in the Fields table schema. |
| 49 | + *  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). |
| 50 | +1. **Client Token**. Enter the Client token value collected from the Akamai platform. |
| 51 | +1. **Client Secret**. Enter the Client secret value collected from the Akamai platform. |
| 52 | +1. **Access Token**. Enter the Access token value collected from the Akamai platform. |
| 53 | +1. **API Host Name**. Enter the API Host Name value collected from the Akamai platform. |
| 54 | +1. (Optional) **Collect Alert Logs**. Select this checkbox to collect the alert logs from the Akamai platform. |
| 55 | + 1. (Optional) **Supported Severity Level**. Select the severity of the alert logs from the dropdown. |
| 56 | + 1. (Optional) **Supported Alert Type**. Select the type of alerts from the dropdown. |
| 57 | + 1. (Optional) **Supported Alert Status**. Select the status of the alerts from the dropdown. |
| 58 | +1. (Optional) **Collect Alert Details**. Select this checkbox to collect the alert details from the Akamai platform. |
| 59 | +1. The **CPC Configs Polling Interval** is set to 12 hours by default, you can adjust it based on your needs. |
| 60 | +1. (Optional) **Processing Rules for Logs**. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in [Create a Processing Rule](/docs/send-data/collection/processing-rules/create-processing-rule). |
| 61 | +1. When you are finished configuring the Source, click **Save**. |
| 62 | + |
| 63 | +## JSON configuration |
| 64 | + |
| 65 | +Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See [Use JSON to Configure Sources](/docs/send-data/use-json-configure-sources) for details. |
| 66 | + |
| 67 | +| Parameter | Type | Value | Required | Description | |
| 68 | +|:--|:--|:--|:--|:--| |
| 69 | +| schemaRef | JSON Object | `{"type":"Akamai CPC"}` | Yes | Define the specific schema type. | |
| 70 | +| sourceType | String | `"Universal"` | Yes | Type of source. | |
| 71 | +| config | JSON Object | [Configuration object](#configuration-object) | Yes | Source type specific values. | |
| 72 | + |
| 73 | +### Configuration Object |
| 74 | + |
| 75 | +| Parameter | Type | Required | Default | Description | Example | |
| 76 | +|:---|:---|:---|:---|:---|:---| |
| 77 | +| 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](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_source`. | `"mySource"` | |
| 78 | +| description | String | No | `null` | Type a description of the source. | `"Testing source"` | |
| 79 | +| category | String | No | `null` | Type a category of the source. This value is assigned to the [metadata](/docs/search/get-started-with-search/search-basics/built-in-metadata) field `_sourceCategory`. See [best practices](/docs/send-data/best-practices) for details. | `"mySource/test"` |
| 80 | +| 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"}` | |
| 81 | +| clientToken | String | Yes | `null` | A unique identifier used to authenticate API requests. | | |
| 82 | +| clientSecret | String | Yes | `null` | User account secret which will be used in authentication. | | |
| 83 | +| accessToken | String | Yes | `null` | Token granting access to the Akamai CPC API on behalf of a client. | | |
| 84 | +| akamaiHostName | String | Yes | `null` | The base URL of the Akamai API endpoint used to interact with CPC services. | | |
| 85 | +| collectAlertsLogs | Boolean | No | `null` | Specify if we need to collect the alert logs. | | |
| 86 | +| severityLevel | String Array | No | `null` | Specify the alert logs severity | | |
| 87 | +| alertType | String Array | No | `null` | Specify the type of alerts. | | |
| 88 | +| alertStatus | String Array | No | `null` | Specify the status of the alerts. | | |
| 89 | +| pollingIntervalAlertsMin | Integer | No | `5 minutes` | Time interval (in minutes) after which the source will check for new data.<br/>**Minimum**: 5 minutes<br/>**Maximum**: 60 minutes | | |
| 90 | +| collectAlertDetails | Boolean | No | `false` | Specify if we need to collect the alert details. | | |
| 91 | +| pollingIntervalCPCConfigsHrs | Integer | Yes | `12 hours` | Time interval (in minutes) after which the source will check for new data.<br/>**Minimum**: 1 hour<br/>**Maximum**: 24 hours | | |
| 92 | + |
| 93 | + |
| 94 | +### JSON example |
| 95 | + |
| 96 | +<CodeBlock language="json">{MyComponentSource}</CodeBlock> |
| 97 | + |
| 98 | +<a href="/files/c2c/akamai-cpc/example.json" target="_blank">Download example</a> |
| 99 | + |
| 100 | +### Terraform example |
| 101 | + |
| 102 | +<CodeBlock language="json">{TerraformExample}</CodeBlock> |
| 103 | + |
| 104 | +<a href="/files/c2c/akamai-cpc/example.tf" target="_blank">Download example</a> |
| 105 | + |
| 106 | +## FAQ |
| 107 | + |
| 108 | +:::info |
| 109 | +Click [here](/docs/c2c/info) for more information about Cloud-to-Cloud sources. |
| 110 | +::: |
0 commit comments