oxeo0/opsec-blogposts
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/opsec-blogposts.git synced 2025-06-08 18:19:32 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

remove paraphrase

Browse source
This commit is contained in:
MulliganSecurity 2025-06-05 11:01:09 +02:00
parent 8fcaf0f6b9
commit 7287e29ba6
1 changed files with 0 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

5
simplexalerts/index.md
View file

@ -33,11 +33,6 @@ There are basically two types of alerting mode:
- can't come up with alert amelioration ideas
## Associated Risks
To paraphrase one of my favourite playwrights:
To alert or not alert? That is the question. Whether 'tis nobler in the mind to unknowingly suffer she slings and arrows of outrageous fortune or to take arms against a sea of anomalies, fighting the advesary dwelling within...
As your perimeter and infrastructure grows, as you add more servers your system complexity will shoot up exponentially. Simple organic alerting shows its limit when you have to correlate logs and behaviors across multiple systems.
That's why you need alerting, if an adversary decides to stealthily probe at your infrastructure and you know what to look for you will see their attempt for what it is. Choosing to remain in the dark about it is foolish at best and irresponsible if you are part of an outfit as your laziness will put others in harm's way.