5 ms·
U.S. Internet leaked years of internal, customer emails
- deleted 3y ago[deleted]
- gfs 3y ago> “The feedback from my team was a issue with the Ansible playbook that controls the Nginx configuration for our IMAP servers,” Carter said, noting that this incorrect configuration was put in place by a former employee and never caught. Even if this were true, that is a pathetic response.
- toomuchtodo 3y agoThis would've been found in even the most cursory of penetration tests performed by a competent practitioner. I am curious if any have been done.
- dylan604 3y agoIt also needs to be part of any regression testing against new releases. Doing it once against current code does nothing other than say "right now we're okay". I know. I've personally been burned by assumption that what was tested previously is assumed to still be good now.
- blincoln 3y agoThat's a very valid concern, but the larger one for me is that it implies that their IMAP servers are sitting right on the internet (no firewall/load-balancer/reverse proxy/whatever), or that they've automated their infrastructure so much that network-level security controls are essentially bypassed because any services in the Ansible definition are assumed to be authorized/intentional, or that someone intentionally added this one as a ham-fisted backdoor into customer email.
- dboreham 3y agoI've consulted at a couple of places with similar security risks to this, where I've suggested that we deploy automated testing (perhaps it might be called monitoring since it targets production services) that their auth checks are working -- e.g. that an unauthenticated client can not access a supposedly secure resource, and that authentication as user A does not allow access to data belonging to user B. Never had any takers.
- jackpirate 3y agoI don't see how that would have helped in this case. This was not a resource at a known location that was supposed to be only available to logged in users. This was a resource that the admins didn't know about available at an unknown url that was exposed to the public internet due to a configuration error. Are you going to write a test case for every possible url in your server to make sure it's not being exposed? Something that could work is including a random hash as a first hidden email inside of every client, and then regularly searching outbound traffic for that hash. But that would be rather expensive.
- toomuchtodo 3y agon=1, head of a security at a fintech. We perform automated scans of external facing sensitive routes and pages after deploys, checking for PII, PAN, and SPI indicators, kicked off by Github Actions. We also use a WAF with two person config change reviews (change management), which assists in preventing unexpected routes or parts of web properties being made public unexpectedly due to continuous integration and deployment practices (balancing dev velocity with security/compliance concerns). Not within the resources of all orgs of course, but there is a lot of low hanging fruit through code alone that improves outcomes. Effective web security, data security, and data privacy are not trivial.
- 15457345234 3y ago> fintech You keep your business logic and account handling code on github? Not an accusation, genuinely asking.
- 1024core 3y agoFrom the screenshot alone, a Google search for "link:usinternet.com link:utue.org link:uthelaw.com" (for example) should get you the website. But since there's no match, I'm assuming Google's crawlers never found the page.
- karaterobot 3y agoThis was a confusing headline until I learned that U.S. Internet Corp is a regional ISP. I wonder if it wouldn't be worth editing the headline to make it clearer.
- dylan604 3y agoThere was also a recent headline saying the US Military leaked data for 20k people. So I thought this was a bad edit to that. I love finding companies with truly poor names like this though. It helps weed them out
- willcipriano 3y agoI figured Krebs wouldn't be so bold to call lobbyists customers.
- webninja 3y agoPerhaps edit the headline from “U.S. Internet” to “U.S. Internet Corp.”
- wolverine876 3y agoMany businesses limit retention by default, deleting everything older than (e.g.) 30 days unless the user saves them. They do it to limit liability, but perhaps that should be the law for every business: As part of the responsibility as a custodian of other people's information, you need to minimize retention: Remove PII and other high-risk information asap, extract data needed for the long-term (rather than retaining the entire original record), delete the entire record when it's no longer used (easily determined by how often it's used). In the networked, electronic era, data becomes much more powerful and control of it becomes much more elusive. That increases our responsibility.
- lazide 3y agoBut then how will we get juicy emails in the press to drag people through the mud, years after someone notices a problem? Think of the clicks man!
- dylan604 3y agoPreserving email is different than anything being discussed here though, and it actually can be a business requirement.
- lazide 3y agoIt's literally the topic we're discussing? Something deleted years ago can't be accidentally leaked or used against you unless someone thought to do so within the 30 day window. That's literally why the '30 day purge' exists to 'limit liability'.
- dylan604 3y agobut some business requirements says you CAN'T delete email because of some regulation is my point. that's specifically aimed at catching the stupid criminals that say things like "please shred all of the incriminating documents before we have to turn them over in discovery". or the emails that gets interrupted in a suspect thread that says "please call me" so that it's specifically not written. we're sort of talking past each other
- lanthade 3y agoAs a USI fiber customer (which has been a great service) the most concerning thing to me about the CEO response is that he didn’t know who he was talking to and then asked about hiring them. Considering that Krebs On Security is no small player or recent arrival to the scene this is a huge blunder. I know you can’t expect a CEO to know in depth all things but there should be people right under him who could have brought him up to speed quick. This is a technology company after all, not some simple widget maker.
- germinalphrase 3y agoI've been a huge advocate for USI, but I agree.
- ls612 3y agoYeah I have USI gigabit and it just works (tm) I’ll be sad when I get my PhD and leave the area.
- krebsonsecurity 3y agoPossibly useful info: A list of customer domains affected. https://docs.google.com/spreadsheets/d/1wgKe1VrfNF8Afav1aJtMrZDeNuqBtSFku58fWlCBp6Q/edit?usp=sharing https://docs.google.com/spreadsheets/d/1wgKe1VrfNF8Afav1aJtM... One caveat: This list should not be considered exhaustive or complete by any means. e.g. changing the URL slightly by incrementing or decrementing a number in the URL caused a slightly different set of customers to be listed. I didn’t have a chance to go through it all before they took it down (note to self: pillage BEFORE burning).
- 1970-01-01 3y agoSo their Privacy Shield statement strongly hints to me that they're in much deeper trouble than they know. They probably need new lawyers. https://usinternet.com/privacy-policy/ https://usinternet.com/privacy-policy/ https://en.wikipedia.org/wiki/EU–US_Privacy_Shield#Swiss–US_Privacy_Shield https://en.wikipedia.org/wiki/EU–US_Privacy_Shield#Swiss–US_...
- greatgib 3y agoSomething not very clear from the title is that US internet corp have a subsidiary specialized in being a cloud gateway for "securing email" for US Internet Corp but also all kind of external customers. And this is the entity, the gateway, that leaked all the emails. In my opinion it is a huge epic fail when you pay a service to secure your emails that leaks them...
- olliej 3y agoHooray for intentionally confusing brand names creating terrible sounding headlines :D [edit: it reminds of I think McDonalds being told off in NZ for using "All Beef" branded hamburger patties or something in the 90s or something?]
- thelemur 3y ago[dead]