Platform Security
Critical Bridge security and accountability
Sales Engineers put their customers' environments into Critical Bridge: asset inventories, network details, log volumes, compliance gaps and bid documents. That information is sensitive, and protecting it is the first requirement of the platform, not a feature added later.
Critical Bridge protects your data in layers: encrypted storage and transport, database-level isolation between organizations, server-side access control, records that protected against rewriting, and targeted security scans and regression tests.
Encryption and infrastructure
Encrypted storage and transport are part of the platform's layered safeguards.
- ·At rest: managed database and file-storage services provide encryption at rest.
- ·In transit: public access uses HTTPS to protect information in transit.
- ·Infrastructure: Critical Bridge uses Lovable Cloud for managed data, authentication and storage. Infrastructure safeguards do not make an individual customer deployment certified.
Your data stays yours
Organization-scoped database policies and server-side authorization protect customer records.
- ·Database-level isolation: row-level security restricts organization-owned records. Cross-organization access requires the applicable explicit authorization, not simply a position in the commercial hierarchy.
- ·Server-side, not screen-deep: isolation does not depend on what the app shows or hides. Hiding a button is never the control.
- ·Organization from the record, not the request: the platform determines ownership from the data being accessed, so a user cannot claim to be in another organization.
- ·Commercial scope is not customer access: Master Reseller tool access is restricted; a commercial relationship alone does not grant access to customer engagements.
- ·Active membership checks: deactivation removes membership-based access on subsequent authorization checks.
Access control
Within your organization, people see and change only what their role allows.
- ·Roles and authorities: membership, assignments and required capabilities are checked beyond the interface. System Administrator authority does not automatically grant review, release or Executive Exception authority.
- ·Least privilege by default: features are available only to the roles and plans that need them.
- ·Signed-in access only: platform data and functions require an authenticated session; public pages expose no customer data.
- ·Sales and customer boundaries: Sales users have a restricted intake and released-report view; customer users do not receive engineering tools or draft-generation access.
No standing access, not even for us
The Critical Bridge support team has no standing access to your engagement data.
- ·Your approval opens the door: reaching your records requires a request tied to an open support ticket, a written purpose, a single scope and an expiry no more than 72 hours out. An administrator on your account approves it, and can end it at any time.
- ·Read-only: support access can view, never change, approve or release anything.
- ·Recorded: every support session records who, what, when and how, and the record cannot be edited.
Records that can't be rewritten
The records that matter most are locked at the database level once they are final, so history cannot be quietly changed.
- ·Immutable records: issued quotes, compliance control results, evidence attestations, GRC document versions and bid review history cannot be edited or deleted after they are finalized, even by administrators using the app.
- ·Permanent audit trail: significant actions are written to an append-only, hash-chained audit log. Database guards refuse mutation and deletion of audit entries, including during organization or customer deletion; chain verification detects tampering.
- ·Evidence you can stand behind: because finalized records cannot be altered, what you show an auditor or a customer is what was actually recorded at the time.
Safe handling of files and input
Supported uploads and spreadsheet workflows include format validation and input protections.
- ·Allowed file types only: uploads accept specific document and spreadsheet formats and refuse everything else with a clear message.
- ·Spreadsheet safety: supported spreadsheet imports and exports include protections against formula execution.
- ·Evidence is not authority: uploaded content is source material for review. AI-assisted drafts cannot authorize release or replace deterministic results.
- ·Maintained dependencies: third-party libraries come from maintained, published releases and are scanned for known vulnerabilities.
Security checks and regression proofs
Automated scans and targeted tests help verify access and protected-record rules.
- ·Automated scanning: code, database access rules and third-party dependencies are scanned for security issues as the platform changes.
- ·Verification: security fixes are checked against the affected behavior; a scan alone is not a guarantee that no vulnerabilities exist.
- ·Security regression tests: automated tests cover permission logic and protected-record rules, and run as the platform changes.
Shared responsibility
Security is a partnership: we secure the platform, and you control who uses it.
| Critical Bridge secures | You control |
|---|---|
| Encryption at rest and in transit | Who is invited to your organization |
| Isolation between organizations | Which role each user has |
| Server-side access control | Removing users who leave your team |
| Immutable records and audit trail | What data you enter and upload |
| Security scans and regression checks | Strong, unique passwords for your users |
Compliance posture
Critical Bridge helps you run compliance work, and we are precise about what that does and does not mean.
- ·Frameworks supported: the platform includes assessment packs for CJIS, HIPAA, PCI DSS, NIST 800-53 Moderate and a general IT and security baseline, to help you assess and document your customers' environments.
- ·Assessment, not certification: framework support helps teams record findings and evidence; it does not certify Critical Bridge or the customer's organization.
- ·Not a system of record for regulated data: do not store Criminal Justice Information (CJI), Protected Health Information (PHI) or payment card data in Critical Bridge. Record findings and evidence about those systems, not the regulated data itself.
- ·Evidence stays where it lives: compliance registers record that a document exists, who owns it and where it is kept, not the document itself. Critical Bridge never becomes the custodian of your policies, audit reports or regulated data.