From ace049e17cf43061755372e2b97e3ef1ddf9d8d2 Mon Sep 17 00:00:00 2001 From: rombernier Date: Wed, 4 Dec 2024 17:33:25 +0100 Subject: [PATCH] remove irrelevant copy intake key --- docs/integration/categories/applicative/1password_epm.md | 5 ----- docs/integration/categories/applicative/azure_files.md | 2 +- docs/integration/categories/iam/azure_key_vault.md | 2 +- docs/integration/categories/iam/okta_system_log.md | 2 +- docs/integration/categories/network_security/bitsight_spm.md | 2 +- docs/integration/categories/network_security/trellix_epo.md | 2 +- 6 files changed, 5 insertions(+), 10 deletions(-) diff --git a/docs/integration/categories/applicative/1password_epm.md b/docs/integration/categories/applicative/1password_epm.md index bba9c8b09e..44b7c5f8d4 100644 --- a/docs/integration/categories/applicative/1password_epm.md +++ b/docs/integration/categories/applicative/1password_epm.md @@ -56,11 +56,6 @@ Go to your Sekoia.io [Intakes page](https://app.sekoia.io/operations/intakes), a | 1Password.ca | https://events.1password.ca | | 1Password.eu | https://events.1password.eu | -4. Copy the **Intake key** - -!!! Note - Save the `Intake key` on a block note. It will be used in the next step. - #### Enjoy your events on the [Events page](https://app.sekoia.io/operations/events) diff --git a/docs/integration/categories/applicative/azure_files.md b/docs/integration/categories/applicative/azure_files.md index 167023144e..2424b57c17 100644 --- a/docs/integration/categories/applicative/azure_files.md +++ b/docs/integration/categories/applicative/azure_files.md @@ -52,7 +52,7 @@ This setup guide describe how to forward events produced by `Azure Files` to Sek ### Create the intake in Sekoia.io -Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format `Azure Files`. Copy the intake key. +Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format `Azure Files`. Set up the intake configuration with the EventHub's `Connection string-primary key`, the hub name, the consumer group, the storage's `Connection string-primary key` and the container name. diff --git a/docs/integration/categories/iam/azure_key_vault.md b/docs/integration/categories/iam/azure_key_vault.md index 0fa5cb65ae..a0c7997244 100644 --- a/docs/integration/categories/iam/azure_key_vault.md +++ b/docs/integration/categories/iam/azure_key_vault.md @@ -32,7 +32,7 @@ Detailed instructions can be found in official docs [here](https://learn.microso ### Create the intake in Sekoia.io -1. Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format `Azure Key Vault`. Copy the intake key. +1. Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format `Azure Key Vault`. 2. Set up the intake configuration with `account_key`, `account_name` and the `container_name`. {!_shared_content/operations_center/integrations/generated/ae62a8c4-11f8-4aea-af5b-6968f8ac04ba_sample.md!} diff --git a/docs/integration/categories/iam/okta_system_log.md b/docs/integration/categories/iam/okta_system_log.md index c3211cf118..c9b383f23a 100644 --- a/docs/integration/categories/iam/okta_system_log.md +++ b/docs/integration/categories/iam/okta_system_log.md @@ -20,7 +20,7 @@ Sign in your Okta organization with administrator role and follow [this guide](h ### Create the intake in Sekoia.io -1. Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format `Okta System logs`. Copy the intake key. +1. Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format `Okta System logs`. 2. Set up the intake configuration with your API Key and the base url of your Okta instance. !!! note diff --git a/docs/integration/categories/network_security/bitsight_spm.md b/docs/integration/categories/network_security/bitsight_spm.md index 31c13a3e49..65f430a625 100644 --- a/docs/integration/categories/network_security/bitsight_spm.md +++ b/docs/integration/categories/network_security/bitsight_spm.md @@ -37,7 +37,7 @@ To collect the events from the Cato Networks platform, an API token is required: ### Create an intake -1. Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format `Bitsight SPM`. Copy the intake key. +1. Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format `Bitsight SPM`. 2. Set up the intake configuration with the Api Token and Company UUIds. {!_shared_content/operations_center/integrations/generated/57eda191-2f93-4fd9-99a2-fd8ffbcdff50_sample.md!} diff --git a/docs/integration/categories/network_security/trellix_epo.md b/docs/integration/categories/network_security/trellix_epo.md index 0fefebb8ce..ff7b58ebca 100644 --- a/docs/integration/categories/network_security/trellix_epo.md +++ b/docs/integration/categories/network_security/trellix_epo.md @@ -32,7 +32,7 @@ This setup guide will show you how to forward your Trellix ePO events to Sekoia. ### Create an intake -1. Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format Trellix. Copy the intake key. +1. Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format Trellix. 2. Set up the intake configuration with the Client Id and Client Secret. {!_shared_content/operations_center/integrations/generated/ba40ab72-1456-11ee-be56-0242ac120002_sample.md!}