---
title: "Discussion on \"Seccomp: The Syscall Firewall\" | Hashnode"
description: "Discussion on \"Seccomp: The Syscall Firewall\". How Linux Decides Which Syscalls Are Allowed to Exist"
url: "https://hashnode.com/posts/seccomp-the-syscall-firewall/69844f9bacfe231545f748c3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Seccomp: The Syscall Firewall](https://cloudsecburrito.com/seccomp-the-syscall-firewall?utm_source=hashnode&utm_medium=feed)

How Linux Decides Which Syscalls Are Allowed to Exist

Feb 5 · 10 min read · cloudsecburrito.com  
Read the article

-   [#linux](https://hashnode.com/tag/linux)
-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#seccomp](https://hashnode.com/tag/seccomp)
-   [#security](https://hashnode.com/tag/security)

## Written by

[Matt Brown](https://hashnode.com/@mattbrownsec)

@mattbrownsec · San Francisco

  
[View profile](https://hashnode.com/@mattbrownsec)

From policy to runtime: open source security in the real world.

Working as a solutions architect while going deep on Kubernetes security — prevention-first thinking, open source tooling, and a daily rabbit hole of hands-on learning. I make the mistakes, then figure out how to fix them (eventually).

## Responses

Markdown supported · ⌘↵ to post

No responses yet.