> wildly negligent to not be running it in a physically-airgapped environment
Why should it be physically airgapped? Clients won't be doing that.
Why should it be physically airgapped? Clients won't be doing that.
Did we learn nothing from all of those Star Trek holodeck jailbreaks?
And if you are too afraid to test it without guardrails, that probably means it shouldn’t be released.
Is it safe to release such software if it has only been tested in environments where certain major risk areas do not exist?
Appendix C Illustrative safeguards, controls, and efficacy assessments has specific examples like:
- Agent actions are all logged in an uneditable database, and asynchronous monitoring routines review those actions for evidence of harm
- Limiting internet access and other tool access
- Limiting credentials
- Limiting access to system resources or filesystem (e.g., sandboxing)
- Limiting persistence or state