||1 month ago|
|.github||2 months ago|
|autoconf||1 month ago|
|cli||2 months ago|
|core||1 month ago|
|docs||1 month ago|
|examples||1 month ago|
|helpers||2 months ago|
|integrations||1 month ago|
|job||1 month ago|
|linux||1 month ago|
|tests||1 month ago|
|utils||1 month ago|
|CHANGELOG.md||1 month ago|
|README.md||1 month ago|
|VERSION||1 month ago|
Make security by default great again !
BunkerWeb is a web server based on the notorious NGINX and focused on security.
It integrates into existing environments (Linux, Docker, Swarm, Kubernetes, …) to make your web services "secure by default" without any hassle. The security best practices are automatically applied for you while keeping control of every setting to meet your use case.
Why BunkerWeb ?
- Easy integration into existing environments : support for Linux, Docker, Swarm and Kubernetes
- Highly customizable : enable, disable and configure features easily to meet your use case
- Secure by default : offers out-of-the-box and hassle-free minimal security for your web services
- Free as in "freedom" : licensed under the free AGPLv3 license
A non-exhaustive list of security features :
- HTTPS support with transparent Let's Encrypt automation
- State-of-the-art web security : HTTP security headers, prevent leaks, TLS hardening, ...
- Integrated ModSecurity WAF with the OWASP Core Rule Set
- Automatic ban of strange behaviors based on HTTP status code
- Apply connections and requests limit for clients
- Block known bad IPs with external blacklists and DNSBL
- And much more ...
Learn more about the core security features in the security tuning section of the documentation.
A demo website protected with BunkerWeb is available at demo.bunkerweb.io. Feel free to visit it and perform some security tests.
You will find more information about the key concepts of BunkerWeb in the documentation.
The first concept is the integration of BunkerWeb into the target environment. We prefer to use the word "integration" instead of "installation" because one of the goals of BunkerWeb is to integrate seamlessly into existing environments.
The following integrations are officially supported :
Once BunkerWeb is integrated into your environment, you will need to configure it to serve and protect your web applications.
Configuration of BunkerWeb is done using what we called the "settings" or "variables". Each setting is identified by a name like
USE_ANTIBOT for example. You can assign values to the settings to configure BunkerWeb.
Here is a dummy example of a BunkerWeb configuration :
SERVER_NAME=www.example.com AUTO_LETS_ENCRYPT=yes USE_ANTIBOT=captcha REFERRER_POLICY=no-referrer USE_MODSECURITY=no USE_GZIP=yes USE_BROTLI=no
You will find an easy to use settings generator at config.bunkerweb.io.
The multisite mode is a crucial concept to understand when using BunkerWeb. Because the goal is to protect web applications, we intrinsically inherit the concept of "virtual host" or "vhost" (more info here) which makes it possible to serve multiple web applications from a single (or a cluster of) instance.
By default, the multisite mode of BunkerWeb is disabled which means that only one web application will be served and all the settings will be applied to it. The typical use case is when you have a single application to protect : you don't have to worry about the multisite and the default behavior should be the right one for you.
When multisite mode is enabled, BunkerWeb will serve and protect multiple web applications. Each web application is identified by a unique server name and have its own set of settings. The typical use case is when you have multiple applications to protect and you want to use a single (or a cluster depending of the integration) instance of BunkerWeb.
Because meeting all the use cases only using the settings is not an option (even with external plugins), you can use custom configurations to solve your specific challenges.
Under the hood, BunkerWeb uses the notorious NGINX web server, that's why you can leverage its configuration system for your specific needs. Custom NGINX configurations can be included in different contexts like HTTP or server (all servers and/or specific server block).
Another core component of BunkerWeb is the ModSecurity Web Application Firewall : you can also use custom configurations to fix some false positives or add custom rules for example.
We provide ready to use prebuilt images for x64, x86, armv7 and arm64 platforms on Docker Hub using the
Usage and configuration of the BunkerWeb container are based on :
- Environment variables to configure BunkerWeb and meet your use cases
- Volume to cache important data and mount custom configuration files
- Networks to expose ports for clients and connect to upstream web services
You will find more information in the Docker integration section of the documentation.
The downside of using environment variables is that the container needs to be recreated each time there is an update which is not very convenient. To counter that issue, you can use another image called autoconf which will listen for Docker events and automatically reconfigure BunkerWeb in real-time without recreating the container.
Instead of defining environment variables for the BunkerWeb container, you simply add labels to your web applications containers and the autoconf will "automagically" take care of the rest.
You will find more information in the Docker autoconf section of the documentation.
To automatically configure BunkerWeb instances, a special service, called autoconf, will be scheduled on a manager node. That service will listen for Docker Swarm events like service creation or deletion and automatically configure the BunkerWeb instances in real-time without downtime.
Like the Docker autoconf integration, configuration for web services is defined using labels starting with the special bunkerweb. prefix.
The recommended setup is to schedule the BunkerWeb service as a global service on all worker nodes and the autoconf service as a single replicated service on a manager node.
You will find more information in the Swarm section of the documentation.
The autoconf acts as an Ingress controller and will configure the BunkerWeb instances according to the Ingress resources. It also monitors other Kubernetes objects like ConfigMap for custom configurations.
You will find more information in the Kubernetes section of the documentation.
List of supported Linux distros :
- Debian 11 "Bullseye"
- Ubuntu 22.04 "Jammy"
- Fedora 36
- CentOS Stream 8
Repositories of Linux packages for BunkerWeb are available on PackageCloud, they provide a bash script to automatically add and trust the repository (but you can also follow the manual installation instructions if you prefer).
You will find more information in the Linux section of the documentation.
Once you have setup BunkerWeb with the integration of your choice, you can follow the quickstart guide that will cover the following common use cases :
- Protecting a single HTTP application
- Protecting multiple HTTP application
- Retrieving the real IP of clients when operating behind a load balancer
- Adding custom configurations
BunkerWeb offers many security features that you can configure with settings. Even if the default values of settings ensure a minimal "security by default", we strongly recommend you to tune them. By doing so you will be able to ensure a security level of your choice but also manage false positives.
You will find more information in the security tuning section of the documentation.
To help you tuning BunkerWeb we have made an easy to use settings generator tool available at config.bunkerweb.io.
As a general rule when multisite mode is enabled, if you want to apply settings with multisite context to a specific server you will need to add the primary (first) server name as a prefix like
myapp.example.com_USE_GZIP=yes for example.
When settings are considered as "multiple", it means that you can have multiple groups of settings for the same feature by adding numbers as suffix like
REVERSE_PROXY_HOST_2=http://myhost2, ... for example.
Check the settings section of the documentation to get the full list.
The "Web UI" is a web application that helps you manage your BunkerWeb instance using a user-friendly interface instead of the command-line one.
- Start, stop, restart and reload your BunkerWeb instance
- Add, edit and delete settings for your web applications
- Add, edit and delete custom configurations for NGINX and ModSecurity
- Install and uninstall external plugins
- View the logs and search pattern
You will find more information in the Web UI section of the documentation.
BunkerWeb comes with a plugin system to make it possible to easily add new features. Once a plugin is installed, you can manage it using additional settings defined by the plugin.
Here is the list of "official" plugins that we maintain (see the bunkerweb-plugins repository for more information) :
|ClamAV||0.1||Automatically scans uploaded files with the ClamAV antivirus engine and denies the request when a file is detected as malicious.||bunkerweb-plugins/clamav|
|CrowdSec||0.1||CrowdSec bouncer for BunkerWeb.||bunkerweb-plugins/crowdsec|
|Discord||0.1||Send security notifications to a Discord channel using a Webhook.||bunkerweb-plugins/discord|
|Slack||0.1||Send security notifications to a Slack channel using a Webhook.||bunkerweb-plugins/slack|
|VirusTotal||0.1||Automatically scans uploaded files with the VirusTotal API and denies the request when a file is detected as malicious.||bunkerweb-plugins/virustotal|
You will find more information in the plugins section of the documentation.
We offer professional services related to BunkerWeb like :
- Custom development
Please contact us at email@example.com if you are interested.
To get free community support you can use the following medias :
- The #help channel of BunkerWeb in the Discord server
- The help category of GitHub dicussions
- The /r/BunkerWeb subreddit
- The Server Fault and Super User forums
Please don't use GitHub issues to ask for help, use it only for bug reports and feature requests.
This project is licensed under the terms of the GNU Affero General Public License (AGPL) version 3.
If you would like to contribute to the plugins you can read the contributing guidelines to get started.
We take security bugs as serious issues and encourage responsible disclosure, see our security policy for more information.