‹ BackHN Continuity

Thread

Humans missed 1 in 3 threats approving AI agent commands across 40k game runs

218 points · 177 comments · Wirbelwind

  1. ilc · · focus · HN ↗
    Sandbox and use Local AI. This is the real answer.
    1. rvz · · focus · HN ↗
      Yet the AI can still escape the "sandbox", unless it is physically unable to connect to another computer and completely airgapped.
      1. ux266478 · · focus · HN ↗
        If the sandbox has vulnerabilities, which you can also use the AI to fuzz for. Obviously at the point in which it can talk to the internet it doesn't really matter, but there are a very finite number of zero-days that can exist in a bytecode interpreter hosting a harness.
        1. rvz · · focus · HN ↗
          Well it turns out that we have yet another sandbox escape just released today called "Zapscape".

          My point is if an agent recited how to find one in its memory or training set and it is air-gapped, the chances of it spreading and infecting other computers is pretty low.

          [0] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=49198843">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=49198843

          1. ux266478 · · focus · HN ↗
            Gonna have to point out that&#x27;s a KVM CVE. I was very specific about using a bytecode interpreter.

            If you&#x27;re serious about a secure sandbox, you don&#x27;t touch hardware virtualization with a 10 foot pole. In fact, you don&#x27;t even use an emulator that lowers code into native machine code like QEMU. The standard for secure sandboxes is Bochs: <a href="https:&#x2F;&#x2F;github.com&#x2F;bochs-emu&#x2F;Bochs" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;bochs-emu&#x2F;Bochs

            Not that Bochs is perfect, a new CVE was discovered back in June. But that&#x27;s the 5th CVE it&#x27;s had in its lifetime, and it has a much smaller upper bound on possible CVEs it can have compared to something like KVM or QEMU.

            The reason why you use something like this isn&#x27;t just for the security you get out of it, but also the deep introspection and analysis facilities you get out of it as well. Unless you&#x27;re a very well funded lab, it&#x27;s actually quite hard to do analysis on bare metal when you can&#x27;t trust your own kernel. You can always airgap the host machine (and good defense in depth does), but that&#x27;s still not an appropriate sandbox by itself, even if it&#x27;s theoretically secure.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.