Skip to content
Compliance · SOX Section 404 and PCAOB AS 2201

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.

FAQ

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.

Ask an Autharva SME

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.
Bigger than a question?Share a problem statement or use case with the team that plans our roadmap →
0/2000

We use these details only to reply. Privacy statement

Next step

What can your identities really reach?

Find out before an attacker or an examiner does.