jlkinsel

Joined 16 years ago

Karma
66
Submissions
42
Member since
Jan 25
Interests include infosec, cloud computing, and infrastructure.

personal blog - http://theresnomon.co

[ my public key: https://keybase.io/jlk; my proof: https://keybase.io/jlk/sigs/YSK6ePReNHasHNX271Wrb-y0tBjJufXXXjl2i6128jQ ]

View on Hacker News

Recent submissions

Comment · 3 years ago
While it is great, Wazuh is not close to a static analyzer.
Comment · 6 years ago
Actually, the www was working. It's a cname to tp.47cf2c8c9-frontier.amazon.com, which should have been a cname to d3ag4hukkh62yn.cloudfront.net, but that record was broken for about 20 minutes.

Update: that frontier cname seems to be bouncing between Cloudfront and Akamai now, so I suspect they're fighting off either an attack or internal issues. I see issues to other route53 servers as well.

Comment · 10 years ago
I think that was a message from the rebel base?
Comment · 13 years ago
Comment · 13 years ago
I've seen more compromised boxes than one can shake a stick at. There's all sorts of reasons that blocking egress is a great idea. Compromises are usually automated bots, and no, they're not smart enough to bring down iptables. Even if it's a human that's pwned you, it's frequently a stupid human, or a lazy human. It's just good practice to practice security in depth.
Comment · 13 years ago
Time to write a little VBScript to port scan me some Dropbox servers...
Comment · 13 years ago
Soo they didn't forsee how teh hackers would compromise accounts without 2FA...but passwords are dead.

Well, I for one, am sold!

Comment · 13 years ago
To go a little further - at a glance, it's not clear if they've been fined yet or not, but either way there's soft costs to all of this - being in the news in a negative light, some patients will go elsewhere, their insurance premiums are going to go up as a result of the breaches, etc etc.
Comment · 13 years ago
Last year when KC shot themselves in the face, they were running trading algos that hadn't been well tested. When dropped into production, things blew up fairly quickly.

I probably should have left it off the list, it's more of a compliance/procedural issue than purely infosec.

Comment · 13 years ago
Comment · 13 years ago
man how'd I forget hb gary...that's my other favorite
Comment · 13 years ago
Let's see...

TJ Max, UBS, Knight Capital, Heartland Payment Systems, Visa, Sony (already mentioned, but it's my fave), Stanford, Countless other hospitals, e-commerce vendors, banks, and other organizations that handle payment or personal information.

If you want to say "name a startup that's gone out of business because of a security problem" I'll let you away with that. There's still instances, and I'd love startups to pay more attention to security, but I know reality as well...

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton