SecurityRBAC & Roles

RBAC & Roles

ClawNex includes role-based access control with 5 operator roles, 32 permissions, session governance, progressive lockout, and CSRF protection.

Public-facing installs run with RBAC enabled. Local installs may run RBAC off only for localhost-only use.

5 Roles

RoleAccess Level
AdminFull platform access, user administration, configuration, and system operations
Security ManagerSecurity operations, shield policy, access controls, alerts, and break-glass workflows
OperatorDaily monitoring, investigation, shield tests, and operational response
ViewerLimited read-only operational visibility based on assigned permissions
AuditorAudit, evidence, compliance, and security-log review

32 Permissions

When RBAC is enabled, protected API routes require an authenticated session and the relevant permission. Key permissions include:

PermissionDescription
config:readRead configuration settings
config:writeModify configuration
shield:scanRun shield scans
shield:configManage ClawNex Shield Rules and whitelist settings
alerts:readView alerts
alerts:manageAcknowledge, investigate, and resolve alerts
audit:readView audit trail
system:managePerform system operations
workspace:readView agent workspace files
chat:useUse the chat/proxy endpoint
voice:useUse voice and avatar features

Session Management

  • Timeout — configurable from 1 to 720 hours
  • Concurrent limit — maximum 5 sessions per operator; oldest session is revoked when exceeded
  • Password change — revokes all sessions for that operator
  • My Sessions card — operators can view and revoke their own sessions

Progressive Account Lockout

Failed AttemptsLockout Duration
51 minute
105 minutes
1530 minutes
20+Account auto-disabled until an admin re-enables it

Lockout is per account. A successful login resets the failure counter.

Security Implementation

  • SQLite sessions with SHA-256 hashed tokens
  • bcryptjs password hashing with 12 rounds
  • Session-bound HMAC CSRF token on state-changing requests
  • Origin and Referer checks for mutation requests
  • Last-admin protection: the final admin cannot be demoted, deactivated, or deleted

Enterprise Features

FeatureDescription
SSO / SAMLFederated authentication with your identity provider
MFAMulti-factor authentication such as TOTP or hardware keys
Custom RolesDefine custom permission sets beyond the built-in roles
Session IP BindingLock sessions to the originating IP address
Two-Person Break-GlassRequire a second admin to approve break-glass activation

Enterprise features are visible in the UI with an Enterprise badge.