# CAIQ-Lite Self-Assessment

Version 1.0 · Last reviewed 2026-10-26 · Owner: Delora Legal (security@deloralegal.com)

Status: Self-assessment by Delora Legal. Not independently audited.

## How to read this

This is a short self-assessment written in the style of the Cloud Security Alliance Consensus Assessments Initiative Questionnaire (CAIQ). It follows the 17 domains of the Cloud Controls Matrix (CCM) version 4. The questions are our own plain-language paraphrases and are not the official CSA wording. It has 97 questions, which is a lite subset and not the full CAIQ.

- **Yes** means the control is in place today.
- **Partial** means part of the control is in place. The implementation text says what is missing and the planned step.
- **No** means the control is not in place. The planned step is given where there is one.
- **Not Applicable** means Delora does not run that part of the stack. Physical datacenter controls are inherited from Vercel, Neon and Amazon Web Services.
- Planned steps are plans, not commitments to a regulator.
- Twelve security policies are written but are still drafts until the owner approves them in Vanta. Where a control depends on a draft policy the answer is Partial.
- Delora is run by its owner today, who holds every role. There are no employees or contractors with production access.
- This is not a SOC 2 report, not a penetration test result and not a certification. Delora is not SOC 2 audited and holds no ISO 27001 certificate.

The same answers are available as a spreadsheet-friendly CSV: delora-legal-caiq-lite.csv.

## CSA STAR Registry

Delora has not submitted this self-assessment to the CSA STAR Registry and does not appear in it. Nothing in this document should be read as a STAR listing. A STAR Level 1 entry is a self-assessment, not an audit or a certification.

## Summary of answers by domain

| Domain | Yes | Partial | No | Not Applicable | Total |
|---|---|---|---|---|---|
| Audit & Assurance (A&A) | 1 | 2 | 2 | 0 | 5 |
| Application & Interface Security (AIS) | 4 | 2 | 0 | 0 | 6 |
| Business Continuity Management & Operational Resilience (BCR) | 1 | 5 | 0 | 0 | 6 |
| Change Control & Configuration Management (CCC) | 3 | 2 | 1 | 0 | 6 |
| Cryptography, Encryption & Key Management (CEK) | 3 | 2 | 1 | 0 | 6 |
| Datacenter Security (DCS) | 1 | 1 | 0 | 3 | 5 |
| Data Security & Privacy Lifecycle Management (DSP) | 5 | 2 | 0 | 0 | 7 |
| Governance, Risk & Compliance (GRC) | 3 | 3 | 0 | 0 | 6 |
| Human Resources (HRS) | 0 | 4 | 2 | 0 | 6 |
| Identity & Access Management (IAM) | 3 | 2 | 2 | 0 | 7 |
| Interoperability & Portability (IPY) | 2 | 1 | 1 | 0 | 4 |
| Infrastructure & Virtualization Security (IVS) | 2 | 1 | 1 | 1 | 5 |
| Logging & Monitoring (LOG) | 4 | 0 | 2 | 0 | 6 |
| Security Incident Management, E-Discovery & Cloud Forensics (SEF) | 1 | 4 | 1 | 0 | 6 |
| Supply Chain Management, Transparency & Accountability (STA) | 2 | 2 | 1 | 0 | 5 |
| Threat & Vulnerability Management (TVM) | 3 | 3 | 0 | 0 | 6 |
| Universal Endpoint Management (UEM) | 1 | 2 | 2 | 0 | 5 |
| **All domains** | **39** | **38** | **16** | **4** | **97** |

## Answers

#### Audit & Assurance (A&A)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| A&A-01.1 | Do you review on a regular schedule whether your security controls are in place and working? | Partial | Controls enforced in code are tested on every change (repository rules test, cross-tenant tests, end-to-end security inventory). The periodic review of operating controls (weekly alert review, failing-test review, quarterly access review) is written down in draft policies but no review has been recorded yet. Planned: Connect Vanta and start recording the weekly review. |
| A&A-02.1 | Has an independent auditor assessed your controls against a recognised framework (for example SOC 2 or ISO 27001)? | No | No. Delora is not SOC 2 audited and holds no ISO 27001 certificate. A SOC 2 Type I report is the target, with a Type II observation period after it. No date is committed for ISO 27001. |
| A&A-03.1 | Do you commission an independent penetration test at least once a year and fix what it finds? | No | No test has been done yet. The scope for an external tester is written (staging only, synthetic data). The draft policy sets fix targets of 7 days for critical, 30 for high and 90 for medium findings. Planned: External penetration test, criticals and highs fixed before the SOC 2 audit. |
| A&A-04.1 | Do you run automated security checks on every code change before it can be released? | Yes | Yes. GitHub Actions runs typecheck, lint, unit tests (with the real migrations), USCIS form-fill suites, Playwright end-to-end tests including exact security headers, and Trivy on dependencies and committed secrets (fails on fixable HIGH or CRITICAL). The SonarCloud upload runs once its token is configured. Branch protection on main makes lint-and-unit, e2e-playwright and unit-forms mandatory before merge; security-scan runs on every pull request but is not yet a required check (see CCC-02.1). |
| A&A-05.1 | Do you track audit and test findings to closure? | Partial | The draft change-management policy tracks each finding as a GitHub issue or Vanta task until closed. Vanta is still being set up, so there is no closure history yet. Planned: Close every failing Vanta test. |

#### Application & Interface Security (AIS)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| AIS-01.1 | Do you follow a documented secure development process? | Partial | Secure development rules exist as written hard rules for the codebase, checked by an automated repository test, and as a draft change-management policy (pull requests, tests with every change, migrations as code). The policy is a draft awaiting owner approval. Planned: Adopt the draft policies in Vanta. |
| AIS-02.1 | Do you validate all input at every interface? | Yes | Yes. Zod 4 schemas validate every form, route handler and API contract, including the contracts shared with the mobile apps. |
| AIS-03.1 | Do you protect the application against common web attacks with headers, rate limits and similar controls? | Partial | Every response carries CSP (default-src self, frame-ancestors none), HSTS (two years), nosniff, X-Frame-Options DENY, Referrer-Policy, Permissions-Policy and COOP, checked by an end-to-end test. Sign-in, sign-up, password reset, two-factor and demo requests are rate limited in Postgres. Two known gaps: the CSP still allows inline scripts, and HSTS has no includeSubDomains or preload. Planned: CSP nonces and HSTS subdomain coverage. |
| AIS-04.1 | Is every request authorised on the server, with one customer unable to reach another customer's data? | Yes | Yes. All tenant reads and writes run inside requireTenant().run() or withTenant(), which verifies membership. Postgres row-level security is enabled and forced on every tenant table with composite (firm_id, id) foreign keys, and cross-tenant tests cover it. |
| AIS-05.1 | Are your mobile and programmatic interfaces authenticated and rate limited? | Yes | Yes. The Android apps (in development, not yet released) use the /api/v1 interface with bearer tokens that come only from the mobile sign-in flow and are bound to a registered device row. Auth calls go through rate-limited server actions or the v1 client. /api/auth accepts GET only. |
| AIS-06.1 | Do you scan code and dependencies for known vulnerabilities and leaked secrets? | Yes | Yes. Dependabot opens weekly update pull requests (npm and SHA-pinned actions) and separate security updates. Trivy scans dependencies and committed secrets in CI. Local commands run pnpm audit with OSV (security:deps) and gitleaks (security:secrets). |

#### Business Continuity Management & Operational Resilience (BCR)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| BCR-01.1 | Do you have a documented business continuity and disaster recovery plan? | Partial | A draft policy covers targets, backups and restore, failure scenarios (bad deploy, bad migration, Neon or Vercel or Anthropic outage, owner unavailable) and capacity checks. It is a draft awaiting owner approval, and the backup person for the owner is not yet named. Planned: Adopt the draft policies in Vanta. |
| BCR-02.1 | Do you back up customer data, and how far back can you restore? | Partial | Neon keeps continuous point-in-time history of the database. The restore window is up to one day today (7 days on Neon's Launch plan). Restores go into a new branch first and are checked before switching. Moving to a plan with at least 7 days is an open owner step. Document upload is not live and no production file bucket exists yet, so there are no uploaded files to back up; when upload goes live, bucket versioning is an open owner check. Planned: Confirm a Neon plan with at least 7 days of restore history. |
| BCR-03.1 | Do you test restoring from backup at least once a year? | Yes | Yes. A scripted drill (pnpm restore:drill) restores staging into a new branch from point-in-time history and checks row counts, forced RLS, decryption of sealed identifiers and migration state, and reports recovery time. The first run, on 2026-10-27, passed every check in 12 seconds and is on record. It repeats quarterly. Production itself has not needed a restore. |
| BCR-04.1 | Have you set recovery time and recovery point objectives, and do you commit to an uptime figure? | Partial | Targets are proposed in the draft continuity policy (RPO 5 minutes, RTO 4 hours, internal uptime goal 99.5 percent monthly) but are not approved yet. The 99.5 percent monthly uptime goal is published on the Pricing page and in the FAQ as a target, not a service-level agreement. There is no customer-facing uptime SLA. Planned: Targets approved with the policies. No date committed for a published SLA. |
| BCR-05.1 | Do you review capacity and run load tests before large launches? | Partial | k6 load tests exist for staging and intake caps are set in code. A quarterly capacity check of Neon, Vercel and Anthropic limits is written in the draft policy, but no review has been recorded. Planned: First quarterly capacity check after the policy is adopted; no later date committed. |
| BCR-06.1 | Can you keep serving customers if a single hosting region or provider fails? | Partial | The database runs in one region (Neon US East). A documented but never-drilled plan restores the latest history into a new project in another region and repoints DATABASE_URL. Vercel rollbacks and the intake fallback during an Anthropic outage are documented. There is no active failover. Planned: No date committed for drilling the regional failover. |

#### Change Control & Configuration Management (CCC)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| CCC-01.1 | Do you have a documented change management policy, including emergency changes? | Partial | A draft policy covers pull requests, required checks, review, migrations, emergency changes (review within 1 business day) and dependency updates. It awaits owner approval. Planned: Adopt the draft policies in Vanta. |
| CCC-02.1 | Is every production change made through a reviewed pull request with required automated checks? | Partial | CI runs on every pull request and on pushes to main and staging. GitHub branch protection on `main` (checked 2026-10-27) requires the checks lint-and-unit, e2e-playwright and unit-forms to pass on an up-to-date branch, applies to admins, and blocks force pushes and deletion. Not yet: an approving review is not required (single engineer, see CCC-03.1), security-scan is not a required check, and staging is not protected. Planned: Add security-scan to the required checks, protect staging and move the repository to a GitHub organization. |
| CCC-03.1 | Is every change approved by someone other than its author before release? | No | No. Delora has one engineer. The compensating control in the draft policy is a pull request for every change, green required checks and the owner reviewing the full diff, recorded in Vanta as an approved exception until a second engineer joins. Planned: Compensating control recorded. Independent review starts when a second engineer joins; no date committed. |
| CCC-04.1 | Are database schema changes versioned, tested and applied in a controlled way? | Yes | Yes. Schema changes are Drizzle migrations in the repository, run by the migration role during the Vercel build before new code serves traffic. Unit tests run the real migrations on PGlite, and a schema guard test fails when a tenant table lacks its required controls. |
| CCC-05.1 | Are non-production environments separate from production and free of real customer data? | Yes | Yes. Staging runs as a separate Vercel environment on its own Neon branch with its own secrets and synthetic data only. Preview deployments use staging. A repository test fails on SSN-shaped or A-number-shaped values and on non-reserved email domains. |
| CCC-06.1 | Can you roll back a faulty release quickly? | Yes | Yes. Vercel keeps previous deployments and the previous one can be promoted instantly; fixes then go forward through a pull request. Bad migrations are handled by a restore to a point before them. |

#### Cryptography, Encryption & Key Management (CEK)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| CEK-01.1 | Do you have a documented encryption and key management policy? | Partial | A draft policy covers data in transit, at rest, the secrets inventory, rotation intervals and a rotation runbook. It awaits owner approval. Planned: Adopt the draft policies in Vanta. |
| CEK-02.1 | Is customer data encrypted in transit? | Yes | Yes. All traffic is HTTPS with HSTS (max-age two years). Database connections require TLS, and calls to Anthropic, Resend, AWS and Stripe use HTTPS. |
| CEK-03.1 | Is customer data encrypted at rest? | Yes | Yes, at two levels. Neon encrypts database storage (provider-managed AES-256). SSNs, A-Numbers, passport and travel document numbers and USCIS online account numbers are also sealed in the application with AES-256-GCM, bound to the firm, shown masked and decrypted only when a form is filled. Document upload is not live and no production file bucket exists yet, so no uploaded files are stored today; when upload goes live, files will go to Amazon S3 with AES-256 server-side encryption requested on every upload and copy. |
| CEK-04.1 | Are encryption keys generated, stored and accessed under defined controls? | Yes | Yes. FORMS_ENCRYPTION_KEY is a 32-byte key held in Vercel's environment (Sensitive, Production scope) and the password manager, never in the database or repository. Production fails closed without it. Staging, CI and production use separate secrets. The access review lists who can read production secrets. |
| CEK-05.1 | Can you rotate keys without losing data, and have you done it in production? | Partial | The mechanism is built and tested: a key ring with key ids in each sealed value (FORMS_ENCRYPTION_KEYS_PREVIOUS) and pnpm secrets:reseal, which re-encrypts stored values in one transaction. The auth secret rotates the same way. The first production rotation has not been done and recorded yet. Planned: Owner runs and records the first production rotation before the SOC 2 audit. |
| CEK-06.1 | Can customers supply or control their own encryption keys? | No | No. Keys are managed by Delora and its providers. Customer-managed keys are not offered. Planned: No date committed. |

#### Datacenter Security (DCS)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| DCS-01.1 | Do you operate datacenters or other physical facilities that hold customer data? | Not Applicable | Not applicable. Delora operates no datacenters. The service is hosted at Vercel, Neon and Amazon Web Services, and physical controls are inherited from them. Every provider that holds customer data is listed on the subprocessors page. A build and test machine in the owner's office runs CI on synthetic data only and holds no customer data. |
| DCS-02.1 | Do you control physical access, power, cooling and environmental protections for the systems that hold customer data? | Not Applicable | Not applicable to Delora directly. These controls belong to the hosting providers' facilities and are inherited from Vercel, Neon and AWS. |
| DCS-03.1 | Do you rely on your hosting providers for physical security, and is that reliance documented? | Yes | Yes, inherited. The SOC 2 scope treats Vercel, Neon, AWS, Anthropic, Resend and GitHub as subservice organizations: the auditor relies on their own SOC 2 reports and Delora operates the complementary user entity controls they list. The vendor policy requires a yearly review of each high-risk vendor's report. |
| DCS-04.1 | Have you collected and reviewed your hosting providers' current independent assurance reports? | Partial | The requirement is written, but the vendor SOC 2 reports and DPAs are still being collected into Vanta. That is an owner step. No annual review has been recorded yet. Planned: Collect the Vercel, Neon, AWS, Anthropic and Resend reports. |
| DCS-05.1 | Do you move, store or dispose of physical servers or storage media that hold customer data? | Not Applicable | Not applicable. Delora has no physical servers or media for customer data. Paper is not expected; laptops are covered under the endpoint domain. |

#### Data Security & Privacy Lifecycle Management (DSP)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| DSP-01.1 | Do you classify data and define handling rules for each class? | Partial | A draft policy defines Restricted, Confidential, Internal and Public classes. The Restricted class (SSN, A-Number, passport and USCIS account numbers) is already enforced in code through SENSITIVE_KEYS: sealed, masked and never logged or sent to any AI. Planned: Adopt the draft policies in Vanta. |
| DSP-02.1 | Do you document where customer data is stored and how it flows between systems? | Yes | Yes. The system description, architecture and trust boundaries are written down, and the public subprocessor list states which vendor handles which data. |
| DSP-03.1 | Do you enforce retention limits and delete data when it is no longer needed? | Partial | A daily purge (Vercel Cron to /api/cron/purge, fails closed without CRON_SECRET) deletes unsubmitted intakes after 30 days, unaccepted intakes after 180 days, demo leads and deletion requests after 24 months, expired sessions and tokens, and security events after 1 year. Closing a firm deletes its data. Generated PDFs are never stored. Gaps: the audit log is kept for the life of the firm today, there are no per-firm retention settings, and deleted data stays in restore history until the restore window passes. Planned: Audit log retention needs a closed-firm date first and per-firm settings are a later option; no date committed. |
| DSP-04.1 | Do you limit the customer data sent to third parties, including AI providers, to what the task needs? | Yes | Yes. Only the intake conversation and the masked transcript go to the AI provider. Document upload is not live, so no document or photo is sent to any AI today; when it goes live, passports will be read locally and never sent, and only birth and marriage certificate photos will go to the provider, after a local check for identifiers. SSNs are removed before storage and before the model, A-numbers are masked, and sealed case-profile identifiers are never sent to any AI (a test replays the pipeline against a recording AI). Prompts are static. Delora states that firm content is not used to train AI models. |
| DSP-05.1 | Is production customer data kept out of development, test and demo environments? | Yes | Yes. Staging, tests, demos and the repository use synthetic data only, and a repository test fails on SSN-shaped or A-number-shaped values. |
| DSP-06.1 | Can customers export their data and delete their accounts, and do you handle data subject requests? | Yes | Yes. Firm admins download everything as a JSON file and CSV files (sealed identifiers masked in the JSON and left out of the CSVs; export audit-logged). A ZIP of uploaded files is added when document upload goes live; it is not live yet. Users can leave a firm, close a firm they alone belong to, or use the account deletion page. Requests about a firm's client data are forwarded to the firm, which is the controller, under the draft privacy policy. |
| DSP-07.1 | Do you offer customers a signed data processing agreement? | Yes | Yes. A customer DPA with EU Standard Contractual Clauses and the UK Addendum, reviewed by counsel on 2026-10-26 (version 1.1, with changes approved by counsel on 2026-10-29), is signed with customers on request. |

#### Governance, Risk & Compliance (GRC)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| GRC-01.1 | Do you have a named owner for the security program? | Partial | The owner of Delora Legal acts as security officer and holds every role today; there is no separate security staff. The draft information security policy names the role and its duties, and awaits owner approval. Planned: Adopt the draft policies in Vanta. |
| GRC-02.1 | Are your security policies approved by management and reviewed at least yearly? | Partial | Twelve policies are written (information security, access control, change management, encryption, data retention, incident response, logging and monitoring, personnel security, privacy, risk management, vendor management, business continuity). All are drafts until the owner approves them in Vanta. Planned: Adopt the draft policies in Vanta. |
| GRC-03.1 | Do you perform a documented risk assessment at least yearly? | Partial | A starter register of 15 risks with scores and treatments is drafted. The first assessment has not been run or recorded in Vanta. Planned: Risk assessment in Vanta. |
| GRC-04.1 | Do you obtain legal review of customer-facing legal terms and notices? | Yes | Yes. The Privacy Policy, Terms, Subprocessors page and intake disclaimers were reviewed by counsel on 2026-10-26, and counsel approved their current wording, including the intake consent version 2026-10-27, on 2026-10-29. Any wording change goes back to counsel. |
| GRC-05.1 | Are your key engineering and security rules enforced automatically rather than by memory? | Yes | Yes. A repository test checks the hard rules (no SOC 2 certification claims, no PII-shaped values, subprocessor list matching the policy, no PII in logs), and further tests cover tenancy, sealed identifiers and the AI boundary. |
| GRC-06.1 | Do you govern use of AI so that outputs are reviewed and legal advice is not given? | Yes | Yes. Drafted work (intake summaries, form data carried over from an intake, time descriptions) is reviewed by the firm before use, and only an attorney or admin approves a USCIS form. The intake assistant talks with prospects in real time under fixed rules: no legal advice, outcome predictions or filing recommendations, with a filter that holds back advice-like replies and 143 scripted safety evals. |

#### Human Resources (HRS)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| HRS-01.1 | Do you run background checks on people before they get access to production or customer data? | No | No background checks are recorded. Delora has no employees or contractors with production access today. The draft policy requires checks, through Vanta's background-check integrations, before any future person gets access. Planned: Background checks for everyone with access. |
| HRS-02.1 | Does everyone with access complete security awareness training? | No | No training completion is recorded yet. The draft policy requires training at hire and yearly, tracked in Vanta. Planned: Security awareness training. |
| HRS-03.1 | Do people with access sign confidentiality terms and accept your security policies? | Partial | Required by the draft personnel policy (confidentiality agreement and policy acceptance before access). Acceptance cannot be recorded until the policies are approved and adopted in Vanta. Planned: Adopt the draft policies in Vanta. |
| HRS-04.1 | Do you have a documented process for removing access when someone leaves or changes role? | Partial | The draft access-control policy sets a joiner, mover and leaver procedure: leaver access removed within 1 business day, and secrets the person could read rotated. It has never been exercised because no one has left. Planned: Adopt the draft policies in Vanta. |
| HRS-05.1 | Do you have an acceptable use policy and a code of conduct? | Partial | The draft personnel security policy contains acceptable use rules (no real client data in code, tests, tickets or chat; no shared accounts) and a code of conduct that includes not misstating Delora's security or compliance status. It is a draft. Planned: Adopt the draft policies in Vanta. |
| HRS-06.1 | Is there a defined way for people to report suspected security incidents? | Partial | The draft incident response policy tells anyone to email security@deloralegal.com immediately. The mailbox is a Google Workspace alias, recorded in our email setup notes as of 2026-10-26, but the owner still needs to confirm that it receives mail. Planned: Owner confirms the mailbox and adopts the policy. |

#### Identity & Access Management (IAM)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| IAM-01.1 | Do you have a documented access control policy covering least privilege and production access? | Partial | A draft policy requires one named account per person, least privilege, restricted and recorded production database access, 16-character unique passwords from a password manager, and quarterly reviews. It awaits owner approval. Planned: Adopt the draft policies in Vanta. |
| IAM-02.1 | Do you offer multi-factor authentication to customer users, and can a firm require it? | Yes | Yes. Authenticator-app (TOTP) with ten one-time backup codes; no SMS or email codes. Each firm sets its policy: optional, required for admins and attorneys (the default for new firms), or required for everyone. A covered member is blocked until enrolled. Admins can reset a member who lost their phone. |
| IAM-03.1 | Is multi-factor authentication required on your own administrative consoles? | Partial | Required by the draft access-control policy for GitHub, AWS, Vercel, Neon, Anthropic, Resend, the domain registrar, Google Workspace and the password manager. Enabling it on each console is an owner step in progress and is not yet recorded as complete. Planned: MFA on every admin console. |
| IAM-04.1 | Are roles and permissions enforced by role, in code and in the database? | Yes | Yes. Roles are admin, attorney and paralegal per firm. Paralegals cannot accept or decline intakes, replace the intake link, approve forms or edit attorney profiles. Form approval is limited to attorneys and admins in code and by a database trigger. Delora staff have no feature to sign in as a firm. |
| IAM-05.1 | Do you enforce strong password, session and sign-in protections for customer users? | Yes | Yes. Passwords are 12 to 128 characters with email confirmation required. Sessions last 7 days and are revoked on password reset. Reset tokens expire after one hour. Sign-in is limited to 20 attempts per IP and 10 per email per 15 minutes, with a two-factor lockout after repeated wrong codes. |
| IAM-06.1 | Do you review who has access to systems and customer data on a schedule? | No | No review has been performed yet. The draft policy requires a quarterly review of every account, key and secret holder, recorded in Vanta. In the product, firm admins invite attorneys, paralegals and assistants by email (single-use, expiring links) and can remove paralegals, which signs them out everywhere; invitations for admins, removing an attorney, and role changes are not available yet. Planned: First access review. |
| IAM-07.1 | Do you support single sign-on (SAML or OIDC) or passkeys for customers? | No | Not yet. Both are on the roadmap. Planned: No date committed. |

#### Interoperability & Portability (IPY)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| IPY-01.1 | Can customers export all of their data in a standard, machine-readable format? | Yes | Yes. Firm admins export members, clients, matters, case and attorney profiles, form records, intake links and transcripts, document metadata, time entries, invoices, devices and the firm's audit log as one JSON file, with CSV files for spreadsheets. A ZIP of uploaded files, exactly as uploaded, is added when document upload goes live; it is not live yet. Sealed identifiers are masked in the JSON and left out of the CSVs, and the export is audit-logged with row counts only. |
| IPY-02.1 | Do you provide a documented public API for customers? | No | No. The /api/v1 interface exists for Delora's own Android apps, which are in development and not yet released, and is not offered or documented for third-party use. Planned: No date committed. |
| IPY-03.1 | Do your interfaces use standard protocols and open formats? | Yes | Yes. Customers connect over HTTPS, data is exchanged as JSON, the database is standard Postgres, and filled forms are the official USCIS PDFs. |
| IPY-04.1 | Do customers have a defined exit path, including help moving their data and confirmed deletion? | Partial | Self-service export (a JSON file and CSV files; a ZIP of uploaded documents is added when document upload goes live) and firm closure (self-service for a firm's only member, 14 days after the request; all firm data deleted in one transaction) exist. The counsel-reviewed customer DPA, signed on request, covers export at any time, including after the agreement ends, and deletion when the firm closes. There is no separate exit-assistance commitment. The Terms of Service (counsel-approved 2026-10-29) keep a lapsed firm's data until the firm closes its account or asks in writing for deletion. Deleted data stays in database restore history until the restore window passes. Planned: No separate exit-assistance commitment; no date committed. |

#### Infrastructure & Virtualization Security (IVS)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| IVS-01.1 | Are production and non-production environments separated? | Yes | Yes. Staging is a separate Vercel environment on a separate Neon branch with separate secrets. Staging is the only target of the ZAP scan script, which refuses to run against production. |
| IVS-02.1 | Do you harden and patch the servers and hypervisors that run your service? | Not Applicable | Not applicable. The service runs on no servers of Delora's own (the build and test machine in the owner's office is not part of the service). Host and platform patching is done by Vercel and Neon; Delora patches its own application dependencies (see TVM-02.1). |
| IVS-03.1 | Is network access to the production database restricted? | Partial | The database requires TLS and the app connects as a least-privilege role (never superuser or BYPASSRLS, checked at start-up). There is no IP allow list because Vercel egress addresses are dynamic; the draft risk register records this as an accepted risk pending owner sign-off. Planned: Owner signs off the accepted risk. Revisit with static IPs; no date committed. |
| IVS-04.1 | Is multi-tenant separation enforced at the data layer rather than only in application code? | Yes | Yes. Row-level security is enabled and forced on every tenant table, keyed on a transaction-local firm and user context. Without that context a query returns zero rows, and the app refuses to start in production if its role could bypass RLS. |
| IVS-05.1 | Are your cloud accounts hardened (root MFA, central audit trail, threat detection)? | No | Not recorded as done. The hardening steps are written for AWS (root MFA, IAM Identity Center, CloudTrail with one-year retention, GuardDuty, Security Hub, S3 Block Public Access) but the sources do not show them completed. Planned: AWS hardening. |

#### Logging & Monitoring (LOG)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| LOG-01.1 | Do you keep a tamper-resistant audit log of actions taken in customer accounts? | Yes | Yes. The per-firm audit_log records firm creation, intake actions, case profile and form actions and approvals, document links, exports, MFA and policy changes and deletions, with ids only. The app role has INSERT and SELECT but no UPDATE or DELETE grant. |
| LOG-02.1 | Do you log authentication and other security events, and can customers see their own? | Yes | Yes. The append-only security_events table records sign-ins and failures, lockouts, two-factor challenges, sign-out, password resets, email confirmation, MFA changes, admin resets and policy changes with user id, IP and a capped user agent, never an email, password or code. Users see their own events; firm admins see their members'. Retained one year. |
| LOG-03.1 | Are application logs kept free of personal data? | Yes | Yes. Runtime logs use fixed prefixes and carry ids, not names, emails or identifiers; quoted user text is redacted before logging, and a repository test checks for PII in logging. |
| LOG-04.1 | Do you retain application logs for a year and alert on suspicious activity? | No | No. Vercel keeps runtime logs only briefly and nothing yet alerts on error spikes or failed sign-in spikes. The log drain with one-year retention and metric alarms is not built yet. Planned: Log drain and alerts. |
| LOG-05.1 | Do you monitor service availability and alert someone when it fails? | Yes | Yes. Three keyword monitors (home page, login page and the /api/health database check) run every 3 minutes from several regions in Better Stack and email the owner on failure. They have been in use since 2026-10-26. |
| LOG-06.1 | Do you review logs and alerts on a regular schedule? | No | No review has been recorded. A weekly 10-minute review of alerts, failed sign-ins and failing Vanta tests is defined in the draft policy. Planned: Weekly reviews recorded in Vanta. |

#### Security Incident Management, E-Discovery & Cloud Forensics (SEF)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| SEF-01.1 | Do you have a documented incident response plan? | Partial | A draft policy defines severity levels, response start times, triage, contain, investigate, recover and notify steps, and a post-incident review within 5 business days for Sev 1 and 2. It awaits owner approval. Planned: Adopt the draft policies in Vanta. |
| SEF-02.1 | Have you tested the incident response plan with an exercise? | No | No exercise has been run. The draft policy calls for a tabletop at least yearly. Planned: One-hour tabletop. |
| SEF-03.1 | Is there a published way for customers and researchers to report a security issue? | Yes | Yes. The Security page asks reporters to email security@deloralegal.com, promises acknowledgement within 2 business days and a good-faith research safe harbor. The owner still needs to confirm that the mailbox receives mail. |
| SEF-04.1 | Do you have a commitment to notify affected customers of a breach within a set time? | Partial | The customer DPA, reviewed by counsel on 2026-10-26, commits Delora to notify affected firms without undue delay and within 72 hours of becoming aware of a personal data breach. It is contractual for each customer that signs the DPA; for others it is the same commitment as policy. Planned: offer the DPA to every customer at sign-up. |
| SEF-05.1 | Can you collect and preserve evidence for an investigation? | Partial | The audit log and security events are append-only, and the incident policy says to export and not edit evidence. Platform logs are short-lived until the log drain exists, and AWS CloudTrail is not yet confirmed as enabled. Planned: Log drain and AWS CloudTrail. |
| SEF-06.1 | Can you preserve customer data on a legal hold? | Partial | The security officer can pause the daily purge for everyone by removing the cron job or unsetting CRON_SECRET, and records it. There is no per-firm hold yet. Planned: Per-firm hold: no date committed. |

#### Supply Chain Management, Transparency & Accountability (STA)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| STA-01.1 | Do you publish your subprocessors and give customers notice of changes? | Yes | Yes. The public Subprocessors page lists every company that processes firm content, all in the United States, with what each handles. Firm admins are emailed at least 30 days before a new one processes firm content. A repository test keeps the list in step with the vendor policy. |
| STA-02.1 | Do you assess vendors before use and collect their security reports and agreements? | Partial | The draft vendor policy requires a SOC 2 report review, a DPA, a no-training check and a risk rating before a vendor touches customer data, and lists the evidence for each current vendor. The reports and DPAs are still being collected into Vanta. Planned: Vendor documents collected. |
| STA-03.1 | Have you documented which security responsibilities sit with Delora, its providers and its customers? | Partial | Internally yes: the SOC 2 scope carves out the infrastructure providers, and firms are the controllers of client data while Delora is the processor. A customer-facing shared responsibility statement does not exist yet. Planned: Customer-facing statement: no date committed. |
| STA-04.1 | Do you describe your security and compliance status accurately in public? | Yes | Yes. Public copy keeps SOC 2 on the roadmap and makes no certification claim. A repository test blocks certification language, and the sales answer sheet lists claims to avoid. |
| STA-05.1 | Do your AI provider's terms limit retention of the data you send? | No | Not yet. Zero data retention is approved per organization by Anthropic and has been requested as an open owner step. Until it is approved, Anthropic's standard API retention applies. The caveat that intake uses prompt caching is still to be settled with Anthropic. Planned: Anthropic ZDR approval requested. |

#### Threat & Vulnerability Management (TVM)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| TVM-01.1 | Do you scan for vulnerable dependencies on every change and on a schedule? | Yes | Yes. Trivy runs in CI and fails on fixable HIGH or CRITICAL findings; Dependabot runs weekly with separate security updates; pnpm security:deps runs pnpm audit and OSV locally. |
| TVM-02.1 | Do you apply dependency and platform updates promptly? | Yes | Yes. Dependabot opens update pull requests weekly for npm packages and SHA-pinned GitHub Actions, and each goes through CI before merge. |
| TVM-03.1 | Do you have defined deadlines for fixing vulnerabilities by severity? | Partial | Proposed in the draft policy: critical within 7 days, high 30, medium 90, low next planned work or accepted in the risk register. Not yet adopted. Planned: Adopt the draft policies in Vanta. |
| TVM-04.1 | Do you run dynamic security scans against the running application? | Partial | An OWASP ZAP baseline script and rule file exist (pnpm security:zap) and run against staging only. No scheduled run or recorded result exists yet, and the external penetration test is also pending. Planned: First ZAP baseline and the external test. |
| TVM-05.1 | Do you accept and respond to vulnerability reports from outside researchers? | Yes | Yes. The Security page gives a reporting address, an acknowledgement time of 2 business days and a statement that good-faith research that follows its rules will not be pursued. |
| TVM-06.1 | Do you run static code analysis on your source? | Partial | SonarCloud analysis and coverage upload are wired into CI and run once the SONAR_TOKEN secret is set. Lint and strict TypeScript checks run on every pull request. Planned: Owner sets the SonarCloud token; no date committed. |

#### Universal Endpoint Management (UEM)

| Question ID | Question | Answer | Implementation |
|---|---|---|---|
| UEM-01.1 | Do you keep an inventory of the laptops and other devices used to reach production systems? | No | No recorded inventory. The draft policy has every such laptop run the Vanta Agent, which provides the inventory. Planned: Install the Vanta Agent on every laptop with production access. |
| UEM-02.1 | Are disk encryption, screen lock, operating system updates and malware protection enforced and verified on those devices? | No | Required by the draft device policy but not yet verified or recorded. Verification comes from the Vanta Agent. Planned: Verified through the Vanta Agent. |
| UEM-03.1 | Is customer data kept off employee laptops? | Partial | The draft policy forbids copying production data to laptops. Development, tests and demos use synthetic data only, and a repository test enforces that. Direct production database access is limited to migrations, incidents and restores. Planned: Adopt the draft policies in Vanta. |
| UEM-04.1 | Do you have a procedure for lost or stolen devices? | Partial | The draft personnel policy treats a lost or stolen device as an incident to report at once, and the incident response policy then applies, including rotating secrets. It is a draft. Planned: Adopt the draft policies in Vanta. |
| UEM-05.1 | Are customer mobile app sessions tied to a registered device? | Yes | Yes. Mobile bearer tokens come only from the mobile sign-in flow and must be bound to a devices row. |

## Open items

Every Partial and No answer, with its planned step.

| Question ID | Answer | Planned step and date |
|---|---|---|
| A&A-01.1 | Partial | Connect Vanta and start recording the weekly review. |
| A&A-02.1 | No | SOC 2 Type I report, then a Type II observation period. No date is committed for ISO 27001. |
| A&A-03.1 | No | External penetration test, criticals and highs fixed before the SOC 2 audit. |
| A&A-05.1 | Partial | Close every failing Vanta test. |
| AIS-01.1 | Partial | Adopt the draft policies in Vanta. |
| AIS-03.1 | Partial | CSP nonces and HSTS subdomain coverage. |
| BCR-01.1 | Partial | Adopt the draft policies in Vanta. |
| BCR-02.1 | Partial | Confirm a Neon plan with at least 7 days of restore history. |
| BCR-04.1 | Partial | Targets approved with the policies. No date committed for a published SLA. |
| BCR-05.1 | Partial | First quarterly capacity check after the policy is adopted; no later date committed. |
| BCR-06.1 | Partial | No date committed for drilling the regional failover. |
| CCC-01.1 | Partial | Adopt the draft policies in Vanta. |
| CCC-02.1 | Partial | Add security-scan to main's required checks, protect staging and move the repository to a GitHub organization. |
| CCC-03.1 | No | Compensating control recorded. Independent review starts when a second engineer joins; no date committed. |
| CEK-01.1 | Partial | Adopt the draft policies in Vanta. |
| CEK-05.1 | Partial | Owner runs and records the first production rotation before the SOC 2 audit. |
| CEK-06.1 | No | No date committed. |
| DCS-04.1 | Partial | Collect the Vercel, Neon, AWS, Anthropic and Resend reports. |
| DSP-01.1 | Partial | Adopt the draft policies in Vanta. |
| DSP-03.1 | Partial | Audit log retention needs a closed-firm date first and per-firm settings are a later option; no date committed. |
| GRC-01.1 | Partial | Adopt the draft policies in Vanta. |
| GRC-02.1 | Partial | Adopt the draft policies in Vanta. |
| GRC-03.1 | Partial | Risk assessment in Vanta. |
| HRS-01.1 | No | Background checks for everyone with access. |
| HRS-02.1 | No | Security awareness training. |
| HRS-03.1 | Partial | Adopt the draft policies in Vanta. |
| HRS-04.1 | Partial | Adopt the draft policies in Vanta. |
| HRS-05.1 | Partial | Adopt the draft policies in Vanta. |
| HRS-06.1 | Partial | Owner confirms the mailbox and adopts the policy. |
| IAM-01.1 | Partial | Adopt the draft policies in Vanta. |
| IAM-03.1 | Partial | MFA on every admin console. |
| IAM-06.1 | No | First access review. |
| IAM-07.1 | No | No date committed. |
| IPY-02.1 | No | No date committed. |
| IPY-04.1 | Partial | No separate exit-assistance commitment; no date committed. |
| IVS-03.1 | Partial | Owner signs off the accepted risk. Revisit with static IPs; no date committed. |
| IVS-05.1 | No | AWS hardening. |
| LOG-04.1 | No | Log drain and alerts. |
| LOG-06.1 | No | Weekly reviews recorded in Vanta. |
| SEF-01.1 | Partial | Adopt the draft policies in Vanta. |
| SEF-02.1 | No | One-hour tabletop. |
| SEF-04.1 | Partial | Commitment fixed in the customer DPA with counsel. |
| SEF-05.1 | Partial | Log drain and AWS CloudTrail. |
| SEF-06.1 | Partial | Per-firm hold: no date committed. |
| STA-02.1 | Partial | Vendor documents collected. |
| STA-03.1 | Partial | Customer-facing statement: no date committed. |
| STA-05.1 | No | Anthropic ZDR approval requested. |
| TVM-03.1 | Partial | Adopt the draft policies in Vanta. |
| TVM-04.1 | Partial | First ZAP baseline and the external test. |
| TVM-06.1 | Partial | Owner sets the SonarCloud token; no date committed. |
| UEM-01.1 | No | Install the Vanta Agent on every laptop with production access. |
| UEM-02.1 | No | Verified through the Vanta Agent. |
| UEM-03.1 | Partial | Adopt the draft policies in Vanta. |
| UEM-04.1 | Partial | Adopt the draft policies in Vanta. |

That is 55 open items out of 97 questions.
