Sabitlenmiş Tweet
Eli🗿
2K posts

Eli🗿 retweetledi
Eli🗿 retweetledi
Eli🗿 retweetledi

Few years ago, a promising startup called Code Spaces was crippled into closing down due to a security misconfiguration. One tiny mistake in their cloud setup ended up wiping out the entire company.
It began when their engineers noticed unusual activity on their AWS console.
Someone was inside the actual console, the command center of their whole business. At first, they thought it was a false alarm. “Maybe someone logged in from a new device.” “Maybe a test account.” “Nothing to worry about.”
Then a ransom message appeared.
The attacker explained, calmly, that they had full control over Code Spaces’ entire AWS environment. If the company didn’t pay, they would begin deleting resources.
Code Spaces refused. They tried to fight back, revoke access, rotate keys, kill sessions, everything incident response playbooks say you should do.
But the attacker already had admin privileges.
And Code Spaces had made the one mistake countless startups still make today: they stored everything, production servers, databases, snapshots, logs, backups, cross-region replicas, inside a single AWS account, behind a single blast radius. No isolation. No backup of the backup. No out-of-band safety net.
So the attacker began clicking.
Snapshots disappeared.
S3 buckets evaporated.
EC2 instances terminated instantly.
Database backups wiped out.
Even the fallback snapshots stored “safely” across regions were under the same compromised account, and were deleted just as easily.
The engineers watched in real time as years of customer data vanished. Entire repositories. Configurations. Histories. Everything customers trusted them with.
They weren’t dealing with a breach anymore.
They were experiencing erasure.
Within hours, Code Spaces published a devastating announcement: the damage was irreversible. They could not rebuild. There was nothing left to restore. The company was forced to shut down permanently.
It wasn’t a sophisticated hack or an advanced exploit.
It was a simple misconfiguration, an over-permissioned IAM role,
no MFA on the AWS console,
critical backups stored in the same place as production.
One compromised credential, and a thriving startup ceased to exist because they trusted their cloud configuration too much, and learned, the hard way, that in cloud security, one mistake can cost you your entire company.
The Tech Prophet (Amospikins)@Amospikins
Who Leave Admin Panel Open? One Misconfiguration, Big Disaster
English

Eli🗿 retweetledi

"Introduction to Parallel Algorithms" by Guy Blelloch is an excellent companion to MIT's course.
It covers the memory hierarchy from a parallel computing perspective and much more.
cs.cmu.edu/~guyb/paralg/p…



Vivek Galatage@vivekgalatage
MIT's 6.851: Advanced Data Structures (Spring'21) courses.csail.mit.edu/6.851/spring21/ This has been on my recommendation list for a while, and the Memory hierarchy discussions are great in the context of cache-oblivious algorithms.
English
Eli🗿 retweetledi
Eli🗿 retweetledi
Eli🗿 retweetledi
Eli🗿 retweetledi

This man make I think papa. Translated it for those who don’t understand twi.
Chai. The fate of Ghana lies in our hands
#StopGalamseyNow #Freethecitizens
English
Eli🗿 retweetledi

Eli🗿 retweetledi

BART Simpson said we should get the hashtag to a million tweets. We’re at 680k now #FreetheCitizens

English









