From 7f2607ea7946ec6a1126f817b5115c6ad93856f4 Mon Sep 17 00:00:00 2001 From: trimstray Date: Thu, 21 Feb 2019 09:21:50 +0100 Subject: [PATCH] added info about wiki - signed-off-by: trimstray --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 164a1ff..cd3e5e8 100644 --- a/README.md +++ b/README.md @@ -68,7 +68,7 @@ ### General disclaimer -**[The Practical Linux Hardening Guide](https://github.com/trimstray/the-practical-linux-hardening-guide/wiki)** provides a high-level overview of the hardening GNU/Linux systems. It is not an official standard or handbook but it _touches_ and _use_ industry standards. +**The Practical Linux Hardening Guide** provides a high-level overview of the hardening GNU/Linux systems. It is not an official standard or handbook but it _touches_ and _use_ industry standards. This guide also provides you with _practical step-by-step instructions_ for building your own hardened systems and services. @@ -85,6 +85,8 @@ Before you start remember: > This guide also contains my comments that may be differ from certain industry principles. If you are not sure what to do please see **[Policy Compliance](#policy-compliance)** chapter. +Full guide is on the **[wiki](https://github.com/trimstray/the-practical-linux-hardening-guide/wiki)**. + ### The importance of Linux hardening Simply speaking, hardening is the process of making a system more secure. Out of the box, Linux servers don’t come "hardened" (e.g. with the attack surface minimized). It’s up to you to prepare for each eventuality and set up systems to notify you of any suspicious activity in the future.