An IS auditor is reviewing documentation of application systems change control and identifies several patches that were not tested before being put…

The most significant risk of implementing untested patches is the compromise of system integrity. Integrity refers to the accuracy, completeness, and reliability of a system and its data. Untested changes can introduce unforeseen errors, processing flaws, security vulnerabilities, or cause system instability. This directly undermines the assurance that the system is operating as intended and that the data it processes is trustworthy. The failure of the change control process (i.e., skipping the testing phase) creates a direct path for code with unknown effects to enter the production environment, fundamentally threatening the system's integrity.

A. Loss of application support: Applying patches, even if untested, is more likely to be a prerequisite for maintaining vendor support rather than a cause for its loss.

C. Outdated system documentation: While documentation may become outdated, this is an administrative control failure and a secondary risk compared to the immediate operational risk of system failure.

D. Developer access to production: The problem described is a failure in the change management process (lack of testing), not necessarily a failure of access controls. The risk exists regardless of who moved the patch to production.

---

1. ISACA

CISA Review Manual

27th Edition (2019). Domain 3: Information Systems Acquisition

Development

and Implementation

Section 3.4.5

Testing of Changes. The manual emphasizes that all changes

including patches

must be tested in a controlled environment before being moved to production. The primary purpose of this testing is "to provide assurance that the changed system meets the requirements of the users" and does not "adversely affect existing processing

" which are core components of maintaining system integrity.

2. ISACA

COBIT 2019 Framework: Governance and Management Objectives (2018). Management Objective BAI07: Manage Change Acceptance and Transitioning. Key Management Practice BAI07.03 states

"Test the changes before migration to the live environment." The rationale is to mitigate the risk of negative impacts on service stability

business operations

and IT systems. A failure to test directly increases the risk of service disruption and erroneous processing

which are manifestations of a lack of integrity.

3. Pressman

R. S.

& Maxim

B. R. (2020). Software Engineering: A Practitioner's Approach (9th ed.). McGraw-Hill Education. Chapter 19: Software Testing Strategies. This foundational text explains that the goal of testing is to find errors and ensure the software conforms to its requirements. Deploying untested code bypasses this critical quality assurance step

creating a high risk of "latent defects that can cause system failure

incorrect output

or data corruption

" all of which are direct threats to system integrity.