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.

Cloud

12/7/2018
03:45 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

'Simplify Everything': Google Talks Container Security in 2019

Google Cloud's container security lead shares predictions, best practices, and what's top of mind for customers.

Security is top of mind for Google's container customers, with many worried about configuration and other protective measures as they strengthen cloud protection for 2019.

"A lot of configuration and best practice/hardening type questions are coming in," said Maya Kaczorowski, Google product manager for container security, in a roundtable focused on container trends and practices. Most concerns relate to infrastructure, software supply chain, and runtime security, she explained, pointing to common customer questions.

"Users are worried about what's ending up in their environments," Kaczorowski continued. But that's no reason to shy away from containers. "You can have a different security model for containers, and arguably a better security model," she added, if the right steps are taken.

Containers are short-lived and frequently deployed, she explained, meaning you can constantly apply patches and updates without having to worry about downtime. Containers are "meant to be immutable" and should not change when deployed, meaning alterations can be red flags.

"When a container does change, it means something has potentially gone wrong," Kaczorowski said. "A modified container is a built-in security alert." Businesses are growing worried about the security implications of utilizing containers and risks around the software supply chain.

Many users are asking about whether their container images are secure to build and deploy. They want to know how they can ensure their container images are free of vulnerabilities, and how they can ensure images they built aren't changed before they are deployed, she added.

They're also worried about runtime security. Common customer questions relate to protecting and isolating workloads and securely scaling container deployments. Sophisticated users are curious about how they can identify when containers are acting maliciously, said Kaczorowski.

Looking ahead to the new year, she said simplification will be a major trend. Now, the burden on users to get Kubernetes up and running "is quite high," she added. With open source this can be a struggle for users to do themselves, so she anticipates containers building in better default settings to make the process easier for them.

Kaczorowski also expects an increase in container-specific attacks in 2019. Right now, much of the threats targeting containers are drive-by attacks, which scan for known vulnerabilities and run automatic scripts so they can see what's going on.

Attackers who do this "probably don't even realize they're attacking a containerized environment and they probably don't care," she noted. In the future, actors will specifically scan for Kubernetes vulnerabilities to target their victims' cloud environments.

And Kubernetes flaws are proving a problem recently: deployments around the world are showing vulnerabilities, and research shows hundreds of installations have been hijacked for cryptomining. The first major Kubernetes vulnerability was disclosed earlier this week.

Locking Down Container Security

Kaczorowski elaborated on best security practices Google has adopted in years of launching four billion containers each week: encryption by default, automatic upgrades and security patches, and native integrations with identity and access management, Cloud Audit Logging, and Cloud Security Command Center.

For software supply chain security, she recommended container registry vulnerability scanning, which does automatic scans of images and packages for known CVEs, as well as binary authorization. Container infrastructure security measures include private IPs for users' nodes and restricted IP access to masters. Auto-upgrade for nodes ensures the latest security updates.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.