Hmm, for a customer of a cloud provider, this sort of thing will be very hard to defend against.
Maybe if the customer service system had had two-factor security, this might have been avoided (i.e., customer service can access your account only if you read them your hardware token's code).
Requiring SSL/SSH client certificates even for intranet accesses might have deterred this attack.
I hope other cloud providers take note of this incident. This is a very interesting incident.
Maybe if the customer service system had had two-factor security, this might have been avoided (i.e., customer service can access your account only if you read them your hardware token's code).
Requiring SSL/SSH client certificates even for intranet accesses might have deterred this attack.
I hope other cloud providers take note of this incident. This is a very interesting incident.