6 ms·
Love this bit: "Incidentally, if someone gets mad about you running this sort of thing, you probably don't want to work there anyway. On the other hand, if you
by simonw 3y ago
Love this bit:
"Incidentally, if someone gets mad about you running this sort of thing, you probably don't want to work there anyway. On the other hand, if you're able to build such tools without IT or similar getting "threatened" by it, then you might be somewhere that actually enjoys creating interesting and useful stuff. Treasure such places. They don't tend to last."
- Symbiote 3y agoI wonder if this counts as personal data. It's a copy of everyone's name, job title and employment dates. I can certainly see many European businesses would be wary of an employee keeping this list.
- brailsafe 3y agoIf I read it correctly, they just dumped and diffed their uid, not all of that information.
- notso411 3y ago[dead]
- Traubenfuchs 3y agoIn central Europe, we have the complete company organigram in namely, so it can't be that bad.
- athoscouto 3y agoAre you referring to GDPR? Does it apply to employees too, or only customers?
- M2Ys4U 3y agoGDPR applies to everyone in the EU/EEA/UK. They don't need to be a citizen, they don't need to have any sort of contractual arrangement with the data processor. If they're alive and identifiable, the GDPR applies.
- walthamstow 3y agoSo interesting that you say alive. There's always a some obscure bit of GDPR I've never heard of. Does a dead person not have PII?
- thfuran 3y agoThey can't be harmed by mishandling of PII.
- M2Ys4U 3y agoRecital 27 of the GDPR states: >This Regulation does not apply to the personal data of deceased persons. Member States may provide for rules regarding the processing of personal data of deceased persons. It's not part of the operative text of the regulation, but it provides for a clarification on what a "natural person" is, and the principal prohibition in the regulation is the processing of data about an identified or identifiable natural person. I would also assume, but I'm not 100% sure, that there's some case law from the CJEU around whether or not the definition of "natural person" includes dead people, which is why it's not in the main body of the text.
- tirpen 3y agoGDPR definitely applies to employees as well. It applies to all handling of personal data. One of the most important rules in GDPR is the requirement for companies to have an up to date list of all places where personal data is being stored, the reason it's stored there and what it's used for and the retention policy. So an employee creating their own lists of previous employees could potentially get the company in trouble if it was discovered during some external audit if it wasn't listed.
- gregw2 3y agoNot speaking about GDPR, but your post is triggering me (my issue, not yours). Here’s what is crazy to me about employee PII (personally identifiable information) being considered sensitive. Say in a well designed system you can audit who made each change or the last change to each business record. As an example, each database table has a login ID of who modified the last record/row most recently. Now every single such table is polluted with PII? I get having a list of all the places where personal data is stored, but some people think we need a list of all the places a pointer to personal data is stored (ie an identifier that enables linking; that is what “PII” literally means) and that is just such a bigger dataset I don’t think it is appreciated how deep the rabbit trail goes applying policy to technology. Every email in an organization contains PII and every system emails can get saved and attached to. Back to your comment, does GDPR require just listing the personal information locations, or also the (PII) identifiers to it? Is a name alone considered personal information (if I sign my emails with my name does that go on the list and if so, can companies just declare huge subsystems as having personal information?)
- Symbiote 3y agoDepending on the business, employee data can be more of a concern than customers. A business probably handles sensitive private data on employees (e.g. medical conditions, family records). Employees know this, and could report an ex-employer out of spite, especially if they're aware of poor data security.
- M2Ys4U 3y agoThis is definitely processing personal data. What Rachel is describing is absolutely illegal under the GDPR.
- htrp 3y agouids are definitely not pii
- jijijijij 3y ago> Incidentally, if someone gets mad about you running this sort of thing, you probably don't want to work there anyway. If you do want to work there, though, maybe check the legal situation first... I am almost certain, this counts as unauthorized processing of personal information. Just because you have access doesn't mean it's fair game to do whatever you like with it. Especially archiving, keeping a history or linking (external) data is not the intended use for such an interface. If you take the information home with you, e.g. on your work laptop, that may be a whole nother can of worms. May even count as business secrets you're exfiltrating. At least in Europe, abusing such an interface likely would be illegal, certainly if you keep a copy/diff. Your employer may have to act against you, or become liable. Or they may use this misconduct later to conveniently terminate your contract (lol, especially, if you use your insights as leverage). I presume the larger the network, the more likely this will get you in trouble. Conversely, collecting the data has little use otherwise. How about you organize with your colleagues to voluntarily share employment information to gain collective leverage?
- notyourwork 3y agoA diff of the directory is abuse? That seems overly aggressive and I don’t see what that prevents.
- jijijijij 3y agoAre you trying to be pedantic? A diff by itself does not necessarily contain any information at all. However, it should be fairly obvious a complete diff in relation to a reference contains all the information of a prior state. So it's functionally similar to a copy. [LIVE]->[DIFF_N]->[DIFF_N-1]->...->[DIFF_1]=[LIVE_1] You know, that's kinda how Git works.
- maximinus_thrax 3y ago> A diff of the directory is abuse? Yes, if it contains employment information. A bunch of diffs can cross the threshold into event sourcing and if you have enough of them you might end up with a copy of the directory.
- malfist 3y agoAmazon fired a guy that shared an LDAP query to find folks affected by a round of layoffs....after the layoff happened. So it's not like he was leaking information.
- refulgentis 3y agoI don't love it at all. It's over-the-top posturing for posturing's sake. A way to confirm this is to look for HN comments who posture the same. After the Overton window widening, they forget to hold back, and will openly say what we know: it's an abuse of the system that turns an outmoded address book into a gossip rag, to the surprise of the actual people involved. Citations: "First I just cared about which accounts got deactivated. Then I started tracking title changes, last name changes (people getting married), department sizes, company head count over time etc." "LDAP's full of secrets. And to think that you can get nearly all of it with anonymous access. Team or department mergers before they were announced? Yep, I've caught those. Secret mailing lists for internal projects? Check who's a member and you can ferret out what's going on. Bonus if the list mail address gives some of it away." "Lots of weird things depend on the LDAP tree being broadly accessible. It's just that it leaks more information than most people think." "Monitor when and what HR is doing. Detect when users are logging in and out of LDAP."