CSEC_PUBLIC/the-practical-linux-hardening-guide
1
0
Fork 0
mirror of https://github.com/trimstray/the-practical-linux-hardening-guide.git synced 2025-12-06 09:12:46 +01:00
Code Issues Packages Projects Releases Wiki Activity

updated 'General Disclaimer'

Browse Source 
- signed-off-by: trimstray <trimstray@gmail.com>
This commit is contained in:
trimstray
2019-03-04 15:27:45 +01:00
parent 92b41b4465
commit c8ce3eb3b1
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -80,10 +80,6 @@ A few rules for this project:
- some hardening rules/descriptions can be done better
- you can think of it as a checklist
Please also remember:
> This guide also contains my comments that may differ from certain industry principles. If you are not sure what to do please see **[Policy Compliance](#policy-compliance)**.
This guide use following [OpenSCAP](https://www.open-scap.org/) configurations:
- [U.S. Government Commercial Cloud Services (C2S) baseline inspired by CIS v2.1.1](https://static.open-scap.org/ssg-guides/ssg-rhel7-guide-C2S.html)
@@ -94,6 +90,10 @@ This guide use following [OpenSCAP](https://www.open-scap.org/) configurations:
> The requirements are derived from the (NIST) 800-53 and related documents.
Please also remember:
> _The Practical Linux Hardening Guide_ also contains my comments that may differ from certain industry principles. If you are not sure what to do please see **[Policy Compliance](#policy-compliance)**.
### The Importance of Hardening Linux
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.