3 ms·
Whose NOC was hacked? Or what does “thenoc” refer to? We’re talking about hundreds of organizations running MoveIt. Are they all culpable for not having threat
by thedougd 3y ago
Whose NOC was hacked? Or what does “thenoc” refer to?
We’re talking about hundreds of organizations running MoveIt. Are they all culpable for not having threat intelligence better than disclosed vulnerabilities in COTS software? Or worse, in their vendors’ software? What should they subscribe to?
- Terretta 3y agoThe MOVEit vulnerability was covered everywhere all at once. So it didn't matter what you were subscribed to as long as that was more than zero things. The ongoing miss everywhere is less about detection or awareness than about response. Problem is there's lots of these across old back office I.T. stuff all the time, so much noise, and MOVEit is not a "top of mind" tech even though every legacy company uses it or a competitor to exchange files because they haven't heard of Box. So they didn't realize they use MOVEit and didn't think to dig in. That's the actual issue: not knowing what your firm runs on.
- thedougd 3y agoYes, it was covered everywhere all at once, after the event. The ex-filtration happened on May 27th through May 29th, and the vendor issued the alert on May 31st, after the wide-spread hacking. The Maine incident is not a new one, it too was from Memorial Day weekend hacks. https://www.rapid7.com/blog/post/2023/06/14/etr-cve-2023-34362-moveit-vulnerability-timeline-of-events/ https://www.rapid7.com/blog/post/2023/06/14/etr-cve-2023-343...