3 ms·
"Moments later, his computer’s command line came back with a response: “File not found.” He examined the Rackspace server’s contents again. It was empty. Leetha
by tyingq 5y ago
"Moments later, his computer’s command line came back with a response: “File not found.” He examined the Rackspace server’s contents again. It was empty. Leetham’s heart fell through the floor: The hackers had pulled the seed database off the server seconds before he was able to delete it."
I get the compulsion to delete it, but deleting it wouldn't have provided any real comfort. You would have no idea if that was the only copy. So, delete it just in case it is, but it doesn't change what you would have to do afterwards...the master keys have to be assumed leaked.
- PUSH_AX 5y agoI mean you're never not going to delete it when given the option. As tiny as the chances are, it could mean your downstream consumers end up safe. Although yes, it should not stop you going into full damage control mode.
- xyzzy123 5y agoIt's moderately likely the employee in fact deleted that copy and the "disappeared seconds before it happened" is a fig leaf or polite fiction. Have to assume the data were compromised anyway, as you point out.
- wolverine876 5y agoIt might make customers less safe: If you delete the file, you reveal to the attackers what you know. The attackers may move more quickly to exploit the seeds, and it may disrupt your investigation, on which your customers depend: The attackers may abandon that path and follow another one that you are unaware of.