Start a fresh conversation. Replace the highlighted placeholders.
Use openclaw-security-hardening to harden an explicitly authorized self-hosted OpenClaw deployment using the documented threat-model, host/runtime, secrets, network, detection/recovery, and validation workflow for [authorized deployment topology and current configuration], subject to [approved changes, privileged access, service-interruption window, and backup/snapshot references], and deliver the applied-control plan, evidence-based validation results, and rollback readiness against [target RTO and secret-manager references].
Required inputs
[authorized deployment topology and current configuration]
[approved changes, privileged access, service-interruption window, and backup/snapshot references]
[target RTO and secret-manager references]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: openclaw-security-hardeningdescription: Harden OpenClaw self-hosted environments with baseline host controls, auth tightening, secret handling, network segmentation, and safe update/rollback workflows.category: devopsrisk: criticalsource: https://github.com/BagelHole/DevOps-Security-Agent-Skillssource_repo: BagelHole/DevOps-Security-Agent-Skillssource_type: communitydate_added: '2026-09-20'license: MITlicense_source: https://github.com/BagelHole/DevOps-Security-Agent-Skills/blob/main/LICENSEcompatibility: Requires the relevant OS/platform tooling and privileged access where noted. Docs-only; helper scripts and templates not bundled.metadata: author: devops-skills version: '1.0'
When to Use
Provisioning, hardening, or operating the infrastructure described in this skill within an authorized environment.
OpenClaw Security Hardening
Use this skill to reduce exposure in self-hosted OpenClaw deployments before opening access to teammates or external networks.
Build a Threat Model First
Map the highest-risk assets and paths:
Admin/API endpoints for OpenClaw
Provider API keys and model credentials
Prompt/response logs containing sensitive business data
Host-level access (SSH, local admin accounts, remote desktop)
Prioritize controls that reduce credential theft, remote code execution blast radius, and data exfiltration.
Apply Baseline Host Hardening
Keep OS and package dependencies patched on a regular cadence.
Run OpenClaw as a dedicated non-admin user account.
Enable full-disk encryption and secure boot features where available.
Remove unnecessary services and block inbound ports by default.
Lock down remote admin (key-only SSH, no password login, limited source CIDRs).
Example Linux baseline checks:
id openclaw
sudo ss -tulpn
sudo ufw status verbose
sudo systemctl --failed
Harden Application Runtime
Bind OpenClaw to localhost or private VLAN by default.
Place a reverse proxy in front of OpenClaw for TLS, auth, and rate limits.
Enforce authentication on every non-health endpoint.
Disable debug/dev modes in persistent environments.
Restrict outbound egress to only required providers (LLM API, telemetry sink, package mirror).
Example reverse proxy controls to enforce:
TLS 1.2+ only
strict transport security header
request body size limits
request timeout and upstream timeout guardrails
per-IP and per-token rate limiting
Protect Secrets and Tokens
Store secrets in a vault or platform secret manager, not committed .env files.
Rotate provider and admin tokens on a fixed interval and after any incident.
All sensitive endpoints require auth and are unreachable without VPN or gateway policy.
Secrets are absent from repo history and plaintext shared directories.
Host firewall default deny is active for inbound traffic.
TLS termination and rate limits are active at ingress.
Rollback drill can restore service within target RTO.
Related Skills
openclaw-local-mac-mini (openclaw-local-mac-mini) - Local OpenClaw hosting setup
multi-tenant-llm-hosting (multi-tenant-llm-hosting) - Multi-tenant AI isolation patterns
zero-trust (zero-trust) - Private access and identity-aware network controls
When to Use
You are provisioning, configuring, or troubleshooting the infrastructure component covered by this skill (servers, storage, databases, networking, cloud, local AI).
Limitations
Infrastructure commands can disrupt services: confirm target host/scope and have backups/snapshots before mutating state.
Docs-only import: upstream scripts and templates not bundled.