Redirectiong NeuVector notification events

This document (000020937) is provided subject to the disclaimer at the end of this document.

Resolution

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, so they each are limited to 4K.

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.

Alternatives

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.

If your cluster already has a logging management solution to scrap logs. For Kubernetes environments, the following open-source fluentbit helm chart can easily be modified received the NeuVector logs and scrap by your logging management solution. Change the following values.yaml.

Default Values

enableAzurePlugin: true
enableStandardOutput: false

New Values

enableAzurePlugin: false
enableStandardOutput: true

Configure NeuVector under Settings > Configuration > Syslog

Server: fluentbit
Protocol: TCP
Port: 5140

Disclaimer

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.