From eafa0ca5884f4dfe09ca901b7476124d1d3d5c2b Mon Sep 17 00:00:00 2001 From: trimstray Date: Tue, 19 Feb 2019 14:10:33 +0100 Subject: [PATCH] updated headers and TOC - signed-off-by: trimstray --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index dc7a274..385eb23 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ - **[Introduction](#introduction)** * [General disclaimer](#general-disclaimer) * [The importance of Linux hardening](#the-importance-of-linux-hardening) - * [How to hardening GNU/Linux?](#how-to-hardening-gnulinux) + * [How to hardening Linux?](#how-to-hardening-linux) - **[Policy Compliance](#policy-compliance)** * [Center of Internet Security (CIS)](#center-of-internet-security-cis) * [Security Technical Implementation Guide (STIG)](#security-technical-implementation-guide-stig) @@ -196,7 +196,7 @@ Before you start remember: 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. -### How to hardening GNU/Linux? +### How to hardening Linux? In my opinion you should definitely drop all non-industry policies, articles, manuals and other on your production environments. We have a lot of great GNU/Linux hardening policies to provide safer operating systems compatible with security protocols and security policies.