Probably a semicolon!

(I’d assume going to text messaging to set something up, which is why you should know enough about your immediate coworkers to verify their identity via non-public information.)

A reasonably sophisticated attacker could arrange for the entire team to get SIM-swapped and suspended from Facebook when they launch an attack. If only there were some way to have a central rallying point for everyone to meet at. Perhaps some sort of a structure, with the company's name on it, and it would have places to sit inside, with computers connected to the company's infrastructure to use.

In the old days you’d have physical restrictions on access to the datacenter - in a major breach you’d get there physically and shut it down and disconnect it.

With everything cloud now, how do you recover your cloud account of the master got compromised?

For someone Uber’s size, you call your AWS rep and co-ordinate with AWS security.

Could the CTO or some other employee go to Amazon's office to do something like this? I genuinely wonder.

How do they verify your identity?

That's the fun part, you don't!

Who controls the database of RFID cards allowed to open the doors?

Usually the datacenter was manned (sometimes by guys with guns) and they had various mechanisms for ID verifications.

And they had an entirely separate IT setup that wasn’t related to yours.

My not super-secure datacenter requires either a palm-print plus RFID card, or showing ID to a human.

At Dropbox we had an explicit fallback on the DFIR team for the situation where our normal communication methods were considered compromised (not going to give details, obviously). I would hope that most security teams at a company of similar size have discussed this situation, it's not at all uncommon for attackers to sit in on calls, read messages between security people, or even access the SIEM to see what alerts are going off.

Yup, gonna be a rough night for all involved.

Generally speaking infra and sec folk tend to have OOB comms setup because of frequency of Slack outages