From 64d65205a582035ebf10481b35802b03171ca5ea Mon Sep 17 00:00:00 2001 From: surabhipatel_crest Date: Thu, 12 Dec 2024 17:02:38 +0530 Subject: [PATCH 01/16] Updated readme format --- mimecast/README.md | 33 +++++++++++++--------------- palo_alto_cortex_xdr/README.md | 40 +++++++++++++++------------------- sophos_central_cloud/README.md | 37 ++++++++++++++----------------- 3 files changed, 49 insertions(+), 61 deletions(-) diff --git a/mimecast/README.md b/mimecast/README.md index 29266260e8109..73526ae473cfa 100644 --- a/mimecast/README.md +++ b/mimecast/README.md @@ -1,3 +1,5 @@ +# Mimecast + ## Overview [Mimecast][1] is a cloud-based solution designed to protect organizations from a wide range of email-based threats. The product offers a comprehensive set of security features that help to safeguard against advanced threats, such as phishing, malware, spam, and targeted attacks, while also providing data leak prevention and email continuity services. @@ -15,13 +17,9 @@ The Mimecast integration seamlessly collects all the above listed logs, channeli ## Setup -### Configuration - -#### Get Credentials of Mimecast - -To find your application's details in Mimecast Email Security: +### Generate API Credentials in Mimecast -1. Sign into Mimecast Email Security with your credentials. +1. Log in to your **Mimecast account**. 2. Navigate to the **Administration Console**, select **Services**, and then choose the **API and Platform Integrations** section. 3. Proceed to Your **API 2.0 Applications**. 4. Search for your application in the list provided. @@ -30,27 +28,26 @@ To find your application's details in Mimecast Email Security: - Click the **Generate keys** button of Mimecast API 2.0 tile. - Check the **I accept** checkbox, click on **Next**. - In **Application Details** step, fill out the following details according to the instructions: - - Application Name: Enter the application name of your choice + - Application Name: Enter a meaningful name of application - Category: Select **SIEM Integration** - Products: Click **Select all** option - Application Role: Select **Basic Administrator** - Description: Enter the description of your choice - In **Notifications**, provide the contact details of your technical administrator and click on **Next** - - After clicking on **Add and Generate Keys** there will be pop up window showing Client ID and Client Secret. Please copy those keys to a safe place as they won't be displayed again. + - After clicking on **Add and Generate Keys**. There will be a pop up window showing Client ID and Client Secret. Copy and store **Client ID** and **Client Secret** in a secure location. 6. If the application is present, click on its name. -7. Click the **Manage API 2.0 credentials** button and click **Generate**. This generates a new Client ID and Client Secret. Please copy those keys to a safe place as they won't be displayed again. +7. Click the **Manage API 2.0 credentials** button and click **Generate**. This generates a new Client ID and Client Secret. Copy and store **Client ID** and **Client Secret** in a secure location. -#### Mimecast DataDog Integration Configuration +### Connect your Mimecast Account to Datadog -Configure the Datadog endpoint to forward Mimecast logs to Datadog. +1. Add your Mimecast credentials. -1. Navigate to `Mimecast`. -2. Add your Mimecast credentials. + | Parameters | Description | + | ------------------- | ------------------------------------------------------------ | + | Client ID | The Client ID of your registered application on Mimecast | + | Client Secret | The Client Secret of your registered application on Mimecast | -| Mimecast Parameters | Description | -| ------------------- | ------------------------------------------------------------ | -| Client ID | The Client ID of your registered application on mimecast | -| Client Secret | The Client Secret of your registered application on mimecast | +2. Click the Save button to save your settings. ## Data Collected @@ -72,7 +69,7 @@ The Mimecast integration does not include any events. ## Support -For further assistance, contact [Datadog Support][2]. +Need help? Contact [Datadog Support][2]. [1]: https://www.mimecast.com/ [2]: https://docs.datadoghq.com/help/ diff --git a/palo_alto_cortex_xdr/README.md b/palo_alto_cortex_xdr/README.md index 1adb712d95857..73d844ce5e7ae 100644 --- a/palo_alto_cortex_xdr/README.md +++ b/palo_alto_cortex_xdr/README.md @@ -1,4 +1,4 @@ -# Palo Alto Cortex XDR Integration For Datadog +# Palo Alto Cortex XDR ## Overview @@ -6,21 +6,18 @@ This integration ingests the following logs: -- Incident -- Alert +- Incident: Represents information of artifacts, assets, and alerts from a threat event, including their severity, status, and the users who handle them. +- Alert: Represents real-time analysis of alerts, including their severity, frequency, and source. -The Palo Alto Cortex XDR integration seamlessly collect the data of Palo Alto Cortex XDR logs using REST APIs. -Before ingesting the data, it normalizes and enriches the logs, ensuring a consistent data format and enhancing information content for downstream processing and analysis. The integration provides insights into incidents and alerts using out-of-the-box dashboards. +The Palo Alto Cortex XDR integration seamlessly collects the data of Palo Alto Cortex XDR logs using REST APIs. Before ingesting the data, it normalizes and enriches the logs, ensuring a consistent data format and enhancing information content for downstream processing and analysis. The integration provides insights into incidents and alerts using out-of-the-box dashboards. ## Setup -### Configuration +### Generate API credentials in Palo Alto Cortex XDR -#### Get Credentials of Palo Alto Cortex XDR +#### Steps to generate API key -#### Steps to create API key - -1. Sign into your **Palo Alto Cortex XDR** instance. +1. Log in to your **Palo Alto Cortex XDR account**. 2. Navigate to **Settings** > **Configurations** > **Integrations** > **API Keys**. 3. Click on **New Key**. 4. Choose the type of API key based on your desired security level, **Advanced** or **Standard**. @@ -30,7 +27,7 @@ Before ingesting the data, it normalizes and enriches the logs, ensuring a consi 8. Click **Generate** to generate the API key. 9. Copy the API key, and then click **Done**. This value represents your unique **Authorization:{key}** -#### Steps to get Cortex XDR API Key ID +#### Steps to get API Key ID 1. In the API Keys table, locate the ID field. 2. Note your corresponding ID number. This value represents the **x-xdr-auth-id:{key_id}** token. @@ -40,24 +37,23 @@ Before ingesting the data, it normalizes and enriches the logs, ensuring a consi 1. Right-click your API key and select **View Examples**. 2. Copy the **CURL Example** URL. The example contains your unique **FQDN**. -#### Palo Alto Cortex XDR DataDog Integration Configuration +### Connect your Palo Alto Cortex XDR Account to Datadog -Configure the Datadog endpoint to forward Palo Alto Cortex XDR logs to Datadog. +1. Add your Palo Alto Cortex XDR credentials. -1. Navigate to `Palo Alto Cortex XDR`. -2. Add your Palo Alto Cortex XDR credentials. + | Parameters | Description | + | -------------| ------------ | + | API key | The API key from Palo Alto Cortex XDR. | + | API Key ID | The auth id from Palo Alto Cortex XDR. | + | FQDN | The FQDN from Palo Alto Cortex XDR. It is the `baseUrl` part of `baseUrl/public_api/v1/{name of api}/{name of call}/` | -| Palo Alto Cortex XDR Parameters | Description | -| ------------------------------- | ------------ | -| API key | The API key from Palo Alto Cortex XDR. | -| API Key ID | The auth id from Palo Alto Cortex XDR. | -| FQDN | The FQDN from Palo Alto Cortex XDR. It is the `baseUrl` part of `baseUrl/public_api/v1/{name of api}/{name of call}/` | +2. Click the Save button to save your settings. ## Data Collected ### Logs -The Palo Alto Cortex XDR integration collects and forwards Palo Alto Cortex XDR Incident and alert logs to Datadog. +The Palo Alto Cortex XDR integration collects and forwards Palo Alto Cortex XDR incident and alert logs to Datadog. ### Metrics @@ -69,7 +65,7 @@ The Palo Alto Cortex XDR integration does not include any events. ## Support -For further assistance, contact [Datadog Support][2]. +Need help? Contact [Datadog Support][2]. [1]: https://docs-cortex.paloaltonetworks.com/p/XDR [2]: https://docs.datadoghq.com/help/ diff --git a/sophos_central_cloud/README.md b/sophos_central_cloud/README.md index c76d02423ee0e..999ed8a282cde 100644 --- a/sophos_central_cloud/README.md +++ b/sophos_central_cloud/README.md @@ -1,4 +1,4 @@ -# Sophos Central Cloud Integration for Datadog +# Sophos Central Cloud ## Overview @@ -6,44 +6,39 @@ This integration ingests the following logs: -* Alerts - * Sophos Alert refers to a notification or warning generated by Sophos Central Cloud in response to a security event or potential threat. Alerts are triggered based on predefined security policies, detection rules, or anomalous activities identified by the Sophos Central Cloud. -* Events - * Sophos Event refers to a specific occurrence that is detected and recorded by Sophos Central Cloud. Events can include various security-related activities such as malware detection, unauthorized access attempts, system vulnerabilities, and other security events. +- Alert: Represents a notification or warning generated by Sophos Central Cloud in response to a security event or potential threat. Alerts are triggered based on predefined security policies, detection rules, or anomalous activities identified by the Sophos Central Cloud. +- Event: Represents a specific occurrence that is detected and recorded by Sophos Central Cloud. Events can include various security-related activities such as malware detection, unauthorized access attempts, system vulnerabilities, and other security events. The Sophos Central Cloud integration seamlessly collects all the above listed logs, channeling them into Datadog for analysis. Leveraging the built-in logs pipeline, these logs are parsed and enriched, enabling effortless search and analysis. The integration provides insight into alerts and events through the out-of-the-box dashboards. Additionally, the integration enriches corresponding endpoint details along with alert and event logs through the **get_endpoint_details** flag. ## Setup -### Configuration +### Generate API credentials in Sophos Central Cloud -#### Sophos Central Cloud Configuration - -1. Login to [**Sophos Central Platform**][2] with your credentials. +1. Log in to your [**Sophos Central account**][2]. 2. From Sophos Central Admin, go to **My Products** > **General Settings** > **API Credentials Management**. 3. Click **Add Credential**. 4. Provide a credential name, select the appropriate role, add an optional description, and click the **Add** button. The **API credential Summary** for this credential is displayed. 5. Click **Show Client Secret** to display the **Client Secret**. -6. Copy the **Client ID** and **Client Secret**. +6. Copy the **Client ID** and **Client Secret** and store them in a secure location. -#### Sophos Central Cloud DataDog Integration Configuration +### Connect your Sophos Central Cloud Account to Datadog -Configure the Datadog endpoint to forward Sophos Central Cloud events as logs to Datadog. +1. Add your Sophos Central Cloud credentials. -1. Navigate to `Sophos Central Cloud`. -2. Add your Sophos Central Cloud credentials. + | Parameters | Description | + | ------------------------------- | -------------------------------------------------------------------------- | + | Client ID | The Client ID from Sophos Central Cloud. | + | Client Secret | The Client Secret from Sophos Central Cloud. | + | Get Endpoint Details | Set to "true" to collect endpoint details for Sophos Central Cloud Alert and Event Logs, otherwise set to "false". The Default is "true". | -| Sophos Central Cloud Parameters | Description | -| ------------------------------- | -------------------------------------------------------------------------- | -| Client ID | The Client ID from Sophos Central Cloud. | -| Client Secret | The Client Secret from Sophos Central Cloud. | -| Get Endpoint Details | Set to "true" to collect endpoint details for Sophos Central Cloud Alert and Event Logs, otherwise set to "false". Default is "true". | +2. Click the Save button to save your settings. ## Data Collected ### Logs -The integration collects and forwards Sophos Central Cloud Alert and Event logs to Datadog. +The integration collects and forwards Sophos Central Cloud alert and event logs to Datadog. ### Metrics @@ -55,7 +50,7 @@ The Sophos Central Cloud integration does not include any events. ## Support -For further assistance, contact [Datadog Support][3]. +Need help? Contact [Datadog Support][3]. [1]: https://www.sophos.com/en-us/products/sophos-central [2]: https://cloud.sophos.com/manage/login From f09b6dd138be95c83dd8c580ddaa76de3857f480 Mon Sep 17 00:00:00 2001 From: akaila-crest Date: Thu, 12 Dec 2024 17:17:09 +0530 Subject: [PATCH 02/16] update hubspot-content-hub readme --- hubspot_content_hub/README.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/hubspot_content_hub/README.md b/hubspot_content_hub/README.md index a6e04726a05a7..feb80d9f4712c 100644 --- a/hubspot_content_hub/README.md +++ b/hubspot_content_hub/README.md @@ -11,9 +11,7 @@ The integration includes dashboards that show and analyze both Activity Logs and ## Setup -### Configuration - -#### Get HubSpot Content Hub Credentials +### Generate API credentials in HubSpot Content Hub 1. Log in to [HubSpot Content Hub][2] 2. Navigate to **Settings > Integrations > Private Apps**. @@ -27,20 +25,25 @@ The integration includes dashboards that show and analyze both Activity Logs and 7. Review the details in the dialog box and click **Continue creating**. 8. In the success popup, click **Show Token**. -#### Add HubSpot Credentials - -- HubSpot Access Token +### Connect your HubSpot Content Hub Account to Datadog +1. Add your Access Token + |Parameters|Description| + |--------------------|--------------------| + |Access Token|Access token for your HubSpot private app.| +2. Click the Save button to save your settings. ## Data Collected ### Logs -The HubSpot Content Hub integration collects and forward Activity logs to Datadog. +The HubSpot Content Hub integration collects and forwards Activity logs to Datadog. ### Metrics -The HubSpot Content Hub integration collects and forward Analytics metrics to Datadog. +The HubSpot Content Hub integration collects and forwards Analytics metrics to Datadog. + +{{< get-metrics-from-git "hubspot-content-hub" >}} ### Service Checks From d0d03713cc365dfee5f7ba2162c0c31615010461 Mon Sep 17 00:00:00 2001 From: akaila-crest Date: Thu, 12 Dec 2024 17:17:29 +0530 Subject: [PATCH 03/16] update shopify readme --- shopify/README.md | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/shopify/README.md b/shopify/README.md index dbebe4f49dc51..b51b2cf64892b 100644 --- a/shopify/README.md +++ b/shopify/README.md @@ -10,9 +10,7 @@ It includes dashboards that show and analyze logs, making it easier to monitor a ## Setup -### Configuration - -#### Get Shopify credentials +### Generate API credentials in Shopify 1. Log in to [Shopify][2] admin account. 2. The Shopify Store name is the `xxxx` part of the Store URL (`https://admin.shopify.com/store/xxxx`). 3. Navigate to **Settings > Apps and sales channels**. @@ -26,12 +24,15 @@ It includes dashboards that show and analyze logs, making it easier to monitor a - **read_content** - **read_price_rules** 8. Click **Save** to apply the changes. -9. Click **Install app**. -10. Under the **Admin API access token** section, click **Reveal token once**. - -#### Add Shopify credentials -- Shopify Store Name -- Shopify Access Token +9. Click **Install app** and get the **Access Token** from the **Admin API access token** section. + +### Connect your Shopify Account to Datadog +1. Add your Store Name and Access Token + |Parameters|Description| + |--------------------|--------------------| + |Store Name|Store name of your Shopify admin account.| + |Access Token|Access Token for your Shopify admin account.| +2. Click the Save button to save your settings. ## Data Collected From 5257e3809f308b640272a91b52551d9463d17f2a Mon Sep 17 00:00:00 2001 From: akaila-crest Date: Thu, 12 Dec 2024 17:17:47 +0530 Subject: [PATCH 04/16] update StreamNative readme --- streamnative/README.md | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/streamnative/README.md b/streamnative/README.md index ab65f9b40ca2b..1a1ee8f7d53d0 100644 --- a/streamnative/README.md +++ b/streamnative/README.md @@ -14,18 +14,16 @@ The StreamNative integration collects the following types of [metrics][2]: ## Setup -### Configuration +### Generate API credentials in StreamNative -#### Get StreamNative credentials - -Log into the [StreamNative Cloud Console Account][3]. -##### Get the `Organization ID` and `Instance Name`: +Log in to [StreamNative Cloud Console Account][3]. +#### Generate `Organization ID` and `Instance Name`: 1. Click the profile icon and select **Organizations**. 2. Choose the **Organization** for which data needs to be collected. -3. From the **Select an Instance** dropdown, note the **Instance Name**. +3. From the **Select an Instance** dropdown, get the **Instance Name**. -##### Get the `Client ID` and `Client Secret`: +#### Generate `Client ID` and `Client Secret`: 1. Click the profile icon and navigate to the **Accounts & Accesses** tab. 2. Find the Service Account with **Admin** permissions set to **Enabled**. @@ -34,12 +32,16 @@ Log into the [StreamNative Cloud Console Account][3]. 4. Select **Download OAuth2 Key** to obtain the **Client ID** and **Client Secret**. -#### Add StreamNative credentials +### Connect your StreamNative Account to Datadog -- Organization ID -- Instance Name -- Client ID -- Client Secret +1. Add your Organization ID, Instance Name, Client ID, and Client Secret + |Parameters|Description| + |--------------------|--------------------| + |Organization ID|Organization ID of your StreamNative account.| + |Instance Name|Instance name of the corresponding organization.| + |Client ID |Client ID of your service account.| + |Client Secret|Client Secret of your service account.| +2. Click the Save button to save your settings. ## Data Collected @@ -69,4 +71,4 @@ Need help? Contact [Datadog support][4]. [1]: https://streamnative.io/ [2]: https://docs.streamnative.io/docs/cloud-metrics-api#metrics-endpoint [3]: https://console.streamnative.cloud/ -[4]: https://docs.datadoghq.com/help/ \ No newline at end of file +[4]: https://docs.datadoghq.com/help/ From da284355a7fbaec4f28a93490116c362f23dcc75 Mon Sep 17 00:00:00 2001 From: Shubham Vekariya Date: Fri, 13 Dec 2024 16:42:40 +0530 Subject: [PATCH 05/16] Update Trend Micro integrations README --- trend_micro_email_security/README.md | 21 +++++++++++-------- .../README.md | 21 +++++++++++-------- 2 files changed, 24 insertions(+), 18 deletions(-) diff --git a/trend_micro_email_security/README.md b/trend_micro_email_security/README.md index b7ec289113a72..8e496d54f75d9 100644 --- a/trend_micro_email_security/README.md +++ b/trend_micro_email_security/README.md @@ -4,16 +4,14 @@ This integration ingests the following logs: -- Policy events and detection -- Mail tracking +- Policy events and detection - This logs provide information about policy events and detection, allowing you to monitor and respond to potential security threats effectively. +- Mail tracking - This logs provide information about email activities, including accepted and blocked traffic, allowing you to track email messages that have passed through the system and monitor their delivery status. Use out-of-the-box dashboards to visualize detailed insights into email traffic analysis, real-time threat detection, security detection and observation, and compliance monitoring. ## Setup -### Configuration - -#### Get Credentials of Trend Micro Email Security +### Generate API Credentials in Trend Micro Email Security 1. Log on to the Trend Micro Email Security administrator console. 2. Navigate to **Administration** > **Service Integration** > **API Access**. @@ -22,11 +20,16 @@ Use out-of-the-box dashboards to visualize detailed insights into email traffic 5. To identify the **Host Region** of your Trend Micro Email Security, please refer this [link][3]. 6. **Username** is **Login ID** of your Trend Micro Email Security console. -#### Add your Trend Micro Email Security Credentials +### Connect your Trend Micro Email Security Account to Datadog + +1. Add your Host Region, Username, and API Key. + | Parameters | Description | + | ----------- | --------------------------------------------------------------------- | + | Host Region | The Region of the Trend Micro Email Security administrator console. | + | Username | The Username of the Trend Micro Email Security administrator console. | + | API Key | The API Key of the Trend Micro Email Security administrator console. | -- Host Region -- Username -- API key +2. Click the Save button to save your settings. ## Data Collected diff --git a/trend_micro_vision_one_endpoint_security/README.md b/trend_micro_vision_one_endpoint_security/README.md index beea3996ca03b..c3e46ccdabe44 100644 --- a/trend_micro_vision_one_endpoint_security/README.md +++ b/trend_micro_vision_one_endpoint_security/README.md @@ -24,9 +24,7 @@ Use out-of-the-box dashboards to gain detailed insights into system events, netw ## Setup -### Configuration - -#### Get Credentials of Trend Micro Vision One Endpoint Security +### Generate API Credentials in Trend Micro Vision One Endpoint Security 1. Log in to the Trend Micro Vision One console. 2. Go to **Endpoint Security** (Sidebar) > **Standard Endpoint Protection** > **Administration** > **Settings** > **Automation API Access Settings**. @@ -40,18 +38,23 @@ Use out-of-the-box dashboards to gain detailed insights into system events, netw 2. **Communication time-out**: Select 120 seconds for a request to reach Apex Central after the application generates the request. 6. Click **Save**. -#### Get Timezone of Trend Micro Vision One console +### Get Timezone of Trend Micro Vision One console 1. Log in to the Trend Micro Vision One console. 2. Go to **Administration** (Sidebar) > **Console Settings** > **Time Zone**. 3. Check the **Timezone** from **Current console time**. -#### Add your Trend Micro Vision One Endpoint Security credentials +### Connect your Trend Micro Vision One Endpoint Security Account to Datadog + +1. Add your API Host, Application ID, API Key and select the Time Zone from the dropdown. + | Parameters | Description | + | -------------- | ----------------------------------------------------------------------- | + | API Host | The API Host of Trend Micro Vision One Endpoint Security console. | + | Application ID | The Application ID of Trend Micro Vision One Endpoint Security console. | + | API Key | The API Key of of Trend Micro Vision One Endpoint Security console. | + | Time Zone | The Time Zone of the Trend Micro Vision One console. | -- API Host -- Application ID -- API Key -- Time Zone (This timezone should be the same as the Trend Vision One console.) +2. Click the Save button to save your settings. ## Data Collected From 5b4a484d268c86165d6a75354a3df18eaafb06ce Mon Sep 17 00:00:00 2001 From: manan-crest Date: Fri, 13 Dec 2024 18:02:06 +0530 Subject: [PATCH 06/16] Update: Readme for cisco_secure_email_threat_defense and cisco_secure_endpoint integration --- cisco_secure_email_threat_defense/README.md | 18 +++++++++++++- cisco_secure_endpoint/README.md | 27 ++++++++------------- 2 files changed, 27 insertions(+), 18 deletions(-) diff --git a/cisco_secure_email_threat_defense/README.md b/cisco_secure_email_threat_defense/README.md index bded8f0d8ca3b..3dbd9fb891920 100644 --- a/cisco_secure_email_threat_defense/README.md +++ b/cisco_secure_email_threat_defense/README.md @@ -11,7 +11,7 @@ The Cisco Secure Email Threat Defense integration provides out-of-the-box dashbo ## Setup -### Configuration +### Generate API credentials in Cisco Secure Email Threat Defense 1. Log in to the Cisco Secure Email Threat Defense UI. 2. Navigate to **Administration** and select the **API Clients** tab. @@ -20,6 +20,22 @@ The Cisco Secure Email Threat Defense integration provides out-of-the-box dashbo 5. Click on **Submit**. This generates your **Client ID** and **Client Password**. 6. Retrieve the API key from the **API Key** section. +### Connect your Cisco Secure Email Threat Defense Account to Datadog + +1. Add your Cisco Secure Email Threat Defense credentials + + | Parameters | Description | + | ---------- | ----------- | + | Host Name | Host Name is based on the region where your Cisco Secure Email Threat Defense server is located. For details, please reach out to your system administrator. | + | Client ID | Client ID from Cisco Secure Email Threat Defense Account | + | Client Password | Client Password from Cisco Secure Email Threat Defense Account | + | API Key | API Key from Cisco Secure Email Threat Defense Account | + | Verdict Delay | Events are fetched with a delay according to the time(in minute) specified in the Verdict Delay | + + +2. Click the Save button to save your settings. + + ## Data Collected ### Logs diff --git a/cisco_secure_endpoint/README.md b/cisco_secure_endpoint/README.md index 6f88038d18f0f..05008df8dafa9 100644 --- a/cisco_secure_endpoint/README.md +++ b/cisco_secure_endpoint/README.md @@ -12,12 +12,8 @@ The Cisco Secure Endpoint integration provides out-of-the-box dashboards so you ## Setup -### Configuration +### Generate API Credentials in Cisco Secure Endpoint -#### Get API Credentials for Cisco Secure Endpoint - - -Follow the steps below to create a Client ID and an API key: 1. Log in to your Cisco Secure Endpoint Console and navigate to the Menu Panel on the left side. 2. Select `Administration`, then select `Organization Settings`. 3. Click `Configure API Credentials` under the `Features` section to generate new API credentials. @@ -27,22 +23,19 @@ Follow the steps below to create a Client ID and an API key: - Scope: Select `Read-only`. - Click `Create`. - Once you click **Create**, the redirected page will display the client ID (like a third party API client ID) and API Key values. - - **Note:** Make a note of the API Key, as it will only be displayed once. - -#### Cisco Secure Endpoint DataDog Integration Configuration -Configure the Datadog endpoint to forward Cisco Secure Endpoint logs to Datadog. +### Connect your Cisco Secure Endpoint Account to Datadog -1. Navigate to `Cisco Secure Endpoint`. -2. Add your Cisco Secure Endpoint credentials. +1. Add your Cisco Secure Endpoint credentials -| Cisco Secure Endpoint Parameters | Description | -| -------------------- | ------------ | -| API Domain Name | The API Domain Name for Cisco Secure Endpoint Cloud is "api.\.amp.cisco.com". Adjust the "region" part based on the region of the Cisco Secure Endpoint server. If Cisco Secure Endpoint is hosted on VPC (Virtual Private Cloud), directly provide the API Domain Name. | -| Client ID | Client ID from Cisco Secure Endpoint. | -| API Key | API Key from Cisco Secure Endpoint. | -| Get Endpoint Details | Keep it "true" to collect endpoint metadata for Cisco Secure Endpoint event logs, otherwise "false". Default value is "true". | + | Parameters | Description | + | ---------- | ------------ | + | API Domain Name | The API Domain Name for Cisco Secure Endpoint Cloud is "api.\.amp.cisco.com". Adjust the "region" part based on the region of the Cisco Secure Endpoint server. If Cisco Secure Endpoint is hosted on VPC (Virtual Private Cloud), directly provide the API Domain Name. | + | Client ID | Client ID from Cisco Secure Endpoint. | + | API Key | API Key from Cisco Secure Endpoint. | + | Get Endpoint Details | Keep it "true" to collect endpoint metadata for Cisco Secure Endpoint event logs, otherwise "false". Default value is "true". | +2. Click the Save button to save your settings. ## Data Collected From 8040b83837622f6294b1cbe4305b20e46496ae1d Mon Sep 17 00:00:00 2001 From: Bhavik Parmar Date: Mon, 16 Dec 2024 16:17:28 +0530 Subject: [PATCH 07/16] Contentful README.md modified --- contentful/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/contentful/README.md b/contentful/README.md index 8c5e2085e3a5d..572f38845eaa3 100644 --- a/contentful/README.md +++ b/contentful/README.md @@ -1,3 +1,5 @@ +# Contentful + ## Overview [Contentful][1] is a content (articles, photos, and videos) management platform that allows businesses to create, manage, and deliver digital content across various channels like websites and mobile apps through its intuitive interface and robust APIs or SDKs. From f5257d2e97c5bd3c32f05a8b98172ec6f1728011 Mon Sep 17 00:00:00 2001 From: Bhavik Parmar Date: Mon, 16 Dec 2024 16:17:42 +0530 Subject: [PATCH 08/16] Incident.io README.md modified --- incident_io/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/incident_io/README.md b/incident_io/README.md index b4ebc31dc6f69..25710632c5bd2 100644 --- a/incident_io/README.md +++ b/incident_io/README.md @@ -1,3 +1,5 @@ +# Incident IO + ## Overview [incident.io][1] helps companies declare, collaborate, communicate around, and learn from events that disturb their normal course of business-from critical infrastructure being down, to data breaches and security incidents. It is a service that helps teams manage incidents and outages effectively. It typically provides features like incident reporting, tracking, and resolution workflows. From 64b917716693e7f1c71c015732dd96c74c29c0c4 Mon Sep 17 00:00:00 2001 From: Bhavik Parmar Date: Mon, 16 Dec 2024 16:18:18 +0530 Subject: [PATCH 09/16] LastPass README.md format changed --- lastpass/README.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/lastpass/README.md b/lastpass/README.md index b73232f5557f3..c94e04d3b41fc 100644 --- a/lastpass/README.md +++ b/lastpass/README.md @@ -1,3 +1,5 @@ +# LastPass + ## Overview [LastPass][1] is a password management solution that securely stores and manages passwords and other sensitive @@ -10,23 +12,21 @@ reporting events, while out-of-the-box detection rules enhance detection and res ## Setup -### Configuration - -#### Get config parameters of LastPass +### Get config parameters of LastPass -##### Account number +#### Account number 1. Log in to the [Admin Console](https://admin.lastpass.com/) with your email address and master password. 2. On the **Dashboard** tab, click the profile email located in the top right corner to find the account number. 3. Alternatively, you can find the account number by navigating to **Advanced** > **Enterprise API**. -##### Provisioning hash +#### Provisioning hash 1. Log in to the [Admin Console](https://admin.lastpass.com) with your email address and master password. 2. Navigate to **Advanced** > **Enterprise API**. 3. From there, you can create or reset a provisioning hash if you forgot it. -##### Time zone +#### Time zone 1. The options in the **Time Zone** dropdown menu are based on LastPass' time zone values. 2. You must select the time zone that is configured in your LastPass account. @@ -36,18 +36,18 @@ reporting events, while out-of-the-box detection rules enhance detection and res - Navigate to **Account Settings**. - Find the selected time zone under the **Account Information** section. -#### Configure the LastPass and Datadog integration -Configure the Datadog endpoint to forward LastPass logs to Datadog. +### Connect your LastPass account to Datadog + +1. Add your Account number, Provisioning hash and Time zone + |Parameters|Description| + |--------------------|--------------------| + |Account number|The account number of your registered LastPass account.| + |Provisioning hash|The provisioning hash secret of your registered account on LastPass.| + |Time zone|The time zone of your registered account on LastPass.| -1. Navigate to `LastPass` integration on Datadog platform. -2. Add your LastPass credentials. +2. Click the Save button to save your settings. -| LastPass Parameters | Description | -|---------------------|----------------------------------------------------------------------| -| Account number | The account number of your registered LastPass account. | -| Provisioning hash | The provisioning hash secret of your registered account on LastPass. | -| Time zone | The time zone of your registered account on LastPass | ## Data Collected From 3ccf83095f47f96a22b733562fe9f97698af60c2 Mon Sep 17 00:00:00 2001 From: Bhavik Parmar Date: Mon, 16 Dec 2024 16:18:30 +0530 Subject: [PATCH 10/16] MUX README.md format changed --- mux/README.md | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/mux/README.md b/mux/README.md index 26d7b13e44832..06229ff50bbd4 100644 --- a/mux/README.md +++ b/mux/README.md @@ -8,9 +8,8 @@ Integrate Mux with Datadog to gain insights into mux video performance data. ## Setup -### Get config parameters from Mux +### Generate Access Token ID and Secret Key in Mux -#### Find your Access Token ID and Secret Key from Mux 1. Login to [MUX account][2]. 2. In the sidebar, click on **Settings**. 3. Click on **Access Tokens**. @@ -21,9 +20,17 @@ Integrate Mux with Datadog to gain insights into mux video performance data. 8. Click on **Generate Token**. 9. Save the Access Token ID and Secret Key from the **Here's your new Access Token** tab. -### Add your Mux credentials -- Access token ID -- Secret key + +### Connect your Mux account to Datadog + +1. Add your Access Token ID and Secret Key + |Parameters|Description| + |--------------------|--------------------| + |Access Token ID|Access Token ID of MUX account.| + |Secret Key|Secret Key of MUX account.| + +2. Click the Save button to save your settings. + ## Data Collected @@ -43,7 +50,7 @@ The Mux integration does not include any service checks. The Mux integration does not include any events. -## Troubleshooting +## Support Need help? Contact [Datadog support][3]. From 92da55d4c8e014829ab754db37e972a3d02415e0 Mon Sep 17 00:00:00 2001 From: Bhavik Parmar Date: Mon, 16 Dec 2024 17:38:14 +0530 Subject: [PATCH 11/16] README changed for lastpass & mux --- lastpass/README.md | 14 +++----------- mux/README.md | 3 +-- 2 files changed, 4 insertions(+), 13 deletions(-) diff --git a/lastpass/README.md b/lastpass/README.md index c94e04d3b41fc..dd90efa3a3144 100644 --- a/lastpass/README.md +++ b/lastpass/README.md @@ -12,21 +12,13 @@ reporting events, while out-of-the-box detection rules enhance detection and res ## Setup -### Get config parameters of LastPass - -#### Account number +### Generate API credentials in LastPass 1. Log in to the [Admin Console](https://admin.lastpass.com/) with your email address and master password. -2. On the **Dashboard** tab, click the profile email located in the top right corner to find the account number. -3. Alternatively, you can find the account number by navigating to **Advanced** > **Enterprise API**. - -#### Provisioning hash - -1. Log in to the [Admin Console](https://admin.lastpass.com) with your email address and master password. 2. Navigate to **Advanced** > **Enterprise API**. -3. From there, you can create or reset a provisioning hash if you forgot it. +3. You can find the Account number and can create a Provisioning hash. -#### Time zone +### Get Timezone of LastPass 1. The options in the **Time Zone** dropdown menu are based on LastPass' time zone values. 2. You must select the time zone that is configured in your LastPass account. diff --git a/mux/README.md b/mux/README.md index 06229ff50bbd4..a8d40f6bc0831 100644 --- a/mux/README.md +++ b/mux/README.md @@ -17,8 +17,7 @@ Integrate Mux with Datadog to gain insights into mux video performance data. 5. Choose the environment. 6. Under the **permission** section, select **Mux Data(read-only)**. 7. Enter the access token name. -8. Click on **Generate Token**. -9. Save the Access Token ID and Secret Key from the **Here's your new Access Token** tab. +8. Click on **Generate Token** to find Access Token ID and Secret Key. ### Connect your Mux account to Datadog From 6b27d93fc3bc031e61a7a1378c2bd9b755c3bfce Mon Sep 17 00:00:00 2001 From: surabhipatel_crest Date: Mon, 16 Dec 2024 18:15:10 +0530 Subject: [PATCH 12/16] Updated Readme of pingone --- mimecast/README.md | 4 ++-- palo_alto_cortex_xdr/README.md | 7 ++----- ping_one/README.md | 38 +++++++++++++++++----------------- sophos_central_cloud/README.md | 3 +-- 4 files changed, 24 insertions(+), 28 deletions(-) diff --git a/mimecast/README.md b/mimecast/README.md index 73526ae473cfa..b32cc95695683 100644 --- a/mimecast/README.md +++ b/mimecast/README.md @@ -34,9 +34,9 @@ The Mimecast integration seamlessly collects all the above listed logs, channeli - Application Role: Select **Basic Administrator** - Description: Enter the description of your choice - In **Notifications**, provide the contact details of your technical administrator and click on **Next** - - After clicking on **Add and Generate Keys**. There will be a pop up window showing Client ID and Client Secret. Copy and store **Client ID** and **Client Secret** in a secure location. + - After clicking on **Add and Generate Keys**. There will be a pop up window showing Client ID and Client Secret. 6. If the application is present, click on its name. -7. Click the **Manage API 2.0 credentials** button and click **Generate**. This generates a new Client ID and Client Secret. Copy and store **Client ID** and **Client Secret** in a secure location. +7. Click the **Manage API 2.0 credentials** button and click **Generate**. This generates a new Client ID and Client Secret. ### Connect your Mimecast Account to Datadog diff --git a/palo_alto_cortex_xdr/README.md b/palo_alto_cortex_xdr/README.md index 73d844ce5e7ae..ee57b33d9ab5f 100644 --- a/palo_alto_cortex_xdr/README.md +++ b/palo_alto_cortex_xdr/README.md @@ -15,8 +15,6 @@ The Palo Alto Cortex XDR integration seamlessly collects the data of Palo Alto C ### Generate API credentials in Palo Alto Cortex XDR -#### Steps to generate API key - 1. Log in to your **Palo Alto Cortex XDR account**. 2. Navigate to **Settings** > **Configurations** > **Integrations** > **API Keys**. 3. Click on **New Key**. @@ -25,14 +23,13 @@ The Palo Alto Cortex XDR integration seamlessly collects the data of Palo Alto C 6. Provide a comment that describes the purpose for the API key, if desired. 7. Select the desired level of access for this key from existing **Roles**, or you can select **Custom** to set the permissions granularly. 8. Click **Generate** to generate the API key. -9. Copy the API key, and then click **Done**. This value represents your unique **Authorization:{key}** -#### Steps to get API Key ID +### Get API Key ID of Palo Alto Cortex XDR 1. In the API Keys table, locate the ID field. 2. Note your corresponding ID number. This value represents the **x-xdr-auth-id:{key_id}** token. -#### Steps to get FQDN +### Get FQDN of Palo Alto Cortex XDR 1. Right-click your API key and select **View Examples**. 2. Copy the **CURL Example** URL. The example contains your unique **FQDN**. diff --git a/ping_one/README.md b/ping_one/README.md index b12e39317a5d4..4a40239c8ca4c 100644 --- a/ping_one/README.md +++ b/ping_one/README.md @@ -1,18 +1,20 @@ -# PingOne Integration +# PingOne ## Overview [PingOne][1] is an identity-as-a-service (IDaaS) offering by Ping Identity. It's a cloud-based identity platform that provides a range of services related to identity and access management (IAM), including single sign-on (SSO), multi-factor authentication (MFA), user management, and more. -The PingOne integration collects Audit logs and sends them to Datadog. Using the out-of-the-box logs pipeline, the logs are parsed and enriched for easy searching and analysis. This integration includes several dashboards visualizing total Audit events, total successful and total failed login attempts, total successful and total failed kerberos login attempts, and more. +This integration ingests the following logs: -## Setup +- Audit: Represents all actions performed in the PingOne admin console and PingDirectory. They can be used to document a historical record of activity for compliance purposes and other business policy enforcement. + +The PingOne integration seamlessly collects the data of PingOne audit logs using the REST APIs. Using the out-of-the-box logs pipeline, the logs are parsed and enriched for easy searching and analysis. This integration includes several dashboards visualizing total Audit events, total successful and total failed login attempts, total successful and total failed kerberos login attempts, and more. -### Configuration +## Setup -#### PingOne Configuration +### Generate API credentials in PingOne -1. Login to [PingOne][2] with your credentials. +1. Log in to your [PingOne account][2]. 2. From the navigation sidebar, expand the **Applications** section and select **Applications**. 3. Click **+** (plus) to begin creating a new application. 4. Enter an **Application Name**. @@ -21,28 +23,26 @@ The PingOne integration collects Audit logs and sends them to Datadog. Using the 7. Select the **Roles** tab of the application flyout. 8. Click the **Grant Roles** button. 9. Under **Available responsibilities**, in the **Environment Admin section**, select the environments to grant access to, then click **Save**. -10. Select the **Configuration** tab of the application flyout. -11. From the General section, copy the **Client ID**, **Client Secret** and **Environment ID**. +10. Select the **Configuration** tab of the application flyout to get **Client ID**, **Client Secret** and **Environment ID**. -#### PingOne Datadog Integration Configuration +### Connect your PingOne Account to Datadog -Configure the Datadog endpoint to forward PingOne events as logs to Datadog: +1. Add your PingOne credentials. -1. Navigate to `PingOne`. -2. Add your PingOne credentials. + | PingOne Parameters | Description | + | ----------------------------- | ----------------------------------------------------------------| + | Domain | The Top level domain from PingOne. | + | Environment Id | The Environment Id from PingOne. | + | Client Id | The Client Id from PingOne. | + | Client Secret | The Client Secret from PingOne. | -| PingOne Parameters | Description | -| ----------------------------- | -------------------------------------------------------------------------- | -| Domain | The Top level domain from PingOne. | -| Environment Id | The Environment Id from PingOne. | -| Client Id | The Client Id from PingOne. | -| Client Secret | The Client Secret from PingOne. | +2. Click the Save button to save your settings. ## Data Collected ### Logs -This integration collects and forwards PingOne logs to Datadog. +This integration collects and forwards PingOne audit logs to Datadog. ### Metrics diff --git a/sophos_central_cloud/README.md b/sophos_central_cloud/README.md index 999ed8a282cde..3ad838c1ec969 100644 --- a/sophos_central_cloud/README.md +++ b/sophos_central_cloud/README.md @@ -18,9 +18,8 @@ The Sophos Central Cloud integration seamlessly collects all the above listed lo 1. Log in to your [**Sophos Central account**][2]. 2. From Sophos Central Admin, go to **My Products** > **General Settings** > **API Credentials Management**. 3. Click **Add Credential**. -4. Provide a credential name, select the appropriate role, add an optional description, and click the **Add** button. The **API credential Summary** for this credential is displayed. +4. Provide a credential name, select the appropriate role, add an optional description, and click the **Add** button. The API credential summary page with the client ID is displayed. 5. Click **Show Client Secret** to display the **Client Secret**. -6. Copy the **Client ID** and **Client Secret** and store them in a secure location. ### Connect your Sophos Central Cloud Account to Datadog From 5000254a8c3ba76d1a3a6e3e2512e905e0af2072 Mon Sep 17 00:00:00 2001 From: akaila-crest Date: Mon, 16 Dec 2024 19:00:42 +0530 Subject: [PATCH 13/16] format StreamNative readme --- streamnative/README.md | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/streamnative/README.md b/streamnative/README.md index 1a1ee8f7d53d0..6002169ae08bb 100644 --- a/streamnative/README.md +++ b/streamnative/README.md @@ -16,21 +16,19 @@ The StreamNative integration collects the following types of [metrics][2]: ### Generate API credentials in StreamNative -Log in to [StreamNative Cloud Console Account][3]. -#### Generate `Organization ID` and `Instance Name`: +1. Log in to [StreamNative Cloud Console Account][3]. +2. Click the profile icon and navigate to the **Accounts & Accesses** tab. +3. Find the Service Account with **Admin** permissions set to **Enabled**. + - If no Service Account exists, select **New -> Service Account** to create one, and make sure to enable the **Super Admin** option. +4. On the right side of the chosen Service Account, click the `...` button. +5. Select **Download OAuth2 Key** to obtain the **Client ID** and **Client Secret**. + +### Get `Organization ID` and `Instance Name` 1. Click the profile icon and select **Organizations**. 2. Choose the **Organization** for which data needs to be collected. 3. From the **Select an Instance** dropdown, get the **Instance Name**. -#### Generate `Client ID` and `Client Secret`: - -1. Click the profile icon and navigate to the **Accounts & Accesses** tab. -2. Find the Service Account with **Admin** permissions set to **Enabled**. - - If no Service Account exists, select **New -> Service Account** to create one, and make sure to enable the **Super Admin** option. -3. On the right side of the chosen Service Account, click the `...` button. -4. Select **Download OAuth2 Key** to obtain the **Client ID** and **Client Secret**. - ### Connect your StreamNative Account to Datadog From db1a83d0e1fe9fdb17a9ba93c6c92cb53102199f Mon Sep 17 00:00:00 2001 From: DhruvaPatel-crest Date: Tue, 17 Dec 2024 15:29:20 +0530 Subject: [PATCH 14/16] updated readme --- ringcentral/README.md | 116 +++++++++++++++++++----------------------- 1 file changed, 52 insertions(+), 64 deletions(-) diff --git a/ringcentral/README.md b/ringcentral/README.md index 66c6050a85efb..baae42e7213bb 100644 --- a/ringcentral/README.md +++ b/ringcentral/README.md @@ -1,86 +1,72 @@ # RingCentral ## Overview -The RingCentral integration seamlessly collects Voice, Audit, A2P SMS, and Voice(Analytics) data and ingests them into Datadog for comprehensive analysis. Leveraging the built-in logs pipeline, these logs are parsed and enriched, enabling effortless search and analysis. Through intuitive, out-of-the-box dashboards the integration provides insights into call activities, SMS trends, and audit trails. Additionally, it includes pre-configured monitors for proactive notifications on SMS budget overrun and SMS error rates. -### The integration collects: +[RingCentral][5] is a leading cloud-based communication and collaboration platform for businesses. It offers services such as voice, messaging, and video conferencing, seamlessly integrating with various business applications. Known for its reliability, security, and scalability, RingCentral enhances communication efficiency and collaboration. -#### Logs for: -- Voice -- Audit - -#### Metrics for: -- Voice (Analytics) -- A2P SMS +The RingCentral integration seamlessly collects voice and audit logs, as well as Voice (Analytics) and A2P SMS metrics, and sends them to Datadog for comprehensive analysis. ## Setup -### RingCentral Datadog Integration Configuration +### Generate API Credentials in RingCentral -Configure the Datadog endpoint to forward RingCentral logs and metrics to Datadog. +1. Login to your [RingCentral Developer][2] account using a user with Super Admin role or [Custom role](#create-and-assign-a-custom-role). +2. Click **Console**. +3. Under the *Apps* section, click **Register App**. +4. Select **Rest API app** for the App type . +5. Fill in the required details for your application, such as the name and description. + + | Field | Selection | + | --- | ----------- | + | Do you intend to promote this app in the RingCentral App Gallery? | **No** | + | Auth type | **JWT auth flow** | + | Issue refresh tokens | **Yes** | + | Application scopes | Select the following:
  • Analytics
  • Read Audit Trail
  • Read Call Log
  • A2P SMS
| +6. Click on create App. +7. After creating the application, find the `clientId` and `clientSecret` in the application settings. +8. To get the JWT Token, locate the **Credentials** by clicking your username in the top-right corner. +9. Click **Create JWT**. +10. Add an appropriate label and select the **Production** environment. +11. Allow this JWT token for only a specific app and add the `clientId` of the application created above. +12. If you select an expiration date, make sure you create a new JWT and update it in the integration configuration before the expiry date. +13. Click **Create JWT**. -1. Navigate to `RingCentral`. -2. Add your [RingCentral credentials](#get-api-credentials-from-ringcentral). -| RingCentral Parameters | Description | -|------------------------------ |-----------------------------------------------------------------------------------------| -| [Account ID](#ringcentral-account-id) | The Account ID of RingCentral. | -| [Client ID](#ringcentral-application-client-id-and-client-secret) | The Client ID of the RingCentral Application. | -| [Client Secret](#ringcentral-application-client-id-and-client-secret) | The Client Secret of the RingCentral Application. | -| [JWT Token](#ringcentral-jwt-token) | The JWT Token from RingCentral. | -| Get Voice Calls | Enable to collect Voice Call Logs from RingCentral. The default value is True. | -| Get Voice(Analytics) Metrics | Enable to collect Voice(Analytics) Metrics from RingCentral. The default value is True. | -| Get SMS Metrics | Enable to collect SMS Metrics from RingCentral. The default value is True. | -| Get Audit Logs | Enable to collect Audit Logs from RingCentral. The default value is True. | +#### Create and assign a custom role +1. Create a custom role, following the [RingCentral documentation][3]. +2. Select **Standard** role as a starting point. +3. Provide additional **Audit Trail** and **Company Call Log - View Only** permissions to the role. +4. Assign a custom role to a user, following the [RingCentral documentation][4]. -### Get API Credentials from RingCentral -#### RingCentral Account ID +### Get RingCentral Account ID To access the Account ID, you need to first access details for a "Super Admin" user and then locate the Account ID through the URL: 1. Visit [RingCentral][1] and log in as a Super Admin. -1. Under the **Users** section, click **Users with Extensions**. -1. From the list of users, click on the user who has a "Super Admin" suffix in their name to open the user's details panel. -1. Look at the URL in your web browser's address bar. -1. Find the 9-digit number within the URL. This is your RingCentral Account ID. +2. Under the **Users** section, click **Users with Extensions**. +3. From the list of users, click on the user who has a "Super Admin" suffix in their name to open the user's details panel. +4. Look at the URL in your web browser's address bar. +5. Find the 9-digit number within the URL. This is your RingCentral Account ID. - **Example URL:** https://service.ringcentral.com/application/users/users/default/123456789/settings/default - The `123456789` is your Account ID. -#### RingCentral Application Client ID and Client Secret -To find the Client ID and Client Secret, you need to register a new application: -1. Login to your [RingCentral Developer][2] account using a user with Super Admin role or [Custom role](#create-and-assign-a-custom-role). -1. Click **Console**. -1. Under the *Apps* section, click **Register App**. -1. Select **Rest API app** for the App type . -1. Fill in the required details for your application, such as the name and description. - -| Field | Selection | -| --- | ----------- | -| Do you intend to promote this app in the RingCentral App Gallery? | **No** | -| Auth type | **JWT auth flow** | -| Issue refresh tokens | **Yes** | -| Application scopes | Select the following:
  • Analytics
  • Read Audit Trail
  • Read Call Log
  • A2P SMS
-| -1. Click **create App**. -1. After creating the application, find the `clientId` and `clientSecret` in the application settings. -1. Copy these credentials. -- **Note**: Ensure these credentials are stored securely and not exposed in public repositories or insecure locations. - -#### RingCentral JWT Token -1. Login to [RingCentral Developers][2] with the same user you used to find the [Client ID and Client Secret](#ringcentral-application-client-id-and-client-secret). -1. Click **Credentials** under your username. -1. Click **Create JWT**. -1. Add an appropriate label and select the **Production** environment. -1. Allow this JWT token for only a specific app and add the `clientId` of the application created to find the [Client ID and Client Secret](#ringcentral-application-client-id-and-client-secret). -1. If you select an expiration date, make sure you create a new JWT and update it in the integration configuration before the expiry date. -1. Click **Create JWT**. +### Connect your RingCentral Account to Datadog -#### Create and assign a custom role -1. Create a custom role, following the [RingCentral documentation][3]. -1. Select **Standard** role as a starting point. -1. Provide additional **Audit Trail** and **Company Call Log - View Only** permissions to the role. -1. Assign a custom role to a user, following the [RingCentral documentation][4]. +1. Add your RingCentral credentials. + + | Parameters | Description | + | --------------- | --------------------------------------------------------------| + |Account ID | The Account ID of RingCentral. | + |Client ID | The Client ID of the RingCentral Application. | + |Client Secret | The Client Secret of the RingCentral Application. | + |JWT Token | The JWT Token from RingCentral. | + |Get Voice Calls Logs | Enable to collect Voice Call Logs from RingCentral. The default value is True. | + |Get Voice(Analytics) Metrics | Enable to collect Voice(Analytics) Metrics from RingCentral. The default value is True. | + |Get SMS Metrics | Enable to collect SMS Metrics from RingCentral. The default value is True. | + |Get Audit Logs | Enable to collect Audit Logs from RingCentral. The default value is True. | + +2. Click the Save button to save your settings. ## Data Collected @@ -90,7 +76,9 @@ The RingCentral integration collects and forwards Voice and Audit logs to Datado ### Metrics -The RingCentral integration collects and forwards Voice(Analytics) and SMS metrics to Datadog. See [metadata.csv][5] for a list of metrics provided by this integration. +The RingCentral integration collects and forwards Voice(Analytics) and SMS metrics to Datadog. + +{{< get-metrics-from-git "ringcentral" >}} ### Events @@ -104,5 +92,5 @@ For further assistance, contact [Datadog Support][6]. [2]: https://developers.ringcentral.com/ [3]: https://support.ringcentral.com/article-v2/10641-user-roles-permissions-edit-permission-custom-role.html?brand=RC_US&product=RingEX&language=en_US [4]: https://support.ringcentral.com/article-v2/10647-user-roles-permissions-assign-role-user-details.html?brand=RC_US&product=RingEX&language=en_US -[5]: https://github.com/DataDog/integrations-core/blob/master/ringcentral/metadata.csv +[5]: https://www.ringcentral.com/ [6]: https://docs.datadoghq.com/help/ From d39534165876c91ca5fef3faededccdb5447dea7 Mon Sep 17 00:00:00 2001 From: DhruvaPatel-crest Date: Tue, 17 Dec 2024 18:01:34 +0530 Subject: [PATCH 15/16] Added minor changes --- ringcentral/README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/ringcentral/README.md b/ringcentral/README.md index baae42e7213bb..399ccddf69754 100644 --- a/ringcentral/README.md +++ b/ringcentral/README.md @@ -40,8 +40,6 @@ The RingCentral integration seamlessly collects voice and audit logs, as well as ### Get RingCentral Account ID -To access the Account ID, you need to first access details for a "Super Admin" user and then locate the Account ID through the URL: - 1. Visit [RingCentral][1] and log in as a Super Admin. 2. Under the **Users** section, click **Users with Extensions**. 3. From the list of users, click on the user who has a "Super Admin" suffix in their name to open the user's details panel. From 3388bc0fa9d871b88041a17ab413f688fd260ca6 Mon Sep 17 00:00:00 2001 From: DhruvaPatel-crest Date: Fri, 20 Dec 2024 15:27:20 +0530 Subject: [PATCH 16/16] updated readme as per review comments --- cisco_secure_email_threat_defense/README.md | 10 +++--- cisco_secure_endpoint/README.md | 12 +++---- lastpass/README.md | 6 ++-- mimecast/README.md | 12 +++---- mux/README.md | 10 +++--- palo_alto_cortex_xdr/README.md | 10 +++--- ping_one/README.md | 14 ++++---- ringcentral/README.md | 34 +++++++++---------- shopify/README.md | 4 +-- sophos_central_cloud/README.md | 12 +++---- streamnative/README.md | 10 +++--- trend_micro_email_security/README.md | 16 ++++----- .../README.md | 14 ++++---- 13 files changed, 82 insertions(+), 82 deletions(-) diff --git a/cisco_secure_email_threat_defense/README.md b/cisco_secure_email_threat_defense/README.md index 3dbd9fb891920..6b7560897e5e9 100644 --- a/cisco_secure_email_threat_defense/README.md +++ b/cisco_secure_email_threat_defense/README.md @@ -26,14 +26,14 @@ The Cisco Secure Email Threat Defense integration provides out-of-the-box dashbo | Parameters | Description | | ---------- | ----------- | - | Host Name | Host Name is based on the region where your Cisco Secure Email Threat Defense server is located. For details, please reach out to your system administrator. | + | Host Name | Host name is based on the region where your Cisco Secure Email Threat Defense server is located. For details, please reach out to your system administrator. | | Client ID | Client ID from Cisco Secure Email Threat Defense Account | - | Client Password | Client Password from Cisco Secure Email Threat Defense Account | - | API Key | API Key from Cisco Secure Email Threat Defense Account | - | Verdict Delay | Events are fetched with a delay according to the time(in minute) specified in the Verdict Delay | + | Client Password | Client password from your Cisco Secure Email Threat Defense Account. | + | API Key | API key from your Cisco Secure Email Threat Defense Account. | + | Verdict Delay | Events are fetched with a delay according to the time(in minute) specified in the Verdict Delay. | -2. Click the Save button to save your settings. +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/cisco_secure_endpoint/README.md b/cisco_secure_endpoint/README.md index 05008df8dafa9..b2dbc4f60f3bb 100644 --- a/cisco_secure_endpoint/README.md +++ b/cisco_secure_endpoint/README.md @@ -12,7 +12,7 @@ The Cisco Secure Endpoint integration provides out-of-the-box dashboards so you ## Setup -### Generate API Credentials in Cisco Secure Endpoint +### Generate API credentials in Cisco Secure Endpoint 1. Log in to your Cisco Secure Endpoint Console and navigate to the Menu Panel on the left side. 2. Select `Administration`, then select `Organization Settings`. @@ -24,16 +24,16 @@ The Cisco Secure Endpoint integration provides out-of-the-box dashboards so you - Click `Create`. - Once you click **Create**, the redirected page will display the client ID (like a third party API client ID) and API Key values. -### Connect your Cisco Secure Endpoint Account to Datadog +### Connect your Cisco Secure Endpoint account to Datadog -1. Add your Cisco Secure Endpoint credentials +1. Add your Cisco Secure Endpoint credentials. | Parameters | Description | | ---------- | ------------ | - | API Domain Name | The API Domain Name for Cisco Secure Endpoint Cloud is "api.\.amp.cisco.com". Adjust the "region" part based on the region of the Cisco Secure Endpoint server. If Cisco Secure Endpoint is hosted on VPC (Virtual Private Cloud), directly provide the API Domain Name. | + | API Domain Name | The API domain name for Cisco Secure Endpoint Cloud is "api.\.amp.cisco.com". Adjust the "region" part based on the region of the Cisco Secure Endpoint server. If Cisco Secure Endpoint is hosted on VPC (Virtual Private Cloud), directly provide the API domain name. | | Client ID | Client ID from Cisco Secure Endpoint. | - | API Key | API Key from Cisco Secure Endpoint. | - | Get Endpoint Details | Keep it "true" to collect endpoint metadata for Cisco Secure Endpoint event logs, otherwise "false". Default value is "true". | + | API Key | API key from Cisco Secure Endpoint. | + | Get Endpoint Details | Keep the default value of "true" to collect endpoint metadata for Cisco Secure Endpoint event logs. Otherwise, set this to "false". | 2. Click the Save button to save your settings. diff --git a/lastpass/README.md b/lastpass/README.md index dd90efa3a3144..dc66cfe5bada4 100644 --- a/lastpass/README.md +++ b/lastpass/README.md @@ -16,7 +16,7 @@ reporting events, while out-of-the-box detection rules enhance detection and res 1. Log in to the [Admin Console](https://admin.lastpass.com/) with your email address and master password. 2. Navigate to **Advanced** > **Enterprise API**. -3. You can find the Account number and can create a Provisioning hash. +3. Locate the account number and can create a provisioning hash. ### Get Timezone of LastPass @@ -31,14 +31,14 @@ reporting events, while out-of-the-box detection rules enhance detection and res ### Connect your LastPass account to Datadog -1. Add your Account number, Provisioning hash and Time zone +1. Add your account number, provisioning hash and time zone. |Parameters|Description| |--------------------|--------------------| |Account number|The account number of your registered LastPass account.| |Provisioning hash|The provisioning hash secret of your registered account on LastPass.| |Time zone|The time zone of your registered account on LastPass.| -2. Click the Save button to save your settings. +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/mimecast/README.md b/mimecast/README.md index b32cc95695683..4eb57d1e3735c 100644 --- a/mimecast/README.md +++ b/mimecast/README.md @@ -17,9 +17,9 @@ The Mimecast integration seamlessly collects all the above listed logs, channeli ## Setup -### Generate API Credentials in Mimecast +### Generate API credentials in Mimecast -1. Log in to your **Mimecast account**. +1. Log into your **Mimecast account**. 2. Navigate to the **Administration Console**, select **Services**, and then choose the **API and Platform Integrations** section. 3. Proceed to Your **API 2.0 Applications**. 4. Search for your application in the list provided. @@ -34,18 +34,18 @@ The Mimecast integration seamlessly collects all the above listed logs, channeli - Application Role: Select **Basic Administrator** - Description: Enter the description of your choice - In **Notifications**, provide the contact details of your technical administrator and click on **Next** - - After clicking on **Add and Generate Keys**. There will be a pop up window showing Client ID and Client Secret. + - Click on **Add and Generate Keys**. A pop up window appears, showing the client ID and client secret. 6. If the application is present, click on its name. 7. Click the **Manage API 2.0 credentials** button and click **Generate**. This generates a new Client ID and Client Secret. -### Connect your Mimecast Account to Datadog +### Connect your Mimecast account to Datadog 1. Add your Mimecast credentials. | Parameters | Description | | ------------------- | ------------------------------------------------------------ | - | Client ID | The Client ID of your registered application on Mimecast | - | Client Secret | The Client Secret of your registered application on Mimecast | + | Client ID | The client ID of your registered application on Mimecast. | + | Client Secret | The client secret of your registered application on Mimecast. | 2. Click the Save button to save your settings. diff --git a/mux/README.md b/mux/README.md index a8d40f6bc0831..9794818740669 100644 --- a/mux/README.md +++ b/mux/README.md @@ -17,18 +17,18 @@ Integrate Mux with Datadog to gain insights into mux video performance data. 5. Choose the environment. 6. Under the **permission** section, select **Mux Data(read-only)**. 7. Enter the access token name. -8. Click on **Generate Token** to find Access Token ID and Secret Key. +8. Click on **Generate Token** to find the access token ID and secret key. ### Connect your Mux account to Datadog -1. Add your Access Token ID and Secret Key +1. Add your access token ID and secret key. |Parameters|Description| |--------------------|--------------------| - |Access Token ID|Access Token ID of MUX account.| - |Secret Key|Secret Key of MUX account.| + |Access Token ID|Access token ID of your MUX account.| + |Secret Key|Secret key of your MUX account.| -2. Click the Save button to save your settings. +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/palo_alto_cortex_xdr/README.md b/palo_alto_cortex_xdr/README.md index ee57b33d9ab5f..ba935f483b0dc 100644 --- a/palo_alto_cortex_xdr/README.md +++ b/palo_alto_cortex_xdr/README.md @@ -15,7 +15,7 @@ The Palo Alto Cortex XDR integration seamlessly collects the data of Palo Alto C ### Generate API credentials in Palo Alto Cortex XDR -1. Log in to your **Palo Alto Cortex XDR account**. +1. Log into your **Palo Alto Cortex XDR account**. 2. Navigate to **Settings** > **Configurations** > **Integrations** > **API Keys**. 3. Click on **New Key**. 4. Choose the type of API key based on your desired security level, **Advanced** or **Standard**. @@ -24,7 +24,7 @@ The Palo Alto Cortex XDR integration seamlessly collects the data of Palo Alto C 7. Select the desired level of access for this key from existing **Roles**, or you can select **Custom** to set the permissions granularly. 8. Click **Generate** to generate the API key. -### Get API Key ID of Palo Alto Cortex XDR +### Get API key ID of Palo Alto Cortex XDR 1. In the API Keys table, locate the ID field. 2. Note your corresponding ID number. This value represents the **x-xdr-auth-id:{key_id}** token. @@ -34,17 +34,17 @@ The Palo Alto Cortex XDR integration seamlessly collects the data of Palo Alto C 1. Right-click your API key and select **View Examples**. 2. Copy the **CURL Example** URL. The example contains your unique **FQDN**. -### Connect your Palo Alto Cortex XDR Account to Datadog +### Connect your Palo Alto Cortex XDR account to Datadog 1. Add your Palo Alto Cortex XDR credentials. | Parameters | Description | | -------------| ------------ | | API key | The API key from Palo Alto Cortex XDR. | - | API Key ID | The auth id from Palo Alto Cortex XDR. | + | API Key ID | The auth ID from Palo Alto Cortex XDR. | | FQDN | The FQDN from Palo Alto Cortex XDR. It is the `baseUrl` part of `baseUrl/public_api/v1/{name of api}/{name of call}/` | -2. Click the Save button to save your settings. +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/ping_one/README.md b/ping_one/README.md index 4a40239c8ca4c..544eefd7c6da7 100644 --- a/ping_one/README.md +++ b/ping_one/README.md @@ -14,7 +14,7 @@ The PingOne integration seamlessly collects the data of PingOne audit logs using ### Generate API credentials in PingOne -1. Log in to your [PingOne account][2]. +1. Log into your [PingOne account][2]. 2. From the navigation sidebar, expand the **Applications** section and select **Applications**. 3. Click **+** (plus) to begin creating a new application. 4. Enter an **Application Name**. @@ -25,18 +25,18 @@ The PingOne integration seamlessly collects the data of PingOne audit logs using 9. Under **Available responsibilities**, in the **Environment Admin section**, select the environments to grant access to, then click **Save**. 10. Select the **Configuration** tab of the application flyout to get **Client ID**, **Client Secret** and **Environment ID**. -### Connect your PingOne Account to Datadog +### Connect your PingOne account to Datadog 1. Add your PingOne credentials. | PingOne Parameters | Description | | ----------------------------- | ----------------------------------------------------------------| - | Domain | The Top level domain from PingOne. | - | Environment Id | The Environment Id from PingOne. | - | Client Id | The Client Id from PingOne. | - | Client Secret | The Client Secret from PingOne. | + | Domain | The top level domain from PingOne. | + | Environment ID | The environment ID from PingOne. | + | Client ID | The client ID from PingOne. | + | Client Secret | The client secret from PingOne. | -2. Click the Save button to save your settings. +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/ringcentral/README.md b/ringcentral/README.md index 399ccddf69754..242584288907b 100644 --- a/ringcentral/README.md +++ b/ringcentral/README.md @@ -2,15 +2,15 @@ ## Overview -[RingCentral][5] is a leading cloud-based communication and collaboration platform for businesses. It offers services such as voice, messaging, and video conferencing, seamlessly integrating with various business applications. Known for its reliability, security, and scalability, RingCentral enhances communication efficiency and collaboration. +[RingCentral][5] is a leading cloud-based communication and collaboration platform for businesses. It offers services such as voice, messaging, and video conferencing, seamlessly integrating with various business applications. -The RingCentral integration seamlessly collects voice and audit logs, as well as Voice (Analytics) and A2P SMS metrics, and sends them to Datadog for comprehensive analysis. +The RingCentral integration collects voice and audit logs, as well as Voice (Analytics) and A2P SMS metrics, and sends them to Datadog for comprehensive analysis. ## Setup ### Generate API Credentials in RingCentral -1. Login to your [RingCentral Developer][2] account using a user with Super Admin role or [Custom role](#create-and-assign-a-custom-role). +1. Log into your [RingCentral Developer][2] account using a user with a Super Admin role or [Custom role](#create-and-assign-a-custom-role). 2. Click **Console**. 3. Under the *Apps* section, click **Register App**. 4. Select **Rest API app** for the App type . @@ -22,7 +22,7 @@ The RingCentral integration seamlessly collects voice and audit logs, as well as | Auth type | **JWT auth flow** | | Issue refresh tokens | **Yes** | | Application scopes | Select the following:
  • Analytics
  • Read Audit Trail
  • Read Call Log
  • A2P SMS
| -6. Click on create App. +6. Click on Create App. 7. After creating the application, find the `clientId` and `clientSecret` in the application settings. 8. To get the JWT Token, locate the **Credentials** by clicking your username in the top-right corner. 9. Click **Create JWT**. @@ -39,32 +39,32 @@ The RingCentral integration seamlessly collects voice and audit logs, as well as 4. Assign a custom role to a user, following the [RingCentral documentation][4]. -### Get RingCentral Account ID +### Get RingCentral account ID 1. Visit [RingCentral][1] and log in as a Super Admin. 2. Under the **Users** section, click **Users with Extensions**. 3. From the list of users, click on the user who has a "Super Admin" suffix in their name to open the user's details panel. 4. Look at the URL in your web browser's address bar. -5. Find the 9-digit number within the URL. This is your RingCentral Account ID. +5. Find the 9-digit number within the URL. This is your RingCentral account ID. - **Example URL:** https://service.ringcentral.com/application/users/users/default/123456789/settings/default - The `123456789` is your Account ID. -### Connect your RingCentral Account to Datadog +### Connect your RingCentral account to Datadog 1. Add your RingCentral credentials. | Parameters | Description | | --------------- | --------------------------------------------------------------| - |Account ID | The Account ID of RingCentral. | - |Client ID | The Client ID of the RingCentral Application. | - |Client Secret | The Client Secret of the RingCentral Application. | - |JWT Token | The JWT Token from RingCentral. | - |Get Voice Calls Logs | Enable to collect Voice Call Logs from RingCentral. The default value is True. | - |Get Voice(Analytics) Metrics | Enable to collect Voice(Analytics) Metrics from RingCentral. The default value is True. | - |Get SMS Metrics | Enable to collect SMS Metrics from RingCentral. The default value is True. | - |Get Audit Logs | Enable to collect Audit Logs from RingCentral. The default value is True. | - -2. Click the Save button to save your settings. + |Account ID | The account ID of RingCentral. | + |Client ID | The client ID of the RingCentral application. | + |Client Secret | The client secret of the RingCentral application. | + |JWT Token | The JWT token from RingCentral. | + |Get Voice Calls Logs | Enable to collect voice call logs from RingCentral. The default value is "true". | + |Get Voice(Analytics) Metrics | Enable to collect Voice(Analytics) metrics from RingCentral. The default value is "true". | + |Get SMS Metrics | Enable to collect SMS metrics from RingCentral. The default value is "true". | + |Get Audit Logs | Enable to collect audit logs from RingCentral. The default value is "true". | + +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/shopify/README.md b/shopify/README.md index b51b2cf64892b..63212c887c739 100644 --- a/shopify/README.md +++ b/shopify/README.md @@ -26,13 +26,13 @@ It includes dashboards that show and analyze logs, making it easier to monitor a 8. Click **Save** to apply the changes. 9. Click **Install app** and get the **Access Token** from the **Admin API access token** section. -### Connect your Shopify Account to Datadog +### Connect your Shopify account to Datadog 1. Add your Store Name and Access Token |Parameters|Description| |--------------------|--------------------| |Store Name|Store name of your Shopify admin account.| |Access Token|Access Token for your Shopify admin account.| -2. Click the Save button to save your settings. +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/sophos_central_cloud/README.md b/sophos_central_cloud/README.md index 3ad838c1ec969..7fa8bbc873b50 100644 --- a/sophos_central_cloud/README.md +++ b/sophos_central_cloud/README.md @@ -15,23 +15,23 @@ The Sophos Central Cloud integration seamlessly collects all the above listed lo ### Generate API credentials in Sophos Central Cloud -1. Log in to your [**Sophos Central account**][2]. +1. Log into your [**Sophos Central account**][2]. 2. From Sophos Central Admin, go to **My Products** > **General Settings** > **API Credentials Management**. 3. Click **Add Credential**. 4. Provide a credential name, select the appropriate role, add an optional description, and click the **Add** button. The API credential summary page with the client ID is displayed. 5. Click **Show Client Secret** to display the **Client Secret**. -### Connect your Sophos Central Cloud Account to Datadog +### Connect your Sophos Central Cloud account to Datadog 1. Add your Sophos Central Cloud credentials. | Parameters | Description | | ------------------------------- | -------------------------------------------------------------------------- | - | Client ID | The Client ID from Sophos Central Cloud. | - | Client Secret | The Client Secret from Sophos Central Cloud. | - | Get Endpoint Details | Set to "true" to collect endpoint details for Sophos Central Cloud Alert and Event Logs, otherwise set to "false". The Default is "true". | + | Client ID | The client ID from Sophos Central Cloud. | + | Client Secret | The client secret from Sophos Central Cloud. | + | Get Endpoint Details | Keep the default value of "true" to collect endpoint details for Sophos Central Cloud Alert and Event Logs. Otherwise, set to "false". | -2. Click the Save button to save your settings. +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/streamnative/README.md b/streamnative/README.md index 6002169ae08bb..65705ea1d2258 100644 --- a/streamnative/README.md +++ b/streamnative/README.md @@ -16,7 +16,7 @@ The StreamNative integration collects the following types of [metrics][2]: ### Generate API credentials in StreamNative -1. Log in to [StreamNative Cloud Console Account][3]. +1. Log into [StreamNative Cloud Console Account][3]. 2. Click the profile icon and navigate to the **Accounts & Accesses** tab. 3. Find the Service Account with **Admin** permissions set to **Enabled**. - If no Service Account exists, select **New -> Service Account** to create one, and make sure to enable the **Super Admin** option. @@ -30,16 +30,16 @@ The StreamNative integration collects the following types of [metrics][2]: 3. From the **Select an Instance** dropdown, get the **Instance Name**. -### Connect your StreamNative Account to Datadog +### Connect your StreamNative account to Datadog -1. Add your Organization ID, Instance Name, Client ID, and Client Secret +1. Add your organization ID, instance name, client ID, and client secret. |Parameters|Description| |--------------------|--------------------| |Organization ID|Organization ID of your StreamNative account.| |Instance Name|Instance name of the corresponding organization.| |Client ID |Client ID of your service account.| - |Client Secret|Client Secret of your service account.| -2. Click the Save button to save your settings. + |Client Secret|Client secret of your service account.| +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/trend_micro_email_security/README.md b/trend_micro_email_security/README.md index 8e496d54f75d9..a675da5234133 100644 --- a/trend_micro_email_security/README.md +++ b/trend_micro_email_security/README.md @@ -4,14 +4,14 @@ This integration ingests the following logs: -- Policy events and detection - This logs provide information about policy events and detection, allowing you to monitor and respond to potential security threats effectively. -- Mail tracking - This logs provide information about email activities, including accepted and blocked traffic, allowing you to track email messages that have passed through the system and monitor their delivery status. +- Policy events and detection - These logs provide information about policy events and detection, allowing you to monitor and respond to potential security threats effectively. +- Mail tracking - These logs provide information about email activities, including accepted and blocked traffic, allowing you to track email messages that have passed through the system and monitor their delivery status. Use out-of-the-box dashboards to visualize detailed insights into email traffic analysis, real-time threat detection, security detection and observation, and compliance monitoring. ## Setup -### Generate API Credentials in Trend Micro Email Security +### Generate API credentials in Trend Micro Email Security 1. Log on to the Trend Micro Email Security administrator console. 2. Navigate to **Administration** > **Service Integration** > **API Access**. @@ -22,14 +22,14 @@ Use out-of-the-box dashboards to visualize detailed insights into email traffic ### Connect your Trend Micro Email Security Account to Datadog -1. Add your Host Region, Username, and API Key. +1. Add your host region, username, and API key. | Parameters | Description | | ----------- | --------------------------------------------------------------------- | - | Host Region | The Region of the Trend Micro Email Security administrator console. | - | Username | The Username of the Trend Micro Email Security administrator console. | - | API Key | The API Key of the Trend Micro Email Security administrator console. | + | Host Region | The region of the Trend Micro Email Security administrator console. | + | Username | The username of the Trend Micro Email Security administrator console. | + | API Key | The API key of the Trend Micro Email Security administrator console. | -2. Click the Save button to save your settings. +2. Click the **Save** button to save your settings. ## Data Collected diff --git a/trend_micro_vision_one_endpoint_security/README.md b/trend_micro_vision_one_endpoint_security/README.md index c3e46ccdabe44..bcbf6b45a7659 100644 --- a/trend_micro_vision_one_endpoint_security/README.md +++ b/trend_micro_vision_one_endpoint_security/README.md @@ -24,7 +24,7 @@ Use out-of-the-box dashboards to gain detailed insights into system events, netw ## Setup -### Generate API Credentials in Trend Micro Vision One Endpoint Security +### Generate API credentials in Trend Micro Vision One Endpoint Security 1. Log in to the Trend Micro Vision One console. 2. Go to **Endpoint Security** (Sidebar) > **Standard Endpoint Protection** > **Administration** > **Settings** > **Automation API Access Settings**. @@ -46,15 +46,15 @@ Use out-of-the-box dashboards to gain detailed insights into system events, netw ### Connect your Trend Micro Vision One Endpoint Security Account to Datadog -1. Add your API Host, Application ID, API Key and select the Time Zone from the dropdown. +1. Add your API host, application ID, API key and select the time zone from the dropdown. | Parameters | Description | | -------------- | ----------------------------------------------------------------------- | - | API Host | The API Host of Trend Micro Vision One Endpoint Security console. | - | Application ID | The Application ID of Trend Micro Vision One Endpoint Security console. | - | API Key | The API Key of of Trend Micro Vision One Endpoint Security console. | - | Time Zone | The Time Zone of the Trend Micro Vision One console. | + | API Host | The API host of Trend Micro Vision One Endpoint Security console. | + | Application ID | The application ID of Trend Micro Vision One Endpoint Security console. | + | API Key | The API key of of Trend Micro Vision One Endpoint Security console. | + | Time Zone | The time zone of the Trend Micro Vision One console. | -2. Click the Save button to save your settings. +2. Click the **Save** button to save your settings. ## Data Collected