SATCOM terminals under attack in Europe: a plausible analysis

Re:SATCOM terminals under attack in Europe: a plausible anal... by londons_explore on Monday March 07, 2022 @03:55PM (#30593206)

> Is there a plausible explanation for who would do this, besides Russia?

Any engineer could accidentally do it... I can totally imagine the release engineer accidentally pushing the dev version, only to realise later that the dev version doesn't have quite the right config to connect for example.

Blaming it on a cyber attack is a lot less bad than saying "whoops, we bricked everyone's modems".

[ Parent | on HN ]

Re:SATCOM terminals under attack in Europe: a plausible anal... by lxgr on Monday March 07, 2022 @08:12PM (#30595372)

It should be pretty easy to figure out which one it is, except if the deployment vector was actually a malicious firmware update.

A plausibly deniable exploit like that is probably orders of magnitude more expensive, and the timing is suspicious enough that it's probably not even worth trying. In any case, it's not like it's trivial to attribute (beyond reasonable doubt) a "transparent" cyber attack either.

[ Parent | on HN ]

Re:SATCOM terminals under attack in Europe: a plausible anal... by dylan604 on Monday March 07, 2022 @06:12PM (#30594592)

Except for when tensions are this high where that blame could be a lot less casual than other times.

[ Parent | on HN ]

Re:SATCOM terminals under attack in Europe: a plausible anal... by teknopaul on Tuesday March 08, 2022 @06:40AM (#30598845)

Release engineer would own up to it. There would be a trail, with no attempt to hide it.

[ Parent | on HN ]

Re:SATCOM terminals under attack in Europe: a plausible anal... by Nextgrid on Tuesday March 08, 2022 @09:07AM (#30600008)

There's still the incentive to cover it up externally and blame it on a cyberattack as opposed to poor internal processes that allowed such a bug to make it to production.

[ Parent | on HN ]