<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Seccomp on Linux Security</title><link>https://linuxtransfer.com/tags/seccomp/</link><description>Recent content in Seccomp on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 25 Mar 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/seccomp/index.xml" rel="self" type="application/rss+xml"/><item><title>Seccomp</title><link>https://linuxtransfer.com/post/seccomp/</link><pubDate>Sat, 25 Mar 2023 00:00:00 +0000</pubDate><guid>https://linuxtransfer.com/post/seccomp/</guid><description>&lt;h3 id="introduction-understanding-seccomp">Introduction: Understanding Seccomp&lt;/h3>
&lt;p>Seccomp is a Linux kernel feature that enables administrators to restrict the actions that a process can perform, thus providing an additional layer of security. It stands for &amp;ldquo;secure computing mode&amp;rdquo; and was first introduced in the 2.6.12 kernel. Seccomp is a powerful tool for enhancing the security of a Linux system, as it helps to mitigate the risks of exploitation from untrusted code and malware.&lt;/p>
&lt;h3 id="how-seccomp-works">How Seccomp Works&lt;/h3>
&lt;p>Seccomp works by limiting the system calls that a process can make. It does this by providing a list of allowed system calls that a process can make, and any system call not on this list is blocked. This list is often referred to as a &amp;ldquo;filter.&amp;rdquo; Seccomp operates in two modes: strict mode and filter mode. In strict mode, all system calls except for a whitelist of explicitly allowed ones are blocked. In filter mode, only the system calls explicitly listed in the filter are allowed, with all others being blocked.&lt;/p></description></item></channel></rss>