MemOS

Least-privilege permissions

• Restrict data access: Only allow MemOS to read and write the specific information it needs for each task—not your entire database or file system.
• Control credential storage: Never store passwords, API keys, or authentication tokens in MemOS memory; use a separate secure vault instead, and give MemOS only time-limited access when needed.
• Limit user scope: Configure MemOS so different team members only access memories relevant to their role—for example, finance staff shouldn't see technical system logs.
• Audit memory purging: Establish a clear process to permanently delete sensitive memories (like customer PII or client secrets) on a regular schedule, not just when the system decides to.

Network isolation

• Verify storage location: Before deployment, confirm where MemOS stores its memory files—local disk, company servers, or third-party cloud—and ensure the location meets your data residency requirements.
• Encrypt data in transit: If MemOS communicates with external systems to retrieve or store memories, all data should be encrypted during transmission (look for HTTPS/TLS).
• Encrypt data at rest: Require MemOS memory files to be encrypted when sitting on disk or in storage, so even if someone accesses the physical server, they cannot read the data.
• Block unauthorized outbound connections: Use firewalls to prevent MemOS from sending memories to unknown external servers without explicit approval.

Monitoring

• Log all memory access: Track when memories are created, read, modified, or deleted—including who requested it and what data was involved.
• Review skill reuse events: Regularly check which past interactions are being replayed in new tasks to catch if older, compromised instructions are being reused inappropriately.
• Alert on unusual patterns: Set up alerts if MemOS suddenly accesses many sensitive records, loads memories outside normal business hours, or behaves differently than expected.
• Periodic security audits: Before and after major deployments, have a security review of what data MemOS has retained and whether encryption/deletion policies are actually working.

Red flags to watch for

• No clear documentation on data retention: If the vendor cannot explain when/how memories are automatically deleted or compressed, treat this as a major risk—sensitive data could linger indefinitely.
• Early-stage maturity indicators: Low adoption (0 npm downloads despite 11,880 GitHub stars) suggests the tool may not be battle-tested in production environments; start with a pilot program, not company-wide rollout.
• Unencrypted memory storage: If MemOS stores memories in plain text rather than encrypted format, reject it for any sensitive use cases.
• Vague prompt-injection safeguards: Ask the vendor specifically how they prevent an attacker from poisoning early memories so malicious instructions spread to future tasks; if the answer is unclear or absent, delay deployment until they provide one.