US Sarbanes-Oxley Act of 2002 (SOX) — Reference-depth plugin for ICFR scoping, IT General Control (ITGC) testing, and §302/§404/§906 evidence preparation. Backed by the SCF crosswalk (4 SCF → 17 framework controls).

version
0.1.0
GitHub stars
436

Install

/plugin install us-sox@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

Sarbanes-Oxley Act of 2002 (SOX) Expert

Deep, practitioner-level expertise in the Sarbanes-Oxley Act of 2002 — the U.S. federal statute that governs financial reporting controls for SEC-registrant public companies. This skill is written for the security and IT engineer who has been told they "own SOX" or "support SOX" and needs to understand what the audit machine around them actually does.

Framework identity

  • SCF framework ID: usa-federal-law-sox-2002
  • Statute: Sarbanes-Oxley Act of 2002, Public Law 107-204, codified at 15 U.S.C. §§ 7201 et seq. (criminal provisions in 18 U.S.C. §§ 1350, 1519)
  • Region: Americas
  • Country: US
  • Regulators:
    • SEC (Securities and Exchange Commission) — disclosure-rule enforcement, civil actions, criminal referrals
    • PCAOB (Public Company Accounting Oversight Board) — created by SOX §101; oversees auditors of public companies; sets the auditing standards (notably AS 2201 — An Audit of Internal Control over Financial Reporting that is Integrated with an Audit of Financial Statements) that drive the way external auditors test ICFR
    • DOJ (Department of Justice) — criminal enforcement of §802 (document destruction) and §906 (knowing false certification)
  • SCF crosswalk coverage: only 4 SCF controls → 17 SOX-relevant controls. That number is small for a reason — see "Why the SCF mapping is thin" below.

Framework in plain language

SOX is the U.S. response to the Enron and WorldCom accounting frauds of 2001–2002. It does not prescribe specific cybersecurity controls. What it does is impose three things on SEC-registrant public companies and their auditors:

  1. Personal accountability for financial disclosures by the CEO and CFO (§302 and §906 certifications, with criminal exposure under §906).
  2. An annual management assessment of the design and operating effectiveness of Internal Controls over Financial Reporting (ICFR) filed in the 10-K (§404(a)).
  3. An external auditor attestation on management's ICFR assessment for accelerated filers (§404(b), required by 15 U.S.C. § 7262(b)).

The security/IT relevance is indirect but unavoidable: virtually every modern in-scope financial process depends on IT systems, so management's §404(a) assessment must cover the IT General Controls (ITGCs) protecting those systems, and the external auditor will test those ITGCs under AS 2201 as part of the §404(b) attestation. That ITGC testing is where a security or platform engineer's day-to-day SOX work happens.

Why this plugin frames SOX as a governance-over-ICFR layer

The SCF crosswalk maps only 4 SCF controls to SOX. That is correct, not a gap — SOX's statutory text is structured around officer certifications, auditor independence, audit committee composition, document retention, and disclosure rules, not technical control objectives. The control catalog that practitioners actually test against is COSO 2013 Internal Control — Integrated Framework at the entity-level layer, COBIT 5 / 2019 for IT-process controls, and the AICPA Trust Services Criteria where ITGC overlap exists (e.g., a SOC 1 Type II from a service organization is the typical vendor-reliance evidence).

So SOX's role in this plugin is the governance and accountability frame:

  • §302 + §906 = personal certification (the "tone at the top" forcing function)
  • §404(a) = management assessment of ICFR (forces a control inventory, scope, walkthrough, and test program)
  • §404(b) = external auditor attestation (forces independent reperformance of that test program for accelerated filers)
  • §802 = document retention with criminal teeth
  • §409 = real-time material-event disclosure (8-K within 4 business days)

The actual control objectives flow from COSO + COBIT + the auditor's own internal control workpaper templates. This plugin helps you scope SOX correctly, run an honest ICFR-style gap assessment via the SCF crosswalk, and assemble the ITGC evidence package an external auditor will recognize — without pretending SOX is a security framework.

Territorial scope and applicability

Who must comply

Any company whose securities are registered under §12 of the Securities Exchange Act of 1934 (listed on a U.S. national securities exchange like NYSE or Nasdaq) or required to file periodic reports under §15(d) of the 1934 Act (e.g., issuers with publicly registered debt). In short: U.S.-listed public companies, plus a number of issuers required to file 10-K / 10-Q / 8-K reports with the SEC even if not exchange-listed.

Foreign private issuers

A non-U.S. company with securities listed on a U.S. exchange is generally subject to SOX, with limited carve-outs and accommodation for home-country governance practices (e.g., 20-F annual filings instead of 10-K, but the §302 and §404 substance still applies). Don't assume "we're headquartered abroad" gets you out of SOX scope.

Private companies in the SOX runway

Two common cases where a private company should be running SOX-grade ICFR even though it is not yet a §12 registrant:

  • Pre-IPO (S-1 readiness) — once the S-1 lands, the company effectively needs §404(a)-quality ICFR documentation in place; underwriters, auditors, and the SEC review team will probe it. Most pre-IPO companies start the ICFR build 12–24 months before the planned listing.
  • Acquisition by a public company — once acquired, the target's financially significant systems become in-scope for the parent's §404(a) assessment, typically with a one-year integration window.

Filer-status determinations (this drives §404(b) exposure)

The §404(b) external-auditor attestation requirement does not apply to all SOX filers. The applicable categories under SEC rules:

  • Large accelerated filer: public float ≥ $700M. §404(b) required.
  • Accelerated filer: public float ≥ $75M and < $700M. §404(b) required, except where the SEC's 2020 amendments exclude qualifying low-revenue issuers — for example, an issuer with $75M–$700M public float, annual revenues below $100M, and no prior accelerated or large-accelerated-filer status.
  • Non-accelerated filer: public float < $75M. §404(b) not required (per amendments stemming from the Dodd-Frank Act). §404(a) management assessment is still required.
  • Emerging Growth Company (EGC) — under the JOBS Act, an EGC is exempt from §404(b) for up to 5 years from its IPO (or until it loses EGC status by exceeding revenue, debt issuance, or large-accelerated-filer thresholds). §404(a) still applies.
  • Smaller Reporting Company (SRC) — the SRC vs. non-SRC determination affects scaled disclosure rules but is partly orthogonal to §404(b); confirm by walking the current SEC filer-status definitions.

Practitioner tip: Year-1 SOX scope and effort are dominated by whether the company is required to engage an external auditor for §404(b). Confirm filer status with the controller and the external auditor before sizing the SOX program — the difference is the difference between a management self-assessment and a full integrated audit.

Mandatory artifacts (the "named documents" SOX practitioners produce)

SOX has fewer named regulatory artifacts than GDPR or PCI DSS, but practitioners build a recurring set of documents around the ICFR cycle. The ones an auditor will ask for first:

  • Management's §404(a) assessment — included in the 10-K Management's Report on Internal Control over Financial Reporting. Asserts whether ICFR is effective as of the fiscal year-end. Required.
  • §302 quarterly disclosure-controls certification — signed by CEO and CFO; included in each 10-K and 10-Q. Asserts personal review of the report and effectiveness of disclosure controls and procedures.
  • §906 certification — separate criminal certification by CEO and CFO under 18 U.S.C. § 1350 that the periodic report fully complies with the Exchange Act and fairly presents financial condition.
  • External auditor's §404(b) attestation report — for accelerated filers; included in the 10-K alongside the financial-statement audit opinion.
  • ICFR scoping memo — internal document linking material accounts to in-scope processes and in-scope IT systems (often produced by internal audit or the SOX PMO; reviewed by external auditor).
  • Risk and control matrix (RCM) / RACM — the operational artifact that lists each in-scope control, its owner, frequency, evidence type, and links to the financial-statement assertion(s) it supports.
  • Walkthrough documentation — narratives and flowcharts demonstrating that the documented design of each in-scope control matches reality.
  • Test-of-design and test-of-operating-effectiveness workpapers — sample-based testing results, supporting management's §404(a) assertion and feeding the external auditor's §404(b) reperformance.
  • Deficiency log — running list of identified control deficiencies with severity classification (deficiency, significant deficiency, material weakness) and remediation plans.
  • SOC 1 Type II reports for in-scope vendors, plus complementary user entity controls (CUECs) — see "SOC 1 vs. SOC 2" below.

Cadence and timelines

  • 10-K — annual report; includes the §404(a) assessment and (if accelerated filer) the §404(b) attestation. Filing deadlines vary by filer status: 60 days after fiscal year-end for large accelerated, 75 days for accelerated, 90 days for non-accelerated.
  • 10-Q — quarterly report; includes the §302 certification and updates on any material changes to ICFR. Filing deadlines: 40 days after quarter-end for large accelerated and accelerated filers, 45 days for non-accelerated.
  • 8-K — current report for material events. SOX §409 codifies "real-time" disclosure; the SEC's implementing rules require an 8-K filing within 4 business days of a triggering event.
  • ICFR cycle — typical large public-company cadence: scoping refresh in Q1, walkthroughs in Q2, interim operating-effectiveness testing in Q2/Q3, year-end (rollforward) testing in Q4 and into Q1 of the next fiscal year, deficiency aggregation and remediation tracking continuous.
  • Document retention — §802 (codified at 18 U.S.C. § 1519) carries up to 20 years imprisonment for knowing destruction of documents with intent to obstruct a federal investigation. Auditor work papers must be retained for 7 years under PCAOB rules. Practical guidance: retain SOX evidence (testing workpapers, screenshots, walkthroughs, deficiency logs) for at least 7 years.

Regulator and enforcement

SOX enforcement is shared across three institutions — understanding which one is on the line for which provision matters:

SEC (civil disclosure enforcement)

The SEC enforces the disclosure provisions and can bring civil actions against issuers, officers, directors, and gatekeepers (auditors, lawyers) for violations of the Exchange Act, Rules 13a-14 / 13a-15, and the §404 requirements. Sanctions include monetary penalties, officer-and-director bars, disgorgement, and cease-and-desist orders. Common SEC enforcement themes around SOX:

  • Restatements traceable to material weaknesses in ICFR that management failed to disclose
  • §302 certifications signed despite known material control gaps
  • Failure of the audit committee or disclosure committee to perform an effective review

PCAOB (auditor oversight)

The PCAOB does not directly enforce SOX against issuers — it enforces against the audit firms that audit them. PCAOB inspections produce findings on the audit firm's work, including ICFR audit deficiencies under AS 2201. When the PCAOB inspects an audit firm and finds the firm's ICFR audit work insufficient at a particular issuer, the issuer often becomes the subject of additional auditor scrutiny in the next cycle. Practitioner consequence: if your external auditor is in an active PCAOB inspection, your ITGC and process-control evidence requests will be more rigorous than usual.

DOJ (criminal enforcement)

Criminal exposure under SOX runs through two main channels:

  • §906 (codified at 18 U.S.C. § 1350) — knowingly false CEO/CFO certifications. Statutory maximum is 10 years for "knowing" violations and 20 years for "willful" violations, plus fines.
  • §802 (codified at 18 U.S.C. § 1519) — destroying, altering, or falsifying records with intent to obstruct a federal investigation. Statutory maximum 20 years.

These criminal provisions are why §302 and §906 sign-off processes inside public companies are taken with extreme seriousness — the personal exposure is real, and disclosure committees exist specifically to give CEOs and CFOs a documented basis for their certifications.

Penalty calculation

Unlike GDPR's percentage-of-revenue model, SOX civil penalties are statutory and per-violation, with the SEC empowered to bring enforcement actions seeking disgorgement and officer/director bars in addition to fines. There is no published SOX-specific tier table; penalty exposure is driven by the underlying disclosure or accounting violation, not by SOX itself. The criminal exposure under §906 and §802 is the more significant practical deterrent for officers.

Internal Controls over Financial Reporting (ICFR) — where IT and security plug in

SOX itself does not define a control framework. Almost every U.S. public company uses COSO 2013 Internal Control — Integrated Framework as its ICFR framework, because the SEC's §404 implementing rules permit management to use any "suitable" recognized framework and COSO 2013 is the de facto standard. (The PCAOB's AS 2201 is the auditor's standard for testing ICFR; COSO is management's control framework.) This plugin paraphrases COSO concepts but does not reproduce COSO IC-IF text — that text is copyrighted by the Committee of Sponsoring Organizations.

COSO's five components (paraphrased)

  1. Control Environment — the governance "tone at the top": board oversight, ethical values, organizational structure, accountability, HR policies.
  2. Risk Assessment — identifying and analyzing risks to financial-reporting objectives; includes fraud risk assessment.
  3. Control Activities — the policies and procedures that mitigate identified risks, executed at entity, process, and IT levels.
  4. Information and Communication — the systems that produce, capture, and communicate financial information.
  5. Monitoring Activities — ongoing and separate evaluations of whether the other four components are functioning.

Three categories of controls in a SOX program

  • Entity-Level Controls (ELCs) — operate at the company level. Tone-at-the-top, code of conduct, fraud risk assessment, audit-committee composition, whistleblower hotline, period-end financial-reporting controls. Often tested first because effective ELCs let the auditor place reliance on a smaller sample of process-level controls.

  • Process-Level Controls — operate inside a business process. Order-to-cash (revenue recognition), procure-to-pay (expense recognition), payroll, inventory, fixed assets, treasury, financial close and reporting, tax. These are the "business cycle" controls.

  • IT General Controls (ITGCs) — controls over the IT environment that enable reliance on automated process controls and IT-dependent manual controls. This is where security and platform engineers spend almost all of their SOX time. The four classic ITGC domains:

    1. Access to Programs and Data — logical access provisioning / deprovisioning, periodic user access reviews (UARs), privileged access management, segregation of duties (SoD) in IAM, authentication and password controls.
    2. Program Changes — change management for application and infrastructure changes: ticketed change requests, peer code review, segregation between developer and production-deployer, emergency change procedures, change population completeness.
    3. Computer Operations — job scheduling, batch processing monitoring, backup and recovery, incident management, environmental controls in data centers (or attestation reliance for cloud).
    4. Program Development — SDLC controls for new applications and major upgrades: project initiation, requirements / design / testing / approval gates, data conversion controls, post-implementation review.
  • IT-Dependent Manual Controls (ITDMs) — business-process controls that rely on system-generated reports, queries, or calculations. Auditors test these by re-performing the report extract and re-running the manual control on the verified data. ITDMs are why "report integrity" testing matters: if the underlying report's logic is wrong, the manual control built on top of it fails too.

How ITGCs support process-level reliance

The standard mental model: process-level automated controls (e.g., a three-way match in the ERP) can be tested with a single sample if the supporting ITGCs are operating effectively across the period. If ITGCs fail, the auditor must drop reliance on the automated control and either test process-level transactions in much larger samples or qualify the ICFR opinion. This is why ITGC testing dominates the IT SOX workload — a single failed ITGC can cascade into massive additional testing on the business-process side.

Deficiency evaluation

PCAOB AS 2201 defines three severity levels for control deficiencies (paraphrased — do not paste the AS 2201 text into client deliverables):

  • Control deficiency — a control, when designed or operating, does not allow management or employees, in the normal course of performing their assigned functions, to prevent or detect misstatements on a timely basis.
  • Significant deficiency — a deficiency, or combination of deficiencies, less severe than a material weakness, but important enough to merit attention by those charged with governance.
  • Material weakness — a deficiency, or combination, such that there is a reasonable possibility that a material misstatement of the annual or interim financial statements will not be prevented or detected on a timely basis.

A material weakness is the headline outcome: management must disclose it in the 10-K, and the external auditor will issue an adverse §404(b) opinion on ICFR. This is the result every SOX program is structured to avoid. Significant deficiencies are reported to the audit committee but not publicly disclosed.

Severity is judged on likelihood × magnitude. Magnitude is calibrated against the materiality threshold set by the external auditor for the financial statements; likelihood is qualitative and considers the nature of the control, compensating controls, and history of failures.

Materiality, scoping, and the "in-scope" decision

The external auditor sets a financial-statement materiality threshold during planning (commonly 5% of pre-tax income, with significant judgment). Management's ICFR scope must cover all material accounts and significant disclosures; from there, scope cascades to the business processes that feed those accounts and to the IT systems that support those processes.

A practical scoping cascade:

  1. Material accounts and disclosures — driven by the auditor's materiality threshold.
  2. Significant business processes — the cycles that initiate, authorize, process, or report transactions affecting material accounts.
  3. In-scope applications and supporting infrastructure — the systems that record, calculate, or report financial data for those processes. "Supporting infrastructure" includes operating systems, databases, middleware, and identity providers underneath the application.
  4. In-scope vendor systems — SaaS or hosted systems supporting in-scope processes. Reliance is typically established via the vendor's SOC 1 Type II report (see below).

A system supporting only operational decisions, with no financial-reporting impact, is generally out of scope for SOX even if it is critical to the business. A common scoping mistake is treating "important system" as a synonym for "in-scope system" — they are not the same for SOX.

SOC 1 vs. SOC 2 — distinguishing them is a SOX-relevant skill

Both are AICPA service-organization-control reports, both produced by independent CPAs, both come in Type I (point-in-time) and Type II (period-of-coverage) flavors. The difference is what they opine on:

  • SOC 1 — opines on the service organization's controls over financial reporting as relevant to the user entity's ICFR. SOC 1 reports are the appropriate evidence of vendor ITGCs for SOX reliance. They include a description of the service organization's system, the controls in place, the auditor's tests of those controls, and complementary user entity controls (CUECs) — controls the user entity (you) must implement to make the vendor's controls effective on your end.
  • SOC 2 — opines on controls relevant to the AICPA Trust Services Criteria (Security plus optionally Availability, Confidentiality, Processing Integrity, Privacy). SOC 2 is a security and operational-control attestation; it is not designed for SOX ICFR reliance, even though it overlaps heavily with ITGC content.

Practitioner consequence: when your finance team asks you to "get the SOC 2" from a vendor whose system is in-scope for SOX, push back and ask for the SOC 1. If the vendor only has a SOC 2, the external auditor will likely not accept it for §404 reliance, and your team may have to perform direct vendor testing (questionnaires, sample-based control testing on your side) — which is much more work than reading and mapping a SOC 1.

A vendor's SOC 1 mapping work for SOX includes:

  • Confirming the SOC 1 covers your contract's services and your fiscal period
  • Reading the auditor's exceptions and assessing impact on your ICFR
  • Documenting your CUECs and confirming you operate them
  • Confirming the SOC 1 covers any subservice organizations (e.g., the SaaS vendor's underlying cloud provider) using the inclusive or carve-out method appropriately

Interaction with other frameworks

A narrative summary — this plugin deliberately does not ship a hand-maintained crosswalk table. The SCF crosswalk is the authoritative source for control mappings; see /grc-engineer:gap-assessment and the cross-framework analyzer outputs.

  • COSO 2013 IC-IF — the de facto control framework most U.S. public companies use to satisfy management's §404(a) assessment. SOX provides the legal mandate; COSO provides the substantive framework.
  • COBIT 5 / 2019 — IT-process control framework commonly used to map ITGC objectives. Many SOX programs cite COBIT control objectives as the basis for their ITGC testing program.
  • PCAOB AS 2201 — the external auditor's standard for testing ICFR. Drives auditor expectations on test design, sample sizes, evidence sufficiency, and reliance strategy. Practitioners should understand AS 2201's structure even though only auditors execute against it directly.
  • SOC 1 (SSAE 18 / AT-C 320) — vendor reliance evidence for SOX (see above).
  • SOC 2 (TSC) — security/operational attestation; informative but not sufficient evidence of vendor ITGCs for SOX. SOC 2 ITGC-overlap controls (logical access, change management) are conceptually similar but the audit objective is different.
  • NIST 800-53 / 800-171 / CSF — security frameworks that overlap heavily with the IT-side of SOX ITGC content (access control, audit logging, change management) but are not SOX evidence on their own.
  • NYDFS 23 NYCRR 500, ISO 27001, PCI DSS — sector or scope-specific security frameworks that often share underlying controls with SOX ITGCs; many engineering teams structure their ITGC testing program to also produce evidence for these adjacent frameworks.
  • HIPAA Security Rule — separate jurisdiction (ePHI), but for healthcare-sector public companies the same change-management and logical-access tooling typically supports both HIPAA Technical Safeguards and SOX ITGCs.

Common misinterpretations

This plugin should correct the following recurring misunderstandings whenever they appear in user prompts:

  1. "SOX is a cybersecurity regulation." It is not. SOX is a financial-reporting accountability statute. Cybersecurity work happens under SOX only to the extent it supports ICFR over in-scope financial-reporting systems. A breach of a non-financial system (e.g., a marketing CRM) is a serious incident but is not, on its own, a SOX matter. (Cybersecurity disclosure obligations exist under separate SEC rules — most prominently the 2023 cybersecurity disclosure rules requiring an 8-K within 4 business days of determining a material cybersecurity incident — but those derive from §409's real-time disclosure mandate and SEC regulatory authority, not from SOX's ICFR provisions.)
  2. "§404(b) applies to every public company." No — non-accelerated filers are exempt, and emerging growth companies have a 5-year exemption from IPO. Confirm filer status before you scope §404(b) work.
  3. "A SOC 2 satisfies SOX." No. SOC 2 is a Trust Services Criteria attestation. The right vendor-reliance evidence for SOX is a SOC 1 Type II covering the period under audit and the services in your contract. SOC 2 may be useful supplementary evidence but does not satisfy the §404 reliance requirement on its own.
  4. "PCAOB AS 2201 is the management framework." No. AS 2201 is the auditor's standard for the §404(b) integrated audit. Management uses COSO (or another suitable framework) for its §404(a) assessment. The two perspectives are coordinated but not identical.
  5. "Material weakness equals a breach." No. Material weakness is a control-design or operating-effectiveness condition tied to the financial statements. A control deficiency can be a material weakness without any actual misstatement having occurred — the standard is "reasonable possibility" of material misstatement, not actual misstatement.
  6. "If the system isn't financial, it isn't in scope." Mostly true, with two important exceptions: (a) shared identity providers (Okta, AD) are in-scope when they grant access to in-scope financial systems; (b) shared change-management or deployment platforms (Jira, GitHub, CI/CD) are in-scope when they govern changes to in-scope financial systems. The boundary follows the integration, not the application's primary purpose.
  7. "SOX evidence retention is 6 years (like HIPAA)." No. PCAOB rules require auditor work-paper retention of 7 years. §802 (18 U.S.C. § 1519) imposes criminal penalties for knowing destruction of documents in connection with a federal investigation, with no fixed retention period — practitioners default to 7+ years for SOX evidence.

Assessment approach guidance

When asked to perform a SOX assessment or readiness check, walk this sequence:

1. Confirm SEC-registrant status and filer category

  • Is the company a §12 registrant or §15(d) filer? If neither and not on an S-1 runway and not recently acquired by a public company, SOX likely does not apply — confirm and document.
  • What is the filer category (large accelerated, accelerated, non-accelerated, EGC, SRC)? This determines §404(b) applicability and disclosure deadlines.
  • Is the external audit firm engaged for §404(b) attestation, or only for the financial-statement audit?

2. Confirm the materiality threshold and account scope

  • What materiality threshold has the external auditor set for the current fiscal year? (Don't proceed without this — it determines what's in scope.)
  • Which financial-statement accounts and disclosures are above the materiality / qualitatively-significant threshold?

3. Walk the in-scope process inventory

  • Order-to-cash, procure-to-pay, payroll, inventory, fixed assets, treasury, financial close, tax, equity — confirm which are in scope and at what locations.
  • For each in-scope process, identify the supporting applications and the supporting infrastructure (OS, DB, identity provider, scheduler, deployment pipeline).

4. Build the in-scope IT system inventory

  • For each in-scope application: where it runs (own data center, cloud, SaaS), who operates it, how it authenticates, how changes are managed, where its data lives.
  • For SaaS / hosted vendors: do you have a current SOC 1 Type II covering your contract scope and your fiscal period? If not, plan for direct vendor testing or escalate.

5. Identify the four ITGC domains for each in-scope system

  • Access — who provisions, who reviews, where MFA applies, what the SoD model looks like, how privileged access is controlled.
  • Change — change ticketing tool, approval flow, deployment mechanism, emergency change exception process, completeness reconciliation between deployments and tickets.
  • Operations — batch jobs, monitoring, backup schedule and tested-restore evidence, incident management, capacity / availability for financial close.
  • Development — SDLC stage gates for new applications and major upgrades, data conversion controls.

6. Map entity-level controls

  • Code of conduct, ethics hotline, audit-committee charter, board oversight, fraud risk assessment, whistleblower process, period-end close controls, financial reporting policies.

7. Identify IT-dependent manual controls

  • Any process-level control that relies on a system-generated report or query — flag for report-integrity testing.

8. Aggregate deficiencies

  • Run the deficiency severity assessment (deficiency / significant deficiency / material weakness) on all identified gaps. Apply both quantitative (magnitude vs. materiality) and qualitative (nature, history, compensating controls) factors.

9. Produce the readiness output

  • Surface the highest-severity gaps first, especially anything pointing toward a potential material weakness.
  • Frame remediation in terms of control design changes, evidence improvements, or scope adjustments.
  • Note any §404(b)-driven items the external auditor will want to retest after remediation.

Common pain points: the "I just inherited SOX" survival guide

If you have just been handed a SOX program — or your SaaS company has been told it is now in-scope because of an acquisition or an IPO runway — these are the failure modes to look for first. They are also the items external auditors push back on most often in early-program engagements.

Year 1 inventory — what to find first

  1. In-scope financial applications: ERP (NetSuite, SAP, Oracle, Workday), billing system, revenue subledger, equity management, treasury, payroll, expense management, tax provisioning. Add the supporting databases, OSes, identity provider(s), and CI/CD platforms. This list anchors everything else.
  2. The ICFR scoping memo (if it exists): confirms the auditor and management's shared understanding of in-scope accounts → processes → systems. If it does not exist, building one is the most valuable Year-1 deliverable.
  3. Existing user access reviews: how often, who reviews, what evidence is captured, whether privileged accounts are reviewed separately. Privileged-access reviews are the single most common ITGC failure point in Year 1.
  4. Change management completeness: can you reconcile the population of production deployments to the population of approved change tickets? If not, change-management completeness is at risk and likely the auditor's first finding.
  5. Vendor SOC 1 inventory: which in-scope SaaS vendors have SOC 1 Type II reports covering your fiscal period? Where the vendor only provides SOC 2, plan for direct testing.

Auditor pushback — the recurring early-engagement themes

  • IT user access reviews: privileged access reviewed quarterly (or more often), reviewer is independent of the access being reviewed, evidence is signed and dated, removals from the review are tracked to closure. Expect detailed sampling.
  • Segregation of duties (SoD): a documented SoD matrix mapped to roles in each in-scope system, periodic SoD conflict scans, exceptions tracked and risk-accepted at an appropriate level. Auditors will test against the matrix and against actual production role assignments.
  • Change management completeness: a reconciliation between the change-ticketing system and the deployment population for each in-scope system, run at a frequency that supports operating-effectiveness reliance. Emergency-change population is reviewed separately for after-the-fact approval evidence.
  • Vendor reliance / SOC 1: SOC 1 Type II reports for in-scope vendors that cover the right scope and the right period; CUECs are documented and operated; subservice organizations are addressed with the right method (inclusive or carve-out).
  • Backup and restore: tested restores (not just successful backups), with evidence of the test results, for in-scope databases.
  • Logging and monitoring: privileged-action logging on in-scope databases and OSes, log retention sufficient for the audit period.

Year 1 vs. steady state

  • Year 1: scope is contested (auditor and management often disagree on system boundaries); walkthroughs are heavy because no documented narratives exist; ITGC remediation typically dominates Q3 and Q4.
  • Steady state: scope is stable; walkthroughs are confirmation-only ("any changes since last year?"); testing is efficient because workpapers carry forward; the focus shifts to acquisitions, system migrations, and remediation of prior-year deficiencies.

Capabilities

  • SOX ICFR scoping (filer status, materiality cascade, in-scope account/process/system inventory)
  • ITGC testing across the four classic domains (Access, Change, Operations, Development)
  • Entity-level control evaluation (code of conduct, audit-committee charter, fraud risk assessment, period-end close)
  • IT-dependent manual control identification and report-integrity testing
  • §302 / §906 disclosure-controls certification readiness review
  • §404(a) management assessment workflow guidance
  • §404(b) external-auditor coordination guidance for accelerated filers
  • §409 real-time disclosure (8-K) timeline awareness
  • §802 / 18 U.S.C. § 1519 document-retention guidance
  • Deficiency evaluation (deficiency / significant deficiency / material weakness) with magnitude × likelihood logic
  • SOC 1 vs. SOC 2 vendor-reliance distinction and CUEC documentation
  • COSO 2013 component coverage at the conceptual level (paraphrased — does not reproduce COSO IC-IF text)
  • COBIT alignment guidance for ITGC objectives
  • Pre-IPO (S-1 readiness) ICFR build
  • Post-acquisition ICFR integration scoping
  • Cloud-agnostic ITGC patterns with brief vendor-specific examples (e.g., AWS CloudTrail as Operations-domain logging evidence)
  • SCF crosswalk routing (usa-federal-law-sox-2002) — /grc-engineer:gap-assessment integration

Command routing

  • /us-sox:scope — SEC-registrant determination, filer-status, materiality cascade, in-scope inventory
  • /us-sox:assess — gap assessment via the SCF crosswalk for usa-federal-law-sox-2002
  • /us-sox:evidence-checklist — ITGC + entity-level + IT-dependent manual evidence patterns

All three delegate to /grc-engineer:gap-assessment with SCF framework ID usa-federal-law-sox-2002 for the control-by-control mechanics, and wrap the results in SOX-specific terminology (filer status, ITGC domains, deficiency severity, SOC 1 reliance).

Levelling up to Full

A Full-depth follow-on PR could add framework-native workflow commands tied to the ICFR audit ritual. Strong candidates:

  • /us-sox:scope-itgc-population — generate the in-scope IT system inventory from a list of in-scope applications, including supporting infrastructure layers
  • /us-sox:itgc-walkthrough — produce ITGC walkthrough narratives for the four domains, ready for auditor review
  • /us-sox:soc1-reliance-map — capture vendor SOC 1 Type II coverage, exceptions, CUECs, and subservice-organization treatment
  • /us-sox:deficiency-evaluation — apply the magnitude × likelihood logic to a deficiency log and produce a draft severity classification (with the explicit caveat that final classification is a judgment call requiring the external auditor and management's input)
  • /us-sox:302-certification-pack — assemble the disclosure-controls evidence the disclosure committee needs to support a §302 sign-off

Each of those is a "framework-native" workflow that does not fit any generic gap-assessment output and would justify Full depth.

References

Commands 3

SOX Assessment

Runs a gap assessment for the Sarbanes-Oxley Act of 2002 by delegating to /grc-engineer:gap-assessment with the framework's SCF identifier (usa-federal-law-sox-2002), then overlays SOX-specific framing — ICFR scope, ITGC domains, deficiency severity, and SOC 1 vendor reliance.

This is a readiness assessment, not an external audit. The output identifies gaps an auditor would likely surface; final classification of any gap as a control deficiency, significant deficiency, or material weakness is a judgment call requiring management and the external auditor.

Usage

/us-sox:assess [--scope=<scope>] [--sources=<connector-list>]

Arguments

  • --scope: narrow the assessment
    • itgc-access — IT General Controls, Access to Programs and Data
    • itgc-change — IT General Controls, Program Changes
    • itgc-operations — IT General Controls, Computer Operations
    • itgc-development — IT General Controls, Program Development
    • itgc-all — All four ITGC domains
    • entity-level — Entity-Level Controls (ELCs)
    • itdm — IT-Dependent Manual Controls and report-integrity
    • vendor-soc1 — Vendor SOC 1 reliance evaluation
    • certifications — §302 / §404 / §906 certification readiness
    • Default: full SOX readiness assessment
  • --sources=<connector-list>: comma-separated connector plugins (e.g., aws-inspector,okta-inspector,github-inspector) to pull live evidence into the assessment.

Pre-assessment confirmation

Before starting, confirm with the user:

  1. SEC-registrant status and filer category — is the company a §12 registrant or §15(d) filer? Large accelerated, accelerated, non-accelerated, EGC, or SRC? This drives §404(b) exposure. If the user has not yet run scope, route to /us-sox:scope first.
  2. Materiality threshold — has the external auditor set a financial-statement materiality threshold for the period? Without it, scope cannot be set defensibly. Surface as a blocker.
  3. In-scope inventory — confirm in-scope financial accounts, business processes, applications, supporting infrastructure, and vendor systems with SOC 1 reliance.
  4. Audit history — any prior-year significant deficiencies, material weaknesses, or auditor management letter comments? Year-over-year remediation status?
  5. Engagement cycle — interim testing in progress, year-end rollforward, or post-fieldwork remediation?

What the assessment produces

  1. Readiness score — overall SOX ICFR readiness percentage, weighted across in-scope controls.
  2. ITGC heatmap — readiness percentage per ITGC domain (Access, Change, Operations, Development) per in-scope system.
  3. Entity-level control coverage — presence and operating evidence for the standard ELC set.
  4. IT-dependent manual control inventory — ITDMs identified, with report-integrity testing status.
  5. Vendor SOC 1 reliance map — for each in-scope vendor, SOC 1 coverage, exceptions, CUEC status, bridge-letter status.
  6. Gap log — every identified gap with:
    • Affected control(s) and SOX section / ITGC domain reference
    • Evidence available vs. evidence missing
    • Tentative severity (control deficiency / significant deficiency / material weakness candidate) — with the explicit caveat that final classification belongs to management and the external auditor
    • Remediation recommendation
  7. Certification readiness — §302 / §404(a) / §906 sign-off basis, with disclosure-committee and sub-certification population status.

Delegation

Under the hood, the SCF mechanics are handled by the persona plugin:

/grc-engineer:gap-assessment "usa-federal-law-sox-2002" [--sources=<connector-list>]

The SCF crosswalk expands 4 SCF controls into 17 SOX-relevant controls. That number is small because SOX itself does not enumerate technical control objectives — the security and IT control catalog flows in from COSO 2013 IC-IF, COBIT, and the AICPA SOC 1 framework rather than from SOX statutory text. This assess command therefore wraps the SCF gap-assessment output in ICFR-shaped sections and adds the entity-level / ITDM / vendor-SOC 1 dimensions that SCF alone does not capture.

Output structure (suggested)

SOX READINESS ASSESSMENT
========================

Period:               [fiscal year / quarter]
Filer category:       [Large accelerated / Accelerated / Non-accelerated / EGC / SRC]
§404(b) applicable:   [Yes / No / EGC-exempt until <date>]
External auditor:     [firm — engagement type]

Overall readiness:    [N]% (control-weighted)

ITGC HEATMAP (per in-scope system)
----------------------------------
System              Access     Change    Operations  Development
[App 1]             [%]        [%]       [%]         [%]
[App 2]             [%]        [%]       [%]         [%]
...

ENTITY-LEVEL CONTROLS
---------------------
[ELC]                              [Status]    [Evidence]
Audit committee oversight          [PRESENT]   [charter + minutes]
Code of conduct                    [PRESENT]   [policy + ack population]
Whistleblower hotline              [PRESENT]   [hotline summary]
Fraud risk assessment              [PRESENT]   [annual FRA]
Period-end close controls          [PARTIAL]   [JE review log incomplete]
Disclosure committee               [PRESENT]   [charter + Q-end packs]
...

IT-DEPENDENT MANUAL CONTROLS
----------------------------
ITDM                                          Report-integrity   Manual control
[control 1]                                   [TESTED]           [SIGNED]
[control 2]                                   [NOT TESTED]       [SIGNED]
...

VENDOR SOC 1 RELIANCE
---------------------
Vendor       SOC 1 Type II   Period covered   CUECs operating   Bridge letter
[vendor 1]   [YES]           [start - end]    [YES]             [YES]
[vendor 2]   [SOC 2 only]    [n/a]            [n/a]             [n/a — direct testing]
...

GAP LOG
-------
🔴 MATERIAL-WEAKNESS CANDIDATE (n):
  - [gap] (system / domain / SOX section)
    Recommendation: [...]

🟡 SIGNIFICANT-DEFICIENCY CANDIDATE (n):
  - [gap] (system / domain / SOX section)
    Recommendation: [...]

🟠 CONTROL DEFICIENCY (n):
  - [gap] (system / domain / SOX section)
    Recommendation: [...]

🔵 OBSERVATION (n):
  - [gap] (process improvement)

CERTIFICATION READINESS
-----------------------
§302 disclosure-controls basis:  [READY / GAPS — see deficiency log]
§404(a) management assessment:   [READY / GAPS]
§404(b) auditor attestation:     [N/A — non-accelerated / EGC-exempt / coordinated with [firm]]
§906 criminal certification:     [READY / GAPS]
Sub-certification population:    [N collected / M outstanding]

OPEN BLOCKERS
-------------
- [list — e.g., materiality threshold not set, prior-year material weakness not remediated]

NEXT STEPS
----------
- /us-sox:evidence-checklist for collection planning
- Specific remediation items per gap log

Severity classification — caveat

PCAOB AS 2201 defines three levels (paraphrased):

  • Control deficiency — control design or operation does not allow management or employees to prevent or detect misstatements on a timely basis in the normal course of operations.
  • Significant deficiency — less severe than a material weakness, but important enough to merit attention by those charged with governance.
  • Material weakness — a deficiency, or combination, such that there is a reasonable possibility a material misstatement will not be prevented or detected on a timely basis.

This assess command can identify candidate severity tiers based on magnitude (relative to the auditor's materiality threshold) and likelihood (qualitative judgment based on the nature of the control, history, and compensating controls). Final classification is a judgment call requiring management and the external auditor — not an automated output. Material weakness has public-disclosure implications; do not represent automated severity tags as authoritative.

Common assessment scopes

Frequently-requested scopes in practice:

  • Year 1 SOX program — full assessment with emphasis on scoping, walkthroughs, and ITGC baseline establishment. Expect heavy gaps in Access (privileged access reviews), Change (change-completeness reconciliation), and vendor SOC 1 reliance.
  • Pre-IPO (S-1 readiness) — full assessment 12–24 months pre-IPO. Output drives the IPO ICFR build plan.
  • Post-acquisition integration — scope limited to the acquired entity, with a one-year integration runway.
  • Quarterly §302 readiness — narrower scope, focused on disclosure-controls and material-change identification.
  • Year-end rollforward — re-tests interim-tested controls for the rollforward period (Q3 close → year-end).
  • Material-weakness remediation validation — narrow scope on the specific deficiency, with sample-size and operating-period considerations driven by the auditor.

Interactions with sibling frameworks

  • SOC 2 — overlapping content (logical access, change management) but a different audit objective (Trust Services Criteria, not ICFR). Useful supplementary evidence; does not satisfy SOX vendor reliance on its own.
  • SOC 1 Type II — the canonical vendor-reliance evidence for SOX. Always preferred over SOC 2 for in-scope vendor systems.
  • NYDFS 23 NYCRR 500, ISO 27001, NIST CSF / 800-53 — many engineering teams structure ITGC tooling so the same underlying controls (access reviews, change tickets, deployment logs, log retention) generate evidence usable across SOX and these adjacent frameworks. See /grc-engineer:optimize-multi-framework for cross-framework optimization.
  • HIPAA Security Rule — for healthcare-sector public companies, the same change-management and logical-access tooling typically supports both HIPAA Technical Safeguards and SOX ITGCs.
  • PCI DSS — separate scope, but for retailers and card-handling public companies the same change-management discipline often covers both.

Cadence

  • Annual — full §404(a) management assessment in the 10-K; full §404(b) auditor attestation (accelerated filers).
  • Quarterly — §302 disclosure-controls certification in each 10-K and 10-Q; assessment of any material changes to ICFR for the quarter.
  • Per material event — 8-K within 4 business days under §409.
  • Continuous — deficiency logging and remediation tracking; ongoing user access reviews (often quarterly for privileged access); vendor SOC 1 collection on the vendor's cycle.

Common misinterpretations corrected

  • "SOX is a security regulation." It is a financial-reporting accountability statute. Cybersecurity work supports SOX only through ICFR over in-scope financial systems.
  • "§404(b) applies to everyone." Non-accelerated filers and EGCs (for up to 5 years) are exempt.
  • "A SOC 2 satisfies SOX." No — SOC 1 Type II is the appropriate evidence of vendor ITGCs for SOX.
  • "Material weakness equals a breach." Material weakness is an ICFR control condition, not a security incident.

Statute: Public Law 107-204; 15 U.S.C. §§ 7201 et seq. Regulators: SEC, PCAOB, DOJ Depth: Reference (tier 2 of 3) Related commands: /us-sox:scope, /us-sox:evidence-checklist, /grc-engineer:gap-assessment

SOX Evidence Checklist

Generates the recurring evidence list a SOX program produces and an external auditor will request. Organized around the audience that actually consumes SOX evidence — the SOX PMO, internal audit, and the external auditor's IT and process teams — rather than around SCF families, because in practice SOX evidence is filed by ITGC domain, entity-level control, and IT-dependent manual control / report-integrity category.

Never commit evidence artifacts to source control. Evidence files routinely contain user IDs, system identifiers, change tickets, ledger excerpts, and screenshots that are sensitive even when not classified as PII. Use an access-controlled, encrypted evidence locker; honor §802 (18 U.S.C. § 1519) by retaining at least 7 years.

Usage

/us-sox:evidence-checklist [--scope=<scope>] [--family=<SCF_family_code>] [--audience=<aud>] [--format=<fmt>]

Arguments

  • --scope: filter by SOX evidence category
    • itgc-access — IT General Controls, Access to Programs and Data
    • itgc-change — IT General Controls, Program Changes
    • itgc-operations — IT General Controls, Computer Operations
    • itgc-development — IT General Controls, Program Development
    • entity-level — Entity-Level Controls (ELCs)
    • itdm — IT-Dependent Manual Controls and report-integrity
    • certifications — §302 / §404 / §906 certification packs
    • vendor-soc1 — Vendor SOC 1 reliance evidence
    • Default: all categories
  • --family=<SCF_family_code>: optional, restrict to a single SCF family (e.g. IAC, CFG, BCD) when running the SCF-backed half of the assessment.
  • --audience: target audience
    • external-auditor — full evidence pack with citations to §302 / §404 / SOX section, sample sizes annotated
    • internal — readiness checklist for the SOX PMO / control owners
  • --format: table (default Markdown), markdown (detailed list), csv (spreadsheet import)

Mandatory SOX artifacts (the named documents)

Before per-control evidence, the program must be able to produce these top-level artifacts on demand:

ArtifactRequired byOwnerFrequency
Management's Report on Internal Control over Financial Reporting (the §404(a) assessment in the 10-K)15 U.S.C. § 7262(a)CEO / CFO / SOX PMOAnnually
§302 quarterly disclosure-controls certification (in 10-K and each 10-Q)15 U.S.C. § 7241CEO / CFOEach periodic report
§906 criminal certification (in 10-K and each 10-Q)18 U.S.C. § 1350CEO / CFOEach periodic report
External auditor's §404(b) attestation report15 U.S.C. § 7262(b); PCAOB AS 2201External audit firmAnnually (if accelerated filer)
ICFR scoping memoInternalSOX PMO / internal auditAnnually + on material change
Risk and Control Matrix (RCM / RACM)InternalSOX PMOAnnually + on material change
Walkthrough narratives (per process)PCAOB AS 2201 expectationProcess owner / SOX PMOAnnually (refresh)
Test-of-design and test-of-operating-effectiveness workpapersInternal + auditor expectationInternal audit / SOX testersAnnual cycle (interim + rollforward)
Deficiency log with severity classification and remediation plansInternal + audit-committee reportingSOX PMO / internal auditContinuous
Vendor SOC 1 Type II reports + CUEC inventoryPCAOB AS 2201 vendor-reliance expectationSOX PMO / vendor managerAnnually per vendor

ITGC evidence by domain

The four classic ITGC domains are where security and platform engineers spend the bulk of their SOX time. For each in-scope IT system, evidence is expected across all four (when relevant to the system).

Domain 1 — Access to Programs and Data

Evidence ItemCommon FormatNotes / Auditor Expectations
New-hire / role-change / terminations population for the period, reconciled to in-scope system access changesHRIS extract + IAM provisioning logPopulation completeness is the test — sample selections come from this list.
Joiner / mover / leaver tickets with documented manager approvalTicketing system export (Jira / ServiceNow)Tickets for in-scope systems should reference the access requested and the approver's role.
Periodic user access review (UAR) evidence — in-scope systems, all user populationsUAR campaign export with reviewer sign-offs and removals tracked to closureQuarterly is common for privileged access; annual minimum for standard users. Reviewer must be independent of the access being reviewed.
Privileged access review evidence, separated from standard-user UARDedicated privileged-account UARMost common ITGC failure point in Year 1. Auditors expect quarterly cadence and full closure tracking.
Segregation of duties (SoD) matrix mapped to in-scope system rolesSoD matrix documentShould be reviewed annually and exceptions risk-accepted at an appropriate management level.
SoD conflict scan results for the periodSoD tool output (e.g., from GRC platform) or manual analysisAuditor will sample conflicts and trace to risk acceptance or remediation.
MFA enforcement evidence for in-scope systemsIdP configuration export, conditional access policyRequired for remote and privileged access in nearly all modern programs.
Authentication / password policy configurationIdP policy document or screenshotLength, complexity, lockout, history.
Privileged-action logging on in-scope databases / OSesSample log entries + retention configurationOperations-domain logging often satisfies this too — confirm overlap.
Service account inventory and ownershipService account registerService accounts are a common audit finding when ownership is unclear.
Generic / shared account inventory and justificationShared-account register with risk acceptanceAuditor expectation: zero shared accounts for in-scope financial systems where feasible.

Domain 2 — Program Changes

Evidence ItemCommon FormatNotes / Auditor Expectations
Change management policy and procedurePolicy documentMust define change types, approval flow, segregation between developer and deployer.
Standard change population for the period (reconciled to deployments)Deployment log + ticket exportCompleteness is the test. Auditors will reconcile the deployment count to the approved-ticket count; a gap is a red-flag finding.
Change tickets with documented peer review and approver evidenceTicketing system extracts + linked PR / merge recordsApprover must be independent of the developer.
Emergency change population, separately identified, with after-the-fact approvalEmergency-change ticket extractSampled separately; auditor pays particular attention to volume and to approval timeliness.
Code review evidence (peer review on PRs touching in-scope systems)Git platform PR / MR recordsGitHub / GitLab / Bitbucket export tied to the change ticket.
Production deployment evidence with deployer identityCI/CD pipeline logsMust show that deployer ≠ developer for in-scope systems (or that automated deployment with controlled pipeline serves as the SoD).
Configuration / parameter changes to in-scope systems, separately trackedApplication or infrastructure change logConfiguration changes are easy to miss in change populations — confirm coverage.
Database schema change evidenceDDL change tickets + DBA logsCommon gap when DBAs deploy outside the standard CI/CD pipeline.

Domain 3 — Computer Operations

Evidence ItemCommon FormatNotes / Auditor Expectations
Job scheduling and batch monitoring evidence for in-scope batches (financial close, billing runs, payroll runs)Scheduler logs (Control-M, AutoSys, cron + monitoring), failure-handling ticketsSampled across the period; expect testing of failure handling.
Backup schedule and configuration for in-scope databasesBackup tool configuration + run historyBackups alone are not evidence; tested restores are.
Tested-restore evidence for in-scope databases during the periodRestore test reportAt least annual restore test expected; documented test results required.
Incident management tickets affecting in-scope systems during the periodITSM incident exportAuditor will sample incidents to confirm root cause / remediation closure.
Capacity and availability monitoring for in-scope systemsMonitoring dashboard exportsEspecially relevant during financial close windows.
Privileged-action logging and log retention configurationLog aggregator configuration + retention policyLog retention must cover the audit period plus the audit window itself.
Cloud-vendor attestation reliance (e.g., AWS / Azure / GCP SOC 1) for hosting infrastructureVendor SOC 1 Type IIIf you host in-scope systems on a hyperscaler, the cloud provider's SOC 1 typically covers the data-center / physical-environment portion of operations. Pair with your CUECs.
Environmental controls (data-center, on-premises only)Facility audit / vendor attestationMostly covered by hyperscaler SOC 1 for cloud-hosted systems.

Domain 4 — Program Development

Evidence ItemCommon FormatNotes / Auditor Expectations
SDLC policy and stage-gate definitionsPolicy documentMust define gates: requirements, design, build, test, UAT, deploy, post-implementation review.
New-application / major-upgrade project artifacts for the periodProject documentation + sign-off recordsInitiation, requirements, design, test plans, UAT sign-off, go-live approval.
Data conversion controls for system migrationsConversion test plan + reconciliation evidenceData migration is a high-risk SDLC event for SOX; auditor will dig in.
Post-implementation review evidencePIR reportOften the missing artifact; common audit finding.
Segregation between development, QA, and production environmentsArchitecture diagram + access evidenceDemonstrates that developers cannot deploy directly to production.

Entity-Level Controls (ELCs)

Evidence ItemCommon FormatNotes / Auditor Expectations
Audit committee charter and meeting minutesCharter + minutes from the periodConfirms independence and oversight responsibility per SOX §301.
Code of conduct and acknowledgment populationCode document + signed acknowledgment populationShould be acknowledged on hire and periodically thereafter.
Whistleblower / ethics hotline recordsHotline report summaryDemonstrates §301 anonymous-reporting mechanism is operational.
Fraud risk assessmentAnnual FRA documentOwned by SOX PMO or internal audit; refreshed annually.
Period-end financial-reporting controls — close calendar, journal-entry review, account reconciliationsClose package, JE review log, recon binderOften the most heavily-sampled ELC area.
Manual journal entry approvalsJE approval log with reviewer signaturesAuditor will sample large or unusual JEs.
Disclosure committee charter and meeting minutesCharter + minutesSupports CEO / CFO basis for §302 / §906 certifications.
Tone-at-the-top communicationsInternal communications, training recordsDemonstrates control environment per COSO.

IT-Dependent Manual Controls (ITDMs)

For each ITDM, the evidence pack includes both the manual-control evidence and the report-integrity evidence.

Evidence ItemCommon FormatNotes / Auditor Expectations
Source-system query / report logic documentationQuery SQL or report-builder definitionThe report's logic must be locked down and change-controlled.
Report-integrity test — re-perform the query at the audit date and reconcile to a known good sourceReconciliation workpaperAuditor commonly re-performs this independently.
Manual control evidence — reviewer's mark-ups, sign-off, and exception handlingMarked-up report + email or ticket trailReviewer independence and timeliness matter.
Population of report-driven controls in scopeITDM registerOften missing in Year 1; build it early.

§302 / §404 / §906 certification packs

Evidence ItemCommon FormatNotes / Auditor Expectations
Disclosure committee meeting pack (per §302 quarterly cycle)Disclosure committee deck + minutesDocuments the basis for CEO / CFO §302 certification.
Sub-certification population from material-process owners and material-subsidiary controllersSub-cert tracking spreadsheet + signed sub-certsMany large companies cascade §302 sign-off down to process / entity owners.
§404(a) management assessment narrativeSection of the 10-K Management's ReportAsserts effectiveness of ICFR as of fiscal year-end.
External auditor's §404(b) attestation report (accelerated filers)Auditor's report in the 10-KAdverse opinion = material weakness publicly disclosed.
§906 criminal certification (CEO / CFO signatures)Exhibit to the 10-K / 10-Q18 U.S.C. § 1350 — criminal exposure for knowing or willful false certification.
Material-event tracking for §409 / 8-K within 4 business days8-K filing logReal-time material disclosure obligation.

Vendor SOC 1 reliance

Evidence ItemCommon FormatNotes / Auditor Expectations
Vendor SOC 1 Type II report covering the audit periodVendor SOC 1 PDFMust cover services in your contract and the period under audit.
Mapping of SOC 1 controls to your in-scope processSOC 1 reliance matrixDocument which of the vendor's controls you are relying on.
Complementary user entity controls (CUECs) inventory and operation evidenceCUEC checklist + evidence per CUECAuditor will test that you actually operate the CUECs.
Subservice organization treatment (inclusive vs. carve-out)Documented in the SOC 1 reliance matrixIf carved out, you may need separate evidence for the subservice provider.
SOC 1 exception review and impact analysisException log with accept / reject / mitigate decisionsEach exception in the vendor's SOC 1 must be assessed for impact on your ICFR.
Bridge letter for the gap between SOC 1 period-end and your fiscal year-endVendor-issued bridge letterCommon when the vendor's SOC 1 period closes before your fiscal year-end.

Cloud-agnostic technical evidence patterns (optional examples)

These are vendor-neutral examples of how engineering teams typically produce ITGC evidence. They are illustrative — none of them is required by SOX.

  • Identity provider (IdP) export of in-scope app group memberships at period start and period end, used for both UAR evidence and JML reconciliation.
  • Audit log archive for in-scope databases and OSes, retained for the audit period plus the audit window.
  • CI/CD pipeline run history for in-scope systems, used for change-completeness reconciliation.
  • Backup tool run history plus a periodic restore test report, used for Operations-domain testing.

Brief vendor-specific example: AWS CloudTrail (or the equivalent on other clouds) can serve as evidence of privileged-account activity for §404(a) ITGC testing in the Operations and Access domains, provided retention is set to cover the audit period and the trail integrity validation is enabled. This is an example, not a requirement — non-cloud or multi-cloud environments use different log sources.

Output by audience

External auditor (full pack)

Provide an evidence package organized by:

  1. Cover memo — engagement scope, period, in-scope inventory, point of contact
  2. Mandatory SOX artifacts — RCM, walkthroughs, scoping memo, deficiency log
  3. Entity-level controls — full ELC test pack
  4. ITGC evidence — by system × by domain (Access, Change, Operations, Development), with sample selections noted
  5. IT-dependent manual controls — for each ITDM, the manual-control evidence plus the report-integrity workpaper
  6. Vendor SOC 1 reliance — SOC 1 reports + CUEC evidence + bridge letters + exception analyses
  7. Certification artifacts — disclosure-committee packs, sub-certifications, draft §302 / §404(a) / §906 statements

Internal readiness

Simplified checklist for the SOX PMO and control owners:

  • In-scope system inventory current
  • RCM updated for the period
  • All walkthroughs refreshed
  • User access reviews completed for the period
  • Privileged access reviews completed for the period
  • SoD scan run and exceptions risk-accepted
  • Change-completeness reconciliation run for each in-scope system
  • Emergency change population reviewed
  • Backup restore test completed during the period
  • Privileged-action logging active and retained for the audit period
  • SOC 1 Type II reports collected for all in-scope vendors, CUECs operating, bridge letters obtained where needed
  • Period-end close ELC evidence assembled
  • Disclosure committee packs current for each quarter
  • Deficiency log up to date with remediation status

Evidence retention

  • PCAOB rule: auditor work papers must be retained 7 years.
  • §802 (18 U.S.C. § 1519): criminal penalty up to 20 years for knowing destruction of documents with intent to obstruct a federal investigation.
  • Practical default: retain SOX evidence (testing workpapers, screenshots, walkthroughs, deficiency logs, vendor SOC 1s) for at least 7 years in an access-controlled, encrypted store with documented chain-of-custody if subject to litigation hold.

SCF crosswalk

This evidence checklist supplements (rather than replaces) the SCF-driven evidence list produced by /grc-engineer:gap-assessment usa-federal-law-sox-2002. The crosswalk maps 4 SCF controls → 17 SOX-relevant controls — small because SOX itself does not enumerate technical control objectives. Use the SCF gap assessment for the control-by-control mechanics; use this checklist for the artifacts and evidence the SOX cycle actually produces.


Statute: Public Law 107-204; 15 U.S.C. §§ 7201 et seq. Regulators: SEC, PCAOB, DOJ Evidence retention: 7 years (PCAOB rule); §802 (18 U.S.C. § 1519) imposes criminal exposure for knowing destruction Related commands: /us-sox:scope, /us-sox:assess, /grc-engineer:gap-assessment

SOX Scope

Determines whether and how the Sarbanes-Oxley Act of 2002 (Public Law 107-204; 15 U.S.C. §§ 7201 et seq.) applies to the organization, and — if it does — produces the inputs needed to scope an Internal Controls over Financial Reporting (ICFR) program.

SOX is a financial-reporting law, not a security control catalog. The scope determination is a sequence of registrant-status, filer-status, materiality, and process / system-inventory questions. This command should ask only the questions that actually matter and produce a defensible scope verdict — not walk the user through the whole statute.

Usage

/us-sox:scope

What this produces

  • Applicability verdict: In-scope / out-of-scope / pre-scope (S-1 runway or post-acquisition integration)
  • Filer category: large accelerated, accelerated, non-accelerated, EGC, SRC — drives §404(b) attestation requirement and 10-K filing deadline
  • §404(b) exposure: yes / no, with the rule basis (filer status, EGC 5-year exemption, etc.)
  • Materiality cascade input: confirmation that the external auditor has set a financial-statement materiality threshold for the period, since this drives account / process / system scope
  • In-scope account / process / system inventory (initial draft): material accounts → significant business processes → in-scope applications → supporting infrastructure → vendor (SOC 1) reliance map
  • Carve-outs and exemptions: foreign private issuer accommodations, EGC exemption from §404(b), non-accelerated filer exemption from §404(b)
  • Next steps: whether to proceed with /us-sox:evidence-checklist (collection planning) or /us-sox:assess (gap assessment)

Decision tree

Walk these questions in order. Stop and document the verdict at the first decision that resolves applicability.

1. SEC-registrant status

Ask the user:

  • Are the company's securities registered under §12 of the Securities Exchange Act of 1934 (i.e., listed on a U.S. national securities exchange such as NYSE or Nasdaq)?
  • Is the company required to file periodic reports (10-K / 10-Q / 8-K) under §15(d) of the Exchange Act (e.g., publicly registered debt)?
  • Is the company a foreign private issuer (FPI) with U.S.-listed securities? (FPIs are generally subject to SOX with limited home-country accommodations and 20-F annual filings.)
  • Is the company on an active S-1 (IPO) runway, with an underwriter and an external audit firm engaged for ICFR readiness?
  • Has the company recently been acquired by a public company that will need to integrate it into its §404(a) assessment?

Verdict logic:

  • Yes to §12 / §15(d) / FPI → in scope, proceed.
  • S-1 runway → pre-scope (IPO readiness): ICFR build typically begins 12–24 months pre-IPO. Proceed as if in-scope and note the runway timeline.
  • Recent acquisition by a public company → pre-scope (integration window): typical one-year integration before full §404(a) inclusion. Confirm the parent company's expected inclusion date.
  • None of the above → out of scope. Document the verdict and stop.

2. Filer category (drives §404(b))

If in-scope, determine the filer category. The current SEC definitions (paraphrased):

  • Large accelerated filer: public float ≥ $700M. §404(b) external-auditor attestation required. 10-K due 60 days after fiscal year-end.
  • Accelerated filer: public float ≥ $75M and < $700M. §404(b) required (subject to the 2020 SEC narrowing for certain low-revenue filers). 10-K due 75 days after fiscal year-end.
  • Non-accelerated filer: public float < $75M. §404(b) not required (per Dodd-Frank-driven amendments). §404(a) management assessment is required. 10-K due 90 days after fiscal year-end.
  • Emerging Growth Company (EGC) — JOBS Act category. §404(b) exempt for up to 5 years from IPO or until disqualifying threshold breach (revenue, debt issuance, large-accelerated status). §404(a) still required.
  • Smaller Reporting Company (SRC) — orthogonal to §404(b); affects scaled disclosure obligations. Confirm separately.

Practitioner note: confirm filer status with the controller and the external audit engagement letter. Year 1 of accelerated-filer status is a step-change in SOX program effort.

3. Materiality and in-scope account inventory

If §404(a) applies, the next gate is the auditor's financial-statement materiality threshold for the current fiscal year. Without that threshold, scope cannot be set defensibly.

Ask:

  • Has the external auditor set a financial-statement materiality threshold for the period? (Common rule of thumb: 5% of pre-tax income, with significant judgment.)
  • What financial-statement accounts and disclosures sit above the materiality / qualitatively-significant threshold?

If the materiality threshold has not been set, surface this as the first scope blocker — everything downstream depends on it.

4. Significant business processes

For each in-scope account, identify the business process(es) that initiate, authorize, process, or report transactions affecting that account. Common cycles:

  • Order-to-cash (revenue recognition)
  • Procure-to-pay (expense recognition, AP)
  • Payroll
  • Inventory
  • Fixed assets
  • Treasury (cash, debt, hedging)
  • Tax (provision and compliance)
  • Equity (stock-based comp, share issuances)
  • Financial close and consolidation

Ask which cycles are in scope and at which legal entities / locations. Multinational consolidation often pulls in non-U.S. subsidiaries that feed material accounts.

5. In-scope IT system inventory

For each in-scope process, capture:

  • Application: ERP (NetSuite / SAP / Oracle / Workday), billing, revenue subledger, equity management, treasury system, payroll, expense management, tax provisioning, financial consolidation tool.
  • Supporting infrastructure: operating system, database, middleware, identity provider, scheduler, deployment / CI-CD platform underneath the application. ITGC scope follows the integration — a shared identity provider granting access to in-scope apps is itself in-scope.
  • Hosting model: on-premises, IaaS, PaaS, SaaS. SaaS systems pull in vendor-reliance considerations (see step 6).

6. Vendor SOC 1 reliance

For each in-scope SaaS or hosted vendor:

  • Does the vendor produce a SOC 1 Type II report? (Not SOC 2 — see SKILL on the distinction.)
  • Does the report cover the services in your contract and the period under audit?
  • Are there exceptions in the SOC 1 report? (Read them.)
  • What are the complementary user entity controls (CUECs), and do you operate them?
  • Are subservice organizations (the SaaS vendor's own underlying providers) addressed via the inclusive or carve-out method?

If a vendor only has a SOC 2 (or no service-organization report at all), flag direct vendor testing as a likely Year-1 effort.

7. Entity-level controls

Confirm presence and ownership of the standard entity-level controls:

  • Audit-committee charter, composition (independence), and meeting cadence
  • Code of conduct and ethics hotline / whistleblower process
  • Fraud risk assessment (typically annual, owned by internal audit or the SOX PMO)
  • Period-end financial-reporting controls (close calendar, journal-entry review, account reconciliations, manual journal approvals)
  • Disclosure committee charter and meeting cadence (supports §302 / §906 sign-off)

8. IT-dependent manual controls

For each in-scope process, ask whether any control depends on a system-generated report, query, or calculation. These are IT-dependent manual controls (ITDMs) and require report-integrity testing in addition to manual control testing. Common examples:

  • AP three-way-match exception report reviewed by the controller
  • Revenue cutoff report compared to invoice population at period-end
  • Aged-AR review based on a query against the receivables ledger

9. Carve-outs to confirm

  • Foreign private issuer: SOX applies but with home-country governance accommodations (e.g., 20-F filings rather than 10-K, audit-committee composition rules adapted to home-country law). Confirm with counsel.
  • Non-accelerated filer: §404(b) attestation not required; §404(a) management assessment still required. Disclosure-controls (§302) and financial-statement audit still required.
  • EGC: §404(b) attestation exempt for 5 years from IPO or until disqualified. §404(a), §302, §906 still required.
  • Recent acquisitions: a target acquired during the fiscal year is generally allowed up to one year to integrate before being included in the §404 assessment. Confirm the parent's expected inclusion date.

Output template

Structure the output as:

SOX SCOPE VERDICT
=================

Applicability:        [In scope / Pre-scope (S-1) / Pre-scope (acquisition) / Out of scope]
Registrant basis:     [§12 / §15(d) / FPI / S-1 runway / acquired by public co. / N/A]
Filer category:       [Large accelerated / Accelerated / Non-accelerated / EGC / SRC]
§404(a) (mgmt):       [Required / Not required] — [basis]
§404(b) (auditor):    [Required / Not required / EGC-exempt until <date>] — [basis]
10-K filing deadline: [60/75/90 days post fiscal year-end]
Materiality:          [Threshold set / Not yet set — BLOCKER]

In-scope cycles:
  - [list]

In-scope applications + supporting infrastructure:
  - [app] @ [hosting] — supporting [identity provider / DB / OS / scheduler / CI-CD]

Vendor SOC 1 reliance:
  - [vendor] — SOC 1 Type II [coverage period] / SOC 2 only / none
    CUECs documented: [yes/no/n/a]

Entity-level controls present:
  - [list]

IT-dependent manual controls flagged:
  - [process / control / report dependency]

Carve-outs claimed:
  - [list]

Open scope blockers:
  - [list]

Next steps:
  → /us-sox:evidence-checklist [--family=<SCF_family>] for collection planning
  → /us-sox:assess for gap assessment via the SCF crosswalk (usa-federal-law-sox-2002)

Notes for the practitioner

  • Don't conflate "important system" with "in-scope system." Many critical operational systems are not SOX in-scope. The boundary follows financial-reporting impact.
  • Filer status changes. A company can move between accelerated and non-accelerated as public float crosses thresholds, which can materially change SOX program effort year-over-year.
  • Acquisitions reshape scope mid-year. A material acquisition will pull in the target's accounts (and ultimately its IT systems) under the parent's §404(a) assessment, typically with a one-year integration runway.
  • Cybersecurity-only events are not SOX events. A breach of a non-financial system is a serious incident — and may be reportable under SEC cybersecurity disclosure rules separate from SOX — but is not, on its own, a SOX matter.

Statute: Public Law 107-204; 15 U.S.C. §§ 7201 et seq. Regulators: SEC (disclosure), PCAOB (auditor oversight), DOJ (criminal enforcement of §802 / §906) Depth: Reference (tier 2 of 3) Related commands: /us-sox:assess, /us-sox:evidence-checklist, /grc-engineer:gap-assessment

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/us-sox
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70