Works with · Augment Code · Augment

Does an Augment Code review count for SOC 2?

No. Augment Code posts review comments from a bot account. It is not an approval by a qualified person other than the author. PSCO reads its comments and adds the named Officer.

How Augment Code reviews

Augment reviews pull requests with its codebase context engine and posts review comments and suggested changes.

What it cannot do

Augment Code cannot be the independent human approver an auditor is looking for. SOC 2 CC8.1, ISO 27001 A.5.3, PCI DSS 6.2.3.1 and SOX program-change controls all assume a qualified person other than the author approved the change and understood it. A bot account posting "Approve" is a review record, not an accountable person, and as of mid-2026 no auditor reports accepting it as standard practice.

How PSCO reads its output

Augment comments become findings on the Officer’s packet.

Recognized asbot logins
augment-code[bot]Review comments
augmentcode[bot]

Two-step setup

Keep Augment Code.

Keep Augment enabled.

Add PSCO.

Install the PSCO GitHub App, select the repos in scope, and require psco/approved and one approval from @psco-officers.

The shared-model tip

Point it at the same model the Officer uses.

Point Augment at the same rulebook the Officer uses. Add the model’s rules to .augment/rules or reference psco.model.yaml from them. Keep the sensitive paths, required checks and forbidden patterns identical in both places so the robot and the human check the same rules, and so the Officer's packet shows the AI's findings next to the clause they map to.

psco.model.yamlv1 · customer-owned
frameworks: [soc2, iso27001]
sensitive_paths:
  auth/**: deep
  infra/**: deep
required_checks: [ci, tests, sast, secrets]
forbidden: [hardcoded_secret, tls_verify_off]

Keep Augment Code. Add the human who signs.

Connect GitHub and PSCO detects the reviewers already on your repos. Your price comes from your real PR history.