Security
Security and recovery from the current source
This page now describes what Sentinel, Vault and Nexus actually implement. Unsupported claims about automatic raid lockdowns, alt scoring, secret storage and immutable logs have been removed.
Sentinel
Live risk and incident controls
Risk snapshot
Nexus builds the current Sentinel security snapshot from live guild and Kingdom state.
Dangerous-permission visibility
The current Sentinel surface exposes permission-health information and visibility into high-privilege bots or roles.
Incident records
Operators can create Sentinel incidents and update their status through authenticated Nexus endpoints.
Open-incident counts
Nexus derives open and critical-open incident totals from the stored incident lifecycle instead of sample cards.
Kingdom Vault
Vault is the Kingdom state backup and disaster-recovery system. It is not advertised as a browser password manager or credential locker.
- On-demand Kingdom state backups
- Automatic backup support in the Nexus maintenance layer
- SHA-256 backup verification
- Retention handling
- Explicit operator restore endpoint
- Safety backup behavior around restore operations
Nexus authorization
Protected Nexus API reads require a validated Discord session or the configured recovery authorization. Sensitive reads and mutations apply additional operator checks.
- Discord OAuth sessions are revalidated
- Operator-only access for identity, applications, Vault, Studio layouts and audit reads
- CSRF validation on protected write methods
- Rate limiting on authentication and API paths
- Security headers on Nexus responses
- Private Core bridge tokens remain server-side on the HQ Worker
Open the current Kingdom Core stack
Add the Discord application, preview the current /setup3 layout before applying it, and use the production Nexus for authenticated web operations.