logoalt Hacker News

giantg2yesterday at 7:09 PM6 repliesview on HN

How did they get access to 5k passwords? Are they being sent/stored in cleartext? This is the most baffling part of the article for me.

The second part I'm unclear about is how you could pass SOC2 when you aren't terminating account access simultaneously with the employment termination.


Replies

inetknghtyesterday at 7:13 PM

From the article, it sounds like the passwords are indeed stored in cleartext:

> On Feb. 1, 2025, Muneeb Akhter asked Sohaib Akhter for the plaintext password of an individual who submitted a complaint to the Equal Employment Opportunity Commission’s Public Portal, which was maintained by the Akhters’ employer. Sohaib Akhter conducted a database query on the EEOC database and then provided the password to Muneeb Akhter. That password was subsequently used to access that individual’s email account without authorization.

show 1 reply
GorbachevyChaseyesterday at 7:46 PM

Policy and practice might not be the same thing. The company and the entire management staff should be on somebody’s blacklist for future procurement.

show 1 reply
hedoratoday at 3:42 AM

I don’t think you understand what SOC2 is.

First of all, it is viral, and it is almost never adopted based on its own technical merit.

Second, it has lots of levels. The first level is “we wrote down a plan explaining how we’re going to secure stuff”.

The second level is when you start implementation or maybe tracking or something.

The key thing is that first level: When your SOC2 dept says you have to do something idiotic for SOC2 compliance, it is because someone at your company invented the idiocy, and should be fired. However, you still need to follow their dumb plan because that’s the process.

In this case, the “how do we fire people” process, and “how do we prevent one llm from dropping 96 prod DBs in a single session” very well could have had answers in the plan, the plan could have been implemented, and therefore the company is still soc2 compliant, and this is exactly what a working soc2 process is supposed to look like.

skinfaxiyesterday at 8:22 PM

Depends on what their offboarding policy is. If it's 72 hours or something they would not breach policy.

BrandoElFollitoyesterday at 7:26 PM

And how exactly do you want to store passwords if not in plain text (and then encrypted of course)? 5k is a lot, the authorization process is broken, but this is not related to how the passwords are stored.

The only solution is correct access segregation and a bastion

show 7 replies
liendolucasyesterday at 9:12 PM

I can only think of a scenario where this is still valid: spying.

The minimum one can do is have a different randomized password for every service on a possibly completely offline password manager.

Yes, you will depend on a password manager at all times, but at least the blast radius is minimized to the affected service.