mirror of
https://github.com/trimstray/the-practical-linux-hardening-guide.git
synced 2025-12-06 17:22:51 +01:00
@@ -236,15 +236,15 @@ The three levels of understanding this guide:
|
|||||||
|
|
||||||
Making major changes to the direction of your systems can be risky.
|
Making major changes to the direction of your systems can be risky.
|
||||||
|
|
||||||
The basic rule of system hardening that reasonable admins actually use is:
|
The most important rule of system hardening that reasonable admins actually use is:
|
||||||
|
|
||||||
> **`A production environment is the real instance of the application so all your changes make on the dev/test before production!`**
|
> **`A production environment is the real instance of the app so all your changes make on the dev/test!`**
|
||||||
|
|
||||||
The second important rule is:
|
The second important rule is:
|
||||||
|
|
||||||
> **`Don’t do anything that will affect the availability of the service or your system.`**
|
> **`Don’t do anything that will affect the availability of the service or your system.`**
|
||||||
|
|
||||||
The third rule is:
|
And the third rule is:
|
||||||
|
|
||||||
> **`Make backup of entire virtual machines and important components in the middle of them.`**
|
> **`Make backup of entire virtual machines and important components in the middle of them.`**
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user