IT General Controls: The Most Common Deficiencies and How to Fix Them

IT general controls (ITGCs) are the controls over access, program changes and computer operations that support automated controls and reliable system data. The most common deficiencies are incomplete user access reviews, unmonitored privileged access, changes that bypass approval or testing, and unreviewed SOC reports from service organizations.

Automated controls and system-generated reports only deserve trust if the systems behind them are well controlled. That's the job of IT general controls (ITGCs) — and it's why ITGC deficiencies are among the most common findings in SOX programs, internal audits and financial statement audits.

Why ITGCs matter

When an auditor relies on a three-way match in your ERP, a system-calculated revenue schedule or a report used in a review control, they need confidence that:

  • Only appropriate people can access and change the system and its data
  • Changes to the system are authorized, tested and approved
  • The system processes data completely and accurately, day after day

If ITGCs fail, auditors may be unable to rely on the automated controls and reports that depend on them — expanding testing and sometimes leading to significant deficiencies or material weaknesses.

The most common deficiencies

1. Incomplete or ineffective user access reviews

What goes wrong: reviews exclude key applications, databases or the infrastructure beneath them; reviewers approve lists without examining them; the population isn't validated as complete; or removals identified in the review aren't completed.

How to fix it:

  • Define the in-scope systems and layers (application, database, operating system) explicitly
  • Generate user listings directly from systems and validate completeness
  • Give reviewers meaningful information — roles and what they allow, not just usernames
  • Track and evidence every requested change through completion

2. Unmonitored privileged access

What goes wrong: too many people have administrator rights, shared or generic accounts are used, or direct changes to production data aren't logged and reviewed.

How to fix it:

  • Minimize privileged accounts and eliminate shared credentials where possible
  • Use privileged access management tools or break-glass procedures
  • Log privileged activity and direct data changes, and have someone independent review them

3. Terminated users who retain access

What goes wrong: HR notifications lag, access to some systems is missed, or contractors aren't covered by the process.

How to fix it: automate deprovisioning from the HR system where possible, include contractors and service accounts, and reconcile terminations to access removals periodically.

4. Changes that bypass the process

What goes wrong: emergency changes aren't approved after the fact, developers can move their own code to production, vendors make configuration changes outside the process, or there's no way to detect unauthorized changes.

How to fix it:

  • Separate development and production access, or implement compensating monitoring
  • Require documented approval and testing for all changes — including emergency and vendor changes
  • Periodically compare actual production changes against approved tickets

5. Unreviewed SOC reports

What goes wrong: the organization relies on a cloud or service provider but never obtains or reviews its SOC 1 report, ignores exceptions, or fails to implement the complementary user entity controls (CUECs) the report assumes.

How to fix it: inventory relevant service organizations, obtain and review their SOC reports annually, evaluate exceptions and the period covered, obtain bridge letters and document how each CUEC is addressed.

6. Weak controls during system implementations

What goes wrong: data conversion isn't reconciled, security roles are designed late, or controls in the legacy system aren't replaced in the new one.

How to fix it: involve control owners and auditors early in implementations, reconcile converted data and design security roles and segregation of duties before go-live.

Building ITGCs that last

The most durable ITGC programs share a few traits: a clear inventory of in-scope systems, controls designed around how IT actually works, automation of evidence wherever possible and ownership by IT leaders rather than by the compliance team alone.

The bottom line

Most ITGC deficiencies are predictable — and preventable. Scope your systems completely, make access reviews meaningful, watch privileged activity, keep every change in the process and take your service providers' SOC reports seriously. Do that, and your auditors can rely on your systems instead of working around them.

Frequently asked questions

What are the main categories of ITGCs?

Most frameworks group ITGCs into access to programs and data, program changes, program development (including system implementations) and computer operations such as job scheduling and backups.

Do ITGC deficiencies always cause a material weakness?

No. Auditors evaluate the severity of ITGC deficiencies based on their effect on the automated controls and data that depend on them, and whether compensating controls exist.

How do cloud and SaaS applications affect ITGCs?

Responsibility is shared. The provider's SOC report covers its controls, but you remain responsible for user access in the application and for complementary user entity controls described in the report.

This article is for general information only and does not constitute legal, accounting or other professional advice. Requirements change; consult the cited sources and a qualified advisor about your specific situation.

Formos Consulting Risk, compliance, cybersecurity and transformation advisors

Keep reading

Related insights

All insights

Let’s talk about what you need.

Tell us where you are and where you need to be. A senior member of our team will follow up to talk through options.