From 44b26da4cea42c35f50a4892a89f989fe6ba3387 Mon Sep 17 00:00:00 2001 From: trimstray Date: Tue, 19 Feb 2019 19:09:12 +0100 Subject: [PATCH] updated 'How to hardening Linux?' - signed-off-by: trimstray --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9bbfd2b..835555a 100644 --- a/README.md +++ b/README.md @@ -206,7 +206,7 @@ You need to harden your system to protect your assets as much as possible. Why i In my opinion you should definitely drop all non-industry policies, articles, manuals and other especially on your production environments. This stuff exist to give false sense of security. -We have a lot of great GNU/Linux hardening policies to provide safer operating systems compatible with security protocols. +We have a lot of great GNU/Linux hardening policies to provide safer operating systems compatible with security protocols. For me, CIS and the various NSA STIGs are about the best actual prescriptive guides. > Most of all you should use [Security Benchmarks/Policies](#policy-compliance) which describe consensus best practices for the secure configuration of target systems because configuring your systems in compliance with e.g. CIS has been shown to eliminate 80-95% of known security vulnerabilities.