SOC 2 production access: who may reach the database, and what to show

Updated

SOC 2 does not prescribe how engineers reach production; Bytebase says so directly (Bytebase). What the auditor tests is your own written control: who may reach production, who approved it, and a record of what they did. Give each engineer a named account, limit standing access to the few who need it daily, put the rest behind a ticketed request that expires, and keep the logs that show who ran what. These two sources are vendors, not the AICPA, so confirm with your CPA firm.

Which criteria land on production access

Bytebase maps database access to CC6.1, CC6.2 and CC6.3 (logical access, authorization and least privilege), CC6.6 and CC6.7 (boundaries and moving data out), CC7.2 and CC7.3 (monitoring), and CC8.1 (changes), plus C1.1 when the Confidentiality category is in scope (Bytebase). Creately names CC6.1 and CC6.3 (Creately). The read path counts: who can run a query on customer data is access control, not only change management. For changes, see the change management page.

What the auditor asks for

For a sampled control the auditor needs a complete population of relevant events, Bytebase says, and its own audit note asked for evidence that administrator activity is actually logged, not only that logging is enabled. A log sample should show the privileged user, the action, the timestamp and the affected resource; Bytebase's line is that configuration alone does not prove the control operated (Bytebase). Creately lists four artifacts: a dated export of the privileged account inventory, approval records with approver and date, privileged activity logs with timestamps, and a signed, dated review report (Creately).

Where sources differ

TopicBytebaseCreately
Review intervalGives noneMonthly privileged access review
Shared accountsWeaken attribution and monitoringNot addressed
ApprovalRequested with a reason, approved, expiresApproval records with approver and date
Break-glassNot mentionedListed in the inventory; no procedure
SellsDatabase access softwareDiagramming software and a paid template library

Neither page shows a publication date for the claims beyond Bytebase's 17 September 2026 post; Creately's page is undated. Treat both as one vendor's view.

A setup a small team can run

  1. Named accounts through SSO. One identity per engineer, so the log names a person.
  2. A short list of standing production roles for the people who need it daily; everyone else asks. Keep read-only roles wherever write is not needed.
  3. A ticketed, expiring request for the rest: reason, approver, end date. Each ticket is an authorization record and a population the auditor can sample (Bytebase's point about just-in-time requests).
  4. A break-glass credential in a vault, in the account inventory, with its own use log.
  5. One rehearsal: pick an engineer and a date and reconstruct what they touched from the logs. If you cannot, the auditor cannot either.

What the generated policy says

Policyseed sells a kit, so read these as one example, not a requirement. The generated Access Control Policy covers each step; the Logging and Monitoring Policy covers the logs.

Every person has a unique, individually attributable account. Shared accounts are prohibited except for documented break-glass credentials, which are stored in 1Password, restricted to the Security Owner and named Engineering leads, used only when normal access paths are unavailable during an incident, and rotated after every use.

Access Control Policy, item 4.2

Production access to AWS and Vercel is granted only to engineers whose role requires it, through federated identity and short-lived credentials rather than long-lived access keys. Administrators use a separate privileged role that is assumed for a bounded session and logged to Datadog; read-only roles are used wherever write access is not needed.

Access Control Policy, item 4.6

Direct access to customer data in production databases and storage is limited to named engineers with a documented need, performed through audited tooling wherever possible, and logged. Because Northwind Cloud Inc processes PII data, every direct query against customer data is tied to a ticket or incident reference.

Access Control Policy, item 4.7

Production access grants. An engineer requesting a production role in AWS and Vercel states the reason and expected duration. The Engineering lead approves, the Security Owner is notified, and the role is assigned through identity federation with a session limit of no more than twelve hours. Temporary grants carry an expiry and are removed on that date.

Access Control Policy, item 5.2

Break-glass use. Use is announced in the incident channel, the reason is recorded in the incident ticket, the credential is rotated within one business day, and the Security Owner reviews every use.

Access Control Policy, item 5.6

Run the review with the access review sheet and the access review tool, record departures per the offboarding evidence guide, and log any grant outside the policy in the exception register. Where the credentials live is covered in secrets and key management. Whether customer data may be copied out of production into staging is covered in production data in staging. Cadence is covered in the access review frequency guide.

Frequently asked questions

Is a shared read-only database login allowed for SOC 2?
Bytebase, which sells database access software, says shared logins without individual attribution weaken access control and monitoring, because the database's own logs cannot name a person when several engineers use one login. It does not say a shared login is automatically a finding; that depends on how your control is written and what the auditor tests. If you keep one, write the control to match and record who used it. The simpler fix is a named account per engineer.
Do reads of production data need approval?
Bytebase treats read access as part of access control, not only writes, and recommends read access that is requested with a reason, approved and expires on its own, so each request is an authorization record. Creately's privileged access page asks for approval records showing approver and date. Neither source states an AICPA rule; the approval step you write is the one tested.
What does an auditor want to see for production access logs?
Bytebase describes an auditor note asking for evidence that administrator activity is actually logged, not just that logging is enabled, and says a log sample should show the user, action, timestamp and affected resource. Creately lists privileged activity logs with timestamps for the review period. A screenshot of a settings page does not show the control ran.
Do we need a break-glass account?
Neither source gives a procedure. Creately says the privileged account inventory includes admin, root and break-glass accounts, and Bytebase does not use the term. If you keep one, list it in the inventory, store its credential in a vault, record each use with a reason, and rotate it afterward, as the example policy text below does.
How often should production access be reviewed?
The sources differ. Creately's process page lists a monthly review of privileged access. The example policy text below says quarterly for production. Neither is an AICPA number, so choose an interval you will meet and keep the dated review each time. See the access review frequency guide.
Which criteria cover production access?
Bytebase maps database access to CC6.1, CC6.2 and CC6.3 (access, authorization and least privilege), CC6.6 and CC6.7 (boundaries and data movement), CC7.2 and CC7.3 (monitoring), and CC8.1 (changes), plus C1.1 if Confidentiality is in scope. Creately names CC6.1 and CC6.3. Your CPA firm maps your own controls to criteria in the system description.

Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.