Zero-trust postureLeast privilegeAuditable actionsEncrypted transport + storage
Security
Fuze is designed with identity-first access controls, database-level authorization enforcement, and defense-in-depth safeguards. Security is enforced at the data boundary on every request—not in the UI.
Quick overview
- Authentication-backed sessions (no anonymous data access).
- Role + membership-based authorization (unit-scoped, least privilege).
- Encrypted communications and encrypted storage via managed cloud services.
- Actions produce a durable audit trail (who changed what, and when).
Identity and access control
- Identity-backed authentication for all privileged access.
- Role-based access control aligned to leadership/admin/member responsibilities.
- Unit membership gates access (approved/pending/denied states).
- Least-privilege defaults: if a rule doesn’t explicitly allow it, it’s denied.
Multi-tenant isolation
- Data access is scoped by unit context and membership status.
- Predictable document paths support strict authorization enforcement.
- No cross-unit reads/writes unless explicitly authorized for platform admins.
Data protection
- Encryption in transit (TLS) for all client ↔ service communications.
- Encryption at rest via managed cloud storage controls.
- Data minimization: stores readiness metadata and action states, not raw documents.
- Structured records support retention and future governance controls.
Auditability and accountability
- Actions are recorded with actor identity (UID) and timestamps.
- Status changes are traceable (completed/missed/rescheduled).
- Leadership dashboards surface trends and exceptions for oversight.
Application-layer defenses
- Server-only secrets: credentials never ship to the browser.
- Contact and write endpoints are designed to support rate limiting and abuse controls.
- Optional app attestation (App Check) can restrict requests to valid app instances.
Recommended hardening
Rate limiting, CAPTCHA/Turnstile for public forms, and app attestation for client apps.
Operational security
- Environment separation for dev vs production (recommended practice).
- Deployments and rule changes can be managed through controlled releases.
- Monitoring targets auth failures, permission denials, and anomalous write volume.
- Backups/exports support recovery from accidental deletion or bad deployments.
Reporting a security issue
If you believe you’ve found a security vulnerability, please report it responsibly. Do not include sensitive data in screenshots or attachments.
Note: This page describes our security posture at a high level. Specific controls may vary by environment and deployment configuration.