Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add crowdsec section #122

Merged
merged 10 commits into from
Oct 19, 2024
Prev Previous commit
Next Next commit
enhance: Try to fix tip
  • Loading branch information
LaurenceJJones committed Oct 16, 2024
commit b6be7dcbc82de3f06dce81e594b83165caa540ed
5 changes: 1 addition & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2156,14 +2156,11 @@ By default whilst CrowdSec is installing the Security Engine it will auto-discov
```bash
sudo apt install crowdsec-firewall-bouncer-iptables
```

By default whilst the Remediation Component is installing it will auto-configure the necessary settings to work with the Security Engine if deployed on the same host (and if the security engine is not within a container environment).


> ![!TIP]
> If your installation of UFW is not using `iptables` as the backend, you can alternatively install `crowdsec-firewall-bouncer-nftables`. There is no difference in the installed binaries, only the configuration file is different.


By default whilst the Remediation Component is installing it will auto-configure the necessary settings to work with the Security Engine if deployed on the same host (and if the security engine is not within a container environment).
3. Check detection and remediation is working as intended:

CrowdSec package comes with a CLI tool to check the status of the Security Engine and the Remediation Component.
Expand Down