- Set up Kibana to work with Elastic Stack security features.
- .
You can configure the following settings in the kibana.yml
file.
General settings
Action settings
xpack.actions.whitelistedHosts
| A list of hostnames that Kibana is allowed to connect to when built-in actions are triggered. It defaults to [] , allowing any host, but keep in mind the potential for SSRF attacks when hosts are not explicitly whitelisted. An empty list can be used to block built-in actions from making any external connections.
Note that hosts associated with built-in actions, such as Slack and PagerDuty, are not automatically whitelisted. If you are not using the default [ ] setting, you must ensure that the corresponding endpoints are whitelisted as well. |
| A list of action types that are enabled. It defaults to [*] , enabling all types. The names for built-in Kibana action types are prefixed with a . and include: , .slack , .email , .index , .pagerduty , and .webhook . An empty list will disable all action types.
Disabled action types will not appear as an option when creating new connectors, but existing connectors and actions of that type will remain in Kibana and will not function. |
Alert settings
You do not need to configure any additional settings to use alerting in Kibana.