From e8932f41311c2571488cea3fc3fe6dcb761c53d3 Mon Sep 17 00:00:00 2001 From: Rudi Klein Date: Fri, 31 May 2024 17:57:20 +0200 Subject: [PATCH 1/6] Finale doc update --- Writerside/topics/Wazuh-notifier.md | 161 +++++++++++++++------------- 1 file changed, 88 insertions(+), 73 deletions(-) diff --git a/Writerside/topics/Wazuh-notifier.md b/Writerside/topics/Wazuh-notifier.md index c171721..d0f4da1 100644 --- a/Writerside/topics/Wazuh-notifier.md +++ b/Writerside/topics/Wazuh-notifier.md @@ -1,33 +1,34 @@ # Wazuh notify +*version 1.0* ## Table of Contents - [Introduction](#introduction) - [Installation](#installation) - - [Step 1](#step-1-download) - - [Step 2](#step-2-copy-files) + - [Step 1: download](#step-1-download) + - [Step 2: copy files](#step-2-copy-files) - [Python](#python_1) - [Golang](#golang_1) - - [Step 3](#step-3) - - [Step 4](#step-4) -- [Configuration](#configuration) + - [Step 3: copy the TOML file](#step-3-copy-the-toml-configuration-file) + - [Step 4: create .env file](#step-4-create-env-file) +- [Wazuh configuration](#wazuh-configuration) - [Golang](#golang_2) - [Python](#python_2) - [Note](#note) -- [The YAML configuration](#the-yaml-configuration) +- [The TOML configuration file](#the-toml-configuration) - [Setting up the platforms](#setting-up-the-platforms-receiving-the-notifications) ## Introduction -Wazuh notifier enables the Wazuh manager to be notified when selected events occur, using 3 messaging platforms: +Wazuh notifier enables the Wazuh manager to be notified when Wazuh selected events occur, using 3 messaging platforms: [ntfy.sh](https://ntfy.sh), [Discord](https://discord.com) and [Slack](https://slack.com). -There are 2 implementations of Wazuh notify. One written in Golang and the other in Python. Both implementations have -similar functionality, but the Python version is slightly more configurable. +There are 2 implementations of Wazuh notify. One written in Golang, the other in Python. Both implementations have +similar functionality, but the Python version is slightly more configurable for testing purposes. -Wazuh notify is a stateless implementation and only notifies, triggered by selected rules, agents, or threat levels. +Wazuh notify is a stateless implementation and only notifies: triggered by specific rules, agents, or threat levels. -Wazuh notify is triggered by configuring the **ossec.conf** and adding an **active response configuration.** +Wazuh notify is executed by configuring the **ossec.conf** and adding an **active response configuration**. ## Installation @@ -79,27 +80,27 @@ Set the correct permissions {id="set-the-correct-permissions_2"} $ sudo chmod uog+rx /var/ossec/active-response/bin/wazuh-notify ``` -### Step 3 +### Step 3: copy the TOML configuration file -Copy the YAML file to /var/ossec/etc/ +Copy the TOML file to /var/ossec/etc/ ``` -$ sudo cp /wazuh-notify-config.yaml /var/ossec/etc/ +$ sudo cp /wazuh-notify-config.toml /var/ossec/etc/ ``` Set the correct ownership {id="set-the-correct-ownership_3"} ``` -$ sudo chown root:wazuh /var/ossec/etc/wazuh-notify-config.yaml +$ sudo chown root:wazuh /var/ossec/etc/wazuh-notify-config.toml ``` Set the correct permissions {id="set-the-correct-permissions_3"} ``` -$ sudo chmod uog+r /var/ossec/etc/wazuh-notify-config.yaml +$ sudo chmod uog+r /var/ossec/etc/wazuh-notify-config.toml ``` -### Step 4 +### Step 4: create .env file Create an .env file in /var/ossec/etc/ @@ -110,16 +111,16 @@ $ sudo touch /var/ossec/etc/.env Set the correct ownership {id="set-the-correct-ownership_4"} ``` -$ sudo chown root:wazuh /var/ossec/etc/wazuh-notify-config.yaml +$ sudo chown root:wazuh /var/ossec/etc/wazuh-notify-config.toml ``` Set the correct permissions {id="set-the-correct-permissions_4"} ``` -$ sudo chmod uog+r /var/ossec/etc/wazuh-notify-config.yaml +$ sudo chmod uog+r /var/ossec/etc/wazuh-notify-config.toml ``` -## Configuration +## Wazuh configuration #### _Golang_ {id="golang_2"} @@ -169,26 +170,27 @@ Modify the /var/ossec/etc/ossec.conf configuration file and add the following: ``` -#### NOTE: - +#### NOTE: ! The `````` in the `````` section needs to be the same as the `````` in the `````` section. The `````` section describes the program that is executed. The `````` section describes the trigger that runs the ``````. Add the rules you want to be informed about between the ``````, with the rules id's separated by -comma's. -Example: ```5402, 3461, 8777
``` +comma's. +Example: ```5402, 3461, 8777```. + Please refer to the [Wazuh online documentation](https://documentation.wazuh.com/current/user-manual/capabilities/active-response/index.html) for more information. -## The YAML configuration +## The TOML configuration -This is the yaml config file for wazuh-active-response (for both the Python and Go version) +This is the toml configuration file for wazuh-notify (for both the Python and Golang version). The targets setting defines the platforms where notifications will be sent to. -Platforms in this comma-separated string will receive notifications. +Platforms in this comma-separated string will receive notifications, if and when they are set up. +Refer to [setting up the platforms](#setting-up-the-platforms-receiving-the-notifications). ``` targets: "slack, ntfy, discord" @@ -197,7 +199,7 @@ targets: "slack, ntfy, discord" Platforms in this comma-separated string will receive the full event information. ``` -full_message: "" +full_alert: "" ``` Exclude_rules and excluded_agents will disable notification for these particular events or agents that are enabled in @@ -212,42 +214,59 @@ excluded_rules: "99999, 00000" excluded_agents: "99999" ``` -There is a mapping -from [Wazuh threat levels](https://documentation.wazuh.com/current/user-manual/ruleset/rules-classification.html) (0-15) -to priorities (1-5) in notifications. -The colors are derived from -the [Homeland Security Advisory System](https://en.wikipedia.org/wiki/Homeland_Security_Advisory_System). +[The threat levels used in Wazuh](https://documentation.wazuh.com/current/user-manual/ruleset/rules-classification.html) +(0-15) are mapped to notification priority levels (1-5), and their respective colors (Discord only). +The Wazuh threat level scale runs from 0-15, where 15 is the most severe threat. It corresponds to the +[HSAS](https://en.wikipedia.org/wiki/Homeland_Security_Advisory_System) threat scale that runs from 5-1, whereby 1 is +the highest threat level. The configuration allows for customized mapping: in some use cases the mapping could be different. -Enter the values for the threat_map as lists of integers, mention_thresholds as integers and colors as Hex integers. +The mention threshold defines when Discord users receive a DM, next to the common messages they receive in their channel. +Often these common channels are muted and DM's will draw more attention. 1 means that for every notification a DM will be sent. +A mention threshold of 5 means that for every 5th occurrence of this specific event, a DM will be sent also. -The mention_threshold, relates to the number of times a rule has been fired. When the times fired is equal to or greater -than the mention_threshold, the recipient will receive a Discord mention in addition to the normal message. - -This setting is a list notation. +The notify threshold is somewhat similar to the mention threshold. A notify threshold of 1 will send each notification, +a notify threshold of 4 will only send each 4th notification triggered by a specific event. This will reduce high amounts +of notifications for the same event. The fired_times value in the message will show the actual number of the times this +specific event was generated. +Enter a threat_map as a list of integers, +color as a hex RGB color values, +mention/notify_threshold as integers. ``` -priority_map: - - threat_map: [ 15,14,13,12 ] - mention_threshold: 1 - color: 0xec3e40 # Red, SEVERE - - threat_map: [ 11,10,9 ] - mention_threshold: 1 - color: 0xff9b2b # Orange, HIGH - - threat_map: [ 8,7,6 ] - mention_threshold: 5 - color: 0xf5d800 # Yellow, ELEVATED - - threat_map: [ 5,4 ] - mention_threshold: 20 - color: 0x377fc7 # Blue, GUARDED - - threat_map: [ 3,2,1,0 ] - mention_threshold: 20 - color: 0x01a465 # Green, LOW +[[priority_map]] # Priority 1 on the HSAS scale +threat_map = [15, 14, 13, 12] # Wazuh threat levels -> priority 2 +color = 0xec3e40 # Red, SEVERE on the HSAS scale +mention_threshold = 1 +notify_threshold = 1 + +[[priority_map]] # Priority 2 on the HSAS scale +threat_map = [11, 10, 9] # Wazuh threat levels -> priority 2 +color = 0xff9b2b # Orange, HIGH on the HSAS scale +mention_threshold = 1 +notify_threshold = 1 + +[[priority_map]] # Priority 3 on the HSAS scale +threat_map = [8, 7, 6] # Wazuh threat levels -> priority 3 +color = 0xf5d800 # Yellow, ELEVATED on the HSAS scale +mention_threshold = 5 +notify_threshold = 5 + +[[priority_map]] # Priority 4 on the HSAS scale +threat_map = [5, 4] # Wazuh threat levels -> priority 4 +color = 0x377fc7 # Blue, GUARDED on the HSAS scale +mention_threshold = 20 +notify_threshold = 5 + +[[priority_map]] # Priority 5 on the HSAS scale +threat_map = [3, 2, 1, 0] # Wazuh threat levels -> priority 5 +color = 0x01a465 # Green, LOW on the HSAS scale +mention_threshold = 20 +notify_threshold = 1 ``` -The next 2 settings are used to add information to the messages. -Sender translate to the ``` username ``` field in Discord and to the ```title``` field in ntfy.sh. It is not used for -Slack. -Click adds an arbitrary URL to the message. +The next settings are used to add information to the messages. +```Sender``` translate to the ``` username ``` field in Discord and Slack and to the ```title``` field in ntfy.sh. +The ```click``` parameter adds an arbitrary URL to the message. ``` sender: "Wazuh (IDS)" @@ -264,15 +283,14 @@ Enter ```excluded_days``` as a string with comma separated values. Be aware of y excluded_days: "" ``` -Enter ```excluded_hours``` as a tuple of string values. Be aware of your regional settings. +Enter ```excluded_hours``` as a tuple of string values. ``` excluded_hours: [ "23:59", "00:00" ] ``` The following parameters define the markdown characters used to emphasise the parameter names in the notification -messages (Markdown style) -This is a dictionary (object) notation. +messages (Markdown style). This is a dictionary notation. ``` markdown_emphasis: @@ -283,29 +301,26 @@ discord: "**" The next settings are used for testing purposes. -Test mode will add an example event (wazuh-notify-test-event.json) instead of the message received through Wazuh. -This enables testing for particular events when the test event is customized. +```Test mode``` will add an example event (```wazuh-notify-test-event.json```) instead of the message received through Wazuh. +This enables customization for testing of a particular event. ``` test_mode: False ``` -Setting this parameter provides more logging to the wazuh-notifier log. Possible values are -0 (almost no logging), -1 (basic logging) and -2 (verbose logging) +Setting the ```extended_logging``` and ```extended_print``` parameters provides more logging to the wazuh-notifier log +and console. The possible values are: + +0-> limited logging +1-> basic logging +2-> verbose logging ``` extended_logging: 2 -``` - -Enabling this parameter provides extended logging to the console (see extended logging). - -``` extended_print: 0 ``` -## Setting up the platforms receiving the notifications +### Setting up the platforms receiving the notifications Each of the 3 platforms make use of webhooks or similar API's. In order to have the right information in the ```.env``` file, please refer to the platform's documentation. From b32b3a8f4e68d77138483cca5937e42b38adb4b9 Mon Sep 17 00:00:00 2001 From: Rudi Klein Date: Fri, 31 May 2024 20:31:59 +0200 Subject: [PATCH 2/6] Finale doc update + logo --- Writerside/topics/Wazuh-notifier.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/Writerside/topics/Wazuh-notifier.md b/Writerside/topics/Wazuh-notifier.md index d0f4da1..0fe1040 100644 --- a/Writerside/topics/Wazuh-notifier.md +++ b/Writerside/topics/Wazuh-notifier.md @@ -1,6 +1,10 @@ # Wazuh notify *version 1.0* + +Darius-logo-black.svg + + ## Table of Contents - [Introduction](#introduction) @@ -331,4 +335,5 @@ file, please refer to the platform's documentation. [ntfy.sh](https://docs.ntfy.sh/examples/) examples -[Discord](https://discord.com/developers/docs/intro) developers documentation \ No newline at end of file +[Discord](https://discord.com/developers/docs/intro) developers documentation + From 71fa79e450a6811c1971d5760414ecefb921eafd Mon Sep 17 00:00:00 2001 From: Rudi Klein Date: Sat, 1 Jun 2024 13:18:40 +0200 Subject: [PATCH 3/6] Finale doc update + logo --- Writerside/topics/Wazuh-notifier.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Writerside/topics/Wazuh-notifier.md b/Writerside/topics/Wazuh-notifier.md index 0fe1040..5d46391 100644 --- a/Writerside/topics/Wazuh-notifier.md +++ b/Writerside/topics/Wazuh-notifier.md @@ -1,8 +1,7 @@ # Wazuh notify *version 1.0* - -Darius-logo-black.svg +Darius-logo-black.svg ## Table of Contents From e5997713f0d7bfe959f898864974b53eb783f994 Mon Sep 17 00:00:00 2001 From: Rudi Klein Date: Sat, 1 Jun 2024 13:19:18 +0200 Subject: [PATCH 4/6] images --- Writerside/images/Darius-logo-black.svg | 1 + Writerside/images/Darius-logo-wit.svg | 1 + 2 files changed, 2 insertions(+) create mode 100644 Writerside/images/Darius-logo-black.svg create mode 100644 Writerside/images/Darius-logo-wit.svg diff --git a/Writerside/images/Darius-logo-black.svg b/Writerside/images/Darius-logo-black.svg new file mode 100644 index 0000000..bacfd2a --- /dev/null +++ b/Writerside/images/Darius-logo-black.svg @@ -0,0 +1 @@ +Klein Projects``` \ No newline at end of file diff --git a/Writerside/images/Darius-logo-wit.svg b/Writerside/images/Darius-logo-wit.svg new file mode 100644 index 0000000..005054b --- /dev/null +++ b/Writerside/images/Darius-logo-wit.svg @@ -0,0 +1 @@ +```Klein Projects \ No newline at end of file From fd24189e40140c710a565dd22ee28e0cf3a6052a Mon Sep 17 00:00:00 2001 From: Rudi Klein Date: Sat, 1 Jun 2024 20:07:06 +0200 Subject: [PATCH 5/6] Create README.md --- README.md | 338 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 338 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 0000000..4c5191b --- /dev/null +++ b/README.md @@ -0,0 +1,338 @@ +# Wazuh notify +*version 1.0* + + +![](Darius-logo-black.svg){ width="450"} + +## Table of Contents + +- [Introduction](#introduction) +- [Installation](#installation) + - [Step 1: download](#step-1-download) + - [Step 2: copy files](#step-2-copy-files) + - [Python](#python_1) + - [Golang](#golang_1) + - [Step 3: copy the TOML file](#step-3-copy-the-toml-configuration-file) + - [Step 4: create .env file](#step-4-create-env-file) +- [Wazuh configuration](#wazuh-configuration) + - [Golang](#golang_2) + - [Python](#python_2) + - [Note](#note) +- [The TOML configuration file](#the-toml-configuration) +- [Setting up the platforms](#setting-up-the-platforms-receiving-the-notifications) + +## Introduction + +Wazuh notifier enables the Wazuh manager to be notified when Wazuh selected events occur, using 3 messaging platforms: +[ntfy.sh](https://ntfy.sh), [Discord](https://discord.com) and [Slack](https://slack.com). + +There are 2 implementations of Wazuh notify. One written in Golang, the other in Python. Both implementations have +similar functionality, but the Python version is slightly more configurable for testing purposes. + +Wazuh notify is a stateless implementation and only notifies: triggered by specific rules, agents, or threat levels. + +Wazuh notify is executed by configuring the **ossec.conf** and adding an **active response configuration**. + +## Installation + +### Step 1: download + +Download the files from https://github.com/kleinprojects/wazuh-notify to your server. + +### Step 2: copy files + +#### _Python_ {id="python_1"} + +Copy the 2 Python scripts to the /var/ossec/active-response/bin/ folder + +``` +$ sudo cp /wazuh-*.py /var/ossec/active-response/bin/ +``` + +Set the correct ownership {id="set-the-correct-ownership_1"} + +``` +$ sudo chown root:wazuh /var/ossec/active-response/bin/wazuh-notify.py +$ sudo chown root:wazuh /var/ossec/active-response/bin/wazuh_notify_module.py +``` + +Set the correct permissions {id="set-the-correct-permissions_1"} + +``` +$ sudo chmod uog+rx /var/ossec/active-response/bin/wazuh-notify.py +$ sudo chmod uog+rx /var/ossec/active-response/bin/wazuh_notify_module.py +``` + +#### _Golang_ {id="golang_1"} + +Copy the Go executable to the /var/ossec/active-response/bin/ folder + +``` +$ sudo cp /wazuh-notify /var/ossec/active-response/bin/ +``` + +Set the correct ownership {id="set-the-correct-ownership_2"} + +``` +$ sudo chown root:wazuh /var/ossec/active-response/bin/wazuh-notify +``` + +Set the correct permissions {id="set-the-correct-permissions_2"} + +``` +$ sudo chmod uog+rx /var/ossec/active-response/bin/wazuh-notify +``` + +### Step 3: copy the TOML configuration file + +Copy the TOML file to /var/ossec/etc/ + +``` +$ sudo cp /wazuh-notify-config.toml /var/ossec/etc/ +``` + +Set the correct ownership {id="set-the-correct-ownership_3"} + +``` +$ sudo chown root:wazuh /var/ossec/etc/wazuh-notify-config.toml +``` + +Set the correct permissions {id="set-the-correct-permissions_3"} + +``` +$ sudo chmod uog+r /var/ossec/etc/wazuh-notify-config.toml +``` + +### Step 4: create .env file + +Create an .env file in /var/ossec/etc/ + +``` +$ sudo touch /var/ossec/etc/.env +``` + +Set the correct ownership {id="set-the-correct-ownership_4"} + +``` +$ sudo chown root:wazuh /var/ossec/etc/wazuh-notify-config.toml +``` + +Set the correct permissions {id="set-the-correct-permissions_4"} + +``` +$ sudo chmod uog+r /var/ossec/etc/wazuh-notify-config.toml +``` + +## Wazuh configuration + +#### _Golang_ {id="golang_2"} + +Modify the /var/ossec/etc/ossec.conf configuration file and add the following:
+ +*Command section* + +``` + +wazuh-notify-go +wazuh-notify +yes + +``` + +*Active response section* + +``` + +wazuh-notify-go +server + + + +``` + +#### _Python_ {id="python_2"} + +*Command section* + +``` + +wazuh-notify-py +wazuh-notify.py +yes + +``` + +*Active response section* + +``` + +wazuh-notify-py +server + + + +``` + +#### NOTE: ! +The `````` in the `````` section needs to be the same as the `````` in +the `````` section. +The `````` section describes the program that is executed. The `````` section describes the +trigger that runs the ``````. + +Add the rules you want to be informed about between the ``````, with the rules id's separated by +comma's. +Example: ```5402, 3461, 8777```. + +Please refer to +the [Wazuh online documentation](https://documentation.wazuh.com/current/user-manual/capabilities/active-response/index.html) +for more information. + +## The TOML configuration + +This is the toml configuration file for wazuh-notify (for both the Python and Golang version). + +The targets setting defines the platforms where notifications will be sent to. +Platforms in this comma-separated string will receive notifications, if and when they are set up. +Refer to [setting up the platforms](#setting-up-the-platforms-receiving-the-notifications). + +``` +targets: "slack, ntfy, discord" +``` + +Platforms in this comma-separated string will receive the full event information. + +``` +full_alert: "" +``` + +Exclude_rules and excluded_agents will disable notification for these particular events or agents that are enabled in +the ossec.conf active response definition. +These settings provide an easier way to disable event notifications from firing. No need to restart Wazuh-manager. + +Enter rule numbers as a string with comma-separated values. +Enter numeric agent id's as a string with comma-separated values. + +``` +excluded_rules: "99999, 00000" +excluded_agents: "99999" +``` + +[The threat levels used in Wazuh](https://documentation.wazuh.com/current/user-manual/ruleset/rules-classification.html) +(0-15) are mapped to notification priority levels (1-5), and their respective colors (Discord only). +The Wazuh threat level scale runs from 0-15, where 15 is the most severe threat. It corresponds to the +[HSAS](https://en.wikipedia.org/wiki/Homeland_Security_Advisory_System) threat scale that runs from 5-1, whereby 1 is +the highest threat level. The configuration allows for customized mapping: in some use cases the mapping could be different. + +The mention threshold defines when Discord users receive a DM, next to the common messages they receive in their channel. +Often these common channels are muted and DM's will draw more attention. 1 means that for every notification a DM will be sent. +A mention threshold of 5 means that for every 5th occurrence of this specific event, a DM will be sent also. + +The notify threshold is somewhat similar to the mention threshold. A notify threshold of 1 will send each notification, +a notify threshold of 4 will only send each 4th notification triggered by a specific event. This will reduce high amounts +of notifications for the same event. The fired_times value in the message will show the actual number of the times this +specific event was generated. + +Enter a threat_map as a list of integers, +color as a hex RGB color values, +mention/notify_threshold as integers. +``` +[[priority_map]] # Priority 1 on the HSAS scale +threat_map = [15, 14, 13, 12] # Wazuh threat levels -> priority 2 +color = 0xec3e40 # Red, SEVERE on the HSAS scale +mention_threshold = 1 +notify_threshold = 1 + +[[priority_map]] # Priority 2 on the HSAS scale +threat_map = [11, 10, 9] # Wazuh threat levels -> priority 2 +color = 0xff9b2b # Orange, HIGH on the HSAS scale +mention_threshold = 1 +notify_threshold = 1 + +[[priority_map]] # Priority 3 on the HSAS scale +threat_map = [8, 7, 6] # Wazuh threat levels -> priority 3 +color = 0xf5d800 # Yellow, ELEVATED on the HSAS scale +mention_threshold = 5 +notify_threshold = 5 + +[[priority_map]] # Priority 4 on the HSAS scale +threat_map = [5, 4] # Wazuh threat levels -> priority 4 +color = 0x377fc7 # Blue, GUARDED on the HSAS scale +mention_threshold = 20 +notify_threshold = 5 + +[[priority_map]] # Priority 5 on the HSAS scale +threat_map = [3, 2, 1, 0] # Wazuh threat levels -> priority 5 +color = 0x01a465 # Green, LOW on the HSAS scale +mention_threshold = 20 +notify_threshold = 1 +``` + +The next settings are used to add information to the messages. +```Sender``` translate to the ``` username ``` field in Discord and Slack and to the ```title``` field in ntfy.sh. +The ```click``` parameter adds an arbitrary URL to the message. + +``` +sender: "Wazuh (IDS)" +click: "https://documentation.wazuh.com/" +``` + +### From here on the settings are ONLY used by the Python version of wazuh-notify. + +Below settings provide for a window that enable/disables events from firing the notifiers. + +Enter ```excluded_days``` as a string with comma separated values. Be aware of your regional settings. + +``` +excluded_days: "" +``` + +Enter ```excluded_hours``` as a tuple of string values. + +``` +excluded_hours: [ "23:59", "00:00" ] +``` + +The following parameters define the markdown characters used to emphasise the parameter names in the notification +messages (Markdown style). This is a dictionary notation. + +``` +markdown_emphasis: +slack: "*" +ntfy: "**" +discord: "**" +``` + +The next settings are used for testing purposes. + +```Test mode``` will add an example event (```wazuh-notify-test-event.json```) instead of the message received through Wazuh. +This enables customization for testing of a particular event. + +``` +test_mode: False +``` + +Setting the ```extended_logging``` and ```extended_print``` parameters provides more logging to the wazuh-notifier log +and console. The possible values are: + +0-> limited logging +1-> basic logging +2-> verbose logging + +``` +extended_logging: 2 +extended_print: 0 +``` + +### Setting up the platforms receiving the notifications + +Each of the 3 platforms make use of webhooks or similar API's. In order to have the right information in the ```.env``` +file, please refer to the platform's documentation. + +[Slack](https://api.slack.com/) API documentation + +[ntfy.sh](https://docs.ntfy.sh/subscribe/api/) API documentation + +[ntfy.sh](https://docs.ntfy.sh/examples/) examples + +[Discord](https://discord.com/developers/docs/intro) developers documentation + From c5ec486fefe7f14d5fa352aaf9b2c9bc8582eca6 Mon Sep 17 00:00:00 2001 From: Rudi Klein Date: Sat, 1 Jun 2024 20:07:31 +0200 Subject: [PATCH 6/6] Update README.md --- README.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/README.md b/README.md index 4c5191b..49667d2 100644 --- a/README.md +++ b/README.md @@ -1,9 +1,6 @@ # Wazuh notify *version 1.0* - -![](Darius-logo-black.svg){ width="450"} - ## Table of Contents - [Introduction](#introduction)