News for hackers. Stuff that matters.
Re:Update on Meltdown and Spectre by matthewaveryusa on Thursday January 04, 2018 @10:57PM (#16076398)
How does cycling AWS instances quickly provide additional security beyond obscurity?
Re:Update on Meltdown and Spectre by lloydde on Thursday January 04, 2018 @11:12PM (#16076471)
Rotate, Repave, and Repair “Its idea is quite simple. Rotate datacenter credentials every few minutes or hours. Repave every server and application in the datacenter every few hours from a known good state. Repair vulnerable operating systems and application stacks consistently within hours of patch availability. Faster is safer.” https://builttoadapt.io/the-three-r-s-of-enterprise-security...
Re:Update on Meltdown and Spectre by sanxiyn on Thursday January 04, 2018 @11:08PM (#16076449)
Obscurity does provide additional security.
Re:Update on Meltdown and Spectre by MichaelApproved on Thursday January 04, 2018 @11:34PM (#16076569)
They aren’t trying to obscure, they’re trying to be a moving target.
Re:Update on Meltdown and Spectre by TJSomething on Thursday January 04, 2018 @11:43PM (#16076610)
Perhaps proving that you're running on the same hardware as Coinbase is most easily done by statistical attacks, which requires collecting data over time.
Re:Update on Meltdown and Spectre by dsacco on Friday January 05, 2018 @12:28AM (#16076767)
> How does cycling AWS instances quickly provide additional security beyond obscurity?

The same way issuing a new session token for each login improves security. If the changes are unpredictable, whatever process an attacker uses to guess the correct target must be restarted every time the target changes.

Re:Update on Meltdown and Spectre by disordr on Thursday January 04, 2018 @11:31PM (#16076551)
When you reboot your EC2 instance, that VM is provisioned on a (patched) system.
Re:Update on Meltdown and Spectre by _callcc on Thursday January 04, 2018 @11:39PM (#16076591)
Yes, they would have been better off leaving out this "cycling" bit altogether.