<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Enforcement on Tetragon - eBPF-based Security Observability and Runtime Enforcement</title>
    <link>/docs/concepts/enforcement/</link>
    <description>Recent content in Enforcement on Tetragon - eBPF-based Security Observability and Runtime Enforcement</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="/docs/concepts/enforcement/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Persistent enforcement</title>
      <link>/docs/concepts/enforcement/persistent-enforcement/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/concepts/enforcement/persistent-enforcement/</guid>
      <description>This page shows you how to configure persistent enforcement.&#xA;Concept The idea of persistent enforcement is to allow the enforcement policy to continue running even when its tetragon process is gone.&#xA;This is configured with the --keep-sensors-on-exit option.&#xA;When the tetragon process exits, the policy stays active because it&amp;rsquo;s pinned in sysfs bpf tree under /sys/fs/bpf/tetragon directory.&#xA;When a new tetragon process is started, it performs the following actions:&#xA;checks if there&amp;rsquo;s existing /sys/fs/bpf/tetragon and moves it to /sys/fs/bpf/tetragon_old directory; sets up configured policy; removes /sys/fs/bpf/tetragon_old directory.</description>
    </item>
  </channel>
</rss>
