SOC 2 · CC - Common Criteria (Security)
SOC 2 SOC2-CC1.1: CC1.1 Commitment to integrity and ethical values (COSO principle 1)
SOC 2 SOC2-CC1.1 covers CC1.1 Commitment to integrity and ethical values (COSO principle 1). The held text names 4 evidence records for it, the first being Board-approved code of conduct with version history and scope covering contractors and vendor staff. The common gap an assessor flags is Code of conduct never acknowledged by contractors or vendor personnel.
The organisation shows through direction, decisions and behaviour that integrity and ethics matter to how it runs its controls. Points of focus: leadership sets the tone at the top; expected conduct is written into a code that staff, outsourced providers and partners understand; performance of individuals and teams is judged against that code; departures from it are found and corrected promptly and consistently; and contractors and vendor staff are brought within the same conduct expectations, adherence checks and corrective action.
What evidence supports SOC2-CC1.1?
- Control environmentBoard-approved code of conduct with version history and scope covering contractors and vendor staff
- Control environmentSigned acknowledgements of the code at hire and annually, including for contractors
- Control environmentRecords of conduct breaches investigated and the disciplinary or corrective outcome
- Control environmentLeadership communications or town-hall material setting expectations on integrity
Where this requirement comes from
This is our own statement of SOC 2 SOC2-CC1.1, read from the copy we hold (issuer free complete copy) and stated in our words, not the standard verbatim. The framework as we hold it.
Common gaps an assessor flags
- Code of conduct never acknowledged by contractors or vendor personnel
- No evidence that reported violations were investigated or closed
- Acknowledgements collected at hire only, never refreshed
How it maps to ISO 27001:2022
- 6.2 medium Standards of conduct evidence employment terms partially, without security specific contractual clauses.
A link is a topical overlap with a confidence and a reason. It does not establish that meeting one requirement satisfies the other, and it is not certification.