Agree on the result before assessing the risk
Imagine you’re reviewing the week’s backup reports. Every job finished successfully, so the team feels good about recovery. Then a customer asks how quickly you could bring the service back. Sales says a few hours. Engineering says a full business day. Nobody has agreed which records need to come back first.
You have useful backup reports, but you still have a decision to make. What result are you actually asking your team to deliver?
That’s the question behind AICPA CC3.1. You need objectives clear enough to identify and assess what could stop you from achieving them. Once you agree on the outcome, you can make better decisions about risks, safeguards, and resources.
For SOC 2, connect those objectives to the services and trust services categories within your examination scope. Relevant sub-objectives may address security, availability, processing integrity, confidentiality, or privacy. The AICPA points of focus help interpret the criterion; they are not a separate set of mandatory controls.
Let’s work through that in this installment of our SOC 2 Guide. The companies below are fictional, and the measurements and review schedules are examples. Use them to think through your own service, obligations, and resources.
Start with the service people rely on
Start with the service your customers depend on. What do they use it for? What information does it handle? What would a failure mean for them? A payroll processing service and a public brochure website can use similar technology and still need very different objectives.
Bring your customer agreements, approved service descriptions, policies, and management decisions into the conversation. Ask the people selling and supporting the service whether their explanations match those records. If you’ve made conflicting promises, resolve them before building a risk assessment around them.
NIST's Cybersecurity Framework 2.0 offers useful planning context: consider stakeholder expectations, dependencies, and applicable obligations when deciding how to manage cybersecurity risk. That planning guidance can support the practical work below without replacing the criteria used in your SOC 2 examination.
Write down the boundaries. An objective for restoring a customer application should identify the application, relevant data, and dependencies. Clarify whether it covers production only or also a supporting service needed to bring production back online.
Make the objective usable in a decision
Try reading an objective to two people who work on the service. Would they recognize the same result? You want enough detail to decide whether a change, exception, or investment helps you achieve it.
For example, you might set an objective of restoring a service’s essential functions within eight hours of a declared recovery event, with no more than four hours of customer transactions lost. Those figures are illustrative, not recommended targets for every service. You’ll also need to agree when the clock starts and how you’ll confirm a successful recovery.
Keep the reasoning with the target. Perhaps your customers can tolerate a short interruption but would struggle to reconstruct missing transactions. That distinction should shape your backup frequency, restoration tests, and response to a failed backup.
For each objective, consider recording:
- The service or activity covered and the intended result
- The customer promise, business need, or other obligation behind it
- The accountable owner and the people who depend on the result
- How performance will be assessed and when a shortfall needs attention
- The approval date and circumstances that should prompt reconsideration
Use numbers when they make the outcome clearer. Some objectives need a defined condition instead, such as restricting a particular customer dataset to approved support personnel. Explain how the organization determines whether that condition holds.
Keep objectives connected to the work
Return to the backup reports for a moment. Backups contribute to recovery, along with restoration exercises, documented dependencies, and people who know what to do. To judge whether you can meet the objective, you need to understand how those pieces work together.
Walk through a realistic failure with your team. What could keep you from reaching the target? An encryption key stored only in the failed environment or an unavailable specialist may matter more than yesterday’s successful backup job.
Capture those concerns for your risk assessment and assign follow-up where needed. If you don’t have the resources to close a gap, bring that decision to management. Accepting a risk internally doesn’t change a customer agreement, so get appropriate advice before changing commitments.
Avoid importing another organization's objectives without checking the assumptions. A target can look precise while depending on staff coverage, supplier capabilities, or technology your organization does not have.
A bootstrapped five-person business with two founders
Picture yourself as one of two founders in a bootstrapped five-person software business. You handle engineering; your cofounder handles sales and operations. Three employees help deliver the product, and nobody has a separate risk-management job.
You can begin with a short document covering the service outcomes that matter most. Read the customer agreements together, then ask your three employees what tasks and dependencies support those outcomes. Give each objective an owner and a backup for absences.
Suppose you choose the illustrative recovery target above for your core application. During a walkthrough, an employee points out that customer files are backed up differently from the application database. You agree which records need to be recovered together and arrange a test using representative test data.
The test takes longer than expected. Now you have something useful to work with: a recorded result, a cause to investigate, and an improvement to assign. Keep the original target and result accurate. If you later revise the objective, record the reason and check the change against your customer commitments.
Keep the evidence as you go: approved objectives, the obligations you reviewed, owners, walkthrough notes, test results, and decisions about gaps. A small, consistently maintained set of records can explain the work clearly.
Vanta can help you keep the approved objectives and recovery-test record together as document evidence, including links to files you maintain elsewhere. You still need to evaluate the recovery result and decide what to do about it. Having the record easy to find makes that conversation easier.
At 100 people: reconcile service expectations
Now imagine you’re coordinating a 100-person company. Customer success wants faster responses, engineering is protecting reliability, and finance is watching infrastructure costs. Each team has a reasonable priority, but they may be working toward different outcomes.
Bring the service owners together before approving the objectives. For a customer reporting service, agree when reports need to be available, what makes a report complete, and how you’ll identify and correct an inaccurate result.
As you work through the reporting deadline, you discover that an upstream provider can’t reliably deliver the data in time. That gives management a concrete choice: reconsider the schedule, evaluate another supplier, or change the service design before making a new customer promise.
Carry that decision into each department’s plan, with clear owners. When you review performance, check the measurement too. A report showing on-time delivery will give you the wrong impression if failed jobs have been left out.
Evidence to keep: service objectives, approval records, the source of key commitments, dependency assessments, linked departmental actions, and reviews of performance and exceptions.
You could record the supplier-delivery gap in Vanta’s risk management workflow and organize the approved treatment work through its Action Tracker. That gives you a way to follow the related tasks and controls. Your service owner still needs to confirm that the remedy supports the reporting deadline.
At 1,000 people: make shared dependencies visible
At a fictional 1,000-person provider, you’re working across acquired businesses, regional operations, and different customer commitments. A single companywide objective can make that complexity disappear from the report while it remains very real for the teams delivering the service.
Use a common format so you can compare objectives, while allowing each service to state the outcome it needs. Ask service owners to identify critical dependencies and explain differences from the company’s general expectations. A central review can then catch inconsistencies affecting shared operations.
Suppose two services depend on the same identity platform. One promises round-the-clock access, while the other’s recovery plan assumes business-hours support. When you put the plans side by side, you can ask whether the shared platform and responder coverage can support both during an outage.
When management approves an expansion or acquisition, include objective alignment in the transition work. Track unresolved differences and the person responsible for addressing them. Keep service-level results visible so a healthy companywide average does not obscure a serious local shortfall.
Evidence to keep: approved service objectives, ownership records, dependency maps, documented exceptions, management decisions, and transition actions with completion evidence.
A Vanta risk snapshot can preserve the recorded risk scenarios at the time of your management review. Keep the approved objectives, assumptions, and decisions alongside it so a later reviewer can follow your reasoning. Multiple registers and advanced reporting depend on your subscription; choose capabilities that fit the access and features you have.
Keep the history across the Type 2 period
For a SOC 2 Type 2 examination, organize dated records so reviewers can trace the objectives in effect and the related work during the examination period. Keep previous versions when objectives change, together with the reason, approval, and effective date.
Connect each significant revision to the decisions it affected. A revised recovery target may require a new test, different supplier arrangements, or additional coverage. Retaining that connection is more useful than saving several nearly identical documents without context.
Revisit objectives when your service changes, you make a new commitment, or evidence shows an assumption was wrong. Set routine reviews around your risks and operating model. Headcount alone won’t tell you how formal or frequent they should be: a small provider handling highly sensitive data may need more rigorous work than a larger, simpler business. Your commitments, obligations, service criticality, and dependencies should drive the approach. Vanta can support the records and follow-up, while management remains responsible for the objectives and decisions.
Put one objective to work
Before your next risk assessment, choose one important service and ask its owner to explain the intended result, where it came from, and how you know whether you’re achieving it. If the answers differ across the team, that’s a useful place to start.
At Genius GRC, we help you connect service objectives with practical SOC 2 controls and supporting evidence. Talk with us about your SOC 2 needs and the approach that fits your team.
Continue through the SOC 2 Guide. The next article addresses CC3.2, Identifying and Analyzing Risks.
This article provides general guidance. Evaluate the examples with your advisers and auditor in the context of your examination scope and obligations.