CSEC_PUBLIC/How-To-Secure-A-Linux-Server
1
0
Fork 0
mirror of https://github.com/imthenachoman/How-To-Secure-A-Linux-Server.git synced 2025-12-06 01:02:49 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fix errors in README.md

Browse Source
This commit is contained in:
rbromley10
2019-02-16 14:35:01 -08:00
committed by GitHub
parent 4fbdeb7e1e
commit 769167d325
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -68,7 +68,7 @@ At a high level, the second a device, like a server, is in the public domain --
What's worse is, without good security, you may never know if your server has been compromised. A bad-actor may have gained unauthorized access to your server and copied your data without changing anything so you'd never know. Or your server may have been part of a DDOS attack and you wouldn't know. Look at many of the large scale data breaches in the news -- the companies often did not discover the data leak or intrusion until long after the bad-actors were gone.
Contrary to popular, bad-actors don't always want to change something or [lock you out of your data for money](). Sometimes they just want your for their data warehouses (there is big money in big data) or to covertly use your server for their nefarious purposes.
Contrary to popular belief, bad-actors don't always want to change something or [lock you out of your data for money](). Sometimes they just want your server for their data warehouses (there is big money in big data) or to covertly use your server for their nefarious purposes.
([Table of Contents](#table-of-contents))