Protect the knowledge your agents rely on.
Your agent’s memory may contain customer information, internal documents, and business decisions. Akasha, the engine behind Minds, provides encryption and scoped access controls. Review the protections and deployment settings below with your security team.
Security / Boundaries
Follow the permission.
See what a credential allows, what it does not, and where a request stops.
One credential.
A specific purpose.
- Namespace
- research
- Credential permits
- memory:read
- Requested operation
- memory:read
Changing this example sends no request.
Transport
TLS configuredThe example route uses an encrypted connection. The actual certificate, termination point, and internal hops need deployment verification.
Authorization
Within scopeThe request matches the example credential: read from the research namespace.
Storage
Read onlyA read retrieves existing context. Storage protection and backup recovery remain independently configured controls.
The example reader can retrieve from research.
Protect what the request leaves behind.
Encryption, key custody, backups, and recovery are separate operational controls. Configure and verify them for your deployment.
Illustrative policy and configured deployment. Verify controls on your actual instance; this is not a live security assessment.
The mechanisms behind the controls.
These are engine capabilities to verify in your deployed configuration. Storage encryption is disabled in the default core and KV configuration; configure keys and enable it for the deployment. Production access must enforce verified credentials.
- At rest
- AES-256-GCM · 96-bit nonce prepended
- Key derivation
- HKDF-SHA256 · per-namespace
- In transit
- TLS support · certificate configuration required
- Auth
- Ed25519 capability JWT (EdDSA)
- Passwords
- Argon2
- Key material
- Zeroize on drop
Security is also how you run it.
Review encryption settings, certificate management, access policies, backups, and monitoring before handling sensitive data. These engine controls are not an independent certification. Published legal documents and assurance status are available on the Trust page.