CIS Controls v8 IG1 Assessment
56 safeguards assessed
- Implemented: 5
- Partial: 30
- Not implemented: 17
- Not applicable: 4
Version 1.0 · Last reviewed 2026-10-26 · Owner: Delora Legal (security@deloralegal.com)
Status: Self-assessment by Delora Legal against CIS Controls v8 Implementation Group 1. Not independently audited.
About this assessment
The CIS Critical Security Controls (version 8) are a prioritized list of defensive practices published by the Center for Internet Security. Implementation Group 1 (IG1) is the set of 56 safeguards CIS describes as basic cyber hygiene for small organizations with limited security staff. This page records how Delora Legal measures against each of those 56 safeguards today.
Delora Legal makes practice-management software for small US law firms in immigration, consumer bankruptcy, family law and estate planning. It is run by its owner alone, with no employees and no contractors who have production access. Everything it runs is hosted by cloud providers (Vercel, Neon, Amazon Web Services and others listed on the subprocessors page). Delora owns no servers that run the service and no network equipment. Its physical assets are the owner's laptops and phone, and a Mac mini in the owner's office that runs builds and tests on synthetic data and holds no customer data.
Delora wrote this assessment itself. It has not been reviewed by an auditor or by CIS, and it is not a certification. Safeguard titles below are short paraphrases; the authoritative wording is in the CIS Controls v8 document at cisecurity.org.
How to read the status column
- Implemented: the practice is in place.
- Partial: part of the practice is in place, or the practice exists but a named step (usually an owner step) is still open. The "How Delora implements it" text says what is missing.
- Not implemented: the practice is not in place, or it cannot be shown to be in place today. A written plan or policy draft does not move a safeguard out of this status.
- Not applicable: the safeguard applies to equipment or networks Delora does not own or operate. The text says who carries the responsibility instead.
Delora's internal security policies are drafts until the owner approves them in Vanta, the compliance tool Delora is setting up. A safeguard that rests only on a draft policy is marked Partial at best. Several laptop-level safeguards (disk encryption, screen lock, firewall, malware protection, OS updates) are marked Not implemented because nothing records that they are enabled; installing the Vanta Agent will produce that record.
Planned steps are plans, not commitments to customers.
Summary
| Control | IG1 safeguards | Implemented | Partial | Not implemented | N/A |
|---|---|---|---|---|---|
| 1 Inventory and Control of Enterprise Assets | 2 | 0 | 1 | 1 | 0 |
| 2 Inventory and Control of Software Assets | 3 | 1 | 2 | 0 | 0 |
| 3 Data Protection | 6 | 2 | 3 | 1 | 0 |
| 4 Secure Configuration of Enterprise Assets and Software | 7 | 0 | 3 | 2 | 2 |
| 5 Account Management | 4 | 0 | 3 | 1 | 0 |
| 6 Access Control Management | 5 | 0 | 4 | 0 | 1 |
| 7 Continuous Vulnerability Management | 4 | 1 | 3 | 0 | 0 |
| 8 Audit Log Management | 3 | 0 | 3 | 0 | 0 |
| 9 Email and Web Browser Protections | 2 | 0 | 0 | 2 | 0 |
| 10 Malware Defenses | 3 | 0 | 0 | 3 | 0 |
| 11 Data Recovery | 4 | 0 | 3 | 1 | 0 |
| 12 Network Infrastructure Management | 1 | 0 | 0 | 0 | 1 |
| 13 Network Monitoring and Defense | 0 | 0 | 0 | 0 | 0 |
| 14 Security Awareness and Skills Training | 8 | 0 | 2 | 6 | 0 |
| 15 Service Provider Management | 1 | 1 | 0 | 0 | 0 |
| 16 Application Software Security | 0 | 0 | 0 | 0 | 0 |
| 17 Incident Response Management | 3 | 0 | 3 | 0 | 0 |
| 18 Penetration Testing | 0 | 0 | 0 | 0 | 0 |
| Total | 56 | 5 | 30 | 17 | 4 |
In plain terms: 5 of 56 safeguards are fully in place, 30 are partly in place, 17 are not in place, and 4 do not apply to a cloud-only company. Most of the Partial and Not implemented items are company-operations safeguards (laptops, training, written processes) rather than product security. The product's own technical controls (tenant isolation in the database, encrypted identifiers, append-only logs, dependency scanning) are described in the Trust Center.
Controls
Control 1: Inventory and Control of Enterprise Assets
For a cloud-only, single-operator company the enterprise assets are the owner's laptops and phone, the office Mac mini that runs builds and tests, and the cloud accounts and consoles Delora administers. No server runs the service, and there are no routers or other office devices. The practical risk is an unknown device or account with access to production, which is why this control leans on the planned account and access reviews.
Note on pnpm security:inventory: this command lists every page, route handler and server action found in the application source and the access level each must enforce, and fails if one is not listed. It is an inventory of the application's attack surface, tested by the Playwright suite. It is not a hardware or account inventory and is not evidence for safeguard 1.1.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 1.1 | Detailed enterprise asset inventory | Partial | The cloud accounts, consoles and vendors in use are listed in the access-control and vendor-management policies. Laptops and the phone are not yet inventoried in any tool; the Vanta Agent install on every laptop with production access is planned. |
| 1.2 | Address unauthorized assets | Not implemented | No process detects or removes an unknown device or account today. The first access review, listing every person and key with production access, is planned. It will be a manual, quarterly review rather than automated detection. |
Control 2: Inventory and Control of Software Assets
The software that matters is the application's dependency tree and the build pipeline, both controlled through the repository, plus whatever the owner installs on the laptops. The first two are well covered; laptop software is not yet inventoried.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 2.1 | Software inventory | Partial | Every application dependency and its exact version is recorded in pnpm-lock.yaml, and GitHub Actions are pinned to commit hashes. Software installed on the owner's laptops is not inventoried until the Vanta Agent is installed. |
| 2.2 | Authorized software is supported | Implemented | Dependabot opens weekly update pull requests for npm packages and GitHub Actions. Trivy runs on every pull request and fails the build on fixable HIGH or CRITICAL findings. pnpm security:deps (pnpm audit plus OSV-Scanner) fails on high or critical advisories unless a dated, reasoned entry exists in an allowlist. Enabling Dependabot security updates in the repository settings is an open owner step. |
| 2.3 | Address unauthorized software | Partial | CI installs with a frozen lockfile, so a dependency cannot enter a build without appearing in a reviewed lockfile change. There is no control over what is installed on the owner's laptops (no endpoint management tool yet). |
Control 3: Data Protection
Delora holds client and case data for law firms, including sensitive identifiers. This is the area where the product's controls are strongest: firm data is isolated in the database, and the most sensitive identifiers are sealed with application-level encryption. The gaps are in written data-management documents and in encryption of the owner's laptops.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 3.1 | Data management process | Partial | A classification and retention policy (Restricted, Confidential, Internal, Public) is written but is a draft awaiting owner approval. The rules it describes are partly enforced in code (retention purge, sealed identifiers, no PII in logs). |
| 3.2 | Data inventory | Partial | The database schema is in version control and the classification table names the sensitive data types. A firm admin can export all of a firm's data as a JSON file with CSV files. A ZIP of uploaded documents will be added when document upload goes live. There is no separate, owned data inventory beyond the schema and the draft policy. |
| 3.3 | Data access control lists | Implemented | Every tenant table has row-level security enabled and forced, keyed on the firm and user for each transaction. Tenant data is reached only through requireTenant().run() or withTenant(). Child rows reference parents by composite (firm_id, id) foreign keys. The application database role is never superuser or BYPASSRLS, and the app refuses to start in production if it is. Roles (admin, attorney, paralegal) restrict actions in code and, for form approval, with a database trigger. Uploaded files use per-firm key prefixes and short-lived presigned links. |
| 3.4 | Data retention | Partial | A daily job (purge_expired_data(), run by Vercel Cron) deletes unsubmitted intake sessions after 30 days, unaccepted submitted intakes after 180 days, demo leads and similar records after 24 months, expired sessions and tokens, and security events after 1 year. Gaps: the per-firm audit log is kept for the life of the firm because a closed-firm date is not recorded yet, and the schedule itself is a draft policy. |
| 3.5 | Securely dispose of data | Implemented | Closing a firm deletes its data in one transaction (close_firm_data()) and removes its files from storage afterwards; users can delete their own accounts. Generated PDFs are streamed and never stored. Deleted data stays in the database provider's restore history until the restore window passes, which the Privacy Policy states. Disposal of laptops is covered by the draft personnel policy, not by a recorded practice. |
| 3.6 | Encrypt data on end-user devices | Not implemented | Nothing records that full-disk encryption is on for the owner's laptops, so it is not claimed. The draft policy requires it, checked by the Vanta Agent. By design, no real client data is kept in the repository, tests or staging, and the policy forbids copying production data to laptops. |
Control 4: Secure Configuration of Enterprise Assets and Software
The application's configuration is code: security headers, start-up checks and database policies live in the repository and are tested. Delora operates no servers or network devices, so the firewall and network-infrastructure safeguards fall to the hosting providers. The laptop safeguards are not yet evidenced.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 4.1 | Secure configuration process | Partial | The application ships with security headers on every response (CSP, HSTS, frame denial, content-type, referrer, permissions and opener policies), checked exactly by an end-to-end test, and production start-up fails closed when required secrets or the database role are wrong. Known limits: CSP still allows 'unsafe-inline' (nonces planned), and HSTS lacks includeSubDomains and preload until subdomains are confirmed. Cloud console settings are changed by hand and there is no written baseline for them or for laptops. |
| 4.2 | Secure configuration of network infrastructure | Not applicable | Delora owns no network devices. Networking is provided by Vercel, Neon and AWS. |
| 4.3 | Automatic session locking | Not implemented | Laptop screen lock is required by the draft policy (5 minutes or less) but is not evidenced. In the application, sessions last 7 days, refreshed daily, with no idle timeout; a shorter staff idle session is listed as optional hardening. |
| 4.4 | Firewall on servers | Not applicable | Delora runs no servers. Vercel serverless functions and the managed Neon database are protected by the providers' network controls. |
| 4.5 | Firewall on end-user devices | Not implemented | The draft policy requires the built-in firewall on laptops; no record shows it is enabled. To be checked by the Vanta Agent. |
| 4.6 | Securely manage enterprise assets and software | Partial | Configuration is managed as code in version control (Next.js config, versioned database migrations, cron schedule). All access to the application and consoles is over HTTPS or TLS-protected database connections. Console settings are not under version control. |
| 4.7 | Manage default accounts | Partial | The application connects as a restricted database role that cannot bypass row-level security; the schema owner role is used only for migrations. The send-only email credentials are separate from other keys. Removing AWS root access keys and adding root MFA is an open owner step, not yet recorded as done. |
Control 5: Account Management
With one operator there are few accounts, but they are high value: email, source control, hosting, database, cloud and AI consoles. The application also has customer accounts, which are managed by the firms themselves.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 5.1 | Inventory of accounts | Partial | The systems that hold Delora accounts are listed in the access-control policy, and the list of firm members is in the database. There is no recorded inventory of every account and API key; the first access review, still to come, will produce one. |
| 5.2 | Use unique passwords | Partial | The runbooks have the owner keep secrets in a password manager, and the draft policy requires unique 16-character-plus passwords. Customer passwords must be 12 to 128 characters. Use of the password manager across every console is not independently verified. |
| 5.3 | Disable dormant accounts | Not implemented | No process finds or disables dormant company accounts; the quarterly access review would cover this once it exists. In the application, expired sessions and verification tokens are purged, but dormant customer accounts are not disabled. |
| 5.4 | Dedicated administrator accounts | Partial | Administrative database access uses a separate owner role from the application role. The plan for AWS is a read-only role for daily work and a separate admin permission set through IAM Identity Center; that is an open owner step, not yet recorded as done. Delora has one operator, so personal and administrative duties share one person. |
Control 6: Access Control Management
Access to firm data inside the product is controlled by roles and database policies. Access to Delora's own consoles is controlled by one person and, once the open owner steps are finished, by multi-factor authentication on each console.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 6.1 | Access granting process | Partial | The draft access-control policy defines how access is requested and granted. In the product, a firm creator becomes its admin, and firm admins invite attorneys, paralegals and assistants by email (single-use, expiring links; only a hash of the token is stored; an attorney is invited only while the firm's plan can cover the seat). Invitations for admins, and role changes, are not available yet. |
| 6.2 | Access revoking process | Partial | The draft policy sets removal within 1 business day of a leaver, with rotation of any secret the person could read. There are no staff to remove today. In the product, users can leave or close a firm, mobile devices can be revoked, an admin can reset a member's second factor, and firm admins can remove paralegals and assistants, which signs them out everywhere (web and mobile); removing attorneys and admins and changing roles are not available yet. |
| 6.3 | MFA for externally exposed applications | Partial | The Delora application supports authenticator-app MFA with backup codes and a per-firm policy (optional, required for admins and attorneys, or required for all). New firms start with it required for admins and attorneys; a firm admin can relax it to optional, so MFA is not enforced for every customer. MFA on Delora's own externally exposed accounts (email, hosting, source control) is an open owner step, not yet recorded as done. |
| 6.4 | MFA for remote network access | Not applicable | Delora has no enterprise network or VPN to protect. Remote access to cloud consoles is covered under 6.5. |
| 6.5 | MFA for administrative access | Partial | MFA on GitHub, AWS, Vercel, Neon, Anthropic, Resend, the domain registrar and the email provider is an open owner step. It is treated as unfinished until it is recorded. No hardware-key or SSO requirement exists. |
Control 7: Continuous Vulnerability Management
Dependency and secret scanning run automatically on every change, which covers most of what a cloud-only company controls. Scanning of the running application, an external penetration test and written fix deadlines are still to come.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 7.1 | Vulnerability management process | Partial | Trivy (dependencies and secrets), pnpm security:deps, gitleaks (pnpm security:secrets) and an OWASP ZAP baseline scan against staging (never production) are in place. The written process is a draft policy, and no external penetration test has been done yet. |
| 7.2 | Remediation process | Partial | Findings are tracked as GitHub issues or Vanta tasks under the draft policy. Proposed fix deadlines are 7 days for critical, 30 for high and 90 for medium; they are proposals until the owner approves them. Allowlisted advisories need a reason and a review date. |
| 7.3 | Automated operating system patching | Partial | The hosting and database providers patch the systems underneath Delora's code. Automatic OS updates on the owner's laptops are required by the draft policy but are not evidenced. |
| 7.4 | Automated application patching | Implemented | Dependabot raises pull requests weekly for npm and GitHub Actions, and every one runs the full CI suite before the owner merges it. The owner merges the pull requests; they are not merged automatically. |
Control 8: Audit Log Management
Delora keeps two append-only logs inside the product and relies on each provider for logs of its own console. The application logs are in place. Centralized, long-retention runtime logs and alerts are not.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 8.1 | Audit log management process | Partial | A logging and monitoring policy defines what is logged, retention (1 year) and review (weekly, 10 minutes), but it is a draft and the weekly review is not yet a recorded practice. |
| 8.2 | Collect audit logs | Partial | Implemented in the application: a per-firm audit_log records business actions (ids only, never names or chat text), and security_events records sign-ins, failures, lockouts, two-factor events, password resets and policy changes, without email addresses, passwords or codes. Not in place: a log drain for runtime logs, and CloudTrail for AWS activity. |
| 8.3 | Adequate audit log storage | Partial | security_events and audit_log live in the main database; security events are kept for 1 year and purged daily, and the audit log is kept for the life of the firm. Not implemented: one-year retention of application runtime logs (Vercel keeps them only briefly). The log drain to storage Delora controls is planned. |
Control 9: Email and Web Browser Protections
These safeguards are about the browsers and email clients the owner uses and about filtering what they can reach. Nothing is configured or recorded for them today.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 9.1 | Supported browsers and email clients only | Not implemented | There is no written standard for browsers or email clients on the owner's laptops, and the Vanta Agent has not been installed to report on them. Company email is hosted by the email provider's web service. |
| 9.2 | DNS filtering services | Not implemented | No DNS filtering service is configured on the owner's devices. Delora's own outbound email uses SPF, DKIM and DMARC records, but that authenticates mail Delora sends and is not DNS filtering. |
Control 10: Malware Defenses
Document upload is not live in the Delora product, so the product holds no uploaded files today (see "When document upload goes live" below). Malware risk is mostly on the owner's laptops. The draft policy accepts the operating system's built-in protection, but nothing records that it is on and current.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 10.1 | Anti-malware software | Not implemented | The draft policy requires malware protection on laptops and says built-in protection is acceptable. It is not evidenced yet; the Vanta Agent will check it. |
| 10.2 | Automatic anti-malware updates | Not implemented | Not evidenced for the laptops, for the same reason as 10.1. |
| 10.3 | Disable autorun for removable media | Not implemented | No setting or policy addresses removable media. The risk is low because Delora does not use removable media for business data, but nothing records that. |
When document upload goes live
Document upload is not live and no production file bucket exists, so none of this applies today. The design for when it opens: staff on a matter, prospects during intake and clients from the web portal can add files. Each file must be a PDF, JPEG, PNG or HEIC of at most 25 MB, checked by its first bytes, and is always downloaded as an attachment under a name Delora makes, never opened in the browser. Files are not scanned for malware at launch: GuardDuty Malware Protection for S3 is the planned control (an owner decision).
Control 11: Data Recovery
The database is Delora's only store of firm data. Its provider keeps a continuous history that can be restored to any moment in a window set by the plan. Delora does not make nightly dump files. The recovery runbook and a scripted drill exist, but no drill has been recorded yet.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 11.1 | Data recovery process | Partial | A step-by-step production restore runbook exists (stop writes, restore into a new branch, check, switch over) and a scripted drill (pnpm restore:drill) that restores staging and verifies row counts, forced RLS, decryption of sealed identifiers and migration state. The drill runs quarterly; the first run, on 2026-10-27, passed every check in 12 seconds and is recorded in the runbook. The continuity policy with recovery targets is a draft. |
| 11.2 | Automated backups | Partial | Neon keeps continuous point-in-time history automatically. The restore window is up to one day today (7 days on Neon's Launch plan); moving to at least 7 days is an open owner step. Document upload is not live and no production file bucket exists yet; when it goes live, bucket versioning is an open owner check. |
| 11.3 | Protect recovery data | Partial | Restore history is encrypted at rest by the database provider and is tenant-isolated like live data. Sealed identifiers in a restored database remain readable only with the encryption key, which is kept in the password manager (and, per the draft continuity policy, a sealed offline copy). Console MFA is pending (see 6.5). |
| 11.4 | Isolated instance of recovery data | Not implemented | Recovery history lives with the same provider and account as the live database. There is no copy of firm data held in a separate account or provider. Source code and migrations are separately held in GitHub. |
Control 12: Network Infrastructure Management
Delora has no network infrastructure of its own to keep up to date.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 12.1 | Network infrastructure is up to date | Not applicable | All network infrastructure belongs to Vercel, Neon and AWS. Their keeping it current is covered by the provider reports Delora is collecting as a vendor step. |
Control 13: Network Monitoring and Defense
Control 13 has no safeguards in Implementation Group 1, so nothing here is scored. For context, Delora runs three uptime monitors every 3 minutes from several regions (Better Stack, in use since 2026-10-26) and relies on its hosting provider's platform-level DDoS mitigation. It has no intrusion detection or network alerting of its own.
Control 14: Security Awareness and Skills Training
Training is a gap for a one-person company that has not yet taken a formal course. The owner wrote the rules the product follows, but a recorded awareness program does not exist. Vanta's built-in course and background checks are planned.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 14.1 | Security awareness program | Not implemented | No program is in operation. The draft personnel policy requires training at hire and yearly, tracked in Vanta; the course is planned. |
| 14.2 | Recognize social engineering | Not implemented | Not covered by any recorded training yet. |
| 14.3 | Authentication best practices | Not implemented | Not covered by any recorded training. The password-manager and MFA practices are in the draft access-control policy. |
| 14.4 | Data handling best practices | Partial | Data-handling rules are written and enforced in code and tests: synthetic data only outside production, no PII in logs, identifiers never sent to an AI. The draft acceptable-use policy repeats them. These are rules and technical controls rather than delivered training. |
| 14.5 | Causes of unintentional data exposure | Not implemented | Not covered by any recorded training. |
| 14.6 | Recognize and report incidents | Partial | The draft incident-response policy tells anyone who suspects an incident to email security@deloralegal.com at once. No training or tabletop exercise has been delivered; the tabletop is planned. |
| 14.7 | Identify missing security updates | Not implemented | Not covered by any recorded training. |
| 14.8 | Dangers of insecure networks | Not implemented | Not covered by any recorded training. |
Control 15: Service Provider Management
Delora depends on a small number of vendors that host or process customer data, so this control matters most to customers.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 15.1 | Inventory of service providers | Implemented | The vendor policy keeps an inventory with each vendor's use, whether it touches customer data and a risk rating, and the public subprocessors page lists those that process firm content; a repository test fails if the two lists disagree. Open items: collecting each vendor's DPA and SOC 2 report into Vanta, the yearly vendor review, and Anthropic zero-data-retention approval, none of which is claimed here. |
Control 16: Application Software Security
Control 16 has no safeguards in Implementation Group 1, so nothing here is scored. Because Delora is itself application software, it is worth saying what exists beyond IG1: every change is built and tested in CI (type checking, lint, unit tests against a real-migration database, end-to-end tests including exact security headers), the route inventory test fails if a page, route or action is added without a stated access rule, and the project's written hard rules are checked by a repository test. Branch protection on main requires the lint-and-unit, e2e-playwright and unit-forms checks (checked 2026-10-27); required reviews are not in place.
Control 17: Incident Response Management
An incident response policy is drafted. It has not been exercised, and a second person who could act if the owner is unavailable has not been named.
| Safeguard | Title | Status | How Delora implements it |
|---|---|---|---|
| 17.1 | Designate incident handling personnel | Partial | The draft policies name the owner as security officer and incident lead. There is no backup person; the continuity policy lists naming one as an open item. |
| 17.2 | Contact information for reporting incidents | Partial | The Security page publishes security@deloralegal.com for reports and promises acknowledgement within 2 business days. Delora's records are inconsistent on whether the mailbox is confirmed to receive mail, so the owner must test it before it is relied on. Counsel's contact is meant to be kept in the password manager. |
| 17.3 | Process for reporting incidents | Partial | The draft policy defines severity levels, triage, containment, investigation, recovery and notification steps, and a review within 5 business days for severe incidents. The 72-hour customer notification is contractual for customers who sign the counsel-reviewed customer DPA (version 1.1, signed on request) and a policy commitment for the others. A tabletop exercise is planned. |
Control 18: Penetration Testing
Control 18 has no safeguards in Implementation Group 1, so nothing here is scored. Delora has not had a penetration test. The scope for an external tester is written (staging only, synthetic data), and the test is planned, with critical and high findings to be fixed before the SOC 2 audit.
Prioritized remediation plan
Ordered by risk reduced per hour of owner effort. These are plans only.
- Multi-factor authentication on every console and account (safeguards 6.3, 6.5). Enable it on email, GitHub, AWS (including the root user), Vercel, Neon, Anthropic, Resend, the domain registrar and the password manager, then record it in Vanta. This is the largest single risk reduction.
- GitHub organization settings (supports 2.2, 7.4 and Control 16 practices). Require two-factor for members, protect
mainwith a ruleset requiring a pull request and passing checks, and turn on Dependabot security updates, secret scanning and push protection. - AWS account hardening (4.7, 5.4, 8.2). Remove root access keys, create IAM Identity Center users with a read-only role for daily work, and turn on CloudTrail with one-year retention.
- Install the Vanta Agent on every laptop and verify device settings (1.1, 2.1, 3.6, 4.3, 4.5, 7.3, 10.1, 10.2). Confirm disk encryption, screen lock, firewall, automatic OS updates and built-in malware protection are on. This one step is the main way to evidence all of these safeguards.
- Neon plan with at least 7 days of restore history (11.2). The first
pnpm restore:drillpassed on 2026-10-27; adopt the continuity policy to close 11.1. - Approve the draft policies in Vanta (3.1, 3.4, 5.1, 6.1, 6.2, 8.1, 17.1 to 17.3). Several Partial items become Implemented once the policy is approved and the practice it describes is recorded.
- Security awareness training and background check (14.1 to 14.8). Complete Vanta's course and record it.
- Log drain with one-year retention and alerts (8.2, 8.3).
- Incident response tabletop (14.6, 17.3). Name a backup person with sealed access to the password manager emergency kit (17.1), and confirm security@deloralegal.com receives mail (17.2).
- First quarterly access review (1.2, 5.1, 5.3). List every person, account and key with production access and remove what is not needed.
- External penetration test on staging (Control 18, supports 7.1), with critical and high findings fixed before the SOC 2 audit.
- Remaining items. Create a second, isolated copy of recovery data if customers require it (11.4); record the first production key rotation; decide on DNS filtering and browser or email client standards for the owner's devices (9.1, 9.2); record a closed-firm date so the audit-log retention rule can be enforced (3.4); restrict removable-media use or document why it is not needed (10.3).
Contact: security@deloralegal.com.