"in in" is not always wrong (backout 1.18).
Keep the onion metaphor consistent.
This commit is contained in:
parent
6c1a87e738
commit
4c0d8029dc
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=129400
@ -106,8 +106,8 @@ Many of the root holes found and closed to date involve a considerable amount
|
||||
of work by the attacker to cleanup after himself, so most attackers do install
|
||||
backdoors. This gives you a convenient way to detect the attacker. Making
|
||||
it impossible for an attacker to install a backdoor may actually be detrimental
|
||||
to your security because it will not close off the hole the attacker found to
|
||||
break in the first place.
|
||||
to your security because it will not close off the hole the attacker used to
|
||||
break in in the first place.
|
||||
.Pp
|
||||
Security remedies should always be implemented with a multi-layered
|
||||
.Sq onion peel
|
||||
@ -371,7 +371,7 @@ last layer of your security onion is perhaps the most important \(em detection.
|
||||
The rest of your security is pretty much useless (or, worse, presents you with
|
||||
a false sense of safety) if you cannot detect potential incursions. Half
|
||||
the job of the onion is to slow down the attacker rather than stop him
|
||||
in order to give the detection side of the equation a chance to catch him in
|
||||
in order to give the detection layer a chance to catch him in
|
||||
the act.
|
||||
.Pp
|
||||
The best way to detect an incursion is to look for modified, missing, or
|
||||
|
Loading…
Reference in New Issue
Block a user