Coder Social home page Coder Social logo

wazuh / wazuh-documentation Goto Github PK

View Code? Open in Web Editor NEW
172.0 69.0 309.0 664.32 MB

Wazuh - Project documentation

Home Page: https://wazuh.com

Makefile 0.80% Batchfile 0.79% Python 4.78% HTML 4.37% JavaScript 52.33% Dockerfile 0.05% SCSS 36.88%
wazuh documentation reference ossec openscap elasticsearch monitoring security security-hardening pci-dss

wazuh-documentation's Introduction

Wazuh

Slack Email Documentation Documentation Coverity Twitter YouTube

Wazuh is a free and open source platform used for threat prevention, detection, and response. It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments.

Wazuh solution consists of an endpoint security agent, deployed to the monitored systems, and a management server, which collects and analyzes data gathered by the agents. Besides, Wazuh has been fully integrated with the Elastic Stack, providing a search engine and data visualization tool that allows users to navigate through their security alerts.

Wazuh capabilities

A brief presentation of some of the more common use cases of the Wazuh solution.

Intrusion detection

Wazuh agents scan the monitored systems looking for malware, rootkits and suspicious anomalies. They can detect hidden files, cloaked processes or unregistered network listeners, as well as inconsistencies in system call responses.

In addition to agent capabilities, the server component uses a signature-based approach to intrusion detection, using its regular expression engine to analyze collected log data and look for indicators of compromise.

Log data analysis

Wazuh agents read operating system and application logs, and securely forward them to a central manager for rule-based analysis and storage. When no agent is deployed, the server can also receive data via syslog from network devices or applications.

The Wazuh rules help make you aware of application or system errors, misconfigurations, attempted and/or successful malicious activities, policy violations and a variety of other security and operational issues.

File integrity monitoring

Wazuh monitors the file system, identifying changes in content, permissions, ownership, and attributes of files that you need to keep an eye on. In addition, it natively identifies users and applications used to create or modify files.

File integrity monitoring capabilities can be used in combination with threat intelligence to identify threats or compromised hosts. In addition, several regulatory compliance standards, such as PCI DSS, require it.

Vulnerability detection

Wazuh agents pull software inventory data and send this information to the server, where it is correlated with continuously updated CVE (Common Vulnerabilities and Exposure) databases, in order to identify well-known vulnerable software.

Automated vulnerability assessment helps you find the weak spots in your critical assets and take corrective action before attackers exploit them to sabotage your business or steal confidential data.

Configuration assessment

Wazuh monitors system and application configuration settings to ensure they are compliant with your security policies, standards and/or hardening guides. Agents perform periodic scans to detect applications that are known to be vulnerable, unpatched, or insecurely configured.

Additionally, configuration checks can be customized, tailoring them to properly align with your organization. Alerts include recommendations for better configuration, references and mapping with regulatory compliance.

Incident response

Wazuh provides out-of-the-box active responses to perform various countermeasures to address active threats, such as blocking access to a system from the threat source when certain criteria are met.

In addition, Wazuh can be used to remotely run commands or system queries, identifying indicators of compromise (IOCs) and helping perform other live forensics or incident response tasks.

Regulatory compliance

Wazuh provides some of the necessary security controls to become compliant with industry standards and regulations. These features, combined with its scalability and multi-platform support help organizations meet technical compliance requirements.

Wazuh is widely used by payment processing companies and financial institutions to meet PCI DSS (Payment Card Industry Data Security Standard) requirements. Its web user interface provides reports and dashboards that can help with this and other regulations (e.g. GPG13 or GDPR).

Cloud security

Wazuh helps monitoring cloud infrastructure at an API level, using integration modules that are able to pull security data from well known cloud providers, such as Amazon AWS, Azure or Google Cloud. In addition, Wazuh provides rules to assess the configuration of your cloud environment, easily spotting weaknesses.

In addition, Wazuh light-weight and multi-platform agents are commonly used to monitor cloud environments at the instance level.

Containers security

Wazuh provides security visibility into your Docker hosts and containers, monitoring their behavior and detecting threats, vulnerabilities and anomalies. The Wazuh agent has native integration with the Docker engine allowing users to monitor images, volumes, network settings, and running containers.

Wazuh continuously collects and analyzes detailed runtime information. For example, alerting for containers running in privileged mode, vulnerable applications, a shell running in a container, changes to persistent volumes or images, and other possible threats.

WUI

The Wazuh WUI provides a powerful user interface for data visualization and analysis. This interface can also be used to manage Wazuh configuration and to monitor its status.

Modules overview

Modules overview

Security events

Overview

Integrity monitoring

Overview

Vulnerability detection

Overview

Regulatory compliance

Overview

Agents overview

Overview

Agent summary

Overview

Orchestration

Here you can find all the automation tools maintained by the Wazuh team.

Branches

  • master branch contains the latest code, be aware of possible bugs on this branch.
  • stable branch on correspond to the last Wazuh stable version.

Software and libraries used

Software Version Author License
bzip2 1.0.8 Julian Seward BSD License
cJSON 1.7.12 Dave Gamble MIT License
cPython 3.10.13 Guido van Rossum Python Software Foundation License version 2
cURL 8.5.0 Daniel Stenberg MIT License
Flatbuffers 23.5.26 Google Inc. Apache 2.0 License
GoogleTest 1.11.0 Google Inc. 3-Clause "New" BSD License
jemalloc 5.2.1 Jason Evans 2-Clause "Simplified" BSD License
Lua 5.3.6 PUC-Rio MIT License
libarchive 3.7.2 Tim Kientzle 3-Clause "New" BSD License
libdb 18.1.40 Oracle Corporation Affero GPL v3
libffi 3.2.1 Anthony Green MIT License
libpcre2 10.42.0 Philip Hazel BSD License
libplist 2.2.0 Aaron Burghardt et al. GNU Lesser General Public License version 2.1
libYAML 0.1.7 Kirill Simonov MIT License
liblzma 5.4.2 Lasse Collin, Jia Tan et al. GNU Public License version 3
Linux Audit userspace 2.8.4 Rik Faith LGPL (copyleft)
msgpack 3.1.1 Sadayuki Furuhashi Boost Software License version 1.0
nlohmann 3.7.3 Niels Lohmann MIT License
OpenSSL 3.0.12 OpenSSL Software Foundation Apache 2.0 License
pacman 5.2.2 Judd Vinet GNU Public License version 2 (copyleft)
popt 1.16 Jeff Johnson & Erik Troan MIT License
procps 2.8.3 Brian Edmonds et al. LGPL (copyleft)
RocksDB 8.3.2 Facebook Inc. Apache 2.0 License
rpm 4.18.2 Marc Ewing & Erik Troan GNU Public License version 2 (copyleft)
sqlite 3.45.0 D. Richard Hipp Public Domain (no restrictions)
zlib 1.3.1 Jean-loup Gailly & Mark Adler zlib/libpng License

Documentation

Get involved

Become part of the Wazuh's community to learn from other users, participate in discussions, talk to our developers and contribute to the project.

If you want to contribute to our project please don’t hesitate to make pull-requests, submit issues or send commits, we will review all your questions.

You can also join our Slack community channel and mailing list by sending an email to [email protected], to ask questions and participate in discussions.

Stay up to date on news, releases, engineering articles and more.

Authors

Wazuh Copyright (C) 2015-2023 Wazuh Inc. (License GPLv2)

Based on the OSSEC project started by Daniel Cid.

wazuh-documentation's People

Contributors

alberpilot avatar albertomn86 avatar arcapas avatar chantal-kelm avatar chemamartinez avatar crolopez avatar davidfmiranda avatar davidjiglesias avatar desvelao avatar dfolcha avatar dkempny avatar fdalmaup avatar jaochaos avatar javimed avatar jesuslinares avatar jmv74211 avatar juanjijg avatar luiscontrerasdo avatar m3libea avatar marvergara avatar mcarmona99 avatar pilarquesada avatar rauldpm avatar s-ocando avatar santiago-bassett avatar selutario avatar snaow avatar vamera avatar vicferpoy avatar vikman90 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

wazuh-documentation's Issues

Include more OS in Getting started - wazuh agent page

Hello

I think that we could add others OS to the sentence:

The agents can be used to monitor physical servers, virtual machines and cloud instances (e.g. Amazon AWS, Azure or Google Cloud). Pre-compiled agent installation packages are available for Linux, AIX, Solaris, Windows, and Darwin (Mac OS X).

so we could add: HP-UX, AIX.
Thanks!

Add packages list for Kibana and Splunk apps

Just like we have packages list for the Wazuh manager, API and agent components, and a WPK list, we need to add packages list for the two apps for Wazuh (Kibana and Splunk).

Regards,
Juanjo

Problems in `Running API as service`

There are two problems I encountered when I followed the section running-api-as-service in ossec_api_installation.

  • sudo /var/ossec/api/scripts/install_daemon.sh will not work.

The error message is: sed: can't read wazuh-api: No such file or directory
The below is work.

cd /var/ossec/api/scripts
./install_daemon.sh
  • The function status in wazuh-api is empty...

AES encryption for manager-agent connection

Add new option to the reference section as well as the necessary documentation about the new crypto method supported.

<client>
    ...
    <crypto_method>aes|blowfish</crypto_method>

@avinash-gudagi: Please put a note about the CloudTrails digit

Referring to #PR 23

Quoting @avinash-gudagi

I was using your script to get aws logs of cloudtrails from a bucket and then use OSSEC to monitor these trails. I noticed that the s3 bucket also contained logs about cloudtail-digest. The getawslog.py script throws a exception. Just sending a pull request to mention this in a note.

./getawslog.py -b cloudtrails-ossec -d -j -D -l /home/ubuntu/cloudtrail-logs/amazon.log
+++ Debug mode on
+++ Connecting to Amazon S3
+++ Found new log: 072477793200_CloudTrail-Digest_ap-northeast-1_Test-trail_us-west-2_20160802T142331Z.json.gz
Traceback (most recent call last):
File "./getawslog.py", line 101, in
main(sys.argv[1:])
File "./getawslog.py", line 80, in main
records = j["Records"]
KeyError: 'Records'

Let me take a look on it and I will update you in few minutes.

Documentation: <group....> ...</group> required in local_rules.xml

When I follow the instructions for changing an existing rule in the documentation, I get this error when running ossec-logtest:

# /var/ossec/bin/ossec-logtest
...
2018/01/28 08:26:29 ossec-testrule: ERROR: rules_op: Invalid root element "rule".Only "group" is allowed
2018/01/28 08:26:29 ossec-testrule: CRITICAL: (1220): Error loading the rules: 'ruleset/rules/local_rules.xml'.

The rule I am changing comes from 0155-dovecot_rules.xml. If I copy the '<group...> and settings from that file into local_rules.xml, ossec-logtest succeeds:

<group name="dovecot,">
<rule id="9706" level="0" overwrite="yes">
  <if_sid>9700</if_sid>
  <match>: Disconnected: </match>
  <description>Dovecot Session Disconnected.</description>
  <group>pci_dss_10.2.5,pci_dss_8.1.5,pci_dss_8.1.8,gpg13_7.1,</group>
</rule>
</group>

Todo:

Questions:

  • Is the group "name" important -- that is, does it need to match the group name of the original rule?
  • If the group name does not need to match, should the group name in "local_rules.xml" be set to something like "local_rules,"?
  • If the group name needs to (or should) match, can there be multiple <group...> entries in local_rules.xml -- in case I need to change rules from multiple groups?

Agent health check

In previous versions, the agent would log this:

2017/12/15 23:15:29 ossec-agentd(4102): INFO: Connected to the server (172.31.17.4:1514).

And that was my "All's well."

The new version doesn't log that. What is the modern equivalent?

Wazuh Alert Level Description

Hello, i am trying to learn about wazuh ruleset and create my own ruleset but i need to know the description of every level which is written in core ruleset of wazuh.

Feedback

Just want some feedback on a few changes that I've put here.

Ideas for new template

  1. Include specific instructions for each OS you support w/ packages. (Which are those?)
  2. Add curl commands to test functionality
  3. File creations & initial contents should be easily executable via the command line.
  4. Maybe build out installation instructions for each type of machine? manager, agent, api, elastic+kibana? If we build out more comprehensive instructions it might be a good idea to break them out into their own documentation.

msi don't know SERVER_IP

Hello! According to documentation msi should use SERVER_IP from command line, but in reality it uses ADDRESS.

Update new cluster documentation

Hello team,

The new cluster has changed for the next version of Wazuh, so now we need to update the documentation to reflect the new configuration options and the How it works section.

This issue will track the progress on the new documentation for this.

Currently defined tasks:

  • Remove "all cluster nodes must have the same date" note - fcbf5b3
  • Update "How it works" section - d20d429
  • Update "Master" subsection from "How it works" section - 8645f31
  • Make a flow diagram of how the cluster works - d20d429
  • Update "Client" subsection from "How it works" section - 4e86004
  • Remove wazuh-clusterd-internal daemon and update wazuh-clusted daemon from daemons section - 8eb64bb 2a30d32
  • Update cluster_control section - bf7c345
  • Remove cluster database section - d074398
  • Update "use case & how to install" section - 043bd5a
  • Update "how to install on centos6" section - 08a380e
  • Add "how to update cluster" section - db95f25
  • Update cluster configuration section - 45b7d9e
  • Update cluster API calls - 3c246e8

Best regards,
Marta

ossec_amazon

Hey guys,
I've found bunch of things with http://documentation.wazuh.com/en/latest/ossec_amazon.html

  1. After installing awscli, boto, getawslog.py still doesn't work - error is related to AWS credentials. I was able to fix it only by creating .boto file http://boto.cloudhackers.com/en/latest/getting_started.html - Configuring Boto Credentials section. After that I did pip uninstall awscli and everything still works fine. Looks like one doesn't even have to install it.
  2. Security IAM rules Give the user(s) permission to manage security policies, press Attach Policy and select AmazonS3FullAccess policy. defo not the best way to do things. If you don't mind I can create a pull-request with more tighten IAM policy example, which will allow only read and delete access to specific bucket and only list this particular bucket. Also in this case getawslog.py should be a bit adjusted as it would no be able list all buckets in account. I could do a pull-request for this too.
  3. CloudTrail Enable log file validation parameter has to be configured as NO. If YES - then getawslog.py fails with error provided below: (line numbers are different as I modified the script a bit)
 error Traceback (most recent call last):
  File "./getawslog.py", line 100, in <module>
    main(sys.argv[1:])
  File "./getawslog.py", line 77, in main
    records = j["Records"]
KeyError: 'Records'
  1. Let's assume everything with this getawslog.pyworks fine and we have amazon.log filled with data. What should happen next ? Which part of software have to read data in this file ? I suppose ossec-agent has to be configured somehow, but not yet sure about this. Could you please shed some light here ?

Thanks for your work, guys.

elasticsearch: document config requirements during upgrade

Elasticsearch will not start after doing the upgrade on a 2.1 VM appliance (CentOS 7)

Symptom: In step 3 of 'Upgrade Elasticsearch' on this page: https://documentation.wazuh.com/current/installation-guide/upgrading/different_major.html#upgrading-different-major

curl https://raw.githubusercontent.com/wazuh/wazuh/3.0/extensions/elasticsearch/wazuh-elastic6-template-alerts.json | curl -XPUT 'http://localhost:9200/_template/wazuh' -H 'Content-Type: application/json' -d @-
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 17205  100 17205    0     0  79415      0 --:--:-- --:--:-- --:--:-- 79652
curl: (7) Failed connect to localhost:9200; Connection refused

There are new required values in the elasticsearch configuration files, but yum does not overwrite the existing files during the update.

Doing this allows elasticsearch to start, allowing the install to proceed:

cd /etc/elasticsearch
mv elasticsearch.yml elasticsearch.yml.save
cp elasticsearch.yml.rpmnew elasticsearch.yml
mv jvm.options jvm.options.save
cp jvm.options.rpmnew jvm.options

Log Collector with time frequency

I'm using wazuh for my internship in. I need collecting log and analyzing it but not every time after the event in the log happening because there is still no specialize network for communicating this log in my place and if it send everytime it can make the network become crowded.
How can i set collecting log but with time frequency? for example i need to collect apache access and error log but only every 2 hour.

Wazuh 3.x Documentation Regarding Capabilities and VULS

I have Wazuh 3.x installed on a PC with Ubuntu 16.04 LTS Desktop, with several other Windows 10 PCs running agents, in a SOHO environment. Everything is working fine and I have just completed VirusTotal integration successfully.

I started the VULS integration installation script and immediately ran into a problem:

# /var/ossec/wodles/vuls/deploy_vuls.sh ubuntu 16

...This script will install dependencies, download VULS, download CVE and OVAL databases, and configure VULS. This deployment supports the following operating systems:...

https://documentation.wazuh.com/3.x/user-manual/capabilities/vuls.html#how-it-works

The referenced documentation above fails to mention that if you run the installation script, on a Ubuntu 16 Desktop PC, it will uninstall the Ubuntu Desktop among other things like (pardon paraphrases) ttf-mscorefonts-installer, ubuntu-desktop, update-manager, ubuntu-release-updater-gtk, update-notification-common.

I'm sure not many are running this type of software on desktop PCs but it would have been helpful to get a warning.

Just thought someone should know.

Kibana plugin install-proxy

Hi,
Following the documentation I install the Wazuh App plugin for Kibana with the comand below:

$ /usr/share/kibana/bin/kibana-plugin install https://packages.wazuh.com/wazuhapp/wazuhapp.zip

but unfortunately I obtain this error:

Error: Client request error: connect EHOSTUNREACH 54.230.128.120:443 Plugin installation was unsuccessful due to error "Client request error: connect EHOSTUNREACH 54.230.128.120:443"

So I have tried the local installation.
After the download with the command:

/usr/share/kibana/bin/kibana-plugin install wazuhapp url file:///tmp/wazuhapp.zip

I have this also error:

Attempting to transfer from wazuhapp Attempting to transfer from https://artifacts.elastic.co/downloads/kibana-plugins/wazuhapp/wazuhapp-5.5.2.zip Error: Client request error: connect ETIMEDOUT 54.243.108.41:443 Plugin installation was unsuccessful due to error "Client request error: connect ETIMEDOUT 54.243.108.41:443"

Could you have any suggestion to install the plugin with proxy? Many thanks.

Hardware recommendation

There isn't much documented regarding what should be the recommended hardware(RAM, CPU cores, Disk size) setup for Wazuh server and Elasticsearch nodes. This can include recommendations based on number of machines which needs to be monitored.

Improve documentation for database output

The documentation to configure the alert output to the database is not sufficient. The explanation given in wazuh/wazuh#569 may be helpful.

Pending tasks

  • Elaborate a list of steps for both MySQL and PostgreSQL. The list must be minimal but sufficient to properly configure database output:
    • MySQL:
      • Required configuration
      • Wazuh configuration block
    • PostgreSQL:
      • Required configuration
      • Wazuh configuration block

Step 4 of Upgrade Elastic from 2 to 4 is pointing to a wrong document

If we follow the upgrade steps from ELK 2 to ELK 5, there is an error with the step 4 link.
We start at:
https://documentation.wazuh.com/current/installation-guide/upgrading/index.html
then we chose "Upgrade from a legacy version":
https://documentation.wazuh.com/current/installation-guide/upgrading/legacy/index.html#upgrading-wazuh-legacy
then we click on "Upgrade from Elastic Stack 2.x to 5.x"
https://documentation.wazuh.com/current/installation-guide/upgrading/legacy/upgrading-elastic-stack.html#upgrade-from-elastic-stack-2-x-to-5-x
and the step 4 is:

At this point, you are ready to install the new version of Elastic Stack. Follow the appropriate link below for installation instructions for your specific operating system:

Install Elastic Stack with RPM packages
Install Elastic Stack with DEB packages

Both links point to a Elastic Stack version 6 installation. These links must to point to 5 version (Wazuh 2.1 documentation).

Best regards,
Alberto R.

API PowerShell script

Hi everyone,
when I search to add an agent with the PowerShell script I obtain the following error

IE has not had it's initial startup dialogue dismissed, please complete this step and try again. Script will exit. Error: $($geterr)`n .Please Run OSSEC_AgentConfig Seperately once you correct the error

In the code I saw that this error is in Test API integration but I checked the correctness of configuration's part with APIaddress, Wazuh manager IP, username and password.
So how can I proceed?

And could you explain me better this phrase:

Test API integration to make sure IE has run through initial startup dialogue - This can be a problem with new servers

Many thanks

What's the difference between Single Host and DIstributed Architecture ?

Hi Wazuh Team!

I have some question regarding the Architecture section of Wazuh Documentation. It's been bugging me for a days, because it stated on Wazuh Documentation said, that Single Host architecture is recommended for a Small Wazuh deployments (<50 agents), quoted from the wazuh documentation said:

In smaller Wazuh deployments, Wazuh and Elastic Stack with a single-node Elasticsearch instance can all be deployed on a single server. In this scenario, Logstash can read the Wazuh alerts and/or archived events directly from the local file system and feed them into the local Elasticsearch instance.

Compare it with the Distributed ones quoted from wazuh doc :

An Elasticsearch cluster is a collection of one or more nodes (servers) that communicate with each other to perform read and write operations on indexes. Small Wazuh deployments (<50 agents), can easily be handled by a single-node cluster. Multi-node clusters are recommended when there is a large number of monitored systems, when a large volume of data is anticipated and/or when high availability is required.

When the Wazuh server and the Elasticsearch cluster are on different hosts, Filebeat is used to securely forward Wazuh alerts and/or archived events to the Elasticsearch server(s) using TLS encryption.

i am not fully understand with the different between these two Architecture, especially with the advantages and disadvantages on both Architecture. My summary on both Architecture:

  • Single-Host
  1. More recommended in small architecture.
  2. Elastic and Wazuh manager are on the same machine
  • Distrbuted
  1. Strongly recommended on bigger architecture
  2. Have file beat to encrypt the forwarded log
  3. More capable to handle many many agents and log
  4. Elastic and Wazuh are on seperated machine.

I mean, what if i used the distributed architecture on small deployment such as i only have 5 agents that wanted to be monitored, and i only have one ossec server, is it prohibited? I questioned this because i always seen some people that used Distributed architecture even in smaller deployment. I just want to make sure that what i conclude was correct, or am i missed something ?

What's the matter with Wazuh and ELK on different machine ? i know that the answer would be " because in some condition you just want to do it that way," i mean, is there any condition that didnt stated on the wazuh documentation like you want to do it because that or because this or because "when the machine A which has ELK got infected by virus, fortunately, it was separate with machine B which has ossec on it, so my log data and configuration are untouched/safe from virus, thank god".

Regards
fathin

error import gpg key

Hi,

I try to install ossec-hids-agent for debian stretch and follow this link
https://github.com/wazuh/wazuh-documentation/blob/master/source/ossec_installation_deb.rst

but after apt-get update I get

W: GPG error: https://ossec.wazuh.com/repos/apt/debian stretch InRelease: The following signatures were invalid: 9FE55537D1713CA519DFB85114B9C8DB9A1B1C65
W: The repository 'https://ossec.wazuh.com/repos/apt/debian stretch InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.

do I forget something?
many thanks!!

kind regards

Rename repository

Hello, is it possible to rename repo to something like ossec-documentation ?
B/c fork looks a bit strange - netflash/documentation - not really related to anything.

Add CONTRIBUTING.md file to the documentation repository

Hello team,

As the documentation is a collaborative project, it needs organization in how we manage and use the branches to add new articles and sections to the Wazuh documentation.

A CONTRIBUTING.md file is needed to describe this contribution process to ensure good maintainability in this repository.

Regards,
Juanjo

When to use which? (and some other questions and comments)

(sorry for over-loading the Issue)

When does one choose the "OSSEC HIDS" container versus the "OSSEC-ELK" container?

I'm guessing that since the WUI is abandoned and I don't have an ELK of my own, I want OSSEC-ELK, but even if I'm correct, shouldn't that be in the doc somewhere?

Where's the dashboard? I see 5 ports being mapped to the container, but which one is the dashboard? I'll try my browser against them all, but shouldn't that go in the doc, too?

In my opinion, the section that gives credit to xetus-oss should not be in the middle of the Docker installation section. It could be first, or before the container sections, or in the head of each container section, instead.

Last, I wish there was a "bunny slope", a guide for impatient geeks. There are lots of setup choices, and I'm hoping the container is the simplest and fastest.

Thank you for making it easy to offer feedback!

Agent registration in cluster

Hello all,

Our cluster documentation lacks information about agent registration. I think a subsection should be added in the "Configuring a cluster" page.

Best regards,
Marta

ADD NEW API error

when i add new api and click save ,i have a error message "Invalid user field" ,how can i do ?thank you !

ossec-awscloudtrail issue

This is in continuation with the #11 . As mentioned already,

I too have got the same problem as others on #11. Even after using the new rules/decoders I am still stuck with "Unknown problem somewhere in the system". The amazon decoder is working but rule is being satisfied. For e.g. my logs had events of creating users and although the rule "80861" should have been triggered, it only fires rule "1002".
Can you help here please, @jlruizmlg .

Directives - Menu. Error. Could not locate that index-pattern

hi:
in the Wazuh page top show "Directives - Menu. Error. Could not locate that index-pattern (id: f1175040-d5c5-11e7-8ef5-a5944cf52264), click here to re-create it"
but i click to recreate, it's don't work ,in the same time , in the Discover page filter "wazuh-alert-3.x-*" show "No results found"

please tell me how to fix it ,thanks~~

template_file.json not found

In the ElasticSearch section of the Install ElasticSearch with RPM Guide, step 3 includes a request for template_file.json:

$ curl https://raw.githubusercontent.com/wazuh/wazuh-kibana-app/master/server/startup/integration_files/template_file.json | curl -XPUT 'http://localhost:9200/_template/wazuh' -H 'Content-Type: application/json' -d @-
The initial curl command returns a 404, and I can't find a matching file anywhere in the Wazuh repo.

File integrity monitoring

Hi guys :)
With your help I correctly added the new agent. Now, via Wazuh agent manager in windows I have added the folder to monitor like follow:
<syscheck> [...] <!-- My test. --> <directories check_all="yes" realtime="yes" report_changes="yes" alert_new_files="yes">/test</directories></syscheck>

But when I create a new file in that directory no logs appears in wazuh-alert index.

Many thanks

Syscollector documentation

Add the documentation related to the Syscollector module, including the new scans available, as well as the information retrieved for each scan and Operating System.

Update HTTP links to HTTPS where possible

Hello team,

We still have some HTTP links in our documentation articles. We should review and update them to HTTPS if it's possible and if it works.

Regards,
Juanjo

Write new documentation for the Wazuh app

We finished the first stage of Wazuh app documentation. We still need to write more articles, so the community can have more information about how to use the app.

Tasks:

  • Write an article with the package list for the Wazuh App.
  • Write an article to fully customize the Wazuh alerts to use a completely different template and pattern.
  • Write an article for the config.yml file, describing the current parameters, checks, extensions, what it does, etc. Everything related to the configuration since this file will be more complex in the future.
  • Write the troubleshooting guide, collecting all the solutions we've provided to the users on the mailing lists and writing them in an article.
  • Articles for installation, extensions, X-Pack, adding an API, etc.
  • Minor enhancements for currently existing Wazuh app documentation articles.
  • Write a new documentation section with common Wazuh App problems and their best possible solutions. Collect all the notes from helping on the mailing lists and elaborate a collaborative document.

Regards,
Juanjo

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.