Item: SUSE NeuVector
Rating: 10
Author: Edgars Voroboks

Overall Satisfaction with SUSE NeuVector

Use Cases and Deployment Scope

We use SUSE NeuVector:
1) as a Kubernetes firewall to allow containers internal and external network connections which are necessary and block all other connections;
2) to scan our containers for known software vulnerabilities.

In the near future, we also plan to turn on command execution prevention to allow only whitelisted commands in certain containers.

Pros and Cons

Pros

Scans containers software for known vulnerabilities
Denies command execution in containers
Prevents unwanted network connections from/to containers

Cons

I like everything about NeuVector. They are on the right development path.

Most Important Features

Ability to control network connections
Container software vulnerability scanner
Container registry vulnerability scanner

Return on Investment

We went from being blind to what happens in the Kubernetes network to seeing everything and being able to control Kubernetes network communications.
Now we are able to detect vulnerable containers faster.

Alternatives Considered

Sysdig Secure

SUSE NeuVector is deployed on your Kubernetes, and data does not leave your data center. Sysdig is a cloud platform - you have no full control over what happens with your data. Also, SUSE NeuVector has a capability to prevent specific command execution ir containers, but Sysdig does not have such ability. Sysdig is not an open-source solution, but SUSE NeuVector is.

Key Insights

Do you think SUSE NeuVector delivers good value for the price?

Yes

Are you happy with SUSE NeuVector's feature set?

Yes

Did SUSE NeuVector live up to sales and marketing promises?

Yes

Did implementation of SUSE NeuVector go as expected?

Yes

Would you buy SUSE NeuVector again?

Yes

Other Software Used

Oracle Linux, SUSE Rancher, Microsoft Visual Studio Code

Likelihood to Recommend

SUSE NeuVector is exceptional when you want to make your Kubernetes cluster secure. You can limit network connections, scan containers, container registries and Kubernetes nodes for vulnerable software, forbid running specific commands on certain or all containers. You can enable security for individual containers - when SUSE NeuVector has learned container specifics. That's why you can deploy SUSE NeuVector on production Kubernetes clusters where you are already running conteiners - it will not break anything.

Comments

Please log in to join the conversation

SUSE NeuVector makes your Kubernetes secure