SOX ITGC scoping and risk assessment

Deciding which applications, databases, infrastructure, locations and reports fall inside SOX ITGC scope, using the top-down, risk-based approach SEC guidance and PCAOB standards describe.

Which applications and IT layers are in SOX scope

Deciding which financial applications, databases, operating systems, directories and network components carry SOX ITGCs, and why the layers under an in-scope application matter when its automated controls or reports are relied on.

Automated controls and benchmarking in a SOX audit

How automated application controls are tested once and benchmarked in later years, why that only works when change, access and operations ITGCs are effective, and what evidence (compile dates, stable code, vendor software) supports it.

SOX ITGCs for acquired businesses: the one-year exclusion

How an acquisition affects SOX ITGC scope on both sides of the deal: the acquirer's one-year exclusion of the target, disclosing material changes, and the access, change and operations gaps a private target should close before its systems enter the next assessment.

IT risk assessment for SOX: risks that make ITGCs matter

The IT risks PCAOB standards name as threats to financial reporting (unauthorized access and changes, inaccurate processing, data loss, manual intervention) and how management maps them to IT general controls instead of running a separate IT review.

Talk to our team.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.

  • 30-minute call: free, with no obligation.
  • NDA on request: we can sign before you share details.
  • Clear next steps: a scope and plan after the call.