1 KiB
1 KiB
Hermes Hub — Security Policy & Controls
1. Security Invariants
- Zero Secret Leaks: All credentials, tokens, and OAuth keys reside solely in
%LOCALAPPDATA%\hermes\and are excluded from Git via.gitignore. - Policy Enforcement:
WebPolicy: Outbound URL traffic is restricted to verified provider domains. Requests to internal cloud metadata IP169.254.169.254or local networks are blocked.ToolPolicy: Commands matching destructive patterns (format,rmdir /s /q c:\,del /f /s /q c:\windows) are blocked before invocation.
- Process Sandboxing & Registry:
- Every background process spawned by the hub is tagged with a unique UUID, PID, and spawn timestamp in
LifecycleSupervisor. - Cleanup is strictly limited to verified owned processes. Generic
taskkillorkillallcommands are prohibited.
- Every background process spawned by the hub is tagged with a unique UUID, PID, and spawn timestamp in
- Audit Logging:
- Security-relevant events (URL blocking, credential operations, role changes) are appended to
%LOCALAPPDATA%\hermes\logs\hermes-hub.logand displayed in the Event Log.
- Security-relevant events (URL blocking, credential operations, role changes) are appended to