News for hackers. Stuff that matters.
Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @12:17PM (#15207717)
This is a problem, yes, but I think it's worth keeping the perspective that it's a practically universal problem.

That doesn't mean we should be letting Equifax off the hook. But nobody should pretend that RCE on an on-prem webserver wouldn't be game-over, for the entire internal network, across the majority of the Fortune 100.

We have as a society chosen to trade the security of our personal information for greater and cheaper access to products and services. Nobody on HN will like that fact (at least, as stated bluntly like that; plenty of them do like the increase to their earnings capability that results from that tradeoff), but it's generally true.

Re:Apache Struts Statement on Equifax Security Breach by harshreality on Saturday September 09, 2017 @01:51PM (#15208211)
> But nobody should pretend that RCE on an on-prem webserver wouldn't be game-over, for the entire internal network, across the majority of the Fortune 100.

You certainly have more experience with this than the vast majority of the rest of us, but with that kind of data on millions of people, shouldn't it be, and why isn't it, standard practice to put servers storing that data behind an extremely limited API, with a firewall in place to monitor queries and responses and severely rate-limit or stop additional traffic if something suspicious happens, until the monitoring people can take a look?

Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @01:53PM (#15208225)
Because that not only adds operational expense but also requires engineering teams to have a level of systems engineering expertise and diligence that virtually no line-of-business software project has.
Re:Apache Struts Statement on Equifax Security Breach by ethbro on Saturday September 09, 2017 @02:19PM (#15208382)
*adds operational expense without a counterparty willing to pay for that expense

Those with data on Equifax's servers aren't Equifax's customers, so other than "not having a PR cluster&#@_" economic incentives are not aligned to prevent this.

Re:Apache Struts Statement on Equifax Security Breach by sillysaurus3 on Saturday September 09, 2017 @02:27PM (#15208439)
It's probably best to treat Equifax specially rather than making an example out of them for the rest of the industry to follow.
Re:Apache Struts Statement on Equifax Security Breach by concede_pluto on Saturday September 09, 2017 @02:48PM (#15208555)
If they aren't qualified to design with least privilege, what are they qualified for, beyond maybe cat videos?
Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @03:01PM (#15208615)
I've spent about half my professional career finding vulnerabilities in the software of developers who are convinced they're "qualified to design with least privilege".
Re:Apache Struts Statement on Equifax Security Breach by pacaro on Saturday September 09, 2017 @02:31PM (#15208467)
And, even if you know what you are doing, this is intrinsically a hard problem, you need to know exactly what information should be accessible to each server
Re:Apache Struts Statement on Equifax Security Breach by stickfigure on Saturday September 09, 2017 @06:03PM (#15209391)
You can add all the security layers you want, but if the web server needs to display a piece of information, the web server must have access to that information. The keys must be in the car somewhere.

Also... even with multiple layers, what do you think the backend stack would be? Unless it's built by a separate team deliberately using a different technology platform, you're stuck with the same Struts (or whatever) vulnerability.

Re:Apache Struts Statement on Equifax Security Breach by noir_lord on Saturday September 09, 2017 @01:09PM (#15207949)
> But nobody should pretend that RCE on an on-prem webserver wouldn't be game-over,

The system/network I inherited at new job it absolutely would be, it won't be in a year though.

We aren't a fortune 500 but there are simple, practical things you can do to limit the damage an RCE on a webserver can actually do.

Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @01:14PM (#15207978)
Everybody can lock down a small network. Empirically, very few security teams can manage that for large networks with large numbers of stakeholders.
Re:Apache Struts Statement on Equifax Security Breach by chris_wot on Saturday September 09, 2017 @01:41PM (#15208140)
Then systems of governance are utterly broken and management should step in to enforce remedial actions, ASAP.

But I disagree, security teams can and should manage large networks with large numbers of stakeholders.

Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @01:52PM (#15208219)
If they can, why don't they? How many annual site-wide pentests have you heard of that failed hard? And those are the people savvy enough to conduct annual site-wide pentests!
Re:Apache Struts Statement on Equifax Security Breach by michaelt on Saturday September 09, 2017 @03:16PM (#15208683)

  If they can, why don't they?
Insufficient incentives, either caused by inadequate regulation or a belief the regulation won't be enforced.

Think of the standards of network security and software validation used by, say, a Certificate Authority to keep their root certificates safe. Or by Google to secure GMail. Equifax just hasn't made reaching that standard their highest priority.

Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @03:42PM (#15208836)
Certificate authorities to keep their root certificate keys safe... hmm... do go on.

:)

Google would be most people's exception to the rule I'm talking about here, having as they do one of the world's greatest information security teams. And Google has had major incidents!

Re:Apache Struts Statement on Equifax Security Breach by extrapickles on Saturday September 09, 2017 @02:22PM (#15208411)
A common pentest isn't geared towards discovering architectural weaknesses like all Americans PII is one popped webserver away from disclosure.

What's needed is an architectural security review, which is even rarer than people conducting an annual pentest.

Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @02:32PM (#15208471)
What's your point? I'm saying, sitewide pentests almost always succeed.
Re:Apache Struts Statement on Equifax Security Breach by chris_wot on Saturday September 09, 2017 @03:09PM (#15208648)
So they keep going till they fail?
Re:Apache Struts Statement on Equifax Security Breach by wglb on Saturday September 09, 2017 @05:03PM (#15209140)
The target for most network pen tests is to obtain domain by noon of the first day. Generally, they keep going until they succeed and/or someone in the chain cries uncle.
Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @03:42PM (#15208838)
I don't understand your question. When I say a pentest succeeds, I mean that the testers succeeded in compromising their objective.
Re:Apache Struts Statement on Equifax Security Breach by pas on Sunday September 10, 2017 @09:19AM (#15212100)
Parent post is saying that that should constitute a failed audit. And it should be repeated as long as a 2 week effort by a pentesting team yields results.
Re:Apache Struts Statement on Equifax Security Breach by chris_wot on Sunday September 10, 2017 @06:48PM (#15214709)
So they plug the security holes, arrange a new pentest.
Re:Apache Struts Statement on Equifax Security Breach by lomnakkus on Saturday September 09, 2017 @02:28PM (#15208445)
> Everybody can lock down a small network.

You're too optimistic :(

Re:Apache Struts Statement on Equifax Security Breach by justicezyx on Saturday September 09, 2017 @01:03PM (#15207922)
You claim that you keep my data safe. You missed it. It's not a trade off, it's a failure on your part...
Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @01:13PM (#15207973)
It very much is a trade-off, because the expense that would go in to making a large enterprise network reliably secure would be extreme, and would drive prices up, retard economic growth, and most likely result in software engineers making substantially less money.

I'm not saying you should like the tradeoff, or that the existence of the tradeoff doesn't have implications for how we should regulate banks and credit ratings agencies. I'm just saying that if you think there's some other CRA that has reliably protected its IT assets from threats like this, you're wrong.

Re:Apache Struts Statement on Equifax Security Breach by abiox on Saturday September 09, 2017 @01:32PM (#15208090)
> It very much is a trade-off

this seems like goalpost moving. first you said 'we as a society', yet there isn't much 'we' in this. it doesn't seem to me that people (the general public) are properly aware at just how vulnerable they are. they haven't therefore 'decided' that this is okay.

> the expense that would go in to making a large enterprise network reliably secure would be extreme, and would drive prices up, retard economic growth

what is this based on?

Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @01:36PM (#15208110)
Part of living in a society is recognizing that you still belong to it even when it makes decisions you don't agree with.

To more directly answer your question, though, consider a regime of general commercial liability for security incidents caused by failures of engineering (which Equifax is an example of). What would it be like to bring new products to market under such a regime? How much more difficult would it be to enter the field? How much more difficult to hire qualified people? What would that do to the prices of things made possible largely through software engineering work? When the prices of things increase, they're put out of reach of more consumers; markets constrict. What does that do for employment? What does reduced employment in a sector do to wages?

I'm not saying this to justify insecurity. I'm ambivalent about the tradeoffs our society has made on these issues. I just don't think we tend to grapple with them honestly on HN.

Re:Apache Struts Statement on Equifax Security Breach by chris_wot on Saturday September 09, 2017 @01:45PM (#15208168)
If that new product exposes scads of private data, then it's rather irrelevant. These credit scores aren't something most people signed up for, they are a product for financial lenders and not for the direct consumer.
Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @01:54PM (#15208227)
Like I said, the fact of the tradeoff probably does have implications for how we regulate companies like Equifax.
Re:Apache Struts Statement on Equifax Security Breach by Drdrdrq on Saturday September 09, 2017 @02:40PM (#15208508)
Sorry, I have to disagree. Performing regular pen testing is costly, so skiping it is a tradeoff. Employing a team of security engineers is also costly and there aren't enough of them to make that viable for all companies. Tradeoff. But putting such data in direct access of a web server, a single RCE away from exposure? That's not a tradeoff, that's negligence.
Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @03:02PM (#15208619)
You've lost me. I think you may have misunderstood my point about pentests. I mean "success" from the perspective of the testers: you asked me to own your network up, and I succeeded.

My point is: the most savvy companies contract annual sitewide pentests, in addition to all the other stuff they do to secure their networks, and virtually all of those pentests "succeed" (from the perspective of the testers).

Further: not only have I never personally been on an internal network pentest (the kind where you start with an IP "behind the firewall" and nothing else) that failed, but I'm not sure I've even ever heard of one that failed. I'm certain there are some networks that are so resilient that they've stymied a competent internal pentest --- but again, I wouldn't know which one, because I've never heard of that happening.

Re:Apache Struts Statement on Equifax Security Breach by CJefferson on Saturday September 09, 2017 @03:07PM (#15208636)
We've dealt with this for hundreds of years.

Your car kills people? Your biscuits are mouldy, or full of lead? We have strict rules, and companies that don't follow then end up in serious trouble.

Re:Apache Struts Statement on Equifax Security Breach by briandear on Saturday September 09, 2017 @02:42PM (#15208520)
Apple’s payments systems haven’t been breached, nor do I recall a breach of Stripe and I would bet my teeth that their security is far better and more proactive than Equifax — a company that’s entire business is based on data brokering. If they can’t handle the “cost” of correct security or, at the very least keeping dependencies updated, then they ought not be in business. If security makes it expensive, then perhaps there should be more competition? The credit bureaus have a near monopoly so they don’t have to be aggressive about security as a Stripe might need to be. That complacency and just general malfeasance means they ought to be sued out of existence. I bet any number of Silicon Valley startups have better security than Equifax — at far lower budgets. It isn’t a cost issue — it’s a competency one.
Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @02:49PM (#15208556)
More of my former colleagues work on the Stripe security team than at any other firm (besides NCC, our acquirer). They do a great job. But Stripe is a tiny company with very few products and a unified development culture with a management team organized around bringing technology products to market.

And they aren't perfect. They will eventually screw something up.

Comparing Stripe to Equifax is unreasonable. Equifax has about 10,000 employees. Stripe has less than 1,000.

And, once again, please don't try to win an argument by putting me in the position of defending Equifax. That's not what I'm doing. My point is that practically every company of Equifax's size has similar problems.

Re:Apache Struts Statement on Equifax Security Breach by briandear on Saturday September 09, 2017 @06:20PM (#15209459)
If Equifax is too big to have their shit together, they ought not be allowed to store sensitive data. If this were a HIPAA situation, they’d be facing a statutory penalty of about $10,000 per record.

Apple, Facebook and Google have far more data under their control than Equifax and they seem to take security far more seriously than Equifax. The Apple InfoSec team is extremely aggressive — InfoSec is ingrained in Apple culture. I am skeptical that Equifax takes security as seriously.

Being “big” or “other large companies have the same problem” isn’t an excuse. They have no problem fucking people’s credit by reporting inaccurate information — they should be held accountable since that information has such severe consequences.

My hatred of Equifax runs deep because they reported 7 state tax liens on my credit report that weren’t mine and were from a state in which I never lived. Despite providing all kinds of documentation, I ultimately had to sue them. I won the case and a bit of money, but the point is, they were willing to have a team of lawyers go to court against me and tie it up in court for several years — to defend something they knew was wrong. I even had letters from the state tax agency attesting to the error and they still had to be sued to fix the information. If their IT security is as arrogant as the rest of the company, then this breach doesn’t surprise me.

How is that relevant? It’s highly relevant because they have demonstrated a willful disregard for facts. They demonstrate an arrogance based on their near-monopoly power over people’s lives. They don’t care about accuracy — they care about the appearance of accuracy. It follows that they aren’t good stewards of the information with which they have been trusted.

The fact that they are too big and IT security is “hard” — that’s an excuse. General Motors might have bad IT security (I don’t know,) but they also don’t control the financial lives of almost every American.

If they are so big that they can’t handle it, then they ought to be shut down.

To be clear, I don’t have a problem with credit reporting. I have a problem with the fact that Equifax is going to survive this. Some big judgement happens, they’ll file for bankruptcy, they’ll reorganize and be right back at it.

Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @06:31PM (#15209496)
No, they would not. HIPAA providers have suffered mass breaches repeatedly in the past. HIPAA is so toothless large firms just set aside cash to pay the fines rather than invest millions to speculatively comply.

Apple is great. I like Apple's product security team and I like Apple IS&T. But so what? I'm not denying that there are 10-20 firms in the world that have world-class security teams. I'm denying that those teams are in any sense an industry norm, even in the technology industry.

Re:Apache Struts Statement on Equifax Security Breach by justicezyx on Saturday September 09, 2017 @05:32PM (#15209259)
I am not sure how can you justify the company's childish security practice.
Re:Apache Struts Statement on Equifax Security Breach by tedmiston on Saturday September 09, 2017 @01:30PM (#15208075)
"Safe" is full of grey area, just like security isn't binary.
Re:Apache Struts Statement on Equifax Security Breach by bradleyankrom on Saturday September 09, 2017 @02:21PM (#15208403)
> We have as a society chosen to trade the security of our personal information for greater and cheaper access to products and services.

Agree, and it's one of the reasons I generally try to avoid using products that are low-cost or free (the other reason being questionable sustainability, regardless of funding). At some point, products need to break even or they will go out of business. As a customer, you are always paying for the product in some form or another. For something that's free, you might be paying with your personal information now... or later if running on a low budget has caused the product developer to cut some corners when it comes to infosec.

Re:Apache Struts Statement on Equifax Security Breach by nodamage on Saturday September 09, 2017 @02:50PM (#15208560)
Shouldn't we hold credit reporting agencies to a higher standard than the rest of the Fortune 100 though? After all, they store sensitive personal information about the vast majority of US adults.
Re:Apache Struts Statement on Equifax Security Breach by tptacek on Saturday September 09, 2017 @03:00PM (#15208610)
Maybe? I've said that elsewhere on the thread. But I'm not sure. Every big company tends to hold all sorts of hugely sensitive information.