SECURITY
Review the security questions Balaawi uses to scope identity, authorization, tenant isolation, data handling, audit evidence, and deployment.
Security claims should be tied to implemented controls and tested evidence. Balaawi scopes access, ownership, sensitive data, operations, and deployment responsibilities before rollout.
Authentication establishes identity; server-side authorization decides whether that identity may perform an action in the current context.
Tenant context must remain enforced in queries, files, jobs, caches, events, and reports, not merely selected in the browser.
Backups, logging, monitoring, patching, incident response, and release verification need explicit owners and retained evidence.
No. It describes control areas and scoping questions; any compliance assessment requires defined scope and independent evidence.
Yes. Material requirements should be raised during discovery and resolved in written scope before commitment.
Share the actual operating context. Balaawi starts with discovery; the request form creates neither a workspace nor a charge.
Request discovery