• 3 Posts
  • 209 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • I’m not sure if this is just a rhetorical question or a real one?

    Because I didn’t claim it isn’t negligence. It is negligent, however, it is not a problem solvable by just pointing fingers. It’s a problem that solvable through more strict regulation and compliance.

    Cyber security is almost exactly the same as safety in other industries. It takes the same mindset, it manifests in the same ways under the same conditions, it tends to only be resolved and enforced through regulations…etc

    And we all know that safety is not something solvable by pointing fingers, and saying “Well Joe Smo shouldn’t have had his hand in there then”. You develop processes to avoid predictable outcomes.

    That’s the key word here, predictable outcomes, these are predictable situations with predictable consequences.


    The comment above mine is effectively victim blaming, it’s just dismissing the problem entirely instead of looking at solutions for it. Just like an industry worker being harmed on the job because of the negligence of their job site, there are an incredibly large number of websites compromised due to the negligence of our industry.

    Just like the job site worker who doesn’t understand the complex mechanics of the machine they are using to perform their work, the website owner or maintainer does not understand the complex mechanics of the dependency chains their services or sites rely on.

    Just like a job site worker may not have a good understanding of risk and risk mitigation, a software engineer does not have a good understanding of cybersecurity risk and risk mitigation.

    In a job site this is up to a regulatory body to define, utilizing the expertise of many, and to enforce this in job sites. On job sites workers will go through regular training and exercises that educate them about safety on their site. For software engineers there is no regulatory body that performs enforcement. And for the most part software engineers do not go through regular training that informs them of cybersecurity safety.


  • That’s not how systemic problems work.

    This is probably one of the most security ignorant takes on here.

    People will ALWAYS fuck up. The world we craft for ourselves must take the “human factor” into account, otherwise we amplify the consequences of what are predictable outcomes. And ignoring predictable outcomes to take some high ground doesn’t cary far.

    The majority of industries that actually have immediate and potentially fatal consequences do exactly this, and have been for more than a generation now.

    Damn near everything you interact with on a regular basis has been designed at some point in time with human psychology in mind. Built on the shoulders of decades of research and study results, that have matured to the point of becoming “standard practices”.








  • Did you read the article? No? Cmon. You should start doing that before drawing conclusions.

    This is noted as a temporary block on the specific extensions ONLY within the country with regulatory power to ban Firefox. Russia.

    Mozilla has stated this is temporary so they can have the breathing room to figure out how to navigate this. Since this goes against their principles.

    It’s either Firefox is banned in Russia, or they do this. Which causes more harm? That’s a rough choice for them to need to make.