Redirectiong NeuVector notification events
This document (000020937) is provided subject to the disclaimer at the end of this document.
NeuVector notification events can be viewed through the WebUi/Console under Notifications. These are stored in memory with a rolling limit of 4K per sub-type. There are three major types: Security events (which include three sub-types: violation, threats, and incidents), Risk reports, and Events. Risk reports and Events don't have any sub-types.
It is best practice to forward these events to a SIEM system for long-term storage and analysis. The Syslog feature under Settings > Configuration > Syslog allows forwarding these events with various configurable options. (See the below screenshot of configurable options.)
For actionable events, Response rules can be configured to forward the event using webhook. See the documentation for more details on how to setup Response rules.
Often times there may be a logging management solution in place to scrap logs. For Kubernetes environments, the following open source fluentbit helm chart can easily be modify to accomplish this. Simply change the following values.yaml and point NeuVector Syslog Server to the fluentbit setup. (See above screenshot for default parameter values.)
enableAzurePlugin: true enableStandardOutput: false
enableAzurePlugin: false enableStandardOutput: true
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020937
- Creation Date: 18-Jan-2023
- Modified Date:18-Jan-2023
- SUSE NeuVector
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com