EverOS

EverOS Security Hardening Guide

Least-privilege permissions

• Restrict file access: Only allow EverOS agents to read and write memory files in a single, isolated folder—not your entire computer or cloud storage.
• Separate secrets from memory: Store passwords, API keys, and sensitive credentials in a locked vault tool, never in Markdown memory files.
• Limit agent capabilities: Disable unnecessary features (like direct internet access or third-party app integrations) unless you actively need them.
• Review tool permissions: Before connecting a new app or agent to EverOS, check what it can access—camera, microphone, email, documents—and deny anything suspicious.

Network isolation

• Use local mode only: Keep EverOS running on your device without syncing to the cloud until the project matures and publishes a security audit.
• Disable auto-sync: Turn off automatic backup or sharing of memory files across devices or accounts.
• Restrict internet agents: If agents must connect online, only allow them to reach specific, trusted services—not the open internet.
• VPN for sensitive work: When using EverOS with confidential information, connect through a VPN to prevent memory files from being exposed on shared networks.

Monitoring

• Audit memory changes: Regularly review your Markdown memory files for unexpected edits, new sections, or suspicious content added by agents.
• Log agent actions: Enable detailed logging of what each agent reads, writes, and modifies in memory—treat logs as your security camera.
• Watch file timestamps: Check when memory files were last modified; sudden or unexplained changes may signal compromise.
• Test with dummy data first: Before storing real information, test each agent with fake data to confirm it behaves as expected.

Red flags to watch for

• Memory contents you didn't write: If you find new text, code, or links in your Markdown files that you didn't create, stop using the agent immediately.
• Agent behavior changes: An agent that suddenly requests new permissions, accesses files outside its folder, or talks about topics you never discussed may be compromised.
• Errors or crashes during parsing: If EverOS crashes or behaves strangely when reading memory files, stop and report it—may indicate a parsing vulnerability being exploited.
• No security documentation: If the EverOS team has not published a public security policy, threat model, or audit results, treat it as experimental and avoid production use.