




Jan 26 10:17:11 enterprise-security kibana: {"type":"response","@timestamp":"2021-01-26T10:17:11Z","tags":["access:console"],"pid":30859,"method":"post","statusCode":200,"req":{"url":"/api/console/proxy?path=_mapping&method=GET","method":"post","headers":{"host”:”xxxxxxxx:5601","connection":"keep-alive","content-length":"0","accept":"text/plain, */*; q=0.01","kbn-version":"7.6.2","user-agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36","origin":"http://xxxxxxx:5601","referer":"http://xxxxxxx:5601/app/kibana","accept-encoding":"gzip, deflate","accept-language":"en-GB,en-US;q=0.9,en;q=0.8"},"remoteAddress”:”xxxxxxxxx”,”userAgent”:”xxxxxxx”,”referer":"http://xxxxxxx:5601/app/kibana"},"res":{"statusCode":200,"responseTime":298,"contentLength":9},"message":"POST /api/console/proxy?path=_mapping&method=GET 200 298ms - 9.0B"}
[root@enterprise-security ~]#
No error/warn logs in the Elastic Stack log files:

Regards,
Aneesh Sharma
GET /_security/user/_has_privileges
______________________________________________________________________
Confidentiality Notice: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it from your computer. Thank you.
______________________________________________________________________
--
You received this message because you are subscribed to the Google Groups "Wazuh mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wazuh+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wazuh/74986140-ecbc-4968-a5c3-dc142674404fn%40googlegroups.com.

This is done by xpack security feature in Elastic Stack.
xpack.security.enabled: true
2. Restart Elasticsearch and wait for the service to be ready.
systemctl restart elasticsearch
3. Generate credentials for all the Elastic Stack pre-built roles and users.
/usr/share/elasticsearch/bin/elasticsearch-setup-passwords auto
4. Note down the passwords generated from above command.
5. Setting up credentials for Filebeat. Add the next two lines to /etc/filebeat/filebeat.yml
elasticsearch.username: "elastic"
elasticsearch.password: "password_generated_for_elastic"
6. Restart Filebeat.
systemctl restart filebeat
7. Setting up credentials for Kibana. Add the next lines to /etc/kibana/kibana.yml
xpack.security.enabled: true
elasticsearch.username: "elastic"
elasticsearch.password: "password_generated_for_elastic"
8. Restart Kibana.
systemctl restart kibana
9. Open the file at /etc/logstash/conf.d/01-wazuh.conf and add the elastic user credentials on the output section as follows:
output {
elasticsearch {
hosts => ["localhost:9200"]
index => "wazuh-alerts-3.x-%{+YYYY.MM.dd}"
document_type => "wazuh"
user => "elastic"
password => "<elastic_password>"
}
}
systemctl restart logstash
----> I did not had this /etc/logstash/conf.d/01-wazuh.conf mentioned in Step 9 so I enabled logstash and then performed Step 9.


To view this discussion on the web visit https://groups.google.com/d/msgid/wazuh/75587ab2-d581-40ec-a31d-db9ed8b4929cn%40googlegroups.com.