SOC 2 compliance and penetration testing: what a test record can put in front of your service auditor
SOC 2 is an examination of controls at a service organisation, performed by a licensed, independent CPA under the AICPA's attestation standards.
If a customer has asked your business for a SOC 2 report, this guide sets out what the AICPA publishes openly about the examination, its report types and its criteria, where a website or web application test fits, and an evidence timeline with a sample packet for test records you may be asked to put before your service auditor.
In this guide
SOC 2 evidence timeline and sample test evidence packet
One table in two parts, for test records you may be asked to put before a service auditor. Rows T1 to T8 place a test record, scan records, fixes, a narrow check and a retest against the date or dates your CPA firm sets for the report, and three of them, T1, T4 and T5, ask which criterion, if any, your CPA firm ties a record to.
How to use itHide the instructions
Rows P1 to P9 are the parts of an evidence packet for one test, each with a sample entry for Lantern Rostering, an invented business, on invented dates chosen only to show placement. Settle the report type and its dates with your CPA firm, move the table into a spreadsheet of your own and overwrite every sample entry. Row T6 alone sends requests, three in total counting a test-account sign-in, and its limits sit on the row: only an application your business operates or may test under written authorisation, a staging copy where there is one, and test accounts holding invented records only. The other rows file, copy, list or note records and send nothing. No row says a criterion is met. Whether a record is evidence for any criterion is for your service auditor, a licensed, independent CPA, to decide in the examination, and whether what you send meets a customer's request is for that customer. No criterion is quoted or described; read the criteria in the AICPA's own documents.
17 rows
Row and record
When it falls
T1. Report type, report dates and the testing question
- When it falls
- Before anything is booked, when you agree the examination with your CPA firm.
- What to record
- The customer's request in its exact words; the report type and the date or dates your CPA firm sets for the report; the edition of the Trust Services Criteria the examination will apply; and your service auditor's answer to two questions: would a test record dated before or inside those dates be considered, and which criterion, if any, would your CPA firm tie it to. Where the customer's request or the CPA firm's list quotes an identifier, such as CC4.1 or CC7.1, copy it exactly as written.
- Sample entry (invented business, invented dates)
- Request quoted from the customer's questionnaire: "Provide your most recent SOC 2 report." Report type and dates: as the CPA firm set them in writing; for this sample, 1 May to 31 October. Criteria edition: as the CPA firm confirms in writing. Service auditor's answer on testing: filed with the date it arrived.
- What it can show your service auditor
- Nothing on its own. It is the plan every later row is measured against.
- What it cannot show, and who decides
- Which criteria a test record bears on, if any. Your service auditor decides that in the examination, and the customer decides which report type it accepts.
- Limits of this row
- Read-only row: it records agreements and answers and sends no requests.
T2. Test before the report dates begin
- When it falls
- Before the date or dates your report covers begin, with time left to fix and retest.
- What to record
- The test's scope, window and build; each finding with its ratings; and the fix plan, with an owner and a target date for each finding.
- Sample entry (invented business, invented dates)
- Web application and API test of the Lantern portal and its API, 3 to 7 March, build 4.12, two test accounts in each of three roles. Four findings, one rated high for business risk.
- What it can show your service auditor
- What the test found on that build before the report dates began, and that each finding was recorded and given an owner.
- What it cannot show, and who decides
- The state of any control on a date the report covers. Whether a record dated before the report dates is relevant is your service auditor's judgement.
- Limits of this row
- Read-only row: it files the test record and sends no requests. The test itself runs under its own signed scope and authorisation, whoever performs it.
T3. Fixes and retest before the report dates begin
- When it falls
- After the T2 report arrives, and before the date or dates your report covers begin.
- What to record
- For each finding: the fix, the build it was deployed in, the retest date and the status the retest gave it.
- Sample entry (invented business, invented dates)
- Fixes deployed in build 4.13 on 2 April. Retest on 14 April: three findings fixed, one partially fixed and carried into T5.
- What it can show your service auditor
- The status of each reported finding on the retested build, including any the retest did not reach.
- What it cannot show, and who decides
- Anything outside the reported findings, or any change released after the retest. A finding left not retested carries no evidence of a fix.
- Limits of this row
- Read-only row: it records retest results and sends no requests.
T4. Scan records across the report dates
- When it falls
- On whatever schedule your business has set for scanning, for each scan run inside the report dates.
- What to record
- For each scan: the date, the targets, who ran it, the results that were confirmed, and the ticket opened for each confirmed result with the date it closed.
- Sample entry (invented business, invented dates)
- Monthly scans of the portal and API hostnames by the hosting team, 1 May to 31 October: six scan records, two confirmed results, both tickets closed by the target dates the team set.
- What it can show your service auditor
- That scans ran on the dates recorded and what happened to their confirmed results. Before the report dates begin, ask your service auditor whether these records would be considered at all, and which criterion, if any, your CPA firm ties them to.
- What it cannot show, and who decides
- Whether the schedule is adequate, or anything a scan does not reach, such as access between customer accounts. Your service auditor decides what the records show.
- Limits of this row
- Read-only row: it collects scan records your team or provider already keeps and sends no requests.
T5. Test inside the report dates
- When it falls
- Inside or near the date or dates your report covers, at a point your service auditor has said it would consider.
- What to record
- As for T2: scope, window, build, findings and fix plan, plus what this test found about any finding carried from T3.
- Sample entry (invented business, invented dates)
- Second web application and API test, 16 to 20 June, build 4.15, same roles and accounts as T2. Two findings, both rated medium on CVSS v3.1. The finding carried from T3 now behaves as its retest criteria require.
- What it can show your service auditor
- What the test found on that build inside the report dates, and that the finding carried from T3 was checked again. Ask your service auditor whether this record would be considered, and which criterion, if any, your CPA firm ties it to.
- What it cannot show, and who decides
- Whether any control operated on the other dates the report covers. That is for the examination, not the test.
- Limits of this row
- Read-only row: it files the test record and sends no requests. The test runs under its own signed scope and authorisation.
T6. Narrow check after a significant release
- When it falls
- After a significant release inside the report dates, before the next scheduled test.
- What to record
- The release and its date. Then three requests, each with its date, time and the status or on-screen message the application returned: a sign-in as test customer B; while signed in as B, one attempt to open an invoice that test customer A owns, by putting its invoice id in the address; and that same address opened once more from a private browser window that has not signed in.
- Sample entry (invented business, invented dates)
- Release 4.17, a new invoice export, 5 August. On 6 August: test customer B signed in at 10:01; customer A's invoice refused with an access error at 10:02; the same address from the window with no session answered with the sign-in screen at 10:04.
- What it can show your service auditor
- That both attempts on customer A's invoice were turned away on that build. It is a narrow result about one invoice and two attempts, not a test of the release.
- What it cannot show, and who decides
- Anything beyond those attempts. Whether the release needs a scoped test before the next scheduled one is your decision, and whether this record matters to the examination is your service auditor's.
- Limits of this row
- Sends requests: three in total, the sign-in included, one at a time and none repeated. Point it only at an application your business operates or has written permission to test, use a staging copy when there is one, and act only as test customers A and B, whose records are invented. Any email or text the sign-in sends must reach an inbox or phone your business controls. Record statuses, times and messages and nothing else: a password, session token or key, or a link that opens for anyone who has it, never goes in the record. If a vendor runs part of the application, check its terms before you start, ask it about anything they leave unsaid, and stay inside what the terms or its answer permit. If any response contains a real person's details, end the check: log the address and the time, stop opening anything, and pass it to whoever in your business looks after privacy and incidents.
T7. Retest inside the report dates
- When it falls
- After the T5 fixes are deployed, inside the report dates where your service auditor has said that matters.
- What to record
- The retest's date and build, and the status the retest report gives each T5 finding: fixed, partially fixed, still reproducible or not retested.
- Sample entry (invented business, invented dates)
- Retest on 21 July, build 4.16: both T5 findings fixed.
- What it can show your service auditor
- Where each T5 finding stood on the retested build.
- What it cannot show, and who decides
- Anything released after the retest, including the T6 release, unless a later test covers it.
- Limits of this row
- Read-only row: a retest result is written down and nothing is sent.
T8. After the report dates end
- When it falls
- From the day after the last date your report covers, until the next report's date or dates are set.
- What to record
- Tests, scans and fixes dated after the report dates, filed for the next examination, and any question a customer asks about the time since the report.
- Sample entry (invented business, invented dates)
- Scan records from November onwards filed under the next cycle. A customer asks in January what has changed since 31 October, and the answer comes from the post-report records, without stretching the report.
- What it can show your service auditor
- What was tested and fixed after the report dates, for the next examination and for customers who ask.
- What it cannot show, and who decides
- Anything inside the CPA's report. A later test record is not part of it. Ask your CPA firm how a customer's question about the time after the report dates should be answered.
- Limits of this row
- Read-only row: it files records and sends no requests.
P1. Cover and document control
- When it falls
- When you assemble the packet for your service auditor.
- What to record
- The packet's title, version and date; who assembled it; which test it covers; who may read it; and the list of parts P2 to P9.
- Sample entry (invented business, invented dates)
- Lantern Rostering, test evidence packet for the June test (T5), version 1, dated 28 July. Assembled by the head of engineering for the service auditor. Parts P2 to P9 enclosed.
- What it can show your service auditor
- Which test, and which version of the record, the service auditor is reading.
- What it cannot show, and who decides
- Nothing about controls. It is housekeeping that stops two versions of a record being confused.
- Limits of this row
- Read-only row: it describes the packet and sends no requests.
P2. Test scope
- When it falls
- Copied from the signed scope when you assemble the packet.
- What to record
- Targets (hostnames and API addresses), environment, roles and test accounts, depth (one of the methodology guide's three: unauthenticated, authenticated or code-assisted), exclusions, and the signed authorisation with its date.
- Sample entry (invented business, invented dates)
- portal.lantern.example and api.lantern.example on a staging copy matching production; three roles (organisation owner, roster manager, staff member) with two test accounts each, one in each of two customer organisations; authenticated depth. Excluded: the payment provider's hosted checkout and the hosting provider's platform. Authorisation signed 10 June.
- What it can show your service auditor
- What the test covered and what it left out, so no answer reaches further than the scope.
- What it cannot show, and who decides
- Anything excluded. An exclusion is untested, not passed, and whether it matters is your service auditor's judgement.
- Limits of this row
- Read-only row: it copies the scope from signed documents and sends no requests.
P3. Period covered
- When it falls
- When you assemble the packet, using the dates from T1.
- What to record
- The test window, the build or version tested, and where those dates sit against the date or dates your report covers.
- Sample entry (invented business, invented dates)
- Testing 16 to 20 June on build 4.15. The report dates agreed with the CPA firm are 1 May to 31 October, so the test window sits inside them.
- What it can show your service auditor
- Where the record sits against the report, so the service auditor can place it.
- What it cannot show, and who decides
- The state of the system on any other date. Whether a window inside the report dates matters for any criterion is the service auditor's judgement.
- Limits of this row
- Read-only row: it records dates and sends no requests.
P4. Findings summary
- When it falls
- When you assemble the packet, updated after each retest.
- What to record
- Each finding's reference, title, affected area, ratings and status on the packet's date, and the checks that found nothing, with the accounts and build they covered.
- Sample entry (invented business, invented dates)
- F-01: a roster manager could read another customer organisation's staff list by changing an id in an API request; medium on CVSS v3.1, high for business risk. F-02: the server kept a session alive after sign-out, so a copied session token kept working; medium on CVSS v3.1, medium for business risk. No access across organisations found on the report and export routes tested.
- What it can show your service auditor
- What was found and recorded on that build, and which checks found nothing.
- What it cannot show, and who decides
- That nothing else exists. A clean check covers what was checked, on that build, with those accounts, and nothing more.
- Limits of this row
- Read-only row: it summarises the report and sends no requests. Copy the summary, not the reproduction steps, for any finding still open.
P5. Exceptions
- When it falls
- When you assemble the packet.
- What to record
- Anything that departed from the plan: checks in scope that could not run and why, scope changes agreed during the window, pauses, and any point at which testing reached real data, with what was done.
- Sample entry (invented business, invented dates)
- Planned checks of file uploads not run: the upload feature was switched off on staging during the window. No scope changes. No pauses. No real data reached.
- What it can show your service auditor
- Where the test fell short of its plan, so the service auditor reads the findings against what actually ran.
- What it cannot show, and who decides
- These are the test's own exceptions. Any exceptions in a SOC 2 report belong to that report, not to this packet.
- Limits of this row
- Read-only row: it records what happened during the test and sends no requests.
P6. Remediation
- When it falls
- As each fix is deployed.
- What to record
- For each finding: the owner, the fix, the build and date it was deployed, and any finding you chose not to fix, with the reason and who made that decision.
- Sample entry (invented business, invented dates)
- F-01: ownership check added to the staff list route, build 4.16, 10 July, owner the API lead. F-02: session ended on the server at sign-out, build 4.16, 10 July, owner the API lead.
- What it can show your service auditor
- What was changed in response to each finding, and when.
- What it cannot show, and who decides
- That a fix works. The retest in P7 is the record of that, for the findings it covered.
- Limits of this row
- Read-only row: deployed changes are logged and nothing is sent.
P7. Retest status
- When it falls
- On the retest date.
- What to record
- The day of the retest, the build it ran against, and where it left each finding: fixed, partially fixed, still reproducible or not retested.
- Sample entry (invented business, invented dates)
- Retest on 21 July, build 4.16. F-01 fixed. F-02 fixed.
- What it can show your service auditor
- Where each finding stood on the retested build.
- What it cannot show, and who decides
- Anything released after the retest, and any fix for a finding marked not retested.
- Limits of this row
- Read-only row: it copies statuses from the retest report and sends nothing.
P8. Who tested, and their relationship to the system
- When it falls
- When you assemble the packet.
- What to record
- The tester's organisation, whether it built, hosts or runs any part of the system, and any accreditation a customer or contract requires, in its exact wording.
- Sample entry (invented business, invented dates)
- Tested by an outside provider that did not build, host or run the portal. The customer's contract names no accreditation.
- What it can show your service auditor
- The facts a service auditor or a customer may weigh about the tester.
- What it cannot show, and who decides
- Whether the tester suits the purpose. Your service auditor and your customer each judge that for themselves.
- Limits of this row
- Read-only row: facts about the tester are written down and nothing is sent.
P9. What this packet does not cover
- When it falls
- When you assemble the packet, and again before you send it.
- What to record
- A plain list of what sits outside the test: other systems, vendor platforms, people and process controls, dates outside the test window, and a statement that the packet makes no claim about any criterion.
- Sample entry (invented business, invented dates)
- Not covered: the mobile apps, the office network and staff laptops, the payment provider and hosting platforms, staff onboarding and offboarding, backups and restores, and anything released after 21 July. The packet makes no claim about any criterion.
- What it can show your service auditor
- Where the evidence stops, so an answer to a customer or an auditor claims no more than the test covered.
- What it cannot show, and who decides
- It is a boundary, not a finding. Whether a gap matters is your service auditor's judgement, and for a customer's request, the customer's.
- Limits of this row
- Read-only row: it lists boundaries and sends no requests.
SOC 2 as the AICPA describes it: an examination, a report and its criteria
The American Institute of CPAs (AICPA) promulgates the professional standards for SOC engagements, its SOC suite page says, and that page describes SOC as a suite of service offerings CPAs may provide in connection with system-level controls of a service organisation or entity-level controls of other organisations.
A post on the AICPA's Insights blog says its "System and Organization Controls: SOC Suite of Services" webpage provides resources for SOC 1, SOC 2, SOC 3, SOC for Cybersecurity and SOC for Supply Chain examinations. In an announcement dated 28 October 2026, the AICPA describes SOC 2 as "an examination performed by a licensed, independent CPA under the AICPA Attestation Standards that evaluates controls relevant to the security, availability, processing integrity, confidentiality or privacy of an organization's systems".
The AICPA sells a guide for CPAs on performing and reporting on SOC 2 examinations, and the guide's product page says it is updated as of 15 October 2022. Among the guide's key topics, the page lists SOC 2 engagements as an "Assertion-based examination of a service organization's description of its system and its controls relevant to security, availability, processing integrity, confidentiality, or privacy".
The same list names the 2017 trust services criteria (with revised points of focus, 2022), applied when evaluating control design and effectiveness, and the 2018 description criteria (with revised implementation guidance, 2022), used for evaluating management's description of the service organisation's system.
The same page explains why a customer asks. It says that to identify, assess and address the risks associated with a service organisation, its services and the system used to provide them, customers and business partners usually need information about the design, operation and effectiveness of controls within the service organisation's system, and that to support those needs they often request a SOC 2 report from the service organisation. The "usually" and the "often" are the AICPA's words, not this guide's.
In October 2026 the AICPA proposed an update to the criteria. The announcement of 28 October 2026 says the AICPA is seeking comment on a proposed update to the SOC 2 Trust Services Criteria, and that its SOC 2 Working Group is seeking public comment on the exposure draft through 15 January 2027.
It says the proposed updates include targeted restructuring of the criteria, including consolidating duplicative concepts, removing criteria where appropriate, adding new criteria where greater clarity or emphasis is needed, and revising existing criteria language, and that if approved next year, the proposed 2027 criteria would be effective for engagements beginning on or after 31 December 2027, with early adoption permitted.
Before you rely on any criterion identifier, whether it comes from this page, a customer or a CPA firm, ask your CPA firm which edition your examination applies.
This guide is for whoever has to respond when SOC 2 turns up in a customer's questionnaire, a tender or a contract: an owner, a manager or a technical lead. It gives no legal advice and performs no audit. It was written without the text of the AICPA's Trust Services Criteria, and, beyond what the AICPA's Insights post says of CC9.2, it does not say what any criterion covers.
Read the trust services criteria in the AICPA's own document, which its download page offers after you log in or create a free account.
The guide reports what the AICPA's open pages say and leaves every judgement about an examination to your CPA firm, your business and your customers.
Who SOC 2 reaches, and how it arrives at an Australian business
The AICPA writes about SOC 2 in terms of service organisations and the people who rely on them.
Its guide's product page describes organisations outsourcing functions to other organisations, which it calls service organisations, and says outsourcing also results in new risks arising from interactions with the service organisation and its system. Whether your business is a service organisation in that sense, and for which of its services, is a question to put to your CPA firm.
For an Australian business, a request for a SOC 2 report may come in a customer's security questionnaire, a tender or a clause in a contract. None of the AICPA pages this guide cites describes SOC 2 as a legal requirement. Read the clause or the question in full, ask the customer which report and which type it will accept, and have your own adviser tell you what your agreement with that customer requires of your business.
For the other questions in a questionnaire, the security questionnaires guide shows how to back each answer with evidence you already hold.
You may also meet SOC 2 from the buyer's side, when a supplier shows you a logo. The AICPA says it has introduced SOC logos designed to help service organisations communicate they have received "a SOC report issued by a licensed, independent CPA", and its page on logo registration and guidelines says the AICPA's logo for service organisations may be used by any service organisation that has received at least one SOC 1, SOC 2 or SOC 3 report "from a licensed CPA or a non-U.S. equivalent", where the page's open text breaks off mid-sentence.
The same page says the guidelines must be read and understood before the logo is downloaded and used or displayed on any website.
A logo is the supplier's way of saying it has received a report. The report itself is the thing to ask for.
SOC 2 type 1 and type 2: what the AICPA publishes openly
The AICPA publishes separate illustrative material for each type.
Its download pages list an illustrative management representation letter carrying representations specific to a SOC 2 type 1 examination, and an illustrative SOC 2 type 2 report, which the AICPA describes as including management's assertion, the description of the system, the service auditor's report, and tests of controls and results thereof.
None of the AICPA pages this guide cites defines type 1 or type 2 for SOC 2, and this guide does not borrow a definition from elsewhere. The nearest open statements are in a post on the AICPA's Insights blog reporting highlights from a panel at the 2023 AICPA & CIMA SOC & Third-Party Risk Management Conference, and none of them defines the SOC 2 types.
The post quotes panellist Neha Patel of Weaver and Tidwell LLP: "For a type 1, the service auditor is evaluating controls as of a specific date." The post does not say whether that remark concerned SOC 1 or SOC 2.
Separately, the post says a SOC 1 engagement involves reporting on the service organisation's description of its system and the design of its controls and, in a type 2 report, their operating effectiveness, and that SOC 1 engagements differ from SOC 2 engagements. That sentence is about SOC 1 only.
The AICPA describes its SOC 2 guide as the most important resource needed to understand how to perform and report on a SOC 2 examination, and sells it as a publication rather than publishing it openly. Ask the customer which type it will accept, and ask your CPA firm for the definitions its report will follow and the date or dates it will cover.
Why the dates matter for a test record
A test report has dates of its own, and they may or may not fall where the CPA's report does. How they relate is a judgement for the service auditor, not for the tester or for you. The same post reports a hypothetical put to the panel about the timeframe for collecting evidence for a type 1 report with an as-of date, without tying it to SOC 1 or SOC 2.
Panellist Chris K. Halterman of EY LLP said it comes down to professional judgement, and Neha Patel added that if an auditor is using evidential support after the as-of date, the key question is what additional steps the auditor took to validate a control that was in place in the past.
So put the question before the test is booked, not after the report arrives. The timeline on this page lays out where a test record, a scan record and a retest can sit against the date or dates your report covers, and some of its rows carry a question for your service auditor.
SOC 2 criteria: what this guide can tell you, and where to read the rest
The criteria a SOC 2 examination applies are the AICPA's, and so is their text.
The AICPA's download page for the 2017 Trust Services Criteria (With Revised Points of Focus, 2022) says the document presents control criteria established by the AICPA's Assurance Services Executive Committee (ASEC) for use in attestation or consulting engagements to evaluate and report on controls over the security, availability, processing integrity, confidentiality or privacy of information and systems used to provide products or services.
The page offers the document as the Trust Services Criteria with copyright information, and asks you to log in or create a free account before you download it.
This guide's account of SOC 2 is written from the AICPA's open pages only, so it quotes no criterion. You obtain the criteria from the AICPA.
The criteria carry identifiers. The Insights post quoted above says that in a SOC 2 engagement, "common criterion (CC) 9.2 of the trust services criteria gives you an opportunity to report if vendor management processing is not functioning adequately". Beyond that one, this page names and describes no criterion.
A customer's questionnaire or a CPA firm's request list may quote identifiers to you, such as CC4.1 or CC7.1. None of the open AICPA pages this guide cites writes either of those, so the guide says nothing about what they refer to.
Ask whoever quoted them which document and edition they come from, read the wording there or ask your service auditor for it. Whether a test record or a scan record bears on any criterion is then a question for your service auditor.
Points of focus, and the penetration testing question
The document's own title says it carries revised points of focus. The October 2026 announcement says new points of focus in the exposure draft address issues such as AI governance, model monitoring, prompt manipulation, data poisoning, transparency of AI-generated outputs, training data management and the risks associated with automated decision-making, and that these additions are designed to help organisations and auditors evaluate whether controls effectively address the risks introduced by advanced technologies.
Beyond that, the AICPA pages this guide cites do not say what standing points of focus have in an examination, and this guide does not characterise them.
None of those pages says that SOC 2 requires a penetration test. Whether a test belongs among the controls your description sets out is your business's decision, made with its own advisers. Whether a test's records bear on any criterion, and which, is a judgement for your service auditor, in an examination of your description of your system and its controls.
A customer that asks for a penetration test report as well as a SOC 2 report is making a separate request, so read its wording for what it asks.
SOC 2 penetration testing: what a test record can add
A website or application test speaks for one system only: the build it ran against, the days the testing took, the roles and test accounts it used and the scope that was signed.
It is dated and specific. A service auditor reading it can see what was tested, when, by whom, what was found and what became of each finding, and decides what, if anything, that says about the controls your description sets out.
Read against the sample packet on this page, these are the parts of a test report that carry the weight:
- The scope as tested: hostnames, API addresses, environment, roles and depth, with the exclusions. It shows what the test covered, so no answer you give claims more than that.
- The dates and the build: the test window and the version tested, so the record can be placed against the date or dates the report covers.
- Findings with evidence: each finding with redacted requests and responses, its ratings and a fix, showing that a weakness was found and recorded on that build.
- Negative results: checks that came back clean, each recorded with the build and the accounts used. They speak for those checks only.
- Remediation and retest: the fix plan, then each finding's status after the retest on an identified build. Where the retest did not reach a finding, the record says so, and that finding has no evidence of a fix behind it.
- The tester's relationship to the system: whether the tester built, hosts or runs it, which a service auditor or a customer may want to weigh.
Where the records come from
For a Clever Ops test, the methodology guide sets out where each of those parts is made, from the signed scope at the start to the four-state retest ledger at the end. The sample packet on this page fills the same parts in for one invented test, so each one can be seen in use before anything is commissioned.
Where a test record stops in a SOC 2 examination
A SOC 2 examination covers your description of your system and its controls.
A test covers one system in one window. A test report cannot close the gap between the two, and an answer that leans on it to do so invites questions it cannot meet.
- It is not the examination's testing. The AICPA's illustrative type 2 report includes tests of controls and results thereof alongside the service auditor's report. In that illustrative report they are part of the SOC 2 report; a penetration test report is a separate document from a separate engagement.
- It is silent on controls outside the system tested: staff onboarding and offboarding, training, office networks, laptops, backups and restores, change approval, and vendor management, the subject the AICPA's blog post ties to CC9.2.
- It does not cover a vendor's own platform. A test of your application leaves your hosting provider, your payment provider and the other services it depends on untested. Read their terms, and ask each vendor what assurance it offers.
- It is not an opinion. The AICPA lists report opinion types among the key topics of its SOC 2 report walkthrough webcast, and describes SOC 2 as an examination performed by a licensed, independent CPA. A penetration test report, clean or not, is not that examination.
- It does not cover anything released after the test. A significant change inside the report's dates is a reason to ask your service auditor whether the earlier test still speaks for the system.
How to use the evidence timeline and sample packet
The table on this page has two parts.
Rows T1 to T8 are the timeline: where a test record, scan records, fixes and a retest can sit against the date or dates your CPA firm sets for the report, with a question for your service auditor on the rows that need one.
Rows P1 to P9 are a sample evidence packet for one test, filled in for an invented business, Lantern Rostering, with invented dates chosen only to show placement.
- Settle the report type and its date or dates with your CPA firm first. Rows T2 to T8 are placed relative to them.
- Before a test is booked, ask your service auditor whether a record dated where you plan it would be considered, and against which criteria, if any. Keep the answer with the date it reached you.
- Move the table into a spreadsheet of your own and overwrite each sample entry with your business's records. The invented business and its dates stay out of anything you send.
- Only row T6 sends anything to an application, and its limits sit on that row. The other sixteen rows file, copy, list or note records.
- For anything a vendor operates, its terms decide how far you go; put whatever they leave unsaid to the vendor. This guide says nothing about what a vendor permits.
- Should any check bring up a real person's details, halt there. Note where and when, stop there, and raise it with whoever owns privacy and incident handling in your business.
- Send the packet in whatever form your service auditor requests. Because a full report carries reproduction steps for findings still open, keep its circulation to the people your own process allows.
Who weighs a test record, and whose report it is
The examination is the CPA's.
The AICPA describes SOC 2 as an examination performed by a licensed, independent CPA under the AICPA Attestation Standards, and its logos are designed to help service organisations communicate that they have received a SOC report issued by a licensed, independent CPA. Whether a test record is evidence for a control, and for which criterion, is a judgement your service auditor makes in that examination.
Management has a part of its own. The download page for the AICPA's illustrative management representation letter for a SOC 2 type 1 examination says that AT-C section 205, Assertion-Based Examinations, requires the service auditor to request written representations from the responsible party in a SOC 2 engagement, and that these representations should be in the form of a letter addressed to the service auditor.
What your description of your system says about testing, and whether it presents any testing as a control, is for your business to work through with its own advisers before the examination begins.
Your customer decides what it accepts. A SOC 2 report answers a request for a SOC 2 report, and a penetration test report answers a question about testing. Neither stands in for the other in a questionnaire, and the customer judges whether what you send meets what it asked.
Choose the CPA firm with care. In a notice on its SOC suite page, the AICPA says SOC services should be thoroughly evaluated by service organisations and CPA firms.
Two meanings of exceptions
The word can turn up in both documents. Among the learning outcomes of its SOC 2 report walkthrough webcast, the AICPA lists recalling considerations related to exceptions, bridge letters and SOC 3 reports. There the word belongs to the SOC 2 report, and the AICPA pages this guide cites do not define it.
In the sample packet on this page, row P5 uses it for the test's own departures from plan: checks in scope that could not run, scope changes, pauses during the test window and any point at which testing reached real data. Keep the two uses apart when you write to a customer.
Before the examination: the test Clever Ops can run, and the work that goes elsewhere
The parts of a business's systems that customers can reach from a browser or by calling an API are what Clever Ops tests, and the web security hub sets out each of its services.
For a software business preparing for a SOC 2 examination, the report of the web application and API penetration test holds parts the sample packet draws on: the build, dates, roles, accounts and exclusions as tested; each finding with redacted evidence and a fix, carrying a business-risk rating and a CVSS v3.1 score wherever the finding is rated; and negative results for each route and account tried.
One consolidated retest comes with every test, after which every finding is left in one of the four retest states: fixed, partially fixed, still reproducible or not retested.
The AICPA describes SOC 2 as an examination performed by a licensed, independent CPA, so that work sits with the CPA firm your business engages. A Clever Ops test is not that examination, and its report is evidence to weigh, not a SOC 2 report, a certificate or a compliance opinion. Clever Ops also has no security certification or accreditation of its own to put forward.
Because Clever Ops is not CREST accredited, work that a customer, tender or contract says needs a CREST-accredited tester is referred to one. For an application Clever Ops built or hosts, the report says so, names who built and who hosts it, and calls the work a security review rather than independent testing.
When your service auditor or your customer asks for independence, choose a tester that neither built nor runs the system. Clever Ops does not test a vendor's own product or platform, which keeps your hosting provider and your payment provider outside any Clever Ops test.
Internal networks, staff devices, phishing and red team work need specialists in those fields, and load or denial-of-service testing falls outside every Clever Ops service.
Frequently asked questions
None of the AICPA pages this guide cites says so, and this guide does not say so either. The AICPA's SOC 2 guide page lists the 2017 trust services criteria, applied when evaluating control design and effectiveness, and the 2018 description criteria, used for evaluating management's description of the service organisation's system; the trust services criteria are on a download page that asks you to log in or create a free account. Whether a penetration test belongs among the controls your description sets out is your business's call, made with its own advisers, and whether its records bear on any criterion, and which, is your service auditor's judgement in the examination. If a customer asks for a test report as well as a SOC 2 report, that is the customer's own request.
The AICPA describes SOC 2 as an examination performed by a licensed, independent CPA under the AICPA Attestation Standards, and says its SOC logos are designed to help service organisations communicate they have received a SOC report issued by a licensed, independent CPA. Its logo registration and guidelines page says the AICPA's logo for service organisations may be used by any service organisation that has received at least one SOC 1, SOC 2 or SOC 3 report "from a licensed CPA or a non-U.S. equivalent", where its open text stops mid-sentence, and that the guidelines must be read and understood before the logo is downloaded and used or displayed on any website. A penetration test provider is not issuing a SOC 2 report when it reports on a test, and a Clever Ops test report is not a SOC 2 report.
None of the AICPA pages this guide cites defines type 1 or type 2 for SOC 2. The AICPA publishes separate illustrative material for each: a management representation letter with representations specific to a SOC 2 type 1 examination, and an illustrative SOC 2 type 2 report, which it describes as including management's assertion, the description of the system, the service auditor's report, and tests of controls and results thereof. A post on the AICPA's Insights blog quotes Neha Patel of Weaver and Tidwell LLP, a panellist at the 2023 AICPA & CIMA SOC & Third-Party Risk Management Conference, saying that "For a type 1, the service auditor is evaluating controls as of a specific date", without saying whether the remark concerned SOC 1 or SOC 2. Ask your customer which type it will accept, and your CPA firm for the definitions its report will follow and the date or dates it will cover.
In the AICPA's own documents, or ask your service auditor for the wording. The AICPA's SOC 2 guide page names the 2017 trust services criteria for evaluating control design and effectiveness, and the 2018 description criteria for evaluating management's description of the system; the AICPA's download page for the trust services criteria asks you to log in or create a free account first. This guide was written without that text and, beyond what the AICPA's Insights post says of CC9.2, does not say what any criterion covers. If a customer or your CPA firm quotes an identifier to you, such as CC4.1 or CC7.1, ask which document and edition it comes from; none of the open AICPA pages this guide cites writes either of those. The AICPA's October 2026 announcement of proposed 2027 criteria says the proposed updates include consolidating duplicative concepts, removing criteria where appropriate, adding new criteria where greater clarity or emphasis is needed, and revising existing criteria language. Check which edition your examination applies before you rely on any identifier.
No. The AICPA describes SOC 2 as an examination performed by a licensed, independent CPA under the AICPA Attestation Standards, and a test report is neither that examination nor its report. What a test report offers is evidence about one system, on one build, inside one scope, which your service auditor may weigh. A Clever Ops report sets out the scope tested, the findings and the retest results; it is not a SOC 2 report, a certificate or a compliance opinion.
The AICPA pages this guide cites do not say who may receive a SOC 2 report, so ask your CPA firm before you share it. They do describe another report. The AICPA's SOC 3 page says that, like SOC 2, SOC 3 reports address controls relevant to security, availability, processing integrity, confidentiality and privacy, but they do not provide the same level of detail, so they are considered general use reports and can be freely distributed.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.