Skip to content

Commit

Permalink
Merge pull request #1937 from SEKOIA-IO/fix_broken_links
Browse files Browse the repository at this point in the history
Fix broken links
  • Loading branch information
pbivic authored Aug 2, 2024
2 parents d19eb42 + f5317e4 commit 4fc2889
Show file tree
Hide file tree
Showing 9 changed files with 11 additions and 10 deletions.
2 changes: 1 addition & 1 deletion _shared_content/integration/detection_section.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
## Detection section

The following section provides information for those who wish to learn more about the detection capabilities enabled by collecting this intake. It includes details about the built-in rule catalog, event categories, and ECS fields extracted from raw events. This is essential for users aiming to create [custom detection rules](/docs/xdr/features/detect/sigma.md), perform hunting activities, or pivot in the [events page](/docs/xdr/features/investigate/events.md).
The following section provides information for those who wish to learn more about the detection capabilities enabled by collecting this intake. It includes details about the built-in rule catalog, event categories, and ECS fields extracted from raw events. This is essential for users aiming to create [custom detection rules](/xdr/features/detect/rules_catalog/#create-custom-rules), perform hunting activities, or pivot in the [events page](/xdr/features/investigate/events).
6 changes: 3 additions & 3 deletions docs/integration/categories/endpoint/eset_protect.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,13 +65,13 @@ To enable Syslog server in ESET Protect on On-Prem :
1. In admin console go to `More` > `Settings`.
2. Open `Advanced Settings` tab.

![Advanced Settings](/docs/assets/instructions/eset_protect/enable_syslog_1.png)
![Advanced Settings](/assets/instructions/eset_protect/enable_syslog_1.png)

3. Click on `Syslog server` > `Use Syslog server`.
4. Then click on `Logging` > `Export logs to Syslog` and choose `JSON` format.
5. Save configuration.

![Syslog configuration](/docs/assets/instructions/eset_protect/enable_syslog_2.png)
![Syslog configuration](/assets/instructions/eset_protect/enable_syslog_2.png)

To enable Syslog server in ESET Protect on Cloud:
1. In admin console go to `More` > `Admin` > `Settings`.
Expand All @@ -87,7 +87,7 @@ To enable Syslog server in ESET Protect on Cloud:
11. Click `Apply settings`


![Advanced Settings](/docs/assets/instructions/eset_protect/cloud_syslog.png)
![Advanced Settings](/assets/instructions/eset_protect/cloud_syslog.png)

### Instruction on Sekoia

Expand Down
2 changes: 1 addition & 1 deletion docs/integration/categories/endpoint/winlogbeat.md
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,7 @@ Please consult our [guide](/integration/ingestion_methods/https/logstash.md) to

{!_shared_content/operations_center/integrations/generated/021e9def-5a55-4369-941e-af269b45bef1.md!}

The following section provides information for those who wish to learn more about the detection capabilities enabled by collecting this intake. It includes details about the built-in rule catalog, event categories, and ECS fields extracted from raw events. This is essential for users aiming to create [custom detection rules](/docs/xdr/features/detect/sigma.md), perform hunting activities, or pivot in the [events page](/docs/xdr/features/investigate/events.md).
{!_shared_content/integration/detection_section.md!}

{!_shared_content/operations_center/detection/generated/suggested_rules_c10307ea-5dd1-45c6-85aa-2a6a900df99b_do_not_edit_manually.md!}

Expand Down
2 changes: 1 addition & 1 deletion docs/integration/categories/network/dhcpd.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ This setup guide will show you how to forward your ISC DHCP logs to Sekoia.io by

{!_shared_content/operations_center/integrations/generated/9044ba46-2b5d-4ebd-878a-51d62e84c8df.md!}

The following section provides information for those who wish to learn more about the detection capabilities enabled by collecting this intake. It includes details about the built-in rule catalog, event categories, and ECS fields extracted from raw events. This is essential for users aiming to create [custom detection rules](/docs/xdr/features/detect/sigma.md), perform hunting activities, or pivot in the [events page](/docs/xdr/features/investigate/events.md).
{!_shared_content/integration/detection_section.md!}

{!_shared_content/operations_center/detection/generated/suggested_rules_9044ba46-2b5d-4ebd-878a-51d62e84c8df_do_not_edit_manually.md!}

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ In this guide, you will configure the gateway to forward events to syslog. This

{!_shared_content/operations_center/integrations/generated/f0f95532-9928-4cde-a399-ddd992d48472.md!}

The following section provides information for those who wish to learn more about the detection capabilities enabled by collecting this intake. It includes details about the built-in rule catalog, event categories, and ECS fields extracted from raw events. This is essential for users aiming to create [custom detection rules](/docs/xdr/features/detect/sigma.md), perform hunting activities, or pivot in the [events page](/docs/xdr/features/investigate/events.md).
{!_shared_content/integration/detection_section.md!}

{!_shared_content/operations_center/detection/generated/suggested_rules_f0f95532-9928-4cde-a399-ddd992d48472_do_not_edit_manually.md!}

Expand Down
2 changes: 1 addition & 1 deletion docs/integration/categories/network/pulse.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ This setup guide will show you how to forward your Pulse Connect Secure logs to

{!_shared_content/operations_center/integrations/generated/7a12aa3b-ec73-4ebb-8fb3-f7c543fd84a5.md!}

The following section provides information for those who wish to learn more about the detection capabilities enabled by collecting this intake. It includes details about the built-in rule catalog, event categories, and ECS fields extracted from raw events. This is essential for users aiming to create [custom detection rules](/docs/xdr/features/detect/sigma.md), perform hunting activities, or pivot in the [events page](/docs/xdr/features/investigate/events.md).
{!_shared_content/integration/detection_section.md!}

{!_shared_content/operations_center/detection/generated/suggested_rules_7a12aa3b-ec73-4ebb-8fb3-f7c543fd84a5_do_not_edit_manually.md!}

Expand Down
2 changes: 1 addition & 1 deletion docs/xdr/usecases/playbook/whoIs.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ This use case describes how to use Whois module in order to enrich an IP address

You can find the configuration below:

![Playbook WhoIS](/docs/assets/playbooks/library/UseCases/WhoIS.png)
![Playbook WhoIS](/assets/playbooks/library/UseCases/WhoIS.png)

| Module | Configuration |
| --- | --- |
Expand Down
1 change: 1 addition & 0 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -782,6 +782,7 @@ plugins:
xdr/features/collect/integrations/endpoint/sekoiaio/sekoiaio.md: integration/categories/endpoint/sekoiaio.md
xdr/features/collect/integrations/index.md: integration/categories/index.md
xdr/features/collect/integrations/endpoint/sekoiaio.md: integration/categories/endpoint/sekoiaio.md
xdr/features/collect/ingestion_methods/index.md: integration/ingestion_methods/index.md
getting_started/2fa.md: getting_started/account_security.md
getting_started/apikey_creation.md: getting_started/manage_api_keys.md
getting_started/first_steps.md: getting_started/index.md
Expand Down
2 changes: 1 addition & 1 deletion scripts/update_mkdocs/templates/intake.md.jinja
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ In details, the following table denotes the type of events produced by this inte
{% if tests %}
### Transformed Events Samples after Ingestion

This section demonstrates how the raw logs will be transformed by our parsers. It shows the extracted fields that will be available for use in the [built-in detection rules](/docs/xdr/features/detect/rules_catalog) and hunting activities in the [events page](/docs/xdr/features/investigate/events). Understanding these transformations is essential for analysts to create effective detection mechanisms with [custom detection rules](/docs/xdr/features/detect/sigma) and to leverage the full potential of the collected data.
This section demonstrates how the raw logs will be transformed by our parsers. It shows the extracted fields that will be available for use in the [built-in detection rules](/xdr/features/detect/rules_catalog) and hunting activities in the [events page](/xdr/features/investigate/events). Understanding these transformations is essential for analysts to create effective detection mechanisms with [custom detection rules](/xdr/features/detect/sigma) and to leverage the full potential of the collected data.
{% for test in tests %}
=== "{{test['name']}}"

Expand Down

0 comments on commit 4fc2889

Please sign in to comment.