IBM attempts to graft virtual machine security onto container flexibility

Nabla Containers promises reduced attack surface through fewer system calls

IBM researchers have developed a new flavor of software container in an effort to create code that's more secure than Docker and similar shared kernel container systems.

Docker and its ilk are considered less secure than VMs because the compromise of a shared kernel puts all associated containers at risk. With VMs, the kernel is separate from the host kernel, which reduces the risk of collateral damage.

Large businesses, appreciating the benefits of containerization, have shown interest in adopting the technology but many balk at trading security for development and deployment speed.

Thus tech companies interested in serving the enterprise market have been looking at ways to address the security shortcomings of containers.

Toward that end, the OpenStack Foundation recently released the 1.0 version of the Intel-backed Kata Containers, an attempt to combine the security of VMs with the speed of containers. And Google has discussed its approach, gVisor.

Now it's IBM's turn with software dubbed Nabla Containers.

Nabla Containers and Kata Containers both aim to reduce potential avenues of attack. The Kata Container approach does so by giving each container or pod its own lightweight VM and mini-kernel.

Cat sleeps on laptop

Azure Dev Spaces has hit public preview, so El Reg took it for a spin


The Nabla Containers approach differs: It makes fewer Linux system calls by relying on unikernel (library operating systems) techniques in conjunction with the Solo 5 middleware.

"Nabla Containers only use 9 system calls, all others are blocked via a Linux seccomp policy," the project website explains.

The net effect is less communication with the kernel and less surface area to attack.

Google claims gVisor also attempts to overcome the shortcomings of containers by rewriting the Linux system call interface in Go.

But James Bottomley, a distinguished engineer at IBM Research and a Linux kernel contributor contends Google's engineers failed to account for the profligacy of system calls in the Go runtime, making it comparable to Docker or worse in terms of number of system calls.

In a series of recent blog posts, Bottomley describes Nabla Containers as an attempt to reduce horizontal threats, by which a containment failure allows an attacker to access the underlying container host or other tenant virtual machines on that host.

In tests he describes, "Nabla is far and away the best containment technology for secure workloads given that it sacrifices the least performance over docker to achieve the containment and, on the published results, is 2x more secure even than using hypervisor based containment."

Your mileage may vary, unless you happen to be using gVisor. According Bottomley, "gVisor sucks because ptrace is a really inefficient way of connecting the syscalls to the sandbox." ®

Similar topics

Other stories you might like

  • Prisons transcribe private phone calls with inmates using speech-to-text AI

    Plus: A drug designed by machine learning algorithms to treat liver disease reaches human clinical trials and more

    In brief Prisons around the US are installing AI speech-to-text models to automatically transcribe conversations with inmates during their phone calls.

    A series of contracts and emails from eight different states revealed how Verus, an AI application developed by LEO Technologies and based on a speech-to-text system offered by Amazon, was used to eavesdrop on prisoners’ phone calls.

    In a sales pitch, LEO’s CEO James Sexton told officials working for a jail in Cook County, Illinois, that one of its customers in Calhoun County, Alabama, uses the software to protect prisons from getting sued, according to an investigation by the Thomson Reuters Foundation.

    Continue reading
  • Battlefield 2042: Please don't be the death knell of the franchise, please don't be the death knell of the franchise

    Another terrible launch, but DICE is already working on improvements

    The RPG Greetings, traveller, and welcome back to The Register Plays Games, our monthly gaming column. Since the last edition on New World, we hit level cap and the "endgame". Around this time, item duping exploits became rife and every attempt Amazon Games made to fix it just broke something else. The post-level 60 "watermark" system for gear drops is also infuriating and tedious, but not something we were able to address in the column. So bear these things in mind if you were ever tempted. On that note, it's time to look at another newly released shit show – Battlefield 2042.

    I wanted to love Battlefield 2042, I really did. After the bum note of the first-person shooter (FPS) franchise's return to Second World War theatres with Battlefield V (2018), I stupidly assumed the next entry from EA-owned Swedish developer DICE would be a return to form. I was wrong.

    The multiplayer military FPS market is dominated by two forces: Activision's Call of Duty (COD) series and EA's Battlefield. Fans of each franchise are loyal to the point of zealotry with little crossover between player bases. Here's where I stand: COD jumped the shark with Modern Warfare 2 in 2009. It's flip-flopped from WW2 to present-day combat and back again, tried sci-fi, and even the Battle Royale trend with the free-to-play Call of Duty: Warzone (2020), which has been thoroughly ruined by hackers and developer inaction.

    Continue reading
  • American diplomats' iPhones reportedly compromised by NSO Group intrusion software

    Reuters claims nine State Department employees outside the US had their devices hacked

    The Apple iPhones of at least nine US State Department officials were compromised by an unidentified entity using NSO Group's Pegasus spyware, according to a report published Friday by Reuters.

    NSO Group in an email to The Register said it has blocked an unnamed customers' access to its system upon receiving an inquiry about the incident but has yet to confirm whether its software was involved.

    "Once the inquiry was received, and before any investigation under our compliance policy, we have decided to immediately terminate relevant customers’ access to the system, due to the severity of the allegations," an NSO spokesperson told The Register in an email. "To this point, we haven’t received any information nor the phone numbers, nor any indication that NSO’s tools were used in this case."

    Continue reading

Biting the hand that feeds IT © 1998–2021