Columbia admits last year’s data breach exposed victims beyond its students, staff.
See full article...
See full article...
I also did a lot of work around document retention in my career and we made it part of our culture that document retention policies weren't just minimums but also maximums and also everything needed a policy. Part of the reason for maximums is that is protects you in the case of lawsuits - you don't need to turn over records you no longer have, and so long as you are implementing your policies consistently (and not an hour after you get a subpoena) you are free and clear of a lot of issues.I too received this notice from Columbia U. I am over 70 years old, from the midwest, and have never had any association with them. I took my SAT in 1969.
I have never sent Columbia a letter, an email, or other form of communication.
I have never set foot on the campus. I have never visited their website.
So, why do they have my personal information?
Depends on the state. The inflection point for that was 1974 when FERPA passed. The same year, the Patty Hearst situation happened which involved reporters getting personal information from UC Berkeley, and California and UC added additional controls on top of FERPA.I was still used for student IDs back in the late 90s too.
I mean, yeah, practically they are able to cause you a problem. Anyone with enough money to hire lawyers can.It is, but the business claims it really is you and not a scammer. You're stuck trying to prove it was identify theft. The business doesn't care who's left holding the bag and you're easy to find.
And notice how quickly they folded to the Orange Shitgibbon's shakedown. As a result, They need to suffer for their continual "we don't really care about the students"*. Keeping records long term, even about non-students, shows how unserious they are about their security.Ah Columbia. The vastly overpriced community college of the Ivy League.
"Beware of the Leopard"Data retention? Purging of backups? Please. Those policies are on paper in a three-ring binder somewhere, piled in cardboard printer paper boxes stored ten layers deep in a closet nobody uses.
We have public/private key infrastructure.The entire SSN database is available at this point.
It needs to be replaced with some sort of two factor system.
There is absolutely no reason a doctors office, insurance, loan agency needs your SSN.
A valid DL should suffice.
It's not usually used to create unique IDs. It's used to join data from disparate datasets. If you buy data from College Board and also buy data from ACT, how do you join those two datasets to align the same data for the same person? Names and addresses are fairly unreliable to match without a lot of data cleaning effort, so SSN becomes a reliable key to join on even if you don't want to retain SSN - because there are no other reliable keys to use.The fact that Columbia had lists like that seems about par for the course. Back in the latter couple of decades of the previous century, and then into the early days of this one, SSNs were any inexperienced or lazy DB developer's way to create a unique ID for each entry in a list of people. The government had already done 90% of the work to ensure uniqueness and integrity. I'd bet there are countless schools and universities out there with rogue databases of SSNs.
Thank you. You did a far more thorough job of presenting the problem than I. Where I came from (government) we had the enormous problem of people who knew just enough SQL Server or MS Access to get into trouble. They'd create what we called, "rogue databases" by pulling down data from one or more corporate systems and importing it into their desktop DB of choice. But because they didn't know how to do what you describe, the SSN became an instant, easy unique key. This happened all the time. Often these things developed a life of their own and went into a sort of unofficial, undocumented production status. The network admins would have to perform regular whack-a-mole scans of the file repositories to hunt them down. Technically, this was all illegal under the Privacy Act of 1974, but as you can imagine, few paid attention until massive data breaches started making people worry about their jobs.It's not usually used to create unique IDs. It's used to join data from disparate datasets. If you buy data from College Board and also buy data from ACT, how do you join those two datasets to align the same data for the same person? Names and addresses are fairly unreliable to match without a lot of data cleaning effort, so SSN becomes a reliable key to join on even if you don't want to retain SSN - because there are no other reliable keys to use.
Pretty much every data space has this same problem, where there's a kind of mutual agreement on what identifier to use as a key - Title IV school codes, Carnegie codes, and so on. If the government doesn't provide a valid for use key, some other key will be appropriated from whatever source is convenient. Governments create this problem by making it legal to do these things and then making it difficult - so of course data gets misused. If they want it to be legal, then provide a solution to the problem. If they don't want to provide a solution, then make it illegal.
Usania reliance on SSN (with its Schroedinger nature if being both public and private at the sane time) while fighting tooth and nail any sane ID document is wholly amusing ... (same applies to Brits and, supposedly rest if the anglosphere)
That won’t work out so well if the Pritzger Justice Dept subpoenas that organization in 2029 looking for evidence of Trump-driven discrimination. Given the long time periods involved in the academic world discrimination investigations could easily request 20 or even 30 years of data.When I started my current job (working with HR/recruitment systems), I was kinda annoyed that someone decided that all the recruitment data from pre-2023 should be wiped. That's some great analytics gone!
These days, I thank that person daily. Saying "nope, deleted" simply answers every question. That data has never been useful. I'm tempted to just wipe the database every 12 months.
Same here, late 90's I took the SAT and possibly checked the box to send my scores to Columbia but otherwise never applied or had any contact with them. Received a letter to my childhood home where luckily my family still lives. There really should be a financial punishment for hoarding data of folks with no affiliation with the school for close to 30 years.I'm in the same boat as Ms Belanger -- I received a breach notification from Columbia by mail in early February, but have no obvious connection (enrolled or employed), so I was like "whuh?" That the root cause is SAT results or applications, from the early 1990s, sounds plausible -- I may still have a relevant record in my deep hardcopy archives that would confirm the hypothesis.
Re: traces, I occasionally get breach notices from unfamiliar entities who, upon investigation, do have an connection, but it's via a subcontractor or they've been renamed three times. FWIW, as advised by @Spaghettified above, I have frozen my credit reports (and those of my parents) as a best-practices precautionary measure.
I was going to say, it was on both my college id and my drivers license when I lived in Illinois.SSNs were driver’s license numbers in some states in the 90s still.
Every soldier going through basic training shouts their social every time they eat in a cafeteria or go through the gas chamber.
Where did we go wrong treating them like private information? They never have been.
The gas chamber I can understand, but why the cafeteria?Every soldier going through basic training shouts their social every time they eat in a cafeteria or go through the gas chamber.
Or in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying BEWARE OF THE LEOPARD.Data retention? Purging of backups? Please. Those policies are on paper in a three-ring binder somewhere, piled in cardboard printer paper boxes stored ten layers deep in a closet nobody uses.
Mine is in both of those, at least three separate (disclosed) breaches of my state's Treasury department, and more.At some point we really need to let go of thinking SSNs are private data. Raise your hand if you think your SSN is NOT in the Equifax and National Public Data torrents.
I served in the Navy and I don't recall having to spit out my SSN in the boot camp chow line... But we were required to produce it on demand, and it was demanded frequently because very few recruits showed up to boot camp with it already memorized.The gas chamber I can understand, but why the cafeteria?
This squid disagrees. No need whatsoever for the drill sergeant or company commander to breathe down your neck.Sometimes I’ll finish my second plate of food when my daughters have only taken a few bites from theirs. They’ll ask me how in the world I manage to eat that fast. My reply: “High speed military training”. Nothing like eating your meal with a drill sergeant breathing down your neck to motivate you.
And if you have kids, freeze theirs too. It's a total PIA with paper copies via snail mail, but after the Instructure/Canvas school software breach a couple of years ago I just bit the bullet and did theirs too.Don't forget to keep your credit frozen friends, could save you a ton of trouble in case of identity theft
Doesn't the standard require that it show your citizenship status to qualify as RealID? Can't imagine any racist cops ever looking at that to decide if they want to single you out for harrassment because you're a "only" a legal resident, not a citizen?RealID is just a stamp on your state ID showing that the state met some minimum standard in verifying your identity. What is it you think RealID could be “used for” that you’re so worried about?
Only in some states. Which is why the SAVE Act was such a big deal.Doesn't the standard require that it show your citizenship status to qualify as RealID? Can't imagine any racist cops ever looking at that to decide if they want to single you out for harrassment because you're a "only" a legal resident, not a citizen?
The point here isn't the release of SS numbers, genius. The point is that no decently run IT organization should be maintaining non-critical (let alone totally useless) information on anyone, ever. This is just common sense data hygiene, which Columbia's IT is apparently too incompetent to follow.I understand your curiosity, but I really hope you did this for the sake of writing this story. Because otherwise all this research just seems like a real waste of time like who knows where the data breach came from these days. Who knows how they got your social. I tried to change my password on some service the other day and they wouldn’t let me choose it because I use the same password for a different site and they told me it had already been hacked somehow. Whatever. Your Social Security number is already for sale somewhere. That horse left the barn a long time ago. As long as nobody’s actively stealing from you, it’s not worth it