Issue: Insecure web application programming or configuration
FIX: Configure "Content-Security-Policy" header with secure policies
Configure "X-Content-Type-Options" header with "nosniff" value
Config your server to use the "X-XSS-Protection" header with value '1'
I've tried setting csp policy and but it didn't fix the issues.Any suggestions on this??
You can configure Kibana to send custom response headers by specifying server.customResponseReaders in your kibana.yml (example here: Format of kibana server.customResponseHeaders)
Kibana ships with its own set of CSP rules, which it should be sending to the browser on its own already.
The built-in CSP is still pretty unrestrictive, so it is possible that an automated security scanner is still finding issues with the policy that's in place. We are actively working on locking down the policy further, but this takes time, as Kibana uses a lot of libraries that themselves rely on permissive CSP policies.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.