Accounts and sessions
Passwords are salted and hashed with scrypt. Session tokens are stored in the database only as SHA-256 hashes, while the browser cookie is HttpOnly, Secure in production and SameSite.
Protection across every workflow layer
Security in Bendria goes beyond sign-in. It covers the account, building boundaries, documents, audit, backups and production monitoring.
Building and role boundaries
Every server action verifies the signed-in user, active building, role and object ownership. Switching roles never grants access that was not assigned.
Dedicated production database
Accounts, buildings, workflows and sessions are stored in PostgreSQL. Schema migrations are versioned and checked before and after deployment.
Document integrity
Documents receive SHA-256 checksums, files are served only through authorised routes, and voting evidence packages can be verified independently.
Audit chain
Material actions retain the previous event hash and a new event hash, allowing altered history to be detected.
2FA and external integrations
TOTP two-factor protection is available. Registry Centre and qualified signing are never simulated and activate only with production contracts and credentials.
Operational protection
Database and document backups are created as one pair, checksum-verified, encrypted with separate AES-256 keys and automatically copied off the VPS. Production monitoring covers HTTP, database access, migration drift, document storage, disk capacity and backup freshness.
Need a specific answer?
Tell us about your building, security or data-processing question.