SOX 404 ITGC user access reviews
SOX Section 404 requires management of a public company to assess internal control over financial reporting every year, so auditors test IT general controls such as user access reviews, timely removal of leavers and restricted privileged access to financially significant systems. Teams evidence this with complete user listings, review sign-offs and termination-to-removal records; Autharva supports it by covering identities the IGA misses and naming an owner for each.
Who it applies to: Public companies that file annual reports with the SEC (registered investment companies excluded), with the external auditor attestation under Section 404(b) required for accelerated and large accelerated filers.
What the rule asks for
- SOX § 404(a) (15 U.S.C. 7262(a))Management assessment. Each annual report must include management's assessment, as of fiscal year end, of the effectiveness of internal control over financial reporting.
- SOX § 404(b)-(c) (15 U.S.C. 7262(b)-(c))Auditor attestation. The company's registered public accounting firm attests to and reports on management's assessment. Issuers that are neither accelerated nor large accelerated filers, and emerging growth companies, are excluded.
- 17 CFR 240.13a-15(c)Framework-based evaluation. Management, with the CEO and CFO, evaluates control effectiveness each fiscal year against a suitable, recognized control framework.
- 17 CFR 240.13a-15(f)Authorization and asset protection. Internal control over financial reporting includes policies that ensure transactions occur only with management authorization and that give reasonable assurance of preventing or timely detecting unauthorized use of company assets.
- PCAOB AS 2201.36IT in the top-down approach. The auditor should understand how IT affects the company's flow of transactions, and identifies IT risks and controls as part of the top-down audit rather than as a separate evaluation.
Where access evidence usually falls short
- The user listing used for the review is incomplete, so the auditor cannot rely on the population.
- Reviews cover named employees but leave out service accounts, integration accounts and other non-human identities with access to financial systems.
- Leavers are disabled in the identity provider while direct application or database accounts remain active.
- Reviewers approve access in bulk without evidence that inappropriate access was removed.
- Privileged and administrator access to the ERP, general ledger or databases is not reviewed separately.
How Autharva helps
- Shows what every employee, contractor, service account, OAuth grant and AI agent can actually reach in financially significant apps, including through the apps it administers and the accounts it owns.
- Assigns a named owner to every identity, including service accounts that no review currently covers.
- Hands exceptions back to your IGA certification campaigns rather than replacing them.
- Closes excess access only with the owner's approval, so every removal has a decision behind it.
- Produces continuous access-control evidence for SOX 404 instead of a year-end scramble.
Autharva produces evidence that supports these controls. It does not by itself make an organization compliant; your auditor or examiner decides.
Evidence your examiner or auditor will ask for
- Complete user listings for each in-scope application, with how the listing was produced
- Access review sign-offs with evidence that flagged access was removed
- Terminated user listing matched to account removal dates in each in-scope system
- Privileged and administrator account listings with review evidence
- Service and system account inventory with a named owner for each
- Approval records for new and changed access
Questions.
Does SOX require quarterly user access reviews?+
No. Neither Section 404 nor AS 2201 sets a review frequency. The company designs its controls, and the auditor tests whether they operate effectively.
Do smaller public companies need an auditor attestation?+
Management's assessment under Section 404(a) applies broadly. The auditor attestation under Section 404(b) does not apply to issuers that are neither accelerated nor large accelerated filers, or to emerging growth companies.
Should service accounts and AI agents be in the review population?+
If an identity can create, change or approve data in a financially significant system, it affects the controls the auditor tests. Many teams leave these identities out because no one owns them, which is the gap Autharva is built to show.
Does Autharva make us SOX compliant?+
No. Autharva produces evidence for the access-control part of IT general controls. Change management, operations and financial reporting controls remain outside it.
Sources
- 15 U.S.C. 7262, Management assessment of internal controls (Sarbanes-Oxley Act Section 404), Cornell LII, current
- eCFR, 17 CFR 240.13a-15, Issuer's disclosure controls and procedures and internal control over financial reporting, current as of 2026-11-09
- PCAOB, AS 2201: An Audit of Internal Control Over Financial Reporting That Is Integrated with An Audit of Financial Statements, current
Summaries are in our own words for orientation, not legal advice. Read the official text and check with your counsel.
Have a requirement we haven't covered?
Describe your environment, a system you're unsure about, or an audit finding. An Autharva SME reads every message and replies by email.
- Answered by a person, not a script.
- Please don't include passwords, customer data or account numbers.
What can your identities really reach?
Find out before an attacker or an examiner does.