‹ BackHN Continuity

Thread

Security auditing in the age of (good enough) AI

96 points · 16 comments · aray07

  1. AndrewKemendo · · focus · HN ↗
    It’s over security people

    You need to find a new way to do business with the assumption that you’re 100% eventually going to get pwned

    So just assume that going forward and you’ll start to rethink your architecture

    1. Cider9986 · · focus · HN ↗
      FHE would be nice, but there's a lot of products that could be E2EE today. Plenty of breaches are just server-side files and dumps, there's no excuse for not using E2EE cloud storage.

      Databases are much more tricky, but if we're talking a significant shift, it is as good a plan as any. Clearly server trust is not working.

      AI is accelerating both sides for defenders and attackers, but mobile clients are already way ahead of typical desktop. Android's desktop mode exists in the OS now but needs a lot of work and more powerful chips before it can replace desktops.

      For security against remote attacks, I'd rank clients roughly: GrapheneOS, iOS/iPadOS, stock Android on Pixels, ChromeOS, macOS, Windows, desktop Linux. Prefer more secure clients, always, but now the client is all that's left to trust for content.

      Native clients avoid the web E2EE problem and are easier than ever to build. With AI, you can audit the source as often as you want and reproducible builds mean you know that's what you're running.

      1. AndrewKemendo · · focus · HN ↗
        All valid.

        Overall though the point is any particular hole that you have will be exploited

        so what used to be a game of “patch the hole” is going to need to change entirely

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.