A custom AppArmor profile generator for Docker containers that simplifies container security.
Bane is a custom AppArmor profile generator designed specifically for Docker containers. It automates the creation of security profiles that restrict container capabilities, such as filesystem access, network operations, and process execution. This tool solves the problem of manually crafting complex AppArmor rules, which is tedious and error-prone, by generating profiles from simple configuration files.
System administrators, DevOps engineers, and security-focused developers who deploy Docker containers in production and need to enforce strict security policies without manual AppArmor configuration.
Developers choose Bane because it drastically simplifies AppArmor profile management for Docker, offering a declarative configuration approach that reduces human error and saves time compared to writing profiles by hand. Its seamless Docker integration and focus on practical security make it a pragmatic tool for hardening containers.
Custom & better AppArmor profile generator for Docker containers.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates AppArmor profiles from simple TOML files, eliminating the need to write complex AppArmor syntax manually, as demonstrated in the sample.toml config for nginx.
Supports file globbing patterns (e.g., wildcards, directory exclusions) for defining allowed or denied paths, enabling fine-grained access control without hardcoding every file.
Installs profiles directly and applies them with Docker's --security-opt flag, making it easy to enforce security on running containers without extra steps.
Includes LogOnWritePaths for configurable logging of write operations, helping monitor and debug security events, as shown in the dmesg output examples.
Only works on Linux systems with AppArmor enabled, making it unsuitable for environments using SELinux or other security modules, which limits its portability.
Requires users to write and maintain TOML configuration files, which can be error-prone and demands a good understanding of the container's security needs and AppArmor concepts.
Originally a proof of concept for Docker integration, as noted in the README, implying it might lack full production-ready features, active maintenance, or native Docker engine support.