theDocumentId => 1340090 NeuVector Releases Results of 2021 Container ...

Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security

12:45 PM
Dark Reading
Dark Reading
Products and Releases

NeuVector Releases Results of 2021 Container Security Survey

While enterprise DevOps say that security is a priority, they also report a lack of consensus over whose responsibility security is, how to enact it, and how to ensure it doesn't hamper CI/CD velocity.

SAN JOSE, Calif. – February 2, 2021 – NeuVector, the leader in Full Lifecycle Container Security, today announced the results of its 2021 Container Security Survey. The report, available for download here, identifies current trends and challenges enterprises are grappling with as they increasingly turn to microservices architectures.

NeuVector surveyed 156 enterprise DevOps professionals at the most recent KubeCon North America. Among respondents, 80% currently manage active container deployments and 87% are planning new container deployments over the next 6-12 months. Close to 90% of respondents utilize Kubernetes for container orchestration, and the majority name Jenkins their primary CI/CD pipeline automation tool (GitLab is second most-popular, with no other tool garnering more than 10%). When it comes to the role that security plays as more enterprises shift left to protect applications from the beginning of development, implement DevOps processes and cultures, and accelerate workflow productivity, 76% of respondents report that container security is a clear priority at their organization. However, questions over container security responsibilities within enterprises, how to balance security with performance, and how to respond to security incidents are far from settled.

2021 Container Security Survey Highlights

  • There is little consensus on who owns the responsibility for container security

Among respondents, 32% consider container security their organization’s single most important priority as they roll out containers and Kubernetes initiatives; another 44% report it as among their top priorities. That said, enterprises are mixed in how they are addressing security. In questions asking which team should be responsible for securing container environments and Kubernetes, respondents split their answers among security (42%), development (30%), and operations (28%) roles.

  • Nearly two-thirds of respondents would curtail security to maintain high CI/CD velocity

Somewhat contrary to respondents’ stated prioritization of security, 63% of respondents acknowledge that they would curtail or restrain security measures in order to maintain high velocity production. This risky proposition increases the potential that enterprises will face repercussions from known and unknown vulnerabilities. On a positive note, 61% of respondents do use Kubernetes Pod security and/or network security policies, and many supplement those native policies with vulnerability scanning, along with network inspection and blocking.

  • Security incident response functions used in Kubernetes environments are all over the map

To protect critical applications and data when incidents do occur, enterprises are leveraging a broad range of tools and strategies. While Layer 7 network blocking leads the way as a tactic employed by 32% of respondents, nearly as many have adopted Layer 3 and 4 network blocking, network packet capture, container process blocking, file access monitoring, or container quarantining.

  • Additional findings

Interestingly, DevOps respondents indicated a crucial need for information as they deploy Kubernetes and pursue container security measures. Two-thirds report relying on official Kubernetes documentation as their best source of information, while 41% leverage information from Kubernetes security vendors, and 39% turn to documentation from cloud vendors.

“As container security breaches continue to make headlines, we are pleased that a majority of enterprises leveraging containerized environments name security among their highest priorities,” said Fei Huang, Chief Strategy Officer at NeuVector. “At the same time, that fact that a disproportionate number of enterprises would sacrifice security for productivity is both troubling and misguided. We advise organizations to recognize security as essential to the success of their container and Kubernetes implementations, and to select security capabilities that can enable development agility while still achieving fully reliable protection.”

The full report can be accessed here:

About NeuVector

NeuVector, the leader in Full Lifecycle Container Security, delivers uncompromising end-to-end security for modern container infrastructures. NeuVector offers a cloud-native Kubernetes security platform with end-to-end vulnerability management, automated CI/CD pipeline security, and complete run-time security – including the industry’s only container firewall to block zero-day attacks and other threats. NeuVector customers include global leaders in financial services, healthcare, transportation, government and other industries. For customers in highly regulated industries, NeuVector simplifies compliance for PCI, GDPR, HIPAA, and other stringent data security mandates. NeuVector integrates with leading cloud platforms, CI/CD tools, and monitoring tools. Founded by industry veterans from Fortinet, VMware, and Trend Micro, NeuVector has developed patented behavioral learning for container security.


Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-07-26
ArchiSteamFarm is a C# application with primary purpose of idling Steam cards from multiple accounts simultaneously. Due to a bug in ASF code `POST /Api/ASF` ASF API endpoint responsible for updating global ASF config incorrectly removed `IPCPassword` from the resulting config when the caller did no...
PUBLISHED: 2021-07-26
The CheckMK management web console (versions 1.5.0 to 2.0.0) does not sanitise user input in various parameters of the WATO module. This allows an attacker to open a backdoor on the device with HTML content and interpreted by the browser (such as JavaScript or other client-side scripts), the XSS pay...
PUBLISHED: 2021-07-26
In RPCMS v1.8 and below, the "nickname" variable is not properly sanitized before being displayed on page. When the API functions are enabled, the attacker can use API to update user nickname with XSS payload and achieve stored XSS. Users who view the articles published by the injected use...
PUBLISHED: 2021-07-26
In RPCMS v1.8 and below, the "nickname" variable is not properly sanitized before being displayed on page. Attacker can use "update password" function to inject XSS payloads into nickname variable, and achieve stored XSS. Users who view the articles published by the injected user...
PUBLISHED: 2021-07-26
In RPCMS v1.8 and below, attackers can interact with API and change variable "role" to "admin" to achieve admin user registration.