- Rule editor with syntax highlighting, syntax validation, and policy linting
- Trust database manager to synchronize what fapolicyd believes and what exists on disk
- Log analyzer provides insight to help understand and tune fapolicyd runtime behavior
- Disk access profiler to capture file access requests for an executing application
- Configuration file editor for fapolicyd, with syntax validation and linting
- DBUS based control of the fapolicyd daemon which is immune to bad policy lockout
See the User Guide for details.
You can install the Policy Analyzer in one of the following ways
From Fedora Packages
This installation method is currently available for Fedora EPEL 8, EPEL 9, and Fedora 37 or later, including Rawhide.
dnf install fapolicy-analyzerFrom GitHub releases
You can install the Policy Analyzer through the installers available in
the latest release.
Choose an RPM from the latest Fedora stable, Rawhide, and EPEL builds.
From Fedora Copr
The Copr repository contains the latest development builds and release builds prior to publishing to the Fedora repositories.
Follow this method to install a prerelease package.
Install the ctc-oss repo with
dnf install dnf-plugins-core
dnf copr enable ctc-oss/fapolicy-analyzerReleases packages of the Policy Analyzer are generally available from Copr a week before being available from Fedora.
The Policy Analyzer can be installed from the ctc-oss repository with the normal process
dnf install fapolicy-analyzer
Pre-release packages of the Policy Analyzer for all targets are created using the latest commit to master.
Use the dev tag + the commit number from the master branch, for example
dnf install fapolicy-analyzer-1.0.0~dev308
will install the prerelease 1.0.0 version at the 308th commit on the master branch.
From a containerized build environment
Follow this method only if you have cloned the GitHub repository and have Podman installed
make fc-rpmto build a Rawhide RPMmake el-rpmto build a RHEL 8 RPM
After a successful build the container will copy the RPMs into the host /tmp directory.
From a local development environment
Follow this method only if you have installed all required build tools
make run
This requires Pip + Pipenv + Python 3.9 or greater, and Rust 1.62.1 or greater.
Python and Rust dependencies will be installed during the build process.
Compatible with v1.0+
The 
Analyzing from syslog requires the following syslog_format entry:
syslog_format = rule,dec,perm,uid,gid,pid,exe,:,path,ftype,trust
- See the Known Issues
- Start a Discussion
- Create a new Issue
GPL v3