News for hackers. Stuff that matters.
Re:This Obamacare contractor doesn’t take security seriously by eigenvector on Friday October 25, 2013 @12:44PM (#6612700)
> In Slavitt's defense, data security may not have been an explicit feature of QSSI's federal contract

Coming from the construction industry, there isn't a contractor in the world that cares about things which aren't in the contract. Implementing features which the client has not asked for, in the design-bid-build world of public-sector contracting, just means you will lose the bid to a lower bidder who won't do those extras.

Re:This Obamacare contractor doesn’t take security seriously by greenyoda on Friday October 25, 2013 @01:33PM (#6613099)
"Coming from the construction industry, there isn't a contractor in the world that cares about things which aren't in the contract."

In the construction industry, a contract might not explicitly say that the building has to comply with local building, fire and electrical codes - that's taken as a given. To construct a web site that deals with sensitive information without taking security into account is like building a skyscraper with no fire exits - not something that any honest or competent builder would do.

Re:This Obamacare contractor doesn’t take security seriously by lmkg on Friday October 25, 2013 @01:57PM (#6613306)
Yes, but those are actual codes. In fact, that's why they're codes. Contractors won't do more than they're legally required to (nor should they be expected to), so safety features were made legal requirements.

Relying on the honesty or competency of your contractors go above & beyond their requirements is an inefficient and unsustainable solution in a free market. This is a clear case of Moral Hazard: In the same way that bad money drives out good, corner-cutting organizations out-compete honest ones.

Re:This Obamacare contractor doesn’t take security seriously by benmanns on Friday October 25, 2013 @02:04PM (#6613366)
What about reputation? I regularly do more than the legal minimum for my clients and there are companies who do the same for me. Meeting the legal minimums only makes sense for commodities, e.g. this salt is 99.5% pure. This software is 99.5% "secure"? This software is 99.5% "complete"?
Re:This Obamacare contractor doesn’t take security seriously by sanderjd on Friday October 25, 2013 @02:29PM (#6613553)
It seems to me that reputation works better in the free market than the government "market". I don't know why that is, but I suspect it has to do with the same rules for the bidding process that are meant to decrease corruption, but also tend to entrench contractors.
Re:This Obamacare contractor doesn’t take security seriously by pessimizer on Friday October 25, 2013 @02:18PM (#6613472)
I don't think that most RFPs require or make many allowances for "reputation."
Re:This Obamacare contractor doesn’t take security seriously by eigenvector on Friday October 25, 2013 @05:34PM (#6614790)
True, but quantifiable aspects of reputation (like having successfully completed similar projects in the past) can be part of a pre-bid qualification process. This is common for large or complex projects.
Re:This Obamacare contractor doesn’t take security seriously by quesera on Friday October 25, 2013 @02:24PM (#6613521)
> In the construction industry, a contract might not explicitly say that the building has to comply with local building, fire and electrical codes

In the public construction industry, every contract includes that language. It's superfluous, because no contractor that wants to keep his license violates those codes (all construction is inspected by local authorities).

Furthermore, in construction, those codes exist and are easily incorporated into contracts by reference, even non specifically ("all work will comply with local building codes and statutes"). Also, the liability for non-compliance, even if undetected by inspectors, is massive.

In the tech industry, I've seen "work will be performed to professional standards and best practices" and other such meaningless clauses, intended to give the contractee some standing for complaint if they aren't happy later, but it's hard or impossible to measure compliance to generic standards that mostly don't exist.

This is one reason why Engineers say that dorking around on computers isn't Engineering. They do have a point.

Re:This Obamacare contractor doesn’t take security seriously by dragonwriter on Friday October 25, 2013 @02:34PM (#6613586)
> Furthermore, in construction, those codes exist and are easily incorporated into contracts by reference

FIPS actually exist and are easily incorporated into contracts by reference.

Re:This Obamacare contractor doesn’t take security seriously by lrobb on Friday October 25, 2013 @01:58PM (#6613318)
> In the construction industry, a contract might not explicitly say that the building has to comply with local building, fire and electrical codes - that's taken as a given.

That's because you have to have a license to perform that work. If you don't meet the code, you don't keep your license.

This is one of the reasons why McConnell et al have argued that we need professional licensure. Licensed Professional Engineers can lose their licenses if they sign off on half-assed plans.

Re:This Obamacare contractor doesn’t take security seriously by thezilch on Friday October 25, 2013 @01:54PM (#6613274)
Not "would do" but "could do;" you can't build, honest and competent or not, without local code-compliance. Perhaps the same should be true for the web; perhaps there should be damages for poor security; government or not.
Re:This Obamacare contractor doesn’t take security seriously by dragonwriter on Friday October 25, 2013 @02:35PM (#6613593)
> Not "would do" but "could do;" you can't build, honest and competent or not, without local code-compliance.

You can, and people do, and they are cited for it when caught.

Likewise, there are mandatory standards for Federal IT systems, particularly in the area of security.

Re:This Obamacare contractor doesn’t take security seriously by growupkids on Friday October 25, 2013 @01:24PM (#6612993)
Which is also true in government contracting. What's odd is that security requirements are mandated by law, FISMA, so the government is supposed to require that systems meet the FISMA requirements. You shouldn't be able to get an ATO without it, unless the management of that agency "accepts the risks" (SES levels only, gS personnel can't do this) and waives the vulnerabilities.

So if I had to guess, if they didn't protect the data then it's likely those controls were notin place everyone knew they were not and the agency heads said it was ok. All fed systems get tested, and the system certifier is supposed to be an impartial reporter of the facts (these are the vulns, missing controls, risks, etc. and they are almost always impartial). They report those to the DAA along with a recommendation to approve or not approve the system to operate. Given how important this system was, I highly doubt anyone would not have issued the ATO no matter what vulns it had. And that's not to pick on this system, sadly slap dash rush ATOs happen far too often in the USG.

If you spend a ton of time and money on a system, execs in the USG have their careers on the line to show that wasn't wasted and since they don't understand security it all seems like science fiction to them. They almost always ATO the system. And why not, no USG exec has ever been fired for having a poorly protected system broken into.

Re:This Obamacare contractor doesn’t take security seriously by dragonwriter on Friday October 25, 2013 @01:27PM (#6613019)
eigenvector: Implementing features which the client has not asked for, in the design-bid-build world of public-sector contracting, just means you will lose the bid to a lower bidder who won't do those extras.

growupkids: Which is also true in government contracting.

"Public-sector" = "government".

Re:This Obamacare contractor doesn’t take security seriously by smackfu on Friday October 25, 2013 @01:20PM (#6612963)
And if you go beyond the contract, and stuff doesn't work, you get blamed and have to eat the cost of fixing it.
Re:This Obamacare contractor doesn’t take security seriously by nraynaud on Friday October 25, 2013 @02:19PM (#6613484)
actually security is not a feature, but a constraint. It doesn't bring the user anything, but it absence would be a problem for secondary reasons (that might be important in the grand scheme of things).

Imagine a bank (well just an account), on the functional level, you just need to deposit and withdraw money. The fact that they have to secure it is a huge constraint, but at the functional level we're not far from a trash can, a parking lot or a gas tank.

Re:This Obamacare contractor doesn’t take security seriously by gohrt on Friday October 25, 2013 @01:19PM (#6612956)
Right. A solution is for the government to develop a series of security standards that cover a wide range of IT projects, and each project should declare that "implementation must conform to Security Level X, Category Y"
Re:This Obamacare contractor doesn’t take security seriously by dragonwriter on Friday October 25, 2013 @01:36PM (#6613128)
> A solution is for the government to develop a series of security standards that cover a wide range of IT projects, and each project should declare that "implementation must conform to Security Level X, Category Y"

Well, you'd think so, which is why that's essentially already mandated:

http://en.wikipedia.org/wiki/Federal_Information_Security_Ma...

http://en.wikipedia.org/wiki/Federal_Information_Processing_...