norsotec/internal-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: norsotec:5e3c9cbc29688156d7f05052b303f1706a09bd65
Branches Tags
norsotec:main
..
compare: norsotec:main
Branches Tags
norsotec:main

2 Commits
5e3c9cbc29 ... main

Author SHA1 Message Date
Administrator
1a9df9e12e docs: update linux/linux-firewall 2026-03-16 00:26:51 +00:00
Administrator
b643441453 docs: update linux/linux-firewall 2026-03-16 00:24:13 +00:00
1 changed files with 19 additions and 4 deletions
Expand all files Collapse all files

23
linux/linux-firewall.md
View File

@@ -2,8 +2,8 @@
title: Firewall Linux title: Firewall Linux
description: Firewall Konfiguration unter Linux description: Firewall Konfiguration unter Linux
published: true published: true
date: 2026-03-16T00:20:01.180Z date: 2026-03-16T00:26:49.413Z
tags: firewall, linux tags: firewall, linux, fail2ban, ufw, brutforce
editor: markdown editor: markdown
dateCreated: 2026-03-15T23:56:44.726Z dateCreated: 2026-03-15T23:56:44.726Z
--- ---
@@ -44,12 +44,27 @@ Die Maschine neustarten und danach prüfen:
sudo ufw status numbered sudo ufw status numbered
``` ```
## Empfehlungen Firewall Einstellungen ## 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 ```bash
ufw limit 22/tcp ufw limit 22/tcp
``` ```
2) Das blockiert automatisch IPs bei Login-Angriffen 3) Das blockiert automatisch IPs bei Login-Angriffen (fail2ban)
```bash ```bash
apt install fail2ban 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
```