HisabTechBusiness operating systemThis Trust Center separates controls that are implemented today from safeguards that require configuration, ongoing operational evidence or a platform upgrade.
Each control includes its current state and the evidence or limitation buyers should understand.
Owner and administrator mutations require an AAL2 authenticator session before sensitive financial, inventory, payroll, user or security changes are accepted.
Enforced in the application session and PostgreSQL control path.Workspace access is scoped by organization and role so operational users do not automatically receive administrator-level control.
Production health checks include detection of public tables that are missing row-level security.Material financial actions, authentication activity and security alerts can be recorded as organization-scoped audit events.
MFA-verified administrators can export enabled audit streams as spreadsheet-safe CSV evidence.Responses apply a restrictive content security policy, frame protection, MIME-type protection, referrer controls and permissions restrictions.
Security headers are applied centrally by the Next.js request proxy.Authentication and API routes use fixed-window request limits as a baseline against repeated automated requests.
The current in-memory limiter is a fallback and should be replaced with a shared regional limiter as deployment scale increases.New and reset passwords are screened for predictable patterns and checked through a privacy-preserving breach-prefix lookup.
Only a short hash prefix is sent to the breach lookup service; the password itself is not transmitted.Administrators can record encrypted backup evidence, checksums, storage references and isolated restore-test results.
Readiness depends on the organization keeping backup evidence current and performing periodic restore tests.Structured server errors can be logged by the hosting platform and forwarded to an external monitoring endpoint.
External forwarding requires the monitoring webhook environment variable to be configured.Point-in-time recovery is intentionally not presented as active until the connected database plan confirms the capability.
The production controls page keeps this state visible rather than marking an unavailable safeguard as ready.HisabTech maintains product controls. Each organization remains responsible for how users, credentials, exports, devices and operational evidence are managed.
The internal production-control workspace tracks administrator MFA, alerts, audit activity, backup evidence, restore testing, database health and monitoring configuration.
Provide the affected route, observed behavior, reproduction steps and any relevant timestamps. Do not include customer passwords or unnecessary personal data.