home.social

Search

9 results for “boblord”

  1. Myth: “Attackers keep adapting”
    Reality: The difference is real. A fire captain fights physics: unpredictable, indifferent, not trying to win. An army captain fights someone who can wait, feint, spend more, and come back tomorrow.

    You fight an intelligent adversary by changing the landscape and raising the cost of their campaign. That argues for secure by design, not against it. Eliminating the Lucky 13 (see UV-01) does both; patching instances does neither.

  2. Thirty years in, adaptability explains the pressure. It does not excuse the outcome.

  3. Until incentives shift, the market will reward unsafe software.

  4. Market Forces & Effects:
    The software industry isn't a free and fair market — not when it comes to security.

    High switching costs, vendor lock-in, and market concentration reduce competition. Information asymmetries prevent buyers from assessing product security. The result is a classic market failure:

    • Secure software is underproduced
    • Private costs to manufacturers are low
    • External costs are borne by customers and national security
  5. Myth: “It was a sophisticated attack”
    Reality: Most breaches described in headlines as a "sophisticated" or "advanced" attack start with an ordinary technique: a phished credential, a social-engineered helpdesk call, a login with no MFA. The sophistication is rarely in the intrusion, it's in the story told about it afterward.

  6. Elevating an opportunistic break-in to a spy-movie threat actor moves attention away from the mundane design failure that let it happen, an outcome that benefits the manufacturer whose product failed.

  7. Do not judge me, but Department Story Christmas is back on @somafm !

    I can almost taste the Frango Mints...

    Join me!

    somafm.com/deptstore/

  8. Sometimes important work happens without fanfare. When CNAs submit CVE records, the system validates them against some basic standards. Last month, that validation code was refactored into its own library.

    Now that the validation code is its own library, CNAs can run it in-house to ensure their CVE record submissions will not be rejected. It's also now easier to add additional validation code to raise the bar on record quality.

Share on Mastodon

Enter the server where you have an account.