SOC 2 Type 1 vs Type 2 Which Report Do You Need?
SOC 2 Type 1 vs Type 2 comes down to one date versus a period of months. A SOC 2 Type 1 report says your controls were suitably designed and in place on one date. A SOC 2 Type 2 report says those controls kept working across a period of months. It also shows the auditor's tests and what they found. Both come from an independent licensed CPA firm. Petronella Technology Group, Inc. is not a CPA firm and does not issue SOC 2 reports. We handle the readiness work that decides what the report will say. That starts with scoping and a gap assessment. It continues through remediation and evidence, and we stay with you during the examination.
SOC 2 Type 1 vs Type 2: What Is the Difference?
A SOC 2 Type 1 report gives an auditor's opinion on whether your controls were suitably designed and implemented as of a specified date. A SOC 2 Type 2 report covers the same ground and adds an opinion on whether those controls operated effectively throughout a specified period. Type 1 answers "is the system built correctly today?" Type 2 answers "did it keep working, and what did the auditor find when testing it?"
Key Takeaways
- Type 1 is a point in time. The opinion covers the fairness of management's description of the system and the suitability of control design as of one date. Operating effectiveness over time is not tested.
- Type 2 is a period of time. It includes everything in a Type 1, plus the auditor's tests of controls across the period and the results of those tests, including any exceptions.
- A Type 1 is not a prerequisite. You may go straight to a Type 2 if your controls are already running and your customers ask for it.
- The AICPA sets no minimum period. In practice, review periods commonly run three to twelve months, and the evidence has to exist for the whole window.
- Type I and Type 1 are the same thing. The AICPA uses Arabic numerals; many contracts still use Roman numerals.
- Only a CPA firm issues the report. Petronella Technology Group prepares you for it, with policy and evidence work running in the Compliance Armor® platform.
One point of vocabulary. People say "SOC 2 certified" all the time, and everyone knows what they mean. Technically, SOC 2 is an attestation report, not a certification: an independent licensed CPA firm performs an examination under the AICPA's attestation standards (SSAE 18, specifically AT-C sections 105 and 205). The firm then issues a report containing its opinion. What you hand a customer is the report, and its type determines how much that customer can conclude from it.
Both types are measured against the same AICPA Trust Services Criteria (TSP section 100, the 2017 criteria with revised points of focus issued in 2022). Security is always in scope and is often called the common criteria, CC1 through CC9. Availability, Processing Integrity, Confidentiality, and Privacy are added when they match what you promise customers. Category selection works the same way for both types, so the type decision is not about what gets examined. It is about how long the auditor looks and what evidence you must produce. If you are still deciding which SOC report applies to you, start with our overview of SOC compliance.
SOC 2 Type 1 vs Type 2 at a Glance
The two reports share an issuer and a set of criteria. Their structure is the same too. They differ in the time they cover and in the testing behind them. That changes what a reader can infer.
| Factor | SOC 2 Type 1 | SOC 2 Type 2 |
|---|---|---|
| What the auditor concludes | The description of the system is fairly presented, and controls are suitably designed and implemented to meet the criteria | All of the Type 1 conclusions, plus: the controls operated effectively |
| Time dimension | As of a specified date | Throughout a specified period |
| Testing performed | Evaluation of design and confirmation that controls are in place; no testing of operating effectiveness over time | Tests of controls across the period, typically by sampling from complete populations of activity |
| What Section 4 contains | The criteria and the related controls | The criteria, the related controls, the auditor's tests, and the results of those tests |
| Evidence you must produce | Policies, configurations, and an example showing each control exists | Records proving each control ran every time it was supposed to during the period |
| Typical use | First report for a new control environment; interim proof while a Type 2 period runs | Ongoing annual report for customers with formal vendor risk programs |
| What buyers infer | The organization has built a reasonable control system | The organization runs that control system consistently |
| When exceptions appear | Design gaps surface before the report date and can affect the opinion; there are no test results to list | Deviations found in testing are listed in the report next to the control they affect |
| What happens next year | Usually followed by a Type 2 instead of another Type 1 | Usually renewed with a new period that begins where the last one ended |
| Who issues it | An independent licensed CPA firm | An independent licensed CPA firm |
Inside a SOC 2 Type 1 Report: Design on One Date
A Type 1 is an opinion about design on a single date. It is a real examination by a real CPA firm, with a narrower question.
In a Type 1 examination, the auditor's opinion addresses two things as of a date you and the CPA firm agree on. First, whether management's description of the system is fairly presented: does the written description of your services and infrastructure match what actually exists? The same question applies to the software it names. People and procedures are checked the same way, as is the data. Second, whether the controls in that description are suitably designed and implemented to meet the applicable Trust Services Criteria. "Suitably designed" means that if the control operates as described, it would meet the criterion. "Implemented" means the control has actually been put in place, not just written down.
The auditor reaches that opinion by reading your policies and interviewing the people who own each control. The auditor also inspects system configurations and walks through each process. For access control, that might be the written policy plus a view of the identity provider showing that multi-factor authentication is enforced. One completed access request then shows the approval step. The pattern is consistent. The auditor sees the policy and the configuration, then one example of the control in action. What the auditor does not do is test whether the control worked every time over a span of months.
Where a Type 1 Is Strong
- It can be issued without waiting for a review period to elapse, so it fits a deal or a board deadline that cannot wait.
- It forces the hard foundational work: defining the system boundary, writing the description, and mapping controls to criteria.
- It gets an independent CPA firm's eyes on your control design before you commit to months of operating it.
Where a Type 1 Is Limited
- It says nothing about whether controls kept operating after the report date.
- It contains no tests of controls and no results, so a reviewer has less to evaluate.
- Customers with formal vendor risk programs often accept it only as a temporary measure.
Inside a SOC 2 Type 2 Report: Controls Tested Over Time
A Type 2 includes everything in a Type 1 and then asks the harder question: did the controls actually operate, every time, for the whole period?
The opinion in a Type 2 report covers the fairness of the description and the suitability of control design. It adds the operating effectiveness of the controls throughout a specified period. That last element changes the nature of the work. The auditor is no longer satisfied by one example. For each control, the auditor asks for the complete population of times the control should have operated during the period. A sample is drawn from that population, and each selected item is tested.
In concrete terms, expect requests like these, each one covering the entire period:
Access Reviews
Every periodic user access review that fell inside the period. Each one names the reviewer and the date along with the accounts examined. It also proves that flagged access was actually removed.
Change Tickets
A full list of production changes. The auditor picks a sample and checks that each was tested and peer reviewed. Each must also show approval before deployment.
Onboarding and Offboarding Records
Lists of everyone hired and everyone who left. New hires are sampled for background checks and training completion. Departures are sampled for timely removal of access.
Vulnerability Scans
Scan results at the frequency your policy states, plus tickets showing that findings were tracked and remediated within your own stated timeframes.
Backup and Recovery Tests
Backup job results across the period, plus the record of each restore test your policy calls for. Each record shows what was restored and whether it worked.
Incident Records and Vendor Reviews
The log of security incidents with evidence that each followed your response procedure, and the reviews you performed on critical vendors during the period.
When a sampled item does not show what the control says should have happened, the auditor records an exception, also called a deviation. A departed employee whose account stayed active past your stated removal window is an exception. The report lists each one next to the control it relates to, where every customer who reads the report will see it.
That visibility is why a Type 2 carries more weight. A reader does not have to trust that your procedures are followed; they can see what an independent CPA firm tested and what it found. Our SOC 2 Type II readiness services are built around keeping controls operating for the full period, the SOC 2 controls list shows what an examination typically covers, and our SOC 2 Type 2 guide gives a longer walkthrough.
Where the Two Types Actually Differ, Section by Section
Open a Type 1 and a Type 2 next to each other and most of the pages look alike. The differences sit in two places: the wording of the opinion and the contents of Section 4.
| Section | What It Contains | Type 1 vs Type 2 |
|---|---|---|
| Section 1: Independent service auditor's report | The CPA firm's opinion, the scope of the examination, and the responsibilities of each party | Type 1 opines as of a date on description and design. Type 2 opines for a period and adds operating effectiveness. |
| Section 2: Management's assertion | Management's own written statement about the description and the controls | Mirrors the opinion: a date for Type 1, a period plus operating effectiveness for Type 2. |
| Section 3: Description of the system | Services, infrastructure, software, people, procedures, data, boundaries, subservice organizations, and user entity responsibilities | Largely the same content. Type 2 describes the system throughout the period, including significant changes. |
| Section 4: Criteria, controls, tests, and results | Each applicable Trust Services criterion with the controls that address it | Type 1 stops at criteria and controls. Type 2 adds the auditor's tests and the results, including exceptions. |
| Section 5: Other information provided by management | Optional material such as responses to exceptions or future plans | Optional in both. Not covered by the auditor's opinion in either. |
The opinion. Section 1 ends in one of four opinion types. An unqualified opinion is the clean one. A qualified opinion means one or more criteria were not met, and the auditor explains which. An adverse opinion and a disclaimer of opinion are the most serious outcomes; a disclaimer means the auditor did not express an opinion at all. One point surprises many first-time readers: a Type 2 report can list exceptions and still carry an unqualified opinion.
How a buyer's reviewer reads it. A vendor risk analyst usually starts with the type and the date or period. Next comes the opinion in Section 1. Then the analyst confirms that the system described in Section 3 is the product their company is buying. With a Type 2, the reviewer then goes to Section 4 to look for exceptions. With a Type 1 there are no test results to review, which is why the reviewer's confidence stops at design.
Complementary user entity controls. Both types include complementary user entity controls, or CUECs: the things your customer must do for your controls to work as described, such as managing their own user accounts in your product. A careful reviewer reads the list as a to-do list for their own organization, so keep yours accurate and short.
Subservice organizations. Most services run on someone else's infrastructure, such as a cloud hosting provider. Both report types handle these subservice organizations by one of two methods. Under the carve-out method, the provider's controls are excluded from your description and from the auditor's testing, and your own monitoring of that provider is in scope. Under the inclusive method, the provider's relevant controls are included in your description and examined along with yours.
Finally, SOC 2 reports of either type are restricted-use documents. They are normally shared with customers and prospects under a non-disclosure agreement. A SOC 3 report is the general-use summary that can be shared more freely.
The Review Period: How Long, and When It Starts
The period is the single biggest planning decision in a Type 2. It goes by several names. Review period and observation period are common. Some firms say audit period or examination period. One rule cannot be bent: the evidence has to exist.
How long. The AICPA does not fix a minimum length for a SOC 2 Type 2 period; it is agreed between you and your CPA firm. In practice, review periods commonly run from three to twelve months, and a common pattern is a shorter first period followed by twelve-month periods each year after that. These are conventions, not rules. If a key customer's contract or vendor policy names a minimum period, that matters more than any convention, so ask before you commit.
When it starts. The first day of the period is the first day your controls are being judged. If the period opens on the first of the month, multi-factor authentication needs to be enforced on that day. The change approval workflow needs to be mandatory by then. Logging needs to be on and retained. Controls must be operating before day one. A control that starts late gets no partial credit; it shows up as a control that was not operating for part of the period.
Why it cannot be backfilled. A Type 2 tests what happened, and what happened cannot be created afterward. If your policy calls for quarterly access reviews and one quarter's review was never performed, a review done later is evidence of the later date only. The skipped review becomes an exception, and it stays in that period's report permanently. Fixing the process helps next period. It does not rewrite this one.
What this means for planning. The sensible order is: find the gaps, fix them, confirm the controls are producing evidence, and only then open the period. Opening it early to save calendar time is a common route to a first Type 2 report with avoidable exceptions. That is why a SOC 2 readiness assessment comes first: it finds problems while they can still be fixed privately. Check retention as well. The auditor's fieldwork happens after the period ends, so every system holding evidence must keep it long enough, a commitment that belongs in your data retention policy.
Find the Gaps Before the Period Opens
Tell us which customers are asking and where your controls stand today. We will map out which report type fits and what has to be true before day one of a review period. The report itself comes from your independent CPA firm; our job is to make sure you are ready for it.
Do You Need a Type 1 Before a Type 2?
No. A Type 1 is not a prerequisite for a Type 2. An organization may go straight to a Type 2 examination.
When a Type 1 First Makes Sense
- A deal needs proof now. A customer will not sign, or will not go live, without an independent report, and a review period cannot finish in time. A Type 1 gives them something examined to rely on in the interim.
- The control environment is brand new. If most controls were introduced recently, there is no operating history to test. A Type 1 confirms the design is sound before you invest months operating it.
- The board or investors want a checkpoint. A Type 1 is a concrete, externally verified milestone that shows the program is real and on track.
When to Go Straight to Type 2
- Controls are already running. If access reviews, change approvals, and monitoring have been operating with records, the evidence for a period may already be accumulating.
- Buyers ask for Type 2 by name. If the contracts and questionnaires in front of you specify Type 2, a Type 1 may not move those deals forward.
- You want one examination, not two. A Type 1 followed by a Type 2 means paying a CPA firm for two engagements. If nothing forces the first, skipping it is reasonable.
The table below turns that into specific recommendations.
| Your Situation | Recommended Path | Why |
|---|---|---|
| A signed deal is waiting on a report and your controls are newly built | Type 1 now, with the Type 2 period opening right after | The Type 1 unblocks the deal; starting the period immediately shows the customer the Type 2 is already in motion |
| Controls have been operating with records for some time | Straight to Type 2 | You already have what a Type 1 would establish, and a Type 2 is what customers ultimately want |
| Customer contracts name "SOC 2 Type 2" or "Type II" specifically | Straight to Type 2, with interim documentation for the customer | A Type 1 does not satisfy contract language that names the other type |
| The board wants external validation this fiscal year | Type 1 as the checkpoint, Type 2 the following cycle | A Type 1 is achievable inside a fixed calendar and gives the board an independent opinion |
Whichever path you choose, the readiness work is nearly identical. Both need scoping and a system description. Both need policies and control design. Founders may find our startup SOC 2 program useful, and regulated software companies can review the considerations for fintech and healthtech SaaS.
Which Report Will Your Customers Accept?
The right report is the one the person asking for it will accept. Find out what that is before you choose, not after.
Enterprise procurement. Larger buyers run vendor onboarding through a formal third-party risk management program. The analyst works from a written standard that says what evidence is acceptable for a vendor at your risk tier, and that standard frequently names the report type. If it calls for a Type 2 and you supply a Type 1, the analyst may not have the authority to accept it. Ask for the standard early.
Security questionnaires. Many questionnaires ask whether you have a current SOC 2 report. They also ask which type it is and what period it covers. A Type 2 often lets you answer many of the remaining questions by reference to the report. A Type 1 helps less, because questions about whether you actually perform reviews and training on schedule are operating-effectiveness questions. Questionnaires are also expanding to cover artificial intelligence features; see our guide to the AI vendor security questionnaire.
Contracts. A master services agreement or security addendum may obligate you to maintain a SOC 2 report and deliver it annually. Read the exact words. If the contract names a Type II report or a minimum period, a Type 1 does not meet it. If it says only "a SOC 2 report," you have more room, but expect the customer's security team to have a view.
Using a Type 1 as an interim. When a customer wants a Type 2 and you do not have one yet, a workable package is often a Type 1 report plus a commitment letter from your management stating that a Type 2 examination is under way and giving the target period end date. Customers who cannot accept a Type 1 on its own will often accept it with that commitment.
Currency of the report. Customers generally treat a report as current for about twelve months after the end of its period. If the period ended some months ago and the next report is not out yet, they may ask for a SOC 2 bridge letter, covered below.
Evidence: What Changes Between Type 1 and Type 2
The controls are the same in both reports. What changes is the proof. A Type 1 asks "show me it exists." A Type 2 asks "show me every time it happened."
| Control Area | Type 1 Evidence (Design, One Date) | Type 2 Evidence (Operation, Whole Period) |
|---|---|---|
| Access provisioning | Access control policy; role definitions; one approved access request | List of all access granted in the period; sampled requests each showing approval before access was given |
| Access reviews | Documented review procedure and schedule; the most recent completed review | Every scheduled review in the period, with reviewer sign-off and proof that flagged access was removed |
| Offboarding | Termination procedure with a stated timeframe for removing access; one completed example | List of all departures in the period; sampled records showing access removed within the stated timeframe |
| Change management | Change procedure; repository and deployment settings that enforce review; one change record | Full population of production changes; sampled changes each showing testing, review, and approval |
| Vulnerability management | Scanning tool configuration; remediation timeframes in policy; a recent scan | Scans at the stated frequency for the whole period; tickets showing findings fixed within policy timeframes |
| Penetration testing | Policy stating how often testing occurs; the most recent test report, if testing is one of your controls | The test performed during the period, plus tracked remediation of what it found |
| Backups and recovery tests | Backup configuration and schedule; documented recovery procedure | Backup job results across the period; record of each restore test the policy requires and its outcome |
| Incident response | Incident response plan; defined roles; the tracking tool | Log of incidents in the period; sampled incidents showing the plan was followed through to closure |
| Security awareness training | Training policy; course content; assignment configuration | Completion records for sampled new hires and for the workforce at the required interval |
| Vendor management | Vendor management policy; inventory of critical vendors; the review procedure | Reviews actually performed on critical vendors in the period, including review of their own assurance reports |
| Risk assessment | Risk assessment methodology; the current risk register | The risk assessment performed in the period, with evidence that management reviewed it and tracked treatment |
Policies set the bar you are tested against. The auditor tests your controls as you describe them. If your policy says access is removed within one business day of termination, each sampled departure is held to that. An acceptable use policy that every employee acknowledges, a data classification policy that defines what is confidential, and a BYOD policy for personal devices each need to describe what you actually do. A policy that promises more than the organization delivers is a ready-made exception.
People processes generate the most samples. Hiring and departures happen all period long. A consistent employee onboarding checklist and employee offboarding checklist, turn those samples into easy passes when they are followed the same way every time and saved as a record. The same goes for security awareness training: the Type 2 question is whether each sampled person completed it on time.
Technical controls need a trail, not just a tool. Owning a scanner or a backup product satisfies design. Operating effectiveness needs the output. Keep scan results and remediation tickets. Where testing is one of your stated controls, keep the penetration testing report with tracked fixes. Your backup and disaster recovery program should leave restore test records. Monitoring such as managed XDR should leave alert handling records. An accurate IT asset inventory shows that those controls cover every system in scope.
Governance controls run on a calendar. Risk assessments and vendor reviews are typically annual or periodic. Policy reviews are the same. They are easy to design and easy to forget. A written incident response plan covers design; a record that incidents were handled according to it covers operation. A documented cybersecurity risk assessment covers the risk criteria when it is performed within the period and reviewed by management.
Common Mistakes That Turn Into Type 2 Exceptions
Exceptions rarely come from sophisticated failures. They come from ordinary lapses in routine work, recorded permanently because they happened inside the period.
1. Opening the Period Before Controls Are Running
The period starts on a date chosen for sales reasons while remediation is still in progress. Controls that go live partway through are tested against the whole period and come up short for the early part.
2. Skipping a Periodic Review
A quarterly access review is missed during a busy stretch. It cannot be performed retroactively, so the gap is reported as a deviation for that period no matter how good the other reviews were.
3. Slow Offboarding
HR processes a departure but nobody tells IT, or the main account is disabled while access to a secondary application remains. The sampled record shows access outliving the timeframe your own policy states.
4. Changes Without a Recorded Approval
An urgent fix is pushed straight to production. The fix may have been correct, but without a documented emergency change path and an after-the-fact review, the sampled change has no evidence of approval.
5. Policies That Promise More Than You Do
A template policy says logs are reviewed daily or scans run weekly, and practice is less frequent. The auditor tests against the written commitment, so an ambitious sentence becomes a string of exceptions.
6. Findings With No Follow-Through
Vulnerability scans run on schedule, but high-severity findings sit open past the remediation timeframe in policy, with no ticket and no documented risk acceptance explaining why.
7. Evidence That Cannot Be Reproduced
The control operated, but the proof is gone: logs aged out, a ticket was deleted, a screenshot has no date or system name. From the auditor's position, a control without evidence did not demonstrably operate.
8. Scope Drift During the Period
A new production system or critical vendor is added mid-period. Nobody brings it under access reviews or scanning. Backups and vendor review get skipped too. It is in scope the moment it handles customer data.
Every item on this list has the same root cause: a control that depends on someone remembering. The durable fix is to automate the control where possible. Any control that cannot be automated gets a schedule and a named owner. Monitor it either way, so a missed task is noticed within days instead of by the auditor months later. Good IT documentation helps too: when the usual owner is out, someone else can run the control the same way.
After the First Report: Renewal, Gaps, and Bridge Letters
A SOC 2 report is not a one-time project. Customers expect a current one every year.
The annual cadence. Once an organization has a Type 2, the usual practice is an annual examination covering a twelve-month period, which keeps a current report available at all times.
Continuous periods. The cleanest arrangement is for each new period to begin the day after the previous one ended, so customers see unbroken coverage. If you let time pass between periods, a reader comparing the two reports will see the uncovered months and may ask what happened during them.
Bridge letters. A Type 2 report cannot be issued on the last day of its period, because the auditor still has to finish testing and write it. So there is always a stretch when your latest report covers a period that has ended and the next report does not exist yet. The standard answer is a bridge letter, also called a gap letter: a letter from your management, not from the auditor, covering the time since the period ended. It is meant for a short interval, not as a stand-in for an overdue examination. Our page on the bridge letter explains when customers ask for one.
What changes in year two. The second period is easier in one way and harder in another. Easier, because the description and policies already exist, as does the control set. Harder, because a longer period gives each control more chances to slip. Readers will also compare the new report with the old one. An exception that appears two years in a row tells a customer the underlying process was not fixed, so remediate last year's exceptions at the start of the next period, not the end.
How Either Report Type Relates to ISO 27001, HIPAA and CMMC
The controls you operate for SOC 2 do not serve SOC 2 alone. The same disciplines appear, in different words, in nearly every security framework a growing company meets.
The Security category's common criteria run from CC1 through CC9. They start with the control environment and communication. Risk assessment and the monitoring of controls come next, followed by control activities. The rest cover logical and physical access and system operations. Change management and risk mitigation close out the set. Those are families of practice, not SOC 2 inventions. Access control and change control show up at the family level in other frameworks. So do incident response and vendor oversight. You will find them in ISO 27001 and in the safeguards expected under HIPAA. Organizations that handle payment card data meet them in PCI DSS. Defense contractors meet them in CMMC and the NIST SP 800-171 requirements beneath it. Covered financial institutions meet them in the FTC Safeguards Rule.
This matters for the type decision in a practical way. The evidence habits a Type 2 demands make any other assessment easier. Think of scheduled reviews with sign-off and complete populations backed by retained records. Each framework still has its own requirements and its own assessors. Each also produces its own form of result. A SOC 2 report does not substitute for any of them, and none of them substitutes for a SOC 2 report. What carries across is the control set and the evidence it produces.
Our compliance services hub lists the frameworks we support. And if your real question is whether customers need a SOC 1 instead, because your service affects their financial reporting, see SOC 1 vs SOC 2.
Three Ways to Get Ready: An Honest Comparison
In every case the examination and the report come from an independent CPA firm. The choice is how you get ready for it. Each approach suits some organizations and not others.
| Consideration | Do It Yourself | Compliance-Automation Software Alone | Petronella Technology Group Readiness Plus Your CPA Firm |
|---|---|---|---|
| Who does the work | Your own staff, usually on top of their existing jobs | Your own staff, guided by the tool's task lists | Shared: we lead readiness and remediation, your staff own the day-to-day controls |
| Policies | Written from scratch or adapted from templates | Templates supplied; tailoring is up to you | Drafted to match what you actually do, then maintained in ComplianceArmor |
| Technical remediation | Done by your engineers and IT staff | Tool flags gaps; fixing them is still your work | Performed or directed by our security and IT team |
| Evidence collection | Manual: folders, screenshots, spreadsheets | Automated for connected systems; manual for the rest | Organized in ComplianceArmor, with people chasing the manual items |
| Security operations and testing | Sourced and managed separately | Not included; sourced separately | Available from the same team: monitoring, penetration testing, risk assessment |
| Main limitation | Slow if nobody has done it before; easy to mis-scope | A tool cannot decide scope, fix systems, or perform reviews for you | An outside engagement to budget for and coordinate |
| Best fit | Teams with prior SOC 2 experience and time to spare | Engineering-heavy teams with a security owner on staff | Teams without a dedicated security or compliance function |
None of these is wrong. The caution about software alone is that automation collects evidence from connected systems but cannot decide scope. It cannot write policies that match reality. Nor can it perform a thoughtful access review or fix a misconfigured system. The caution about an outside readiness partner is that you still own your controls: the people who approve changes and remove access are yours. Organizations that want the program run on an ongoing basis can look at compliance as a service.
How Petronella Technology Group Prepares You for Either Type
To be plain about roles: Petronella Technology Group is not a CPA firm and does not issue SOC 2 reports. The report comes from the independent CPA firm you engage. We do the readiness work, so that what the CPA firm examines is in order.
Scope and Category Selection
Readiness Assessment
Remediation
Evidence Engine in ComplianceArmor
Period Monitoring
Examination Support
1. Scope and category selection. We start with what your customers are asking for and what you have promised them. That sets the system boundary, the Trust Services categories beyond Security, the subservice organizations involved, and whether a Type 1, a Type 2, or both makes sense.
2. Readiness assessment. We compare your current controls with the applicable criteria and document every gap, separating design gaps (the control does not exist) from evidence gaps (the control exists but leaves no record). The result is a prioritized list of what has to be true before an examination date or day one of a period.
3. Remediation. Closing gaps often means technical work: enforcing multi-factor authentication, tightening access, retaining logs, deploying endpoint protection, testing a restore. Our team does that work or directs yours through it. Where a control calls for independent testing or ongoing monitoring, we can provide it through our penetration testing practice and SOC as a service.
4. Evidence engine in ComplianceArmor. Policies, control mappings, and evidence are organized in ComplianceArmor, our compliance documentation platform. Its SOC 2 software module ties each control to the criteria it addresses and the evidence that supports it, so the auditor's request list is answered from one place instead of scattered inboxes and shared drives.
5. Period monitoring. For a Type 2, we check in on a schedule during the period to confirm that reviews were performed and departures were processed. We also confirm that scans ran and that evidence was captured. A missed task found by the auditor is an exception.
6. Examination support. When the CPA firm begins its work, we help you respond. We assemble populations and answer evidence requests. We also prepare control owners for walkthroughs. The CPA firm is independent. Its testing and its conclusions are its own.
The practice is led by Craig Petronella, CMMC Registered Practitioner and NC Licensed Digital Forensics Examiner (License# 604180-DFE), who founded the company in April 2002. Petronella Technology Group is a CyberAB Registered Provider Organization (RPO #1449) and has held a BBB A+ rating since 2003. Craig is the author of 15 books on cybersecurity and compliance. As Craig Petronella details in How Hackers Can Crush Your Business, cybercriminals exploit the vulnerabilities that small and midsize businesses leave open, which is the practical reason to operate the controls behind a SOC 2 report well and not just document them.
We work with organizations in Durham, Cary, and across the Triangle from our Raleigh office, and with clients elsewhere in the country remotely. The engagement can take the form of advisory SOC 2 consulting for a team running its own program, our full SOC 2 compliance services, or an ongoing virtual CISO relationship in which a security leader owns the program with you year after year. In all three, the report itself comes from an independent CPA firm.
"His knowledge of systems sets him apart from anybody else."
Nicholas Smith, Southeastern Managing Director, Winmark CapitalPetronella Technology Group is rated 4.7 across 92 verified TrustIndex reviews and 5.0 across 15 Google reviews.
Type 1, Type 2, or Both? Get a Straight Answer
Send us the exact wording from the contract or questionnaire that is asking for a SOC 2 report. We will tell you which type it calls for, whether an interim Type 1 is likely to help, and what readiness would involve for your environment.
Explore Related SOC 2 Resources
SOC 2 Compliance Checklist
The practical steps from first scoping conversation to examination, in order.
Learn moreSOC 2 Controls List
The control areas an examination covers and how they map to the Trust Services Criteria.
Learn moreSOC 1 vs SOC 2
How to tell whether customers need assurance over financial reporting or over security.
Learn moreSOC 2 for Startups
Sequencing a first report when the team is small and the first enterprise deal is close.
Learn moreSOC 2 for SaaS Companies
What SOC 2 scope and evidence look like for a cloud-hosted software product.
Learn moreCybersecurity for SaaS
The security operations that sit underneath a SOC 2 program and keep it honest.
Learn moreSources
- AICPA: SOC suite of services: how SOC 1, SOC 2 and SOC 3 reports differ and who uses each.
- AICPA: 2017 Trust Services Criteria (with revised points of focus, 2022): the criteria every SOC 2 examination is evaluated against.
- AICPA: Description Criteria for a SOC 2 report: what management's system description must contain.
- AICPA: Illustrative SOC 2 report with description and assertion: a sample report showing the auditor's opinion, tests of controls and results.
- AICPA: Illustrative management representation letter, SOC 2 Type 1: the representations management makes for a point-in-time examination.
Craig Petronella
Craig Petronella founded Petronella Technology Group, Inc. in 2002. He is a CMMC Registered Practitioner (CMMC-RP), Cisco CCNA, Certified Wireless Network Expert (CWNE) and North Carolina Digital Forensic Examiner (License 604180-DFE), and the author of 16 books. He leads Petronella Technology Group's compliance practice, which prepares service organizations for SOC 2 examinations performed by independent CPA firms.
Questions We Hear About Type 1 and Type 2 Reports
What is the difference between SOC 2 Type 1 and Type 2?
Do I need a SOC 2 Type 1 before a Type 2?
How long is the SOC 2 Type 2 observation period?
Is SOC 2 Type 2 better than Type 1?
Is SOC 2 Type I the same as SOC 2 Type 1?
Can a SOC 2 Type 2 report have exceptions?
Who issues a SOC 2 report?
How long is a SOC 2 report valid?
Choose the Right Type, Then Earn a Clean Report
Petronella Technology Group will help you pick the report your customers will accept and get the evidence in order before a period opens. Your independent CPA firm issues the report; we make sure you are ready when its examination begins.
Written by Craig Petronella, CMMC Registered Practitioner and NC Licensed Digital Forensics Examiner (License 604180-DFE), founder of Petronella Technology Group, Inc. in Raleigh, North Carolina.
Last Updated: November 17, 2026 | Petronella Technology Group, Inc. | 5540 Centerview Dr., Suite 200, Raleigh, NC 27606 | 919-348-4912 | info@petronellatech.com