SOC 2 (2017 TSC) CC1.4 — Competence and Training

What this control requires

The entity demonstrates a commitment to attract, develop, and retain competent individuals in alignment with objectives.

In plain English

The entity demonstrates a commitment to attract, develop, and retain competent individuals in alignment with objectives. In practice, this means you can prove you commitment objectives-level controls on a defined cadence.

Why it matters

Every SOC 2 audit opinion is built control-by-control from the Trust Services Criteria. A missing or failing criterion produces an exception in the report, which buyers, partners and procurement teams read line-by-line during vendor reviews.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A SOC 2 auditor (under AT-C §§ 105/205) tests both design and operating effectiveness over the audit window. For each criterion they expect a written control, a control owner, a population of events, and a sample tested against the population — including remediation tickets for exceptions.

Within Common Criteria (Security), the assessor will trace your implementation back to the catalogue reference (Criterion CC1.4) and look for objective evidence on the latest two assessment cycles.

How to implement

Secure Development

Pipeline. Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline.

Branch protection. Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence.

Code Review Testing

Pipeline. Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

Operational checklist

• Commitment. Document the trigger, the owner and the cadence.
• Competence. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Secure. Document the trigger, the owner and the cadence.
• Scope: objectives.

Evidence to collect

• Code Repo Scan. Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports.

Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Competence and Training (Original component: Control Environment).

Common pitfalls

• CI security checks set to warn-only; the merge button is faster than the security feedback.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• CIS Controls v8 16.3 — Perform Root Cause Analysis on Security Vulnerabilities
• BSI C5:2020 DEV-08 — Version Control
• GDPR Article 97 — Commission reports
• NIST SP 800-53 Rev. 5 AT-2(3) — Social Engineering And Mining
• ISO/IEC 27001:2022 A.8.28 — Secure coding

Related controls in SOC 2 (2017 TSC)

• Criterion CC1.3 — Organizational Structure and Reporting Lines
• Criterion CC7.2 — Anomaly Detection
• Criterion CC1.1 — Commitment to Integrity and Ethical Values
• Criterion P5.2 — Correction and Amendment of Personal Information
• Criterion CC5.1 — Control Selection and Development

References

• AICPA / ASEC — SOC 2 (2017 TSC)
• Catalogue identifier: Criterion CC1.4

Topics: secure developmentawareness trainingcode review testingdevsecopssecurity training