How nacre.sh Handles OpenClaw Security for You

OpenClaw security is a growing concern as the platform's user base has expanded beyond technical audiences. The ClawHavoc malware campaign targeting ClawHub skills, CVE-2026-25253's canvas host remote code execution vulnerability, and the ongoing challenge of credential management mean that security for a self-hosted OpenClaw instance requires genuine expertise. nacre.sh exists, in large part, to make all of that someone else's problem — specifically, theirs. Here's what they handle and how.

Automatic Security Patches

nacre.sh monitors OpenClaw security disclosures and applies patches to all customer instances without requiring any action from you. When CVE-2026-25253 — a remote code execution vulnerability in the canvas host component — was publicly disclosed, nacre.sh deployed patches across all instances within four hours. Most self-hosted users took days to weeks to apply the same fix, leaving their instances exposed.

The patch deployment process is staged: nacre.sh tests patches on canary instances, validates functionality, then rolls out to all customer instances. This prevents the scenario where a hasty patch breaks your agent's configuration.

Isolated Instances

Every nacre.sh customer receives a dedicated container — never shared with other users. This is a critical security distinction. In shared environments, a compromised neighboring tenant could potentially affect your instance through shared process namespaces or storage. With dedicated containers, your agent's memory, credentials, and configuration exist in complete isolation.

TLS Everywhere

All connections to your nacre.sh instance are TLS-encrypted. Certificates are provisioned automatically using Let's Encrypt on deployment and renewed before expiry without any action required. There's no period where your instance is accessible over unencrypted HTTP, and no risk of your agent's API traffic being intercepted due to an expired certificate.

Nightly Backups to Cloudflare R2

Your OpenClaw agent's memory, skills configuration, and openclaw.json are backed up nightly to Cloudflare R2 in your chosen region. Backups are retained according to nacre.sh's retention policy, allowing recovery from accidental deletions, corrupted states, or ransomware attacks. You can also trigger manual backups at any time from the dashboard.

Credential Security

API keys (for your LLM providers) are stored encrypted in your isolated instance environment. nacre.sh uses envelope encryption — keys are encrypted with a key encryption key that is itself stored in a hardware security module (HSM). This means even a breach of nacre.sh's infrastructure does not expose plaintext API keys.

Managed Firewall

Your instance is not directly exposed to the public internet beyond the necessary ports. nacre.sh manages a network firewall that restricts inbound traffic to HTTPS (port 443) and the specific ports required for your connected channels. SSH access is only available through the nacre.sh web terminal, with session logging enabled.

What You Still Need to Handle

nacre.sh manages infrastructure security, but application-level security is still your responsibility. Be careful about:

• Prompt injection: Malicious content in documents you process can manipulate your agent
• ClawHub skill vetting: Only install skills from verified publishers
• Channel permissions: Restrict who can message your agent on each channel

Frequently Asked Questions

Does nacre.sh hold my API keys in plaintext?

No. Keys are encrypted using envelope encryption backed by an HSM. The encryption key for your API keys is never stored on the same system as the encrypted keys themselves.

How quickly does nacre.sh respond to new CVEs?

For critical/high severity CVEs affecting OpenClaw, nacre.sh targets patch deployment within 4–8 hours of disclosure. Medium severity vulnerabilities are patched within 48 hours.

Can I see the security audit logs for my instance?

Yes. The nacre.sh dashboard provides access to your instance's access logs, including all web terminal sessions and channel connection events.