5 ms·

> IIRC the Ubiquiti 'hack' was an insider attack from an employee lying and intentionally breaking things while pushing his lies to the press to hurt his employ

> IIRC the Ubiquiti 'hack' was an insider attack from an employee lying and intentionally breaking things while pushing his lies to the press to hurt his employer. "Their undetected security breach was by an insider" is not the sterling defence of Ubiquiti that you seem to think it is.

gonehome 5y ago
These types of attacks are extremely hard to defend against. Considering the nature of the attacker (and the HN comments about the guy at the time of the attack) my take away of ubiquiti from this event and their response was positive. I also down ranked my expectation of Krebs’ accuracy. It’s not personal - he writes lots of great stuff, but his response to being wrong in this case was worse than Ubiquiti’s response to the incident.
- ikiris 5y ago
  Its really not that hard to defend / audit the actions of a single lone wolf, even if they're the head of security. This is just more and more embarrassment for a company that clearly just doesn't understand security, and yet wants to force all their users of their products to rely on them as a trust model by making all of their ongoing product systems completely cloud reliant or at least holding third party root keys to sell ads / customer telemetry.
- nottorp 5y ago
  But the only reason the insider job worked is because they insist on making their gear dependent on the "cloud" for no good reason?
- sofixa 5y ago
  Their response, which was to not disclose the breach? Or their late response, which was a vague email you might need to change your credentials? Or the fact that their cloud environment was a joke run by a one man show? It's like Okta. Of course it's hard to protect against an insider ( although Ubiquti didn't really try), but that's not an excuse to screw up the disclosure.
- CodeWriter23 5y ago
  > These types of attacks are extremely hard to defend against. And yet, enterprise-level suppliers do it successfully every day.
more_corn 5y ago
It was more nuanced than that. There were extortion attempts, abuse of trusted access, deliberate attempts to mislead and misreport.
passivate 5y ago
How many developers that you know have been fired for introducing security bugs?
cr3ative 5y ago
The insider was responsible for their AWS architecture. This isn't a lowly disgruntled employee.

gonehome 5y ago

These types of attacks are extremely hard to defend against. Considering the nature of the attacker (and the HN comments about the guy at the time of the attack) my take away of ubiquiti from this event and their response was positive. I also down ranked my expectation of Krebs’ accuracy. It’s not personal - he writes lots of great stuff, but his response to being wrong in this case was worse than Ubiquiti’s response to the incident.

ikiris 5y ago
Its really not that hard to defend / audit the actions of a single lone wolf, even if they're the head of security. This is just more and more embarrassment for a company that clearly just doesn't understand security, and yet wants to force all their users of their products to rely on them as a trust model by making all of their ongoing product systems completely cloud reliant or at least holding third party root keys to sell ads / customer telemetry.
nottorp 5y ago
But the only reason the insider job worked is because they insist on making their gear dependent on the "cloud" for no good reason?
sofixa 5y ago
Their response, which was to not disclose the breach? Or their late response, which was a vague email you might need to change your credentials? Or the fact that their cloud environment was a joke run by a one man show? It's like Okta. Of course it's hard to protect against an insider ( although Ubiquti didn't really try), but that's not an excuse to screw up the disclosure.
CodeWriter23 5y ago
> These types of attacks are extremely hard to defend against. And yet, enterprise-level suppliers do it successfully every day.

more_corn 5y ago

It was more nuanced than that. There were extortion attempts, abuse of trusted access, deliberate attempts to mislead and misreport.

passivate 5y ago

How many developers that you know have been fired for introducing security bugs?

cr3ative 5y ago

The insider was responsible for their AWS architecture. This isn't a lowly disgruntled employee.