Re:How An Attacker's Blunder Gave Us a Rare Look Inside Thei...
by coppsilgold on Tuesday September 09, 2025 @03:12PM
(#45187201)
I would assume any machine not owned by me is fully compromised and there is no recovery possible. And treat it accordingly, such as using it just for the purpose the owner of the machine dictates assuming I value that relationship.
The startup script you blocked could have just been a decoy. And set off a red flag.
A lot of these EDR's operate in kernel space.
Re:How An Attacker's Blunder Gave Us a Rare Look Inside Thei...
by boston_clone on Tuesday September 09, 2025 @02:42PM
(#45186618)
Directly impinging the enterprise-approved security tooling is really not a good idea, no matter your own personal opinions on their functionality.
Unless maybe you just want to develop a more personal relationship with your internal cybersecurity team, who knows.
Re:How An Attacker's Blunder Gave Us a Rare Look Inside Thei...
by jacquesm on Wednesday September 10, 2025 @04:07AM
(#45194693)
Or with the HR team and the corporate security guys assisting your departure from the building holding a small cardboard box.
However, it's obvious that protection-ware like this is essentially spyware with alerts. My company uses a similar service, and it includes a remote desktop tool, which I immediately blocked from auto-startup. But the whatever scanner sends things to some central service. All in the name of security.