On Monday, February 11, Docker released an update to fix a privilege escalation vulnerability (CVE-2019-5736) in runC, the Open Container Initiative (OCI) runtime specification used in Docker Engine and containerd. This vulnerability makes it possible for a malicious actor that has created a specially-crafted container image to gain administrative privileges on the host. Docker engineering worked with runC maintainers on the OCI to issue a patch for this vulnerability.
Docker recommends immediately applying the update to avoid any potential security threats. For Docker Engine-Community, this means updating to 18.09.2 or 18.06.2. For Docker Engine- Enterprise, this means updating to 18.09.2, 18.03.1-ee-6, or 17.06.2-ee-19. Read the release notes before applying the update due to specific instructions for Ubuntu and RHEL operating systems.
Summary of the Docker Engine versions that address the vulnerability:
Docker Engine Community |
Docker Engine Enterprise |
18.09.2 |
18.09.2 |
18.06.2 |
18.03.1-ee-6 |
|
17.06.2-ee-19 |
To better protect the container images run by Docker Engine, here are some additional recommendations and best practices:
Official Images are a curated set of Docker repositories hosted on Docker Hub that are designed to:
Orange claims the largest enterprise SD-WAN deployment in the world rolling out more than 1,500...
The flaw basically allows an infected container to gain control of the overarching host container...
Yasir Liaqatullah, Vice President of Product Management at A10 Networks, discusses new attack...
The new security tool it built analyzes data across 150 sources. It then uses machine learning to...
The investment is further validation that microsegmentation is real, and Illumio CEO Andrew Rubin...
The president’s commitment comes as his top cybersecurity chief warns that China could use Huawei’s 5G networking equipment to steal “trillions” of dollars of intellectual property.
Cloudflare Access secures your internal sites by adding authentication. When a request is made to a site behind Access, Cloudflare asks the visitor to login with your identity provider. With service tokens, you can now extend that same level of access control by giving credentials to automated tools, scripts, and bots.
When users attempt to reach a site behind Access, Cloudflare looks for a JSON Web Token (a JWT) to determine if that visitor is allowed to reach that URL. If user does not have a JWT, we redirect them to the identity provider configured for your account. When they login successfully, we generate the JWT.
When you create an Access service token, Cloudflare generates a unique Client ID and Secret scoped to that service. When your bot sends a request with those credentials as headers, we validate them ourselves instead of redirecting to your identity provider. Access creates a JWT for that service and the bot can use that to reach your application.
Within the Access tab of the Cloudflare dashboard, you’ll find a new section: Service Tokens. To get started, select “Generate a New Service Token.”
You’ll be asked to Continue reading
A while ago we published a guest blog post by Christoph Jaggi explaining the high-level security challenges of most SD-WAN solutions… but what about the low-level details?
Sergey Gordeychik dived deep into implementation details of SD-WAN security in his 35C3 talk (slides, video).
TL&DW: some of the SD-WAN boxes are as secure as $19.99 Chinese webcam you bought on eBay.
Read more ... Huawei and ZTE's list of woes continue as Germany, Canada, Poland, and the U.S. all appear to be working to impose new bans.
The cloud giant wants the rest of the industry to get behind its open source confidential computing framework. And it launched a $15K challenge to accelerate this technology.
This approach provides a granular level of security control by matching functionality to specific use cases and business requirements.
CEO Tim Eades won’t comment on his company’s valuation. But he says the investment puts it on track for an IPO and profitability within the next 12 to 18 months.
The SWIFT Controls Framework was created to help customers figure out which controls are needed to better secure their SWIFT environment. The SWIFT security controls framework is broken down into objectives, principles, and controls. The three objectives are “Secure your environment, Know and Limit Access, and Detect and Respond”.
Customers interested in exploring VMware product alignment with the SWIFT framework should evaluate the end-to-end solution. This includes VMware products, as well as other technology that support a customer’s SWIFT platform. The following is a high-level alignment of some of the SWIFT framework controls and VMware products.
As part of a SWIFT deployment, a secured and zoned off environment must be created. This zone contains the SWIFT infrastructure that is used for all SWIFT transaction. Two SWIFT Principles that we will discuss are
These controls are required to be enforced on the SWIFT infrastructure. SWIFT requires that all traffic from the general IT infrastructure to the SWIFT zone be as restricted as possible. They also Continue reading
Versa has now signed managed service provider agreements with more than 80 global providers.
It’s a smart move for the networking vendor. Gartner estimates that 20.4 billion connected things will be in use by organizations worldwide by 2020.
The company expanded data protection with new and enhanced features to its Data Domain and Integrated Data Protection Appliance (IDPA) products.
Cloudflare seeks to help its end customers use whichever public and private clouds best suit their needs. Towards that goal, we have been working to make sure our solutions work well with various public cloud providers including Microsoft’s Azure platform.
If you are an Azure customer, or thinking about becoming one, here are three ways we have made Cloudflare’s performance and security services work well with Azure.
We are proud to announce an application for Cloudflare Argo Tunnel within the Azure marketplace. As a quick reminder, Argo Tunnel establishes an encrypted connection between the origin and the Cloudflare edge. The small tunnel daemon establishes outbound connections to the two nearest Cloudflare PoPs, and the origin is only accessible via the tunnel between Cloudflare and origin.
Because these are outbound connections, there is likely no need to modify firewall rules, configure DNS records, etc. You can even go so far as to block all IPs on the origin and allow traffic only to flow through the tunnel. You can learn more here. The only prerequisite for using Argo Tunnel is to have Argo enabled on your Cloudflare zone. You can Continue reading
Netsurion’s BranchSDO platform is the company’s natural evolution of its SD-WAN service. “What’s next for SD-WAN is really removing the handcuffs off of the branch and allowing this resilient, agile security solution that also delivers compliance,” said John Ayers, VP of product at...