ITGC Audit Process: Complete Guide from Planning to Testing
MTJ Job Solutions ITGC Training Team
Kavya worked on the IT support team of a mid sized logistics company in Hyderabad. One Monday morning her manager walked to her desk and said, “The auditors arrive in three weeks. I need your help with our ITGC audit.” Kavya nodded politely, but inside she was lost. She knew how to reset passwords and fix printers. She had never heard of an ITGC audit process.
That night she searched online and found long documents full of heavy words. So she did what many beginners do. She made her own simple notes, one stage at a time. This blog is a clean copy of those notes. Read it like a story, because every stage of the process has a reason behind it.
What Is the ITGC Audit Process?
ITGC means IT general controls. These are the basic rules that keep a company’s computer systems safe, correct and reliable. An IT general controls audit checks two things. Do these rules exist? And do people really follow them?
Think of a school. There are rules about who can enter the building, how the timetable can change, and what to do in an emergency. An auditor asks the same kind of questions about computer systems.
The ITGC audit process moves in six stages: planning, risk assessment, testing of the main control areas, evidence collection, reporting and follow up. The main control areas are access management, change management, and backup and recovery. Some companies also add IT operations. Kavya wrote all of this on one sheet and stuck it on her monitor.
Audit Planning: Decide What to Check
Planning is the first stage, and it saves the most time later. The team decides the scope. Scope simply means which systems, which time period and which locations the audit will cover.
Kavya’s team made a short list of systems that handle money or reports: the billing application, the payroll system and the database behind them. They left out a small internal quiz tool, because it did not affect any report. They also fixed the dates, named the person responsible for each system, and listed the documents the auditor would probably ask for.
She also learned two useful terms. A design check asks whether a rule is well written and makes sense. An operating check asks whether people followed that rule all through the year. Auditors test both.
Risk Assessment: Find What Can Go Wrong
Next comes risk assessment. A risk is something that can go wrong, along with how likely it is and how much harm it can cause. Kavya’s manager asked her one question: “What could go wrong with the billing system?”
She listed three things. A person who left the company might still be able to log in. A wrong update might go live without anyone checking it. A server might fail with no backup to restore. She marked each risk as high, medium or low. High risks are tested first and in more detail.
Then she matched each risk with a control, which is the rule that stops it. The leaver risk matched the access review. The wrong update risk matched the change approval process. Where a risk had no control, she had found a gap, and it is far better to find a gap before the auditor does. A good habit is to refresh this list whenever the company adds a new system.
Access Management: Who Can Enter?
Access management decides who can use a system and what they can do inside it. Auditors usually look for a few simple things:
Approved requests. A manager approves every new user before the account is created.
Right roles. People get only the access their job needs, and no single person can do everything.
Quick removal. When someone leaves, their access is closed within a set time.
Regular reviews. Managers check the user list on a schedule and remove what is not needed.
Strong sign in. Good passwords and a second check, plus extra care for admin accounts.
Kavya’s own test was simple. She exported the user list from the billing system and compared it with the HR list of current employees. Three accounts belonged to people who had already left. Accounts of former staff are one of the most common findings in any audit, so she was glad to catch them early. She closed the accounts and kept a screenshot with the date.
Change Management: Control Every Update
Every company keeps changing its systems with fixes, new features and settings. Change management makes sure each change is requested, approved, tested and released by the right people, and that a record is left at every step.
Auditors expect the test area to be separate from the live system. They also expect that the person who writes a change is not the same person who releases it. Emergency changes are allowed, but they need a record and a review afterwards. These rules stop a small mistake from becoming a big outage.
Kavya picked a sample of recent changes and followed each one from request to release. Most were fine. One fix had gone live on a Friday evening, and its only approval was a chat message. She asked the team to attach proper approvals to the ticket in future. If you want to go deeper on this area, read our guide on ITGC change management testing.
Backup and Recovery: Can You Get Data Back?
Backups are copies of data that can save a company on its worst day. Auditors want to know how often backups run, which systems are covered, where the copies are stored, and whether someone notices when a backup fails. Copies should be kept away from the main system, so one problem does not destroy both.
The most important question is about restore testing. A backup nobody has tested is only a hope. Auditors ask when the team last restored data from a backup and whether the result was written down. They also ask about recovery goals, such as how much data loss and how much waiting time the business can accept.
Kavya found that backups ran every night, but nobody had ever tested a restore. She booked a test for the next week and saved the report. That one small act turned a weak area into a strong one.
Evidence Collection and ITGC Testing
Here Kavya learned the golden rule of auditing. If it is not written down, it did not happen. Evidence is the proof that a control worked. Auditors trust dated records, not memory. Common evidence includes system reports, user lists, tickets, approval emails, dated screenshots, logs and backup reports.
ITGC testing uses four simple methods:
Inquiry. The auditor asks people how the control works.
Inspection. The auditor reads records, tickets and reports.
Observation. The auditor watches the control happen.
Repeating the control. The auditor does the check again on their own and compares the result.
Auditors cannot check every single item, so they pick a sample. A control that runs many times in a year usually needs a bigger sample than one that runs only once. Kavya also made her own rules for evidence. She gave files clear names, added dates, and saved everything in one shared folder as the work happened, not in a rush at the end.
After testing, the auditor writes a report. Each finding has a rating and a suggested fix. Management replies with an action and a date, and the auditor follows up later to confirm the fix was done.
Kavya’s Audit Day
Three weeks passed quickly. On audit day Kavya handed the auditors one neat folder with the scope, the risk list, the user list check, the change samples and the restore report. The auditors found two small issues, and both already had a fix plan and a date. Her manager smiled across the table.
That evening Kavya understood something. The ITGC audit process is not scary. It is a habit of planning, checking and keeping proof. And she enjoyed it so much that she started thinking about it as a career.
If you feel the same, learning with a trainer and real practice makes the journey faster. Many learners search for an ITGC course in Ameerpet because the area is full of training centres, while others choose an ITGC Course in Hyderabad that fits their timings. Whichever you pick, make sure it covers every stage in this blog and lets you practise with real samples and evidence.
Frequently Asked Questions
What is the ITGC audit process?
It is the set of stages used to check whether a company’s basic IT rules work. The stages are planning, risk assessment, testing, evidence collection, reporting and follow up.
Which areas does an IT general controls audit cover?
The main areas are access management, change management, and backup and recovery. Many audits also look at IT operations, such as job monitoring and incident handling.
What is the difference between design and operating testing?
Design testing checks whether a control is well planned. Operating testing checks whether it worked every time during the audit period. A control must pass both to be trusted.
What evidence do auditors ask for?
They ask for dated records such as user lists, approval tickets, system reports, logs and backup or restore reports. The evidence should show who did what and when.
Can a fresher learn ITGC testing?
Yes. You do not need to be a programmer. You need to understand the control areas, practise with sample data and learn how to keep clear evidence.