7 ms·
Move Over, Software Developers – In Cybersecurity, the Government Wants to Drive
- pipo234 3y ago> Like the White House, the EU confuses its stated goal of helping the software market work more efficiently with an attempt to control what can be in the market. Control would make sense if governments had a clear, flawless track record of developing software; that state of perfection could be attributed (solely) to a bunch of existing government guidelines and the only problem would be that developers fail to meet those guidelines. We're not there.
- piva00 3y ago> Control would make sense if governments had a clear, flawless track record of developing software; Why? The government does not have a clear, flawless track record developing food, nor medicine, still it controls and regulates them for the safety of society. You can't demand absolute knowledge as a pre-requisite of regulations, that's absurd and unachievable. Extremely black-and-white thinking as well.
- pipo234 3y agoThanks for pointing out my exaggeration. You are right, I'll tone it down a little. What I meant to say is that as it stands most governments aren't a shining example when it comes to overseeing their own software efforts.
- mrkeen 3y agoIf you want an uneditorialised take, here's what they quote: The Administration will work with Congress and the private sector to develop legislation establishing liability for software products and services. Any such legislation should prevent manufacturers and software publishers with market power from fully disclaiming liability by contract, and establish higher standards of care for software in specific high-risk scenarios.
- enkid 3y agoThis seems like a good thing? Making software makers have liability for a shifty product should have happened a long time ago.
- AnimalMuppet 3y agoAs with many good things, it comes at a price. Windows, back in the day, was both buggy and full of security holes. It was also $99, and enabled an inexpensive computer to do near-workstation feats. If it cost, say, three times as much, that would have changed the market dynamic quite a bit. Fewer of us would have been able to afford computers with Windows, and few of us wanted bare-metal computers. Well, you say, that's just fine, we could have put Linux on it, and the world would have been a better place. Well, could you have put Linux on it? Can Linux survive in this regulatory environment? Can it survive as open as it is, as modifiable as it is, as free as it is? What about the rest of free software, that doesn't necessarily have a large company behind it? The second-order effects of this could completely change the software landscape. We may not like the results.
- phoehne 3y agoYou'll have a blessed version of Linux from IBM/RedHat that specifically meets USC x.y.z requirements for use in a, b, and c industries. You'll have a supported version of Postgres, etc. etc. They'll be a version or two behind and everything else we might have to add riders on the licenses like 'not for use in the following industries' or 'for demonstration and education purposes only.' Given that everything's getting either a WiFi or bluetooth chip in it, could we see coffee makers that are not approved for use in a commercial, health-care, industrial, or business setting?
- red-iron-pine 3y agoI mean Redhat is already FIPS compliant, and there are things like CMMC.
- pipo234 3y ago
- b112 3y agoIMO, every software dev using node, with endless thousands of packages, all with unknown licenses, and with unknown origins, unaudited, and by default, the ability to execute scripts and code during install... And which if you audit all those packages, 10 seconds later they could be sold/stolen/hijacked for malicious intent... Yet devs think this is awesome... Shows why we're stuck gping dpwn this path. Because devs have shown, they do not care about security, at all.
- glitchc 3y agoThat's it. Devs are cobbling together systems as quickly as possible from what are effectively black boxes. There's minimal insight into their underlying behaviour.
- pipo234 3y ago> devs have shown, they do not care about security, at all. Could add a grain of salt there, but I get your sentiment and would not want to argue their are big problems in the software industry, supply chain being one. We could be angry about that, but what can be done to improve the situation? Specifically: what should the government do? Proposed solution of adding a safe harbor framework to shield [companies] from liability is like saying: don't use npm, use our blessed supply chain. Sounds like a bold experiment, but IMO it's not obvious that this will curtail the reckless behaviours of those software devs you refer to.
- phoehne 3y agoUsing a blessed supply chain is not as stupid as it sounds. We do it at work so that every dependency we take is scanned.
- pipo234 3y agoInteresting. Is the blessing done by you, someone in your team, someone in another team, someone in another company, someone in government? Is the blessed supply chain comparable (not in volume, but in features, ease of use) to NPM or pip ecosystem? What do you do when you need the feature that isn't in the blessed set?
- thadt 3y agoOn one hand, there are a ton of downsides from the government sticking their noses into this - development will become slower, more costly, and in many cases no more secure or higher quality. On the other hand, as a rando off the street consumer, I appreciate that an FDA exists to help make sure someone selling me bread isn’t mixing sawdust in the flour to help juice those sweet startup bakery numbers. There are plenty of places to criticize the FDA, but we wouldn’t need that regulatory oversight if the public weren’t being harmed by such practices.
- noughtme 3y agoSawdust is unfortunately an actual food ingredient you’re more likely to find in industrial food regulated by the FDA. There’s an argument to be made that the free market, mom and pop/artisanal providers will be of higher quality than something regulated by the government.
- loup-vaillant 3y agoThere’s an argument for sure, but personally I would be more interested in evidence.
- c0pium 3y agoAs long as it’s food safe saw dust then the FDA is doing it’s job. We should be perfectly happy to trade in higher quality but dangerous products for lower quality but safe ones. The airline industry kills many fewer people than it used to, and most crashes and fatalities happen in the less regulated parts. Because of course they do.
- red-iron-pine 3y agoif you've ever had pre-shredded cheese, like a bag fulla pre-shreded mozzarella, you have eaten sawdust. FDA regulated, food-safe sawdust. tiny, very tiny, particles of saw dust (labeled "cellulose" in the ingredients), is used to keep the cheese from clumping up. go and watch your favorite pizza chain make pizza, with giant bags of pre-shredded cheese, and then ponder your sawdust intake.
- loup-vaillant 3y agoSeeing the regulation and accountability hammers falling upon us sure is scary. But. Isn’t it past time we actually get accountable for our work? Isn’t it past time we provide some form of guarantee of merchantability and suitability for some purpose? Sure amateur work should not be forbidden. But come on, when we sell something for profit, we should be accountable when it falls short of its promises. I don’t know how to best handle it. I’m even pretty sure some unintended consequences are inevitable (though they can probably be minimised). Still, do we really want to keep the status quo, where we can sell insecure software and never be liable for this? Most other industries are liable already, why wouldn’t we? One thing’s for sure: voting with our wallets clearly isn’t enough. One way or another our market needs a little reshaping.
- paulryanrogers 3y agoMost tech is heavily dependent on other tech, and networks are often only best effort. So I'd agree industrial, auto, and medical software should have some more regulation around safety and security; but not all commercial work.
- john_the_writer 3y agoImagine CI/CD with a gov body in there. Deploy once a year.
- staunton 3y agoMore like "deploy once ever, maybe"
- loup-vaillant 3y agoAgreed. It’s not just about the amount of regulation though. The kind of regulation is important too. Take 3 random examples: Single player game: maybe we want to cut back on the skinner boxes, or automatically mark 18+ any actual gambling. Professional accounting: maybe we want the thing to be error-free under normal operating conditions (good luck defining "normal" here though). Media player: that thing routinely reads stuff from the Internet, maybe it should be robust to hostile input.
- dotnet00 3y agoRegulation in general is way past overdue for software. How many other world changing technologies were allowed to become so utterly fundamental to the functioning of society before we started making rules to set a minimum standard?
- indigochill 3y agoThis has actually been a common pattern in the industrial revolution: 1. Invent new technology that revolutionizes society (e.g. railroad, telephone, software) 2. Quickly amass a fortune exploiting this new technology. 3. Use a portion of that fortune to lobby for industry regulation under the guise of concern for customers which just so happens to also raise the ladder and make it harder for startups to disrupt the incumbents, thus securing their fortune. That said, even with the cynical take, I find it hard not to be in favor of regulation (assuming it's done well, which has been a bit hit and miss over the years). A lot of software has potentially severe liabilities and it's time companies took responsibility for those instead of shifting them onto customers.
- dotnet00 3y agoYeah, I can relate with that cynical take, I suppose the more accurate way to put it would be that good regulation is way past overdue for software.
- phoehne 3y agoIt does create moats where non existed before. I do think the government over-estimates how well and up to date it keeps its standards. I don't know if it's still true, but 8 years ago (2015), you had to submit documentation to the FDA on CDROM. No. You couldn't just upload it.
- keepamovin 3y agoI don't see anything particularly disqualifying raised in this take on the new cyber direction. Its concerns around limiting free expression, duty to adhere to standards of care, and market power could be alleviated by suitable legal tests. I agree liability for vulns in court is problematic because of the elaborate possible futures that can occur in court, and the costs involved, but I see that this would likely be set by a sensible implementation of these ideas as a "last resort", with plenty of escape hatches to avoid it on the way, leaving the effect not toothless but just. I'm interested to see where this will go, I don't think it will be a bad thing for my company's cybersecurity products. A potential for abuse tho I think is the misuse of whatever collection of laws and rules results, to compel and gag deliberate weakening for the purposes of maintaining backdoor access, which should instead be negotiated through dedicated channels (warrants etc). Whenever there's commentary on new laws, it's pertinent to ask what lobbyists might be representing what interests in any discussion? I don't know the answer here, but I'd like to see speculation. One awesome thing that I hope results from this is that more lay people get somewhat conversant in what constitutes secure by design software. An increase in such security literacy can only be good--I think! Unless it's like that situation where people go to their doctors with their diagnosis and treatment already worked out thanks to Google, and are just looking for the doc to rubber stamp it! Which...depending on you and your doc, might be the right choice! Haha :)
- phoehne 3y agoI think I would rephrase one sentence 'what constitutes secure software by design.' to 'it may make some places actually realize there's an activity called software design, which is when you think about how the software should be have before you whack something together.'
- keepamovin 3y agoYes! Haha :)
- fallingknife 3y ago> more lay people get somewhat conversant in what constitutes secure by design software This will never happen anymore than laypeople will start thinking about the engineering principles behind building the reliable internal combustion engine in our cars. We want things that work without us thinking about it, and that's the end of it.
- freetanga 3y agoHow is this different from let’s say Banks, having to be audited by a third party and said reports reviewed by a Banking Regulator that can fine or close said Bank? And if controls fail and a Bank buckles down, they need to respond with their own capital. (Political favors and bailouts aside)
- phoehne 3y agoThat's a fair point. I think the casualties will be the stuff that's released that's not directly monetized. The open source developer doesn't make any money to justify paying for any of the process to get a seal of approval. Nor would they generally want to spend their evening preparing paperwork for someone else to review. A lot of critical projects have 'teams' that are basically 1 person. And what's considered 'critical' might be overly broad. Is the manufacture of Kleenex brand facial tissues critical? It might be under the final law. If your SaaS is used by Kleenex, do you now have to produce design documents, software process documents, audits of your process, etc. to show you can continue to be used by Kleenex to produce a trusted name brand in facial tissues? Do you do all the work to keep Kleenex as a customer only to have them switch to your Indian competitor who does none of that? Inquiring minds want to know.
- zeroCalories 3y agoI see this going in several directions. 1. The most obvious direction is that everything slows down in development. Innovation is killed in established businesses, startups need more initial investment. 2. If startups are not affected like in the EU, then there will be an explosion of them as large companies outsource their innovation or spin off their own startups. Innovation within large companies will still suffer. Maybe that's a good thing. 3. Greater focus is put into fewer projects to develop a stronger ecosystem and engineering culture so that we can increase productivity and still have time for strong standards. Might end up like 1 anyways.
- phoehne 3y agoSometimes slowing down and better process and standards are two parts of the same coin. While unit testing might speed you up on net, creating design specs, design reviews, architecture reviews, control boards for configuration changes, etc. slow things down. Sometimes in a useless way and sometimes in a good way. It all depends. But I doubt the EU would be any more lax over time.
- thunky 3y ago4. Nowhere, after spending an enormous amount of money. And it could spawn a boom for compliance consultancies that can maneuver the regulations and check the boxes on behalf of companies so that they can remain free from liability. All without any meaningful impact.
- pipo234 3y agoUnfortunately, I concur that this is the most likely outcome. I would love to believe we could inch a little toward: > 3. Greater focus is put into fewer projects to develop a stronger ecosystem and engineering culture [...] A hopeful sign might be stuff like PCI compliance: major impact on velocity, money wasted on consultants, brain-dead training and project managers, but also much less catastrophes than what might have been. But it's just as likely it goes the SLA-way, where promises and legal documents paint some desirable level of control that in reality does not exist, just because asses need covering.
- 3y ago
- phoehne 3y agoWhat we have now is kind of untenable, but I'd argue it's not about the incentives for developers, it's what customers will pay for. I had one customer, as [sic] government agency, lecture me about how sensitive their documents were and had to be protected. They even displayed them as images, not as text, to prevent 'copy and paste.' (I'll wait until you're done laughing). I then mentioned that in their current software, all the URLs were directly accessible, since the image requests were not checked by their terrible, terrible, hand-made, bespoke, authentication and authorization system. They said basically that was okay, because the URLs were complicated. They weren't, it was a path and a sequential image id. They wanted to pay for features but not to fix an obvious security hole. And that's probably the norm for most customers - why do they want to spend 300k fixing bad, old code that they think works? Most developers do care and try to make correct software. Some developers are ass-hats that are barely competent, going from project to project before they are 'found out.' Some contractors will put anyone with a pulse on the contract to avoid losing billable hours. And when's the last time you heard someone putting off new features if their competitors were already rolling similar features out? That being said, I can see this resulting in the market for at least some products completely drying up, or getting very expensive. It would basically cement some players into the market, like IBM/RedHat for Linux, ARM and their toolchains for embedded devices, or Microsoft/AWS for cloud. It would be a way to create a moat against competition. It will probably spawn and insurance market, making it impossible for small developers to also purchase the policy to release their software. Maybe you could add additional clauses to open source licenses, such as 'not licensed for use in any sensitive or critical system as defined by USC x.y.z'. And it still doesn't fix the problem of the pointy-haired boss ignoring risks or releasing too early to meet a schedule or competitive pressure.
- hardware2win 3y ago>They even displayed them as images, not as text, to prevent 'copy and paste.' (I'll wait until you're done laughing). Have you considered hidden watermarks just like printers? :)
- loup-vaillant 3y agoOne thing I have observed when giving security advice (and having the street cred to do so): people don’t believe it. You tell them no, really 2+2 is not 5, here’s the Peano arithmetic to prove it (2+2 = 1+3 = 0+4 = 4), and they don’t believe you. Real example, I was working on TPM provisioning once. There was something fishy about the process: though they ostensibly wanted a secure channel between the provider and the TPM, the connection procedure didn’t properly authenticate the TPM. It could be replaced by a fake or emulated TPM, the provider would be none the wiser. Not too big a deal (it all happens inside the factory), but still worth pointing out. Anyway, my team lead did not believe me. Fast forward a number of weeks (the TPM is a freaking mess, I was slow), most of the provisioning was done, secure channel and all, the whole procedure worked without a hitch… on an emulated TPM. Told you so: we need to validate the public key shown in the certificate the TPM provides, else it could come from any manufacturer. Anyway, I had working code to prove my case, and my team lead still did not believe me. Me, the guy who wrote a cryptographic library, and was put to work on the TPM precisely because of that expertise. I had to escalate to the security guy on a meeting, and he believe me. Probably because he actually knew his shit. So at last, I was allowed to fix the bug. The lesson I draw from that is that demonstrating a security exploit is freaking important. It’s not enough to point out the bridge isn’t finished, people need to see a car falling down to its doom.
- fidotron 3y agoWhile there is an increasing amount of noise from various sectors about what not to do we as an industry need to be concerned with what to do. I would have a lot more faith in regulation as a spur for security innovation if the overwhelming proportion of self labeled security people weren’t just obstructionist grifters. And I would have a lot more faith in software developers if they didn’t go all in with npm madness and like to tell anyone that points this out that they’re out of touch. Or when we collectively take a decentralized system and use it in a centralized way because we are too lazy. One of the clearest things we must get a handle on is auditing where code came from, and on which machines, under which jurisdictions, any building, packaging, signing etc. occurred. I would tend to also believe we need to have much stronger code permissions enforcement, especially moving towards a whitelist only model around network host access. If we can enable only sub sections of our code to have such permissions so much the better. What we must not do is allow a few government supported gatekeeping organizations to act as man in the middle signatories, where dealing with them is mandatory to deploying anything. That is a government run App Store.
- cookiengineer 3y agoI always lobby actively for golang because of this. Golang is a "batteries included" language ecosystem, where golang.org/x is the package that implements almost all RFCs you could ever think of. In most industries that I worked in, management folks do not understand how graciously they have fucked up for politicians to care about something unmeasurable as cyber security. A lot of developers I have spoken with think that workflow patterns like Test Driven or Domain Driven Design will make their code inherently more secure. Even when you point out absolute rookie mistakes like missing sanitization of user input they're always smart-assing you about how this will never affect anything that they built. If you then point out RCEs in libraries they keep reintroducing for whatever opinionated reasons they deflect the blame upon the random guy on the internet that built this library on the weekend. I am glad the US made the first move after the pipeline incident, and I am glad that government projects started with SBOMs. Why? Because it showed up how little companies know about their risk management of operational dependencies. It's easy to blame the log4j maintainer, but it isn't easy to blame the guy for a mistake that he made more than 20 years ago, and fixed it meanwhile while already documenting it. Because that is totally upon software/development managers and the total lack of quality assurances and testing in their workflows. And that is talking only about something as easily fixable as a java dependency in your xml file. Imagine how messed up security could be if there's a babel library affected, and joyent would not hard-fork it to force-fix it for everyone. There's no way to guarantee anything in npm, by nature of the pre/post hooks in its package manifest format.
- bottled_poe 3y agoI welcome this change, greatly. The world of software engineering is an awful shitshow of cowboys, vulnerabilities, amateurism and mud balls. The metaphorical well barely contains any water, it’s almost entirely piss. It’s disgusting and reduces the reputation of the work good engineers can actually achieve. More regulation is a good thing to weed out the amateurs from the professionals and to bring some value back to what we do.
- mikewarot 3y agoThe root cause of this foolishness continues to go un-noticed. Imagine a parallel world where where we no fuses, nor circuit breakers, nor any type of thing. You'd have government very carefully regulating what could and couldn't be hooked to the local power grid, just like this. We live in a parallel universe to that, where nobody even considers only giving a program or "app" access to a carefully contained set of resources, instead of the whole computer, and internet. We find "as if" solutions, like VMs or containers, while still ignoring the root issue. Wake up!
- mianos 3y agoImagine when the clowns running Australia go for the same thing. They just blew 2.8B last week on a failed IT project. It happens once every few months. While the private industry struggles to deliver IT, the government here completely fails. Now, they start to tell the private sector how to do things. LOL.