Compare commits
2 Commits
5e3c9cbc29
...
main
| Author | SHA1 | Date | |
|---|---|---|---|
| 1a9df9e12e | |||
| b643441453 |
@@ -2,8 +2,8 @@
|
||||
title: Firewall Linux
|
||||
description: Firewall Konfiguration unter Linux
|
||||
published: true
|
||||
date: 2026-03-16T00:20:01.180Z
|
||||
tags: firewall, linux
|
||||
date: 2026-03-16T00:26:49.413Z
|
||||
tags: firewall, linux, fail2ban, ufw, brutforce
|
||||
editor: markdown
|
||||
dateCreated: 2026-03-15T23:56:44.726Z
|
||||
---
|
||||
@@ -44,12 +44,27 @@ Die Maschine neustarten und danach prüfen:
|
||||
sudo ufw status numbered
|
||||
```
|
||||
## Empfehlungen Firewall Einstellungen
|
||||
1) SSH Bruteforce Schutz
|
||||
1) Default Policies setzen (sehr wichtig)
|
||||
```bash
|
||||
sudo ufw default deny incoming
|
||||
sudo ufw default allow outgoing
|
||||
```
|
||||
2) SSH Bruteforce Schutz
|
||||
```bash
|
||||
ufw limit 22/tcp
|
||||
```
|
||||
2) Das blockiert automatisch IPs bei Login-Angriffen
|
||||
3) Das blockiert automatisch IPs bei Login-Angriffen (fail2ban)
|
||||
```bash
|
||||
apt install fail2ban
|
||||
```
|
||||
Damit kann man überprüfen, ob fail2ban läuft:
|
||||
```bash
|
||||
systemctl status fail2ban
|
||||
```
|
||||
|
||||
4) Logging vom default low zu medium erhöhen
|
||||
Die Logfiles findet man allgemein hier: `sudo less /var/log/ufw.log`
|
||||
```bash
|
||||
sudo ufw logging medium
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user