Siam Thanat Hack Co., Ltd.

SOC 2 Type II and Security Testing Evidence

SOC 2 Type II evaluates control design and operating effectiveness over a specified period. Penetration testing can support evidence according to risk, service commitments and the controls selected for the examination.

Overview
Target Audience
Technology service providers, cloud platforms, SaaS vendors, fintechs, and data centers hosting or processing customer data
Testing and Review Frequency
Type II examines operating effectiveness over a specified period, with testing based on risk and selected controls
Assessment Scope
Security Trust Services Criteria (CC7.1), cloud workloads, production infrastructure, SaaS software, APIs, and CI/CD pipelines
Relevant Risks
Qualified auditor opinions, enterprise customer churn, procurement disqualification, and reputational damage

SOC 2 Type I and Type II

SOC 2 reports assess service organization controls using the applicable Trust Services Criteria.

SOC 2: trust services criteria: Security, Availability, Confidentiality, Processing Integrity, Privacy
SOC 2: trust services criteria

An explanatory overview. Read the article for scope, applicability and supporting evidence.

  • Security — Protect systems and information
  • Availability — Meet availability commitments
  • Confidentiality — Protect confidential information
  • Processing Integrity — Complete and accurate processing
  • Privacy — Handle personal information appropriately
  • The criteria address security, availability, processing integrity, confidentiality and privacy. Select the categories relevant to the service and examination scope.
  • Type I evaluates control design at a specified date. Type II also evaluates operating effectiveness over a specified period.
  • Agree the systems, services, commitments and examination period with the auditor before planning evidence.

How testing supports CC4.1 and CC7.1

Connect technical evidence to the objectives of the controls the organization uses.

SOC 2: technical evidence: System scope, Risk-based testing, Remediate and retest, Prepare for the auditor
SOC 2: technical evidence

An explanatory overview. Read the article for scope, applicability and supporting evidence.

  • System scope — Applications, APIs and infrastructure
  • Risk-based testing — Verify controls and record findings
  • Remediate and retest — Track owners and supporting evidence
  • Prepare for the auditor — Scope, methods, results and limitations
  • CC4.1 corresponds to COSO Principle 16 and concerns ongoing or separate evaluations of whether internal controls are present and functioning.
  • CC7.1 concerns detection and monitoring of configuration changes that introduce vulnerabilities and susceptibility to newly discovered vulnerabilities.
  • Determine testing scope, methods, frequency, tester qualifications and evidence according to risk and selected controls, in consultation with the auditor.
  • Select vulnerability assessment, penetration testing or other methods for the control objective. An annual schedule or external-provider requirement adopted by one organization is not automatically a requirement for every organization.

Remediation and evidence for the auditor

Keep traceable evidence and explain the limits of the testing performed.

SOC 2: audit readiness: Set period and scope, Evaluate controls, Track deficiencies, Auditor evaluation
SOC 2: audit readiness

Illustrative preparation during a Type II examination period. The auditor evaluates the evidence and expresses an opinion. A pentest result does not guarantee that opinion.

  • Set period and scope — Identify systems and assessed controls
  • Evaluate controls — Collect operating evidence
  • Track deficiencies — Remediate and verify with retesting
  • Auditor evaluation — Evaluate evidence and issue the report
  • CC4.2 concerns timely evaluation and communication of internal-control deficiencies to those responsible for corrective action.
  • Assign owners and remediation timelines according to risk, organizational policy and commitments, and verify effectiveness.
  • Testing and retest reports can support the examination when relevant to its scope and period.
  • A testing summary should state scope, dates, methods and limitations. It is not a SOC 2 report or a security guarantee. Testing results do not guarantee the auditor’s opinion.

References and Assessment Scope

Summary of source references, assessment scope, and review timing in the context of each item.

Reference Topic Assessment Scope Testing Cycle
Trust Services Criteria CC4.1 Control evaluation Evaluate whether internal controls are present and functioning using methods and evidence appropriate to the selected controls. According to risk and the organization’s evaluation process
Trust Services Criteria CC7.1 Configuration and vulnerability monitoring Detect changes introducing vulnerabilities and susceptibility to newly discovered vulnerabilities. According to risk and controls selected for examination
Trust Services Criteria CC4.2 Deficiency evaluation and communication Notify those responsible for corrective action and retain follow-up evidence. Timely action according to risk and organizational commitments

Implementation Checklist

Select items your organization has completed. The percentage shows selected items only and does not assess security or compliance.

0%

Frequently Asked Questions (FAQ)

Key answers and practical guidance addressing common compliance questions.

How do Type I and Type II differ?

Type I evaluates control design at a specified date. Type II also evaluates operating effectiveness over a specified period.

Must every SOC 2 organization obtain an annual pentest from an external company?

Determine testing scope, methods, frequency, tester qualifications and evidence according to risk and selected controls, in consultation with the auditor. Select vulnerability assessment, penetration testing or other methods for the control objective. An annual schedule or external-provider requirement adopted by one organization is not automatically a requirement for every organization.

How should testing reports be shared with auditors and service users?

Provide evidence relevant to the controls and examination scope through secure channels. A separate summary for service users can omit sensitive vulnerability details while stating the testing scope and limitations.

Official source documents

Explore AICPA Trust Services Criteria and SOC 2 Type II audit guidance on the AICPA-CIMA website.

Go to the official source

Request a quote