How does IronClaw prevent prompt injection attacks from exposing credentials?
IronClaw's security model does not rely on the AI to protect secrets. Instead, credentials are stored in an encrypted vault within a Trusted Execution Environment (TEE) on NEAR AI Cloud. The AI never directly sees the raw credential values; they are injected into requests only for pre-approved endpoints at the host boundary.
What is the role of 'sandboxed tools' in IronClaw's security architecture?
Sandboxed tools ensure that if a skill is compromised, it cannot affect other parts of the system or exfiltrate data. Each tool operates within its own WebAssembly (Wasm) container, with capability-based permissions, allowlisted endpoints, and strict resource limits.
How does IronClaw ensure that even the cloud provider cannot access sensitive data?
IronClaw instances run inside Trusted Execution Environments (TEEs) on NEAR AI Cloud. This means that data, including credentials, is encrypted in memory from the moment the instance boots until it shuts down, making it inaccessible even to the underlying cloud provider.
What mechanism does IronClaw use to detect and prevent credential exfiltration?
IronClaw employs real-time leak detection by scanning all outbound network traffic. Any data resembling a secret attempting to leave the system is automatically blocked, preventing unauthorized credential exfiltration.
How does IronClaw leverage the Rust programming language for enhanced security?
IronClaw is built in Rust, which inherently prevents entire classes of exploits common in other languages. Rust's compile-time memory safety enforcement eliminates issues like garbage collector vulnerabilities, buffer overflows, and use-after-free errors, contributing to a more secure codebase.