seccomp
A secure computing mode provided by the Linux kernel that filters the system calls a process may execute. It is often combined with namespaces and cgroups to achieve operating-system-level sandbox isolation.
Core Facts
Timeline (last 90 days)
Classic implementations of runtime enforcement include Linux's seccomp, SELinux's mandatory access control (MAC), and runtime application self-protection (RASP) in web applications.
Linux security modules such as seccomp and AppArmor can further tighten permissions at the system call level.
Common OS sandbox implementation approaches include Linux namespaces and cgroups, seccomp, chroot, as well as Python-level subprocess privilege reduction and tools such as firejail.
Codex uses OS-level sandboxing: Seatbelt on macOS, seccomp on Linux, and native sandbox or WSL on Windows.
Security hardening measures for Agent sandboxes include running as a non-root user, mounting read-only file systems, disabling the network or restricting egress IP whitelists, setting execution timeouts, and using seccomp to filter dangerous system calls.
On Linux, Agent sandboxing is typically implemented through kernel mechanisms such as namespaces, cgroups, and seccomp.
Linux has more than 300 system calls, and most containers only need about 50 of them.
Common sandbox implementations include Docker containers, WebAssembly (Wasm) runtimes, and OS-level seccomp and AppArmor policies.
将推理引擎运行在严格隔离的沙箱环境中（容器隔离、seccomp、最小权限）是防御此类威胁的直接方案
将推理引擎运行在严格隔离的沙箱环境中，结合容器隔离、seccomp和最小权限运行，可在引擎被攻破时限制攻击者控制宿主机
2 more timeline events
All Facts (13)
seccomp is a system call filtering mechanism provided by the Linux kernel, and the seccomp-bpf extension allows fine-grained inspection of system call parameters using BPF programs.
65%UnverifiedClassic implementations of runtime enforcement include Linux's seccomp, SELinux's mandatory access control (MAC), and runtime application self-protection (RASP) in web applications.
50%UnverifiedLinux security modules such as seccomp and AppArmor can further tighten permissions at the system call level.
50%UnverifiedCommon OS sandbox implementation approaches include Linux namespaces and cgroups, seccomp, chroot, as well as Python-level subprocess privilege reduction and tools such as firejail.
50%UnverifiedCodex uses OS-level sandboxing: Seatbelt on macOS, seccomp on Linux, and native sandbox or WSL on Windows.
50%UnverifiedSecurity hardening measures for Agent sandboxes include running as a non-root user, mounting read-only file systems, disabling the network or restricting egress IP whitelists, setting execution timeouts, and using seccomp to filter dangerous system calls.
50%UnverifiedOn Linux, Agent sandboxing is typically implemented through kernel mechanisms such as namespaces, cgroups, and seccomp.
50%UnverifiedLinux has more than 300 system calls, and most containers only need about 50 of them.
50%UnverifiedCommon sandbox implementations include Docker containers, WebAssembly (Wasm) runtimes, and OS-level seccomp and AppArmor policies.
50%Unverified将推理引擎运行在严格隔离的沙箱环境中（容器隔离、seccomp、最小权限）是防御此类威胁的直接方案
50%Unverifiedseccomp是Linux内核提供的安全机制，允许进程声明只使用哪些系统调用，内核会拒绝所有未声明的系统调用
50%Unverified将推理引擎运行在严格隔离的沙箱环境中，结合容器隔离、seccomp和最小权限运行，可在引擎被攻破时限制攻击者控制宿主机
50%UnverifiedAgent执行沙箱主流实现分为进程级隔离（seccomp、namespace）、容器级隔离（Docker、gVisor）、虚拟机级隔离（Firecracker、Kata Containers）三个层次
50%