I think I know the problem, they probably don't have one of those 25 minute annual data governance trainings to teach/remind them how to handle PII.
IRS accidentally releases taxpayers’ private data again
51–60 of 69 posts
Re: IRS accidentally releases taxpayers’ private data again
#52Re: IRS accidentally releases taxpayers’ private data again
#53I'm less concerned about the occasional unintentional f'up, and much more concerned about the targeted and politically motivated intentional leaking of information.
Are you saying “I’m not concerned about data leaks that I could potentially be affected by and have my own personal information leaked through as much as I am about a celebrity billionaire getting their tax records released after years of litigation and after lawsuits going all the way to the Supreme Court (or others like him)?”
Re: IRS accidentally releases taxpayers’ private data again
#54> "The agency is reconsidering its relationship with the contractor Accenture on this project, according to a person familiar." Any time I start to feel that Impostor Syndrome creeping in, I need to remind myself that there's someone who's working at Accenture probably earning 2x or 3x what I am, who gets to fuck up big not once but _twice_ doing the same wrong thing.
Doesn't Accenture offshore a lot of its work to India and other third-world countries? So the Accenture engineer probably gets paid a lot less than you. Edit: According to Wikipedia, yes: > In 2015, the company had about 150,000 employees in India,[31] 48,000 in the US,[32] and 50,000 in the Philippines.[33] Edit2: s/outsource/offshore, thanks. What I intended was: companies hire Accenture to outsource their developm…
A developer in the U.S. has far better employment options.
Re: IRS accidentally releases taxpayers’ private data again
#55Accenture is the contractor responsible.
IMO the resposibility is entirely on IRS. They chose the contractor, they wrote the legal terms and conditions, they vetted them out and they presumably did the due diligence for security.
Contractors come and go, and the government isn’t supposed to micromanage them - that’s one of the features theoretically making them less expensive than staff - so those qualified people may never be seen after the start of the project, or they might be in some kind of “oversight” capacity where they’re quintuple booked theoretically keeping the much cheaper people doing the actual work from failing too badly.
On the government side, they likely don’t have qualified technical staff (or enough of their time) after years of “cost savings” where every dollar cut from the staff budget corresponds to 2-3 dollars going to contractors. That means that problems will progress further, especially because the contract PM isn’t going to say that the contract developers are doing terribly after months of saying sprint velocity is good. Even if they’re on different contracts, the odds are good they’ve either worked together before or don’t want to rule out future work at the other company.
So, things careened down the tracks and now people are realizing that the green lights on dashboards were in fact optimistic. The government can ask for things to be fixed but if there’s pushback, they risk _every_ project on that contract and it’s expensive because they have to show some kind of malfeasance to get money back or possibly even to stop wasting more (want to bet there’s never been any scope creep which could be blamed?). It’s _much_ easier to try seeing whether the claim that this was a one-time mishap was true than to deal with all of that.
Any time you see something like this, it’s always possible that you have someone totally failing to do their job but it’s far more likely that you’re seeing a bunch of people trying to do their best with a system they know isn’t effective but which they have no direct means to improve.
Re: IRS accidentally releases taxpayers’ private data again
#56Earlier quoted context omitted.
> So the Accenture engineer probably gets paid a lot less than you. Given that roughly 1/3 of Accenture employees are in the US, is there any evidence for you to believe that this was someone outside the US?
even in the US accenture's IT is not known for high wages. The only reason people stay there is being enslaved by US work visa like L-1, which allows Accenture to pay below market wage and keep employees on a short leash. You won't be able to find a single american software engineer in Accenture, because of work conditions and wages, all engineers are foreigners on visas. The only americans there are salesmen and adm…
That is false.
You do know that legally Accenture has to go above market wages in that locale for H1B workers?
Re: IRS accidentally releases taxpayers’ private data again
#57Earlier quoted context omitted.
Are you saying “I’m not concerned about data leaks that I could potentially be affected by and have my own personal information leaked through as much as I am about a celebrity billionaire getting their tax records released after years of litigation and after lawsuits going all the way to the Supreme Court (or others like him)?”
No. I was talking about https://www.golocalprov.com/news/hedge-fund-manager-sues-irs...
Re: IRS accidentally releases taxpayers’ private data again
#58Earlier quoted context omitted.
I don't believe this is correct, which is why competing leagues pop up every few years. You might be thinking of Major League Baseball?
A trust or monopoly doesn't prevent competitive companies forming, just makes it very hard for them to succeed. Baseball has an exemption due to a court case, though their hiring cartel was broken in the courts, resulting in free agency (same for NFL, with the Roselle(?) case). But the important one is all about the money: monopoly control over monetization of broadcast. I direct you to 15 U.S. Code § 1291 which you…
Re: IRS accidentally releases taxpayers’ private data again
#59Earlier quoted context omitted.
> US Football league NFL, are "non-profit" This is not true now, and arguably never was (at least not with the intention it's generally applied). The NFL relinquished its tax exempt status in 2015, but even before that the NFL was not a 501(c)(3) but a 501(c)(6) (a trade organization) -- for interests of fairness (proven more necessary recently by actions of the Washington Commanders) the NFL collected ticket moneys…
> This is not true now, and arguably never was you mean to say in your first breath that the 501(c) series of US IRS tax structures are not called "non-profit" but then in the next breath confirm that the NFL was in fact 501(c)(6) ? I do not say I was "mad" so, let's not include that as a summary of what I wrote, eh?
If that wasn't what you were trying to do, then I apologize for letting my confirmation bias get in the way of more accurately addressing the criticism.
Re: IRS accidentally releases taxpayers’ private data again
#60I think I know the problem, they probably don't have one of those 25 minute annual data governance trainings to teach/remind them how to handle PII.