SOC 2 CC1.1: Commitment to Integrity and Ethical Values

Commitment to integrity and ethical values

It is late on Friday, and your team is trying to finish a customer’s security questionnaire. One question asks whether every production change receives an independent review. Your normal process does, but emergency changes follow a different procedure. Someone suggests answering “yes” so the deal can move forward.

This is where your code of conduct earns its place. Your team needs to know who can check the answer, how to explain the exception, and where to turn if a senior colleague insists on sending something misleading. The pressure is real. Your expectations need to be usable in that moment.

SOC 2 CC1.1 asks your organization to demonstrate a commitment to integrity and ethical values. The AICPA Trust Services Criteria connect that commitment to leadership’s example, communicated standards, evaluation of conduct, and timely responses when people fall short. Those expectations also reach relevant contractors and vendor personnel working on your behalf.

This is the first article in our SOC 2 Guide. We are looking at the common criteria used for the Security category in a SOC 2 Type 2 examination. The scenarios below are fictional, so you can picture how the same principle might work in your business without treating any example as a prescribed control.

Make your conduct standards useful

Start with situations your people actually face. A useful code explains how you expect them to handle customer information, represent your security practices, report mistakes, disclose conflicts of interest, and question an instruction that crosses a line.

Give the code an owner, have the appropriate leader approve it, and make the current version easy to find. Explain who it covers and how you communicate relevant expectations to contractors and vendor personnel. Their process may differ from employee onboarding; you still need to know it reaches the right people. Bring in HR or legal advice where the wording affects employment rights or legal obligations.

Then look at the decisions your leaders reward. If someone wins a contract with a misleading answer and gets congratulated for it, your team has learned something powerful about the company’s priorities. Reinforce the conduct you ask for, especially when an honest answer makes the sale harder.

Help people make the decision

Return to that questionnaire. Have the person preparing it check with your change-management owner. Together, they can confirm the standard and emergency procedures and write an accurate explanation. If the customer’s form only accepts yes or no, ask how to supply the qualification. If an earlier answer was wrong, arrange a correction through the appropriate customer contact.

Use a situation like this during onboarding or when you change expectations. Ask your team what they would do and whom they would contact. A dated acknowledgment helps you show that someone accepted the policy. Their explanation helps you understand whether they can apply it.

Give concerns somewhere safe to go

Name a primary reporting contact and an alternative for concerns involving that person. Confirm both contacts understand the role, can initiate a response, and have coverage when unavailable. A name on a policy is only useful if the person is ready to help.

Explain your protection against retaliation for good-faith reporting. Be precise about confidentiality and anonymity: you may be able to restrict who sees a concern without being able to conceal the reporter’s identity, particularly in a small team. Promise what your process can deliver.

For each actual concern, assign a reviewer, establish the facts, record the decision, and follow the resulting actions to completion. An unclear instruction, an honest mistake, and deliberate misconduct may call for different responses. Apply the standards consistently to senior personnel too, and bring in HR, legal, or security expertise when needed. Keep detailed case information restricted to those who need it.

Applying CC1.1 at five people

Imagine you and your cofounder run a software company with three employees. You handle the commercial side; your cofounder leads engineering. When that questionnaire arrives, you work through the answer together and explain the emergency-change procedure to the customer.

At your next team discussion, use the experience as a fictional practice scenario for everyone: who checks a claim, and what happens when the person pushing for the sale is a founder? Agree on a concise code and a reporting route. If a concern involves both founders, identify an appropriate outside contact who has accepted the responsibility and understands how to respond.

For the administrative follow-through, you could use Vanta’s policy workflow to distribute the approved code and collect policy acceptances. You still lead the discussion and decide how to handle concerns. Keep sensitive case details in an appropriately restricted location.

Evidence to keep: your approved code, dated acceptances, discussion notes, confirmed reporting contacts, and records of actual concerns and follow-up. A restricted register can be proportionate, provided your process covers absences and fits the sensitivity of your work. Five people handling highly sensitive data may need stronger arrangements.

Applying CC1.1 at 100 people

Now picture your company with separate sales, support, engineering, and HR teams. A support manager notices that people are using an unapproved tool to send customer files. Before assuming misconduct, you investigate whether the approved process is clear and workable.

HR coordinates the response, security checks the exposure, and the responsible manager follows through on coaching or other corrective action. You also look for the same problem elsewhere. Repeated concerns can reveal a process that needs fixing.

Use Vanta personnel tasks to help track assigned policy acceptances and identify overdue items. Reconcile the covered population against employees and relevant contractors, and have managers follow up. Keep original deadlines and actual completion dates so a later 100% completion figure does not hide late acknowledgments.

Evidence to keep: onboarding and acknowledgment records, the populations they cover, manager guidance, missed-step follow-up, and restricted case records showing what you decided and changed.

Applying CC1.1 at 1,000 people

At this size, imagine one business unit reports almost no concerns while others regularly raise issues. It is tempting to conclude that the quiet unit is doing especially well. Talk with its leaders and examine awareness of reporting routes before reaching that conclusion. Silence can also reflect uncertainty or fear of speaking up.

Maintain a common code, with local guidance or translations where appropriate. Define how HR, legal, security, and compliance coordinate, and which serious or recurring issues reach senior leadership or the board. Give case handlers consistent instructions and restrict access to detailed files.

Vanta’s policy-acceptance records can help you identify groups that need follow-up, alongside your local personnel records. Check the features and permissions available in your Vanta setup when planning this work. Your leadership review should also consider what concerns reveal, which actions remain overdue, and whether people trust the reporting process. Share only the personal detail needed for that review.

Evidence to keep: approved standards and local guidance, training and acknowledgment history, case-handling procedures, and leadership decisions with follow-up.

Choose controls and evidence that fit your risks

Choose your reporting arrangements, tools, and review frequency around your services, data, workforce, and customer commitments. CC1.1 does not set a headcount threshold for a hotline or prescribe one training schedule. The points of focus help you interpret the criterion rather than impose a single implementation.

A SOC 2 Type 2 examination addresses control design and operating effectiveness over a specified period. The AICPA SOC 2 guide explains that framework. Keep policy versions, acknowledgment dates, reviews, and corrective actions as the work happens. Documents collected at period-end cannot establish that a missed activity occurred earlier.

If nobody reported a concern, record that accurately. Where relevant to your control, retain evidence that the channel was available and reviewed. Never create cases to make the record look busier. Agree with your auditor on appropriate access, disclosure, and retention for sensitive case information. The auditor determines the testing and evidence needed; these examples cannot guarantee an opinion.

Start with a conversation your team can use

Pick a realistic situation your team could encounter this week. Ask who makes the decision, what information they need, and where they go if their manager is part of the concern. Follow up on any gap you discover. That gives you a useful starting point for making your expectations work in practice.

Need help with CC1.1?

At Genius GRC, we can help you build practical controls and organize the evidence behind them. Discuss your SOC 2 needs with us and we can work through an approach suited to your business.

Visit the SOC 2 Guide for the full series, including CC1.2 and oversight of internal control.

This article provides general guidance. Adapt the examples to your examination scope and obligations with your advisers and auditor.

More Posts

SOC 2 CC5.1 Selecting and Developing Control Activities

CC5 Control Activities Your risk assessment says an unauthorized production change could expose customer information. Someone suggests adding an approval. Someone else suggests another scanner. Both may help, but neither tells you whether the proposed control will interrupt the way that risk could actually occur. Before buying another tool or

SOC 2 CC4.1 Ongoing and Separate Evaluations

CC4 Monitoring Activities Imagine you’re looking at your weekly backup report. Every job succeeded. Nothing needs your attention, so you move on. A few weeks later, your team runs a restoration exercise. The backup is there, but nobody running the exercise can retrieve the key needed to decrypt it. Recovery

SOC 2 CC3.4 Identifying and Assessing Changes

Imagine someone on your team removes an approval step to make a routine process easier. The change looks sensible to the people doing the work. Then, at the next risk meeting, you discover that the step was there to protect a customer commitment. Nobody asked the control owner before it

SOC 2 CC3.3: Fraud Risk

Consider deliberate misuse before it happens Imagine your team is gathering evidence for a customer review. Someone notices that several access reviews required by your policy were completed late. A manager suggests changing the dates so the records look consistent with the process. That’s an uncomfortable moment, and it’s worth