On this page
Does a small agency need a SOC 2 report?
That depends on the services you provide and on what the buyer actually requires. Ask whether a SOC 2 report is mandatory, which of your services it must cover and which alternatives the reviewer will accept.
When the buyer explicitly requires one, nothing else stands in for it. A security tool or a record of your devices cannot replace a SOC 2 examination.
What is SOC 2?
What SOC 2 is.
An outside firm examines how a company that serves clients protects their systems and data, following the standards of the AICPA, the American body for accountants. The result is a signed report.
It is a report about one service over a stated scope, written by the examiner. You cannot get one by installing software, and it covers only what it names.
Why bigger clients ask
Over a third
of companies lost a deal because they lacked a security certification. Ask early what each client needs.
Source: A-LIGN Compliance Benchmark Report
30%
of the data leaks Verizon studied involved a third party, such as a supplier. So larger clients check their suppliers, agencies included.
Source: Verizon DBIR 2025
Ask what the requirement applies to.
A promising project reaches procurement, and someone asks for SOC 2. Before you buy anything, find out what the request is about: your agency, software you run for the client, or the cloud provider that hosts the client’s system. Those are three different things. A report that belongs to one of your suppliers does not cover the work your own team does.
Ask the reviewer to name the service, the scope, the report type and the deadline. Find out whether the requirement is mandatory, or whether there is a documented alternative review for a small supplier. Get that answer early, before your team spends weeks on a proposal built on the hope that procurement will make an exception.
turn a vague request into a decisionthree steps
- 1
Clarify what this buyer requires.
Is the report mandatory, or will the reviewer accept an alternative?
- 2
Scope the service and systems involved.
Which of your services, which report type, which period and which deadline.
- 3
Decide.
Meet the requirement, or agree an alternative the buyer accepts.
Does our cloud provider’s report count?
Your report, or your supplier’s.
A report belongs to the company that was examined. Your cloud provider’s report covers the provider’s service. It does not cover how your own team works, who on your side can reach client data or how you hand over access.
It can still help answer questions about hosting. Ask the reviewer whether it is enough for the part of the work they mean.
Understand what a SOC 2 report actually is.
SOC 2 is an outside examination of the controls at a company that provides a service, carried out under AICPA standards, and the report it produces. A Type 1 report looks at the controls on one date. A Type 2 report also looks at how they worked over a period. Agree the right scope with a qualified practitioner.
It is a report about your service. It is not a badge you install.
For an agency, the service under review can involve people, development processes, cloud systems and client information, as well as laptops. A record of your Macs covers only part of that picture. Never call a device score, a mapping to a framework or a finished questionnaire a SOC 2 certification. Use the real name and scope of the evidence you hold.
| Evidence | What it can answer | What it cannot say |
|---|---|---|
| A SOC 2 reportwritten by an outside examiner | How the controls of the examined service held, on a date or over a period, within the scope the report names. | Anything outside the scope it names. |
| A dated record of your Macskept by a tool such as Cybee | Which technical controls held on the assessed Macs, and since when. | How changes are approved, what contractors were trained on or what your policies say. It is not a SOC 2 examination. |
| A finished questionnairewritten by your team | Your answers to one client’s questions, as far as your evidence goes. | Anything the evidence behind each answer does not show. |
Type 1 or Type 2. What is the difference?
Type 1 and Type 2.
A Type 1 report describes your controls as they stood on one date. A Type 2 report also tests whether they kept working over a period, so the records for that period have to exist first.
Ask the reviewer which type they need before you talk to anyone about an examination.
Provider guidance: AICPA: System and Organization Controls services
Prepare a useful answer while the requirement is clarified.
Put together a small evidence pack for the work you are proposing. Include the devices involved, how access is given and taken away, how the relevant accounts are protected, your backups, training and who handles an incident. Mark what you do not know yet and what is missing. Say which people and systems each record covers, instead of claiming the whole agency is secure.
An example: the reviewer asks whether everyone who handles their project uses a protected device. A dated record for the assessed Macs helps answer that device question. It does not show how changes to the live system are approved, or whether every contractor finished their training. Send those questions to the person who owns that part of the work.
evidence pack for one proposal26.09.2026
- Devices on the project26.09.2026Ready
- Access given and removedAnaReady
- Account sign in protectionLucaReady
- Backups and a restore testLucaOpen
- TrainingAnaOpen
- Who handles an incidentAnaReady
Two items open, each with an owner. Nothing in this pack is a SOC 2 report.
Keep the evidence current, not collected once a year.
Many small teams treat security evidence as a yearly chore. The week before a review, someone screenshots the settings and files them in a folder. The folder is accurate for exactly one afternoon.
Say a five person agency takes its screenshots in March. In June a laptop is replaced and the new one never gets disk encryption. Nobody notices until the next March, and a careful reviewer who asks since when the encryption has been on gets a shrug. A record built from checks that keep running answers that question, because every fact carries its own date.
On the Macs, that is what Cybee does. Each Mac audits itself three minutes after it joins and then every 12 hours, and a setting that drifted is put back and recorded. The record shows what holds today and since when. It covers the technical controls on the assessed Macs only, so accounts, backups and people need records of their own.
| The question | A folder made once a year | Checks that keep running |
|---|---|---|
| What does it show? | How things stood on the day of the screenshots. | How things stood on each day since monitoring began. |
| A laptop changes in June | The folder does not know until someone redoes it. | The next check sees it, and the record shows the date. |
Cybee reports how the settings on your Macs line up with ten frameworks, among them SOC 2, ISO 27001, HIPAA, PCI DSS and NIST CSF. It maps technical controls on Macs only. The table shows what that gives you for three names a client may mention, and what it leaves with you.
| Name a client uses | What a Mac record can show | What stays with you |
|---|---|---|
| SOC 2one of the ten | Which device controls held on the assessed Macs, such as disk encryption and screen lock, and since when. | The examination, your policies, how changes are approved, your people and your cloud systems. |
| HIPAAthe US health privacy law, its Security Rule is one of the ten | The technical controls on the Macs that handle patient data, with dates. | Your written risk assessment, who may open patient records in other systems and every policy and contract around them. |
| GDPRthe EU data protection law, not one of the ten | One security measure the law names as an example: encryption, shown as disk encryption on the Macs listed. | Almost everything else the law asks: why you hold personal data, who you share it with, how you answer a deletion request. |
GDPR is a law, not a list of controls. Its Article 32 asks for security measures that fit the risk and names encryption as one example. A Mac record supports that one part of the answer. It does not meet GDPR or HIPAA for you, so where a client names one, ask which of its requirements they mean.
What is a framework?
A framework.
A framework is a published list of controls, the things an organisation should do and be able to show. SOC 2 and ISO 27001 are such lists. A law like GDPR is something else: it sets duties, and the lists help you meet them.
Mapping means matching one thing you can show, such as disk encryption on a Mac, to the line of a list that asks for it.
Make the decision against your real sales pipeline.
If several serious prospects require the report, talk to a qualified provider about the examination, the preparation and what you would have to keep doing afterwards. Ask what your team must do, which records need to build up over time and how the scope changes the engagement. Do not treat a platform subscription as the whole cost, or as a promise that every buyer will accept the result.
If one prospect is asking, and your service touches little of their systems, an alternative review may be worth discussing. The buyer decides whether it is acceptable. Keep the conversation honest. It can end three ways.
-
several require it
Meet it.
Plan the examination with a qualified provider, and start keeping the records it needs.
-
one buyer asks
Agree an alternative.
Your work touches little of their systems. Propose another review, and if the buyer accepts it, get that in writing.
-
mandatory, out of reach
Not this one, yet.
This opportunity may not fit how your agency works today. Say so early.
Make today’s security work useful either way.
Protect your work devices, review who has access, keep software current and write down the decisions your team makes. That helps the business whether an outside examination comes next month or next year. Give each task an owner and keep the records current. A folder built once for a sales call goes stale as people and systems change.
Cybee covers the Mac side: protection, the 118 checks, safer settings kept on and dated evidence. Its list of AI tools and their connections helps explain the tools around the work. Accounts and training each need their own record. Use every record within the scope it states. The aim is to walk into a bigger client conversation knowing what you can show, what is still open and what the buyer actually requires.
What exactly is a Trust Passport?
The Trust Passport.
The Trust Passport is a dated record of how your Macs are protected. Your client or insurer opens it through one link and sees what holds, since when, and what Cybee could not see. It is not a certification or an audit, and it does not answer for your policies, your people or your cloud. It says so on the page.
So it can support the device answers in a review. It does not replace a SOC 2 report.
Cybee and Vanta: what each is built for See the plans Answer the renewal questions about your Macs What the Trust Passport shows
Five steps to start this week.
You do not need a project plan. You need one request, a short list and a habit.
start with one requestfive steps
- 1
Pick the one request in front of you.
One client, one service. Ask what it covers before you collect anything.
- 2
List where each proof lives.
Devices, accounts, training, backups, incidents. One name next to each.
- 3
Switch to checks that keep running.
Replace each screenshot with a check that repeats and keeps its date. For the Macs, that is the free protection and the 118 checks.
- 4
Fix the first gap and write down why.
One gap closed, one line on who decided. Leave the rest visible instead of hiding it.
- 5
Look again every month.
Put it in the calendar. Open the record, read what changed and update the owners.
What to remember.
- Ask whether the buyer requires a report or accepts another review.
- A tool or a record of your devices is not a SOC 2 examination.
- Base your next step on the real scope and deadline of an actual sales opportunity.
- Evidence you keep current beats a folder made once. Date every fact and name its owner.
Sources and further reading.
- AICPA: System and Organization Controls services
- NCSC (United Kingdom): security guidance for small organisations
- The EU’s official law site: Regulation (EU) 2016/679, Article 32 on the security of processing
- US Department of Health and Human Services: summary of the HIPAA Security Rule
Product scope and provider guidance can change. Check the linked source for your own setup. Stuck on a word? Look it up in the security glossary.
Put it to work.
See a client’s security questions answered from dated facts, and the questions your team still owns.


