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.

Black Hat Asia
May 10-13, 2022
Hybrid/Marina Bay Sands, Singapore
Black Hat USA
August 6-11, 2022
Las Vegas, NV, USA
Black Hat Europe
December 5-8, 2022
London
End of Bibblio RCM includes -->
11/5/2018
12:00 PM
Hari Srinivasan, Director of Product Management, Qualys
Hari Srinivasan, Director of Product Management, Qualys
Event Updates

Build Security into Container Deployment

Container adoption has skyrocketed, and with it the importance of securing the applications that DevOps teams create and deploy using this method of OS virtualization.

Container adoption has skyrocketed, and with it the importance of securing the applications that DevOps teams create and deploy using this method of OS virtualization.

The protection that security teams provide must be comprehensive across the container lifecycle, and built seamlessly and unobtrusively into the DevOps pipeline.

Accomplishing this requires understanding Docker container technology, and adopting processes and tools tailored for these environments.

Container security challenges

Containers qualities that developers find attractive, such as packaging an application and its dependencies without a guest OS, also create create security and compliance issues.

These challenges include developers’ use of software from public repositories, which often has vulnerabilities, and their deployment of weakly-configured containers.

In addition, containers communicate directly with each other via exposed network ports bypassing host controls, and their ephemeral nature makes them hard to track.

Protecting the container pipeline

All phases of container deployment have to be secured -- build, ship and runtime. Let’s look at them in detail.

Build

In this phase, the goal is blocking vulnerable images from your organization’s repositories, especially images pulled from a public repository.

To keep unsafe images out, you should leverage REST APIs or native plug-ins, so that security checks can automatically run within your DevOps team’s CI/CD tools.

These integrations will also let security teams give developers access to security tools. That way, developers can perform security functions from CI/CD tools without involving security teams.

Ship

In this phase, you should make sure that images in your repositories are checked for vulnerabilities. Registries and repositories should be inventoried. As images are added, scan them for vulnerabilities.

Also check that your organization’s images come from reputable sources that keep images current and scrubbed of vulnerabilities. Using notary services can help ensure only trusted images are used in your environment.

Runtime

With the container images now on your registry and available for production use, it’s critical to have visibility and continuous monitoring of runtime environments, as well as the ability to prevent and respond to breaches.

Security teams must detect rogue, vulnerable containers, identify where they are, and assess their potential impact based on how widespread they are in your environment.

A key here is to flag containers already running on the system that are breaking off from the “immutable” behavior of their parent image, which could indicate a breach.

After identifying rogue containers, your security tool should allow you to enforce counter measures of blocking or quarantining, and to drill down into anomalies’ details.

An even better option: Automatically validate the image against security policies using your tool, and block unapproved images from being spun up as containers. Here you can leverage orchestrators like Kubernetes to prevent rogue containers from entering the environment via admission controllers.

Summary

We hope this article has helped you better understand the particular security challenges of containers, and how to address them throughout their lifecycle.

Comment  | 
Print  | 
More Insights
//Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
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
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
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
Video
Cartoon
Current Issue
Creating an Effective Incident Response Plan
Security teams are realizing their organizations will experience a cyber incident at some point. An effective incident response plan that takes into account their specific requirements and has been tested is critical. This issue of Tech Insights also includes: -a look at the newly signed cyber-incident law, -how organizations can apply behavioral psychology to incident response, -and an overview of the Open Cybersecurity Schema Framework.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-4202
PUBLISHED: 2022-11-29
A vulnerability, which was classified as problematic, was found in GPAC 2.1-DEV-rev490-g68064e101-master. Affected is the function lsr_translate_coords of the file laser/lsr_dec.c. The manipulation leads to integer overflow. It is possible to launch the attack remotely. The exploit has been disclose...
CVE-2022-40799
PUBLISHED: 2022-11-29
Data Integrity Failure in 'Backup Config' in D-Link DNR-322L <= 2.60B15 allows an authenticated attacker to execute OS level commands on the device.
CVE-2022-41568
PUBLISHED: 2022-11-29
LINE client for iOS before 12.17.0 might be crashed by sharing an invalid shared key of e2ee in group chat.
CVE-2022-43326
PUBLISHED: 2022-11-29
An Insecure Direct Object Reference (IDOR) vulnerability in the password reset function of Telos Alliance Omnia MPX Node 1.0.0-1.4.[*] allows attackers to arbitrarily change user and Administrator account passwords.
CVE-2022-45329
PUBLISHED: 2022-11-29
AeroCMS v0.0.1 was discovered to contain a SQL Injection vulnerability via the Search parameter. This vulnerability allows attackers to access database information.