logoalt Hacker News

baxtr • yesterday at 3:55 PM • 7 replies • view on HN

It’s the same thing: let’s say Microsoft or AWS got hacked. Then you’re definitely not the only one who got hacked.

So, you can always say: Look, it’s not us (especially not my org!). It f’ing Microsoft/AWS! Everyone got hacked.

You and your career are gonna be just fine.


Replies

SkyPuncher • yesterday at 6:08 PM

In a prior role, we realized something similar with outages. For our particular product, we AWS went down - we went down. We freaked out the first time, but after it was done we realized not a single customer had inquired. This felt unusual since we were getting emails quickly if we have a self-inflicted outage.

Turns out, when a major provider went down all of our users were too busy fighting their own fires. When they do notice, it's on a day when ALL of their vendors are struggling so we don't get singled out as a bad apple.

codegeek • yesterday at 4:07 PM

The whole "No one gets fired for using IBM" analogy.

nrmitchi • yesterday at 6:33 PM

This is especially true if the majority of your customers are also on Microsoft/AWS/etc.

Literally 0 of your customers will notice that you are down if their own systems are also not working.

This is perfectly valid for many businesses, up to a (shockingly high) level.

➕ show 1 reply
temp0826 • yesterday at 7:22 PM

It's today's "nobody ever got fired for buying IBM". You're really just want the the SLA (someone to blame when things inevitably fail)

InsideOutSanta • yesterday at 4:33 PM

Yeah, if Exchange goes down, you get a day off. If the little boutique email provider you chose goes offline, you get a day in calls with everyone yelling at you.

esseph • yesterday at 4:50 PM

If you need deniability, sure.

But it you actually NEED security, it's clearly not an option.

➕ show 2 replies
Krasnol • yesterday at 7:03 PM

You are just describing how they're a more valuable target for an attack.