What happens when the controls are defined, but the evidence doesn't tell the full story? This case study explores how cybersecurity professionals can navigate gaps in control evidence, business pressure and assurance expectations while maintaining integrity and professional responsibility.
A security compliance manager is coordinating the organization's readiness for a SOC 2 Type II examination ahead of an important customer commitment. During evidence collection, they identify several control activities that were not consistently performed or documented during the review period, including quarterly access reviews, change approval documentation, and vulnerability scan records.
The organization has defined controls in place, but the available evidence does not always show that those controls operated as intended throughout the period. Some teams explain that required activities occurred but were not formally recorded. Others provide documentation that is incomplete, inconsistent, or does not align with the control description. In some cases, alternative evidence, such as system logs, tickets, approvals, or other records, may help validate whether the activity occurred, but it is not clear whether that evidence is sufficient.
Business leaders emphasize the importance of staying on schedule because a key customer expects the report before finalizing a contract. They encourage the team to close gaps quickly and keep the process moving. At the same time, the external auditor conducting the examination will apply professional standards and independent judgment when evaluating whether the available evidence is sufficient. Given those pressures, the security compliance manager must determine how to represent the control environment accurately, whether remediation or additional evidence is needed, and how to communicate concerns. They also must avoid formalizing activities that did not actually occur during the review period, creating documentation after the fact, or implying that current fixes demonstrate past control performance.
Situations like this can raise questions around:
This scenario demonstrates how the Code of Professional Conduct can inform professional judgment when assurance expectations and business pressures are in tension. Considerations include integrity, accuracy, accountability and responsible communication when determining how control performance and evidence gaps should be represented.
Download the Cybersecurity Practices Guides to review three guides showing how the Code of Professional Conduct can be applied in daily work across key professional areas.