Join our Newsletter — 33% off our NHI Course
Governance, Ownership & Risk

ITGC

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Governance, Ownership & Risk

ITGC, or information technology general controls, are the foundational controls that support reliable systems, access management, change management, and evidence integrity. They matter because financial reporting controls depend on the underlying technology environment behaving predictably and proving that behaviour through traceable records.

What ITGC Covers in Practice

Information technology general controls are the shared control layer that makes business applications dependable enough for reporting, audit, and downstream assurance. They do not prove a transaction is correct on their own, but they help ensure the systems that create, process, store, and evidence that transaction behave consistently and can be trusted.

For ITGC work, the key question is whether the surrounding technology environment is controlled well enough that application-level outputs remain reliable. That is why ITGC is usually discussed alongside access, change, operations, and evidence, rather than as a standalone technical control set.

Access Management as an ITGC Foundation

Access controls sit at the centre of ITGC because uncontrolled access can change data, conceal activity, or weaken the reliability of logs and reports. Strong access management is not just about who can log in, but about whether privileged access is approved, reviewed, removed when no longer needed, and kept aligned to job responsibilities.

This is also where segregation of duties matters most. If the same person can both create, approve, and obscure changes, the control environment stops being independently reliable. Access governance therefore supports both prevention and traceability.

Where access is tied to privileged accounts or service accounts, the control expectation expands from simple user administration to lifecycle discipline, reviewability, and evidence that access paths were appropriate throughout the reporting period.

Change Management and System Stability

Change management is the other major ITGC pillar because unreviewed or poorly tested changes can alter system behaviour without leaving a credible audit trail. In practice, ITGC expects organisations to manage production changes through approval, testing, separation of duties, and traceable deployment records.

The control objective is not to prevent change. It is to make change controlled, observable, and reversible enough that financial systems remain predictable. When change evidence is incomplete, auditors often cannot rely on the environment even if the business application appears to work.

ITGC also covers the supporting disciplines around configuration and release control, because unstable baselines, emergency fixes, and undocumented hot patches can all undermine trust in the reports produced by the system.

Evidence Integrity and Auditability

ITGC is only as strong as the evidence behind it. Logs, approvals, tickets, test results, and control attestations must be complete enough to show that the control operated as intended, not merely that it was designed well.

Traceability is therefore part of the control objective. If records can be altered, lost, or selectively reconstructed, the organisation may still have a technical process but not a dependable control environment. This is why evidence integrity is treated as foundational, especially where controls support financial reporting or external audit reliance.

The practical standard is simple: if a control cannot be demonstrated consistently from source records, it is difficult to rely on it for assurance.

Risk and Threat Considerations

ITGC failures can create material exposure because weak access, uncontrolled change, or poor evidence handling can hide erroneous or malicious system behaviour. That matters especially where reporting relies on technology platforms that multiple teams share and few people fully understand.

Failure mechanism: Excessive privilege, unauthorised production change, log tampering, or missing evidence can break the chain of trust between the system of record and the reported output. Once that chain is broken, the environment may still operate, but it is no longer reliable for assurance purposes.

Impact: The result can be undetected data manipulation, unsupported reporting, audit findings, remediation effort, and in serious cases, a loss of confidence in the control environment itself.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-2 — Account ManagementITGC access governance depends on controlled account lifecycle and reviewability.
AC-6 — Least PrivilegeITGC relies on limiting privileged access so changes and actions remain controlled.
CM-3 — Configuration Change ControlChange management is a core ITGC mechanism for predictable system behaviour.
Recommendation — Enforce account lifecycle controls and periodic review for production and reporting-system access. Restrict privileges to the minimum needed for operations, support, and reporting. Require approved, tested, and traceable changes before production release.
ISO/IEC 27001:2022A.5.15 — Access controlITGC access management depends on defined access rules and governance.
Recommendation — Define and enforce access rules for systems that support financial reporting.

Practitioner Guidance

Why practitioners should care: ITGC is the control backbone that makes application controls, reporting controls, and audit evidence believable. If access, change, or evidence discipline is weak, downstream control assertions often fail even when the business process itself looks sound.

Governance implication: Ownership for ITGC usually spans infrastructure, application, security, and assurance teams, so responsibilities must be explicit rather than assumed. The recurring failure mode is not a missing policy, but unclear accountability for access review, change approval, and evidence retention.

Practitioner takeaway: Treat ITGC as an operating discipline, not a documentation exercise, and validate it from real records rather than policy statements alone.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org