Landlock Rulesets with Nono Profiles - Paranoid Level Sandboxing #3
Source: YouTube · Data Lab Tech · published Aug 4, 2026 · 26:05
This video provides a practical introduction to configuring Landlock rule sets using the Nonono CLI to sandbox a containerized AI development environment called "great," covering profile composition, network whitelisting, GPU access, and debugging techniques 0:00.
Key Takeaways:
• The project uses custom composable profiles—such as base, GPU, and C development tool profiles—that extend a default profile and are rendered at runtime by a wrapper script 0:44.
• Network access is restricted using a whitelist (e.g., Hugging Face, GitHub, OpenRouter domains) that gets injected into the profile's network.allow.domain rules during the image build 1:28.
• The base profile grants read/write access to specific directories like /workspace and /models, read access to SSL certificates, and controls internal ports (using open-port for bidirectional and listen-port for external-only traffic) 5:01.
• GPU support requires explicitly allowing access to specific PCI device paths and CUDA library files, with the presenter noting these paths should ideally be detected dynamically rather than hardcoded 9:01.
• Debugging missing permissions involves removing the no-diagnostics flag from the Nonono wrapper, which enables interactive output showing exactly which file or device accesses were denied 10:42.
Nonono leverages the Linux Landlock kernel API for filesystem and network sandboxing, offering a lightweight security layer that can complement or even replace traditional container isolation 24:42.
Sources:
- 0:00 Introduction to Landlock rule sets and Nonono basics
- 0:44 Explanation of custom composable profiles and how they extend the base profile
- 1:28 Reviewing the network domain whitelist configuration
- 5:01 Filesystem permissions and network port control (
open-portvslisten-port) - 9:01 GPU profile details including hardcoded PCI device and CUDA library paths
- 10:42 Debugging denied permissions by toggling the
no-diagnosticsflag - 24:42 Comparison of Nonono to container isolation and mention of kernel API support
Generate CPE Credits
Generate a professional CPE document from this video's transcript.
Estimated credit: 0.5 CPE hours
Estimate uses the video runtime (1 hour ≈ 1 CPE, rounded to the nearest 0.5, minimum 0.5, maximum 2.0). The final amount can be lower after review, never higher.
Topic: Cybersecurity. Commonly maps to: Security and Risk Management, Security Operations. Exact CISSP domains are assigned during generation.
Free account. One generation at a time, with a daily limit.
CPEBuddy is independent and not affiliated with or endorsed by ISC2, ISACA, or any certification body. Exports are formatted for common CPE submissions; acceptance is at your certification body's discretion.
Transcript Preview
First 800 characters of the transcript
So today we're going to talk about uh landlock rule sets. Uh how to use no no to set this up. Uh and I'm going to cover pretty much just the basics of no no and show you how we use no no uh with great on great to implement this uh create several profiles that we extend uh the base profile from. uh and you'll pretty much learn how to use the command line to test uh some permission. You'll learn about diagnostics uh how to disable them for production uh and some few other details. Okay, let's get into it. So, we're going to talk about uh how we use no no uh in great. So uh we use what we call custom composible profiles which pretty much means that we've got a bunch of tiny profiles for GPU uh support for uh supporting C development tools. Uh and then we use this to extend the basic uh great …