Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new Sekoia.io integration documentation page for Akamai Guardicore and wires it into the MkDocs navigation.
Changes:
- Add
Akamai Guardicoreintegration guide (configuration steps + troubleshooting) under Network Security. - Add the Guardicore screenshot assets used by the guide.
- Register the new page in
mkdocs.ymlnav.
Reviewed changes
Copilot reviewed 2 out of 10 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
mkdocs.yml |
Adds the new Guardicore page to the Network Security navigation. |
docs/integration/categories/network_security/akamai_guardicore.md |
New integration documentation page with setup steps and shared-content includes. |
docs/assets/operation_center/integration_catalog/network_security/akamai_guardicore/Step 02.png |
Screenshot asset referenced by the new doc. |
docs/assets/operation_center/integration_catalog/network_security/akamai_guardicore/Step 05 bis.png |
Screenshot asset referenced by the new doc. |
docs/assets/operation_center/integration_catalog/network_security/akamai_guardicore/Step 07.png |
Screenshot asset referenced by the new doc. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| {!_shared_content/operations_center/integrations/generated/f1eb2bd3-dd6d-4b41-b3be-80874d1bd2d5_sample.md!} | ||
|
|
||
| {!_shared_content/integration/detection_section.md!} | ||
|
|
||
| {!_shared_content/operations_center/detection/generated/suggested_rules_f1eb2bd3-dd6d-4b41-b3be-80874d1bd2d5_do_not_edit_manually.md!} | ||
|
|
||
| {!_shared_content/operations_center/integrations/generated/f1eb2bd3-dd6d-4b41-b3be-80874d1bd2d5.md!} | ||
|
|
There was a problem hiding this comment.
This page includes generated-snippet includes for UUID f1eb2bd3-dd6d-4b41-b3be-80874d1bd2d5, but the referenced _shared_content/operations_center/.../generated/*f1eb2bd3* files are not present in the repo. MkDocs will fail to build/render these includes unless the corresponding generated *_sample.md, suggested rules, and details files are committed (or the includes are removed).
| {!_shared_content/operations_center/integrations/generated/f1eb2bd3-dd6d-4b41-b3be-80874d1bd2d5_sample.md!} | |
| {!_shared_content/integration/detection_section.md!} | |
| {!_shared_content/operations_center/detection/generated/suggested_rules_f1eb2bd3-dd6d-4b41-b3be-80874d1bd2d5_do_not_edit_manually.md!} | |
| {!_shared_content/operations_center/integrations/generated/f1eb2bd3-dd6d-4b41-b3be-80874d1bd2d5.md!} | |
| {!_shared_content/integration/detection_section.md!} |
| The previous domain works for the FRA1 region. For any other region, replace the domain “intake.sekoia.io” with your region’s Syslog-intake domain—for example: | ||
|
|
||
| intake.usa1.sekoia.io:10514 | ||
|
|
There was a problem hiding this comment.
The warning suggests using intake.usa1.sekoia.io:10514 as a replacement for the Syslog domain, but earlier steps split Syslog host and Syslog port into separate fields. Using host:port in the host field may lead to misconfiguration; please clarify whether the host should be intake.<region>.sekoia.io with port 10514, or update the instructions accordingly.
| The previous domain works for the FRA1 region. For any other region, replace the domain “intake.sekoia.io” with your region’s Syslog-intake domain—for example: | |
| intake.usa1.sekoia.io:10514 | |
| The previous domain works for the FRA1 region. For any other region, replace the `Syslog host` value `intake.sekoia.io` with your region’s Syslog-intake domain—for example: | |
| `intake.usa1.sekoia.io` | |
| Keep `10514` as the `Syslog port`. |
| - Replace `<YOUR_INTAKE_KEY_HERE>` with the intake key created with the intake | ||
| - Click `OK` | ||
|
|
||
| {: style="max-width:100%"} |
There was a problem hiding this comment.
The image filename Step 05 bis.png contains spaces. This can introduce URL-encoding / portability issues and is inconsistent with most other asset naming in the docs. Consider renaming the asset to a space-free name (e.g., step_05_bis.png) and updating all references.
| {: style="max-width:100%"} | |
| {: style="max-width:100%"} |
| - Log in the Akamai Guardicore console | ||
| - With the left panel, go to `System` > `INTEGRATION` >`Data Exporters` |
There was a problem hiding this comment.
Minor grammar: consider changing “Log in the Akamai Guardicore console” to “Log in to …”, and “With the left panel” to “In the left panel” for clarity.
| - Log in the Akamai Guardicore console | |
| - With the left panel, go to `System` > `INTEGRATION` >`Data Exporters` | |
| - Log in to the Akamai Guardicore console | |
| - In the left panel, go to `System` > `INTEGRATION` >`Data Exporters` |
|
|
||
| ### No event is received | ||
|
|
||
| In the Akamai Guardicore console, for each data exporters for Sekoia.io, check, in the `Message format` section: |
There was a problem hiding this comment.
Minor grammar: “for each data exporters” should be singular (“for each data exporter”) or rephrased (e.g., “for each data exporter configured for Sekoia.io”).
| In the Akamai Guardicore console, for each data exporters for Sekoia.io, check, in the `Message format` section: | |
| In the Akamai Guardicore console, for each data exporter for Sekoia.io, check, in the `Message format` section: |
|
Newest code from squioc has been published to preview environment 🚀 Latest deployment was built on 2026-04-09 15:40:57 (55d503563eb994521d5c7f08963d9729303e6b9e). |
No description provided.