WikiFrameworksSOC 2Perform Ongoing and Separate Evaluations

Perform Ongoing and Separate Evaluations

Updated: 2026-02-23

Plain English Translation

Under SOC 2 CC.1, organizations must conduct ongoing and separate evaluations to ensure their internal controls are actively working. This SOC 2 Type 2 internal control evaluation process involves a mix of real-time automated monitoring and periodic manual reviews, such as internal audits. By implementing a robust SOC 2 CC.1 monitoring activities control, the organization can detect security events, system failures, and compliance gaps, confirming that safeguards remain present and functioning as the business environment changes.

Executive Takeaway

Combining continuous system monitoring with periodic internal audits ensures controls remain effective and adapt to organizational changes.

ImpactHigh
ComplexityMedium

Why This Matters

  • Detects system vulnerabilities, capacity constraints, and control failures before they escalate into security incidents.
  • Satisfies ongoing and separate evaluations SOC2 compliance mandates by establishing a baseline understanding of internal control effectiveness.

What “Good” Looks Like

  • Deploying real-time alerting for capacity, security events, and latency issues across infrastructure. Tools like WatchDog Security's Posture Management can automate misconfiguration detection and remediation to further strengthen ongoing evaluations.
  • Conducting annual internal audits, penetration testing, and management reviews to objectively evaluate the control environment. Independent evaluations, supported by tools such as WatchDog Security's Vulnerability Management, help provide an additional layer of assessment.

CC.1 is the SOC 2 CC.1 monitoring activities control that requires organizations to select, develop, and perform evaluations. It ensures that the components of internal control are present and functioning to achieve organizational objectives.

Organizations learn how to perform ongoing evaluations for SOC 2 CC.1 by integrating monitoring tools directly into business processes. This includes utilizing real-time dashboards and alerting systems to track security events, network performance, and system capacity.

Separate evaluations are required to provide an objective assessment of internal controls. They help identify systemic issues that ongoing, day-to-day monitoring might miss during the SOC Type 2 audit internal control testing process.

Examples of ongoing evaluations include automated vulnerability scanning, daily capacity monitoring alerts, and real-time security event logging. These SOC continuous monitoring and evaluation strategies detect anomalies as they occur.

SOC 2 CC.1 auditors expectations include reviewing monitoring dashboards, alert configurations, and internal audit reports. They look for evidence that organizations actively track control performance and adjust their evaluations based on risk.

The main difference between ongoing and separate evaluations SOC requires is frequency and integration. Ongoing evaluations are built into daily operations for real-time feedback, while separate evaluations are periodic, objective reviews like internal audits or penetration tests.

Ongoing evaluations should occur continuously or in real-time, integrated into standard business processes. Separate evaluations are performed periodically, with their scope and frequency adjusted based on risk and the rate of change in the environment.

Documentation includes screenshots of monitoring dashboards, log samples, automated alerts, and formalized internal audit reports. These records demonstrate the SOC 2 internal control presence and functioning checks required for compliance.

Yes, penetration testing and independent certifications are explicitly recognized as valid examples of separate evaluations in SOC compliance. They provide an objective, external perspective on the effectiveness of security controls.

Organizations use centralized logging solutions, automated vulnerability scanners, and continuous control monitoring platforms. These tools provide the necessary data to perform ongoing evaluation methods for SOC 2 controls efficiently.

WatchDog Security's Compliance Center can automate evidence collection for SOC 2 evaluations, streamlining the process of conducting continuous internal control assessments. By integrating real-time monitoring tools, it ensures that controls are actively functioning and provides compliance teams with the necessary documentation to support audits.

With tools like WatchDog Security's Vulnerability Management and Posture Management, organizations can automate vulnerability scanning and remediation processes. These tools serve as separate evaluations, ensuring that internal controls are assessed periodically and that any issues are identified and addressed before they impact security.

WatchDog Security's Compliance Center can automate evidence collection for SOC 2 evaluations, streamlining the process of conducting continuous internal control assessments. By integrating real-time monitoring tools, it ensures that controls are actively functioning and provides compliance teams with the necessary documentation to support audits.

With tools like WatchDog Security's Vulnerability Management and Posture Management, organizations can automate vulnerability scanning and remediation processes. These tools serve as separate evaluations, ensuring that internal controls are assessed periodically and that any issues are identified and addressed before they impact security.

SOC2 CC4.1

"COSO Principle 16: The entity selects, develops, and performs ongoing and/or separate evaluations to ascertain whether the components of internal control are present and functioning."

VersionDateAuthorDescription
1.0.02026-02-23WatchDog Security GRC TeamInitial publication