Home / Solutions

Pass SOC 2 audits while using Cursor

Cursor has SOC 2 Type II attestation and provides reports on request through its trust portal.

Updated November 16, 2026

Cursor's audit report covers only Cursor's own service

Cursor edits workspace files and runs terminal commands. Its SOC 2 report examines Cursor's service. ZeroTB's software and team keep post-audit controls working for US software, AI, fintech and healthtech companies.

  • Assess the service. Cursor's report supports vendor review. Your repositories and releases need their own evidence

  • Scope the approval. Name the repositories, information and access Cursor may use for the approved work

  • Review later requests. Check new tools and repositories against that scope before work proceeds

Cursor SOC 2 reports cover a past period

Cursor SOC 2 Type II evidence covers a period, usually 3 to 12 months. Its security page links to the trust portal for reports.

Check report dates. Customers usually treat a SOC 2 report as current for about 12 months.

Read the scope. The report identifies which parts of Cursor's service the examination covers.

Read beyond attestation. The public attestation statement explains neither the report's scope nor its observation period.

Privacy Mode keeps customer code out of training

With Privacy Mode enabled, Cursor excludes customer data from training under its data-use policy. Requests still pass through Cursor's backend.

Account for processing. Requests pass through Cursor's backend even when you use a personal API key.

Check retention exceptions. The policy describes temporary caching, abuse investigations and models without zero-retention arrangements.

Decide before sharing. Resolve requirements to keep project data in one environment before supplying it to Cursor.

Cursor's agent saves edits before anyone reviews them

Cursor saves workspace edits immediately but treats configuration files separately. Its agent security documentation says terminal commands require approval by default.

Check run modes. Selected run modes can allow commands without a prompt for each action.

Account for limits. Cursor describes run modes as best-effort safeguards when explaining command approval.

Inspect automatic reload. Automatic reload can execute saved edits before a developer reviews them.

MCP connections hand Cursor's agent outside credentials

Model Context Protocol (MCP) gives Cursor access to external tools. A connection needs approval separately from the calls made through it.

Review tool approvals. Specific tools can be pre-approved for the agent to use.

Inspect credential permissions. The connected service determines which records and actions its credential can reach.

Assign access owners. A tool that changes records needs someone to decide whether later access remains appropriate.

Missing branch rules let Cursor changes merge unreviewed

A Cursor change may receive review even when the branch rule is missing. That leaves the next merge outside your required SOC 2 review.

Check beyond scans. A passing code scan leaves open whether the change can merge unreviewed.

Inspect new repositories. Agent pull requests can reach new repositories before their protections are set.

Review bypass rights. Revised branch rules and bypass rights can change which merges require review.

Deployment records match tested code to shipped code

A deployment record connects reviewed code to the system it reached. Test results and release permissions explain how that change passed through.

Match tested changes. The test result must identify the examined change and match the deployed one.

Check release stops. The agreed process determines whether a failed required check stops release.

Own each exception. Record the bypass owner, affected systems, permitted use and review date.

ZeroTB rechecks repository and release rules every day

ZeroTB checks SOC 2 commitments in GitHub daily and carries gaps through verified restoration. It examines systems Cursor changes without a coding-agent connection.

Approve scoped repairs. ZeroTB drafts pull requests after read-only checks. Scoped, approved write access remains revocable.

Keep uncertainty visible. Stale or disconnected observations leave the present condition unknown and require investigation.

Keep failures open. A failed verification leaves the gap open until a check confirms the control works.

Change and development controls

Cursor's safeguards and ZeroTB answer different audit questions

Cursor's SOC 2 report answers a vendor-review question. The other safeguards govern development, with ZeroTB investigating and repairing failures in your controls.

TaskCursor's SOC 2 reportCursor's agent settingsBranch rulesZeroTB
What it coversSOC 2 Type II evidence for Cursor's serviceCommand approval under selected run modesWhich merges need a reviewerSOC 2 commitments checked daily
What it leaves openYour repositories, reviews and releasesEdits saved before reviewBypass rights and new repositoriesCursor's service remains covered by its report
Who acts on gapsCursor under its own auditThe developer choosing run modesThe repository ownerZeroTB prepares repairs, your team approves
What auditors seeCursor's report on requestYour record of approved useThe current branch ruleA signed Verified Control Record

Example of restoring a missing merge review rule

Here, a repository requires review again after repair. The Verified Control Record connects the requirement, original condition, approved change and verification result.

Require review before merging
A review rule correction: merges allowed without approval, the owner's approved restoration of required review, and verification that a merge now needs the specified approval.
  1. Missing review rule. Policy requires another reviewer, but the repository permits merging without one.

  2. Approved rule change. The owner approves restoring the required review rule on the repository.

  3. Verified merge restriction. A later check confirms that another change needs the specified approval before merging.

Five checks keep a Cursor approval current

Define approved use

Identify the repositories, information and workflow within Cursor's approved scope.

Inspect agent access

Check available files, commands and connected services under the chosen permissions.

Check release paths

Follow one change through review, tests and deployment.

Review retained exceptions

Check who approved each bypass, why it remains and when approval needs review.

Examine closure evidence

Compare the verification result with the approved correction and the requirement it restores.

Sources

  1. Cursor, Security, updated August 25, 2026.
  2. Cursor, Data Use & Privacy Overview, updated September 3, 2026.
  3. Cursor, Agent Security, accessed November 4, 2026.
  4. Cursor, Model Context Protocol, accessed November 4, 2026.

Start with the Pilot

Discuss Cursor controls. Over eight weeks, the Pilot maps up to 25 commitments and takes two real gaps through verified restoration.