Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| en:it-security:smb-hardening [2023/11/13 13:53] – created psycore | en:it-security:smb-hardening [2024/02/05 07:34] (current) – old revision restored (2024/02/04 23:30) psycore | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{tag> | ||
| ====== SMB Hardening ====== | ====== SMB Hardening ====== | ||
| ===== Technical background to the SMB protocol ===== | ===== Technical background to the SMB protocol ===== | ||
| - | [[wpde> | + | [[wpde> |
| The SMB signing explicitly assigns each initiated session to the client. This means that it is still possible to hijack the authentication, | The SMB signing explicitly assigns each initiated session to the client. This means that it is still possible to hijack the authentication, | ||
| Line 19: | Line 20: | ||
| ===== Procedure ===== | ===== Procedure ===== | ||
| - | * Step 1 - Deactivate SMBv1 | + | < |
| - | | + | flowchart |
| - | | + | Z[Flow] |
| + | A[Disable SMBv1] | ||
| + | B[SMB signing] | ||
| + | C(Client) | ||
| + | D(Server) | ||
| + | E(optional activation) | ||
| + | F(forced activation) | ||
| + | Z--Step 1-->A | ||
| + | | ||
| + | B-->C | ||
| + | B-->D | ||
| + | C--Step 2-->E | ||
| + | D--Step 3-->F | ||
| + | </ | ||
| ==== Step 1 - Deactivate SMBv1 ==== | ==== Step 1 - Deactivate SMBv1 ==== | ||