---
title: "SOC 2 and Enterprise Security Reviews: What Buyers Ask Vendors"
date: "2026-10-05"
video_id: "7693178704674983199"
tiktok_url: "https://www.tiktok.com/@sd141414/video/7693178704674983199"
creator: "@sd141414"
category: "Business"
tags: ["security review", "soc 2", "caiq", "vendor questionnaire", "enterprise sales"]
excerpt: "How an enterprise security review works: the SOC 2 report and questionnaires that come first, the controls buyers check, and what they ask about your code."
---
An enterprise security review checks whether a vendor can explain where customer data lives, who can reach it, what gets logged and what happens when something fails. A TikTok from @sd141414 says buyers start by asking someone on your team to explain the system. The four questions it lists are real control requirements, but the review starts with documents you write, and buyers do ask about your code in writing.

## What buyers ask in a security review

The video lists four things a buyer wants explained: "Where the data is stored, who can access it, what gets logged, and what happens when a piece of it fails." Each one maps to a published criterion.

**Data location.** CAIQ v4.0.2 question DSP-19.1 asks: "Are processes, procedures, and technical measures defined and implemented to specify and document physical data locations, including locales where data is processed or backed up?" ISO/IEC 27001:2022 covers the same ground in Annex A control A.5.23, "Information security for use of cloud services."

**Access.** SOC 2 criterion CC6.1 in the AICPA 2017 Trust Services Criteria reads: "The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives." ISO 27001:2022 carries the same requirement as A.8.3, "Information access restriction."

**Logging.** SOC 2 CC7.2 requires that "The entity monitors system components and the operation of those components for anomalies," with a point of focus on "logging of unusual system activities." CAIQ LOG-04.1 asks: "Is access to audit logs restricted to authorized personnel, and are records maintained to provide unique access accountability?" ISO 27001:2022 A.8.15 is titled "Logging."

**Failure behavior.** SOC 2 criterion A1.2, in the availability category, covers "environmental protections, software, data backup processes, and recovery infrastructure."

The video's follow-up question, "Can one customer's data ever reach another customer?", is a plain-language version of CAIQ IVS-06.1, which asks whether tenant access is "appropriately segmented, segregated, monitored, and restricted from other tenants." On what buyers ask, the video is accurate.

## How does an enterprise security review start?

The video opens with "Enterprise buyers don't ask to see your code. They ask someone on your team to explain the system. That's what a security review is."

In practice the review starts with a document request. The first document is usually a SOC 2 Type II report. That report includes a system description written by the vendor, and its content is governed by AICPA DC section 200, the 2018 Description Criteria. DC section 200 has nine criteria. DC1 covers the services provided and how customers use the system. DC2 covers the principal service commitments and system requirements. Another criterion requires a statement of the system's boundaries, meaning what is in scope and what is not.

Alongside the report, or in place of it, the buyer sends a standard questionnaire:

- **CAIQ v4.1.0** has 261 yes-or-no questions mapped to 207 controls across 17 domains.
- **HECVAT 4**, released by EDUCAUSE on 10 February 2025 and now at revision 4.1.6, has 321 questions across 7 sections.
- **The Shared Assessments SIG** comes in a Lite form of roughly 126 questions and a Core form of roughly 855 questions across 21 risk domains.

All of that is written and finished before anyone schedules an architecture call. The live conversation in the video does happen, but as an escalation. It comes up when written answers contradict each other, when a control is marked as the customer's responsibility and the buyer expected the vendor to own it, or when an answer is a bare "Yes" with no description of how the control works.

## Do enterprise buyers ask to see your code?

They will not read your repository. CAIQ, HECVAT and the SIG are control attestations, and SOC 2 is an auditor's opinion on controls rather than a code audit.

The questionnaires do ask about your code in writing:

- CAIQ AIS-05.1 asks whether the testing strategy sets "criteria to accept new information systems, upgrades, and new versions."
- AIS-05.2 asks: "Is testing automated when applicable and possible?"
- AIS-06.1 asks whether you deploy "application code in a secure, standardized, and compliant manner."
- AIS-07.1 asks: "Are application security vulnerabilities remediated following defined processes?"
- TVM-06.1 asks about "the periodic performance of penetration testing by independent third parties."

Large buyers also ask for the code itself through source code escrow. The vendor deposits source with a third-party agent, and the agent releases it to the customer on defined triggers such as the vendor's bankruptcy or failure to maintain the product. ISACA's 2022 guidance describes escrow as something to raise in the RFP at procurement and then settle in the contract.

## Are AI agents writing most of the code?

The video's turn is the line "But now that agents are writing most of it, creating code faster than anyone can read, a team can ship a working product that no one can explain."

Anthropic's 2026 Agentic Coding Trends Report gives a smaller figure. It says developers "use AI in roughly 60% of their work" but "report being able to 'fully delegate' only 0-20% of tasks." The report describes the shift as one "from writing code to reviewing, directing, and validating AI-generated code," and says "the human role remains central." It does predict that organizations will use agents to review large volumes of AI-generated code, but that is a forecast in the document rather than a measurement.

The video's broader point still holds. As more implementation is delegated, fewer people hold the full picture of the system, and the security review is where that shows. The "most of it" figure is the part that does not match the source.

## Does hesitating on a question count against you?

The video says "If your answer is, I'd have to check, the buyer hears yes." No framework scores verbal hesitation. SOC 2 scores whether a control operated over an observation period. CAIQ and HECVAT score written answers. No criterion in the Trust Services Criteria, CCM v4 or HECVAT 4 turns "I would have to check" into a finding. An unanswered architecture question usually produces a follow-up request or a remediation item.

## Bottom line

The four questions in the video are the right ones, and each maps to a SOC 2, CAIQ or ISO 27001 control. The review starts with a vendor-written SOC 2 system description and a questionnaire, and the architecture call comes later if gaps show up. Buyers ask about testing, deployment and patching in writing, and large deals can require source code escrow.

## Sources

- [AICPA 2017 Trust Services Criteria](https://arpio.io/wp-content/uploads/2020/08/trust-services-criteria.pdf) - text of CC6.1, CC7.2 and A1.2.
- [CAIQ v4.0.2, completed example](https://configcat.com/assets/files/CAIQv4.0.2_STAR-Security-Questionnaire_ConfigCat.pdf) - text of IVS-06.1, DSP-19.1, LOG-04.1, AIS-05, AIS-06, AIS-07 and TVM-06.
- [Wolfia, all 261 CAIQ v4 questions by domain](https://wolfia.com/blog/we-mapped-all-261-caiq-v4-questions-by-domain) - CAIQ v4.1.0 question and control counts.
- [EDUCAUSE Review, "HECVAT 4: Better than Ever"](https://er.educause.edu/articles/2025/2/hecvat-4-better-than-ever) - HECVAT 4 release details.
- [Shared Assessments, About the SIG](https://sharedassessments.org/about-sig/) - the SIG questionnaire.
- [Ledger Audits, DC Section 200](https://www.ledgeraudits.com/blog/dc-200-guidelines) - the vendor-written SOC 2 system description criteria.
- [ISMS.online, ISO 27001:2022 Annex A 8.15](https://www.isms.online/iso-27001/annex-a-2022/8-15-logging-2022/) - ISO 27001 control titles.
- [Anthropic, 2026 Agentic Coding Trends Report](https://resources.anthropic.com/2026-agentic-coding-trends-report) - AI usage and delegation figures.
- [Wikipedia, Source code escrow](https://en.wikipedia.org/wiki/Source_code_escrow) - how escrow works.
- [ISACA, "How Important Is Source Code Escrow"](https://www.isaca.org/resources/news-and-trends/newsletters/atisaca/2022/volume-42/how-important-is-source-code-escrow) - escrow in procurement.


## Video description and verification notes

**The artifact is a 61.36-second vertical talking-head clip (1:01), 1080x1920, HEVC Main video at 29.97 fps and 742,498 bps, HE-AACv2 audio at 48,128 bps in stereo at 44.1 kHz, 6,116,241 bytes on disk (5.8 MB), posted 2026-10-05 at 13:43:06 UTC by @sd141414 under the channel nickname "Steve | Systems & AI". The audio track is listed in the yt-dlp dump as "original sound" credited to "Steve | Systems, AI", so there is no licensed music bed. At capture on 2026-10-06 the post showed 9,203 views, 470 likes, 19 comments and 42 reposts. I read 18 of the 31 extracted frames (2-second intervals, 540 px wide) and the transcript runs 182 words. The shot is a single unbroken selfie-framed take of a man in a grey-green v-neck t-shirt and heavy black rectangular glasses, grey beard, seated in front of a matte-black open shelving unit. Hanging from the shelf are race medals and finisher ribbons whose lettering reads backward on screen ("FINISHER" renders as mirrored type, and a red ribbon reading "2018" is reversed to "8102"), which means the footage was published in mirrored selfie-preview orientation rather than flipped back. Behind him on the right is a teal and grey curtain in a repeating Greek-key pattern, white crown molding above, and a spider plant on the shelf. From frame 011 onward a wooden desk edge, a keyboard and a yellow-green cup enter the bottom-right corner. Two graphic layers run over the video. A red rounded banner pinned near the top reads "Enterprise buyers don't ask to see your code" and is visible in frames 001 through 006, then removed. Burned-in karaoke captions in white italic condensed uppercase sit in the lower third, one keyword per card boxed in solid red: "ENTERPRISE BUYERS DON'T ASK TO SEE", "TO EXPLAIN THE SYSTEM.", "WHERE THE DATA IS STORED, WHO", "WHAT GETS LOGGED, AND WHAT HAPPENS", "WHEN A PIECE OF IT FAILS.", "SOMEBODY HAS TO ANSWER IN PLAIN", "CAN ONE CUSTOMER'S DATA EVER REACH", "IT BEING LOGGED?", "IF YOUR ANSWER IS, I'D HAVE", "YOU COULD ANSWER THIS FROM MEMORY.", "BUT NOW THAT AGENTS ARE WRITING", "READ.", "PRODUCT THAT NO ONE CAN EXPLAIN.", "REVIEW GOES QUIET.", "PERSON WHO CAN TRACE A REQUEST", "BE DIFFICULT TO UNDO.", "BUT SOMEONE NEEDS TO CARRY IT", and finally "TO TALK TO." Starting at frame 009 (roughly the 16-second mark) a blue pill-shaped lower-third reads "prodblueprint.dev" and stays on screen through the last frame. That domain resolves to a client-rendered page titled "The Production-Ready Blueprint™", which gates a checklist behind a newsletter signup.**

## The four questions the video lists are real control requirements, and they are traceable to specific criteria

The transcript names four things a buyer wants explained: "Where the data is stored, who can access it, what gets logged, and what happens when a piece of it fails." That list is not invented. Each item maps to a published criterion.

Data location is [CAIQ v4.0.2](https://configcat.com/assets/files/CAIQv4.0.2_STAR-Security-Questionnaire_ConfigCat.pdf) question DSP-19.1, which asks: "Are processes, procedures, and technical measures defined and implemented to specify and document physical data locations, including locales where data is processed or backed up?" The same ground is covered by ISO/IEC 27001:2022 Annex A control [A.5.23, "Information security for use of cloud services"](https://www.isms.online/iso-27001/annex-a-2022/8-15-logging-2022/).

Access is SOC 2 criterion CC6.1 in the AICPA [2017 Trust Services Criteria](https://arpio.io/wp-content/uploads/2020/08/trust-services-criteria.pdf): "The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives." Its first point of focus requires that "Logical access to information assets, including hardware, data (at-rest, during processing, or in transmission), software, administrative authorities, mobile devices, output, and offline system components is restricted through the use of access control software and rule sets." ISO 27001:2022 carries the same requirement as A.8.3, "Information access restriction."

Logging is SOC 2 CC7.2, which requires that "The entity monitors system components and the operation of those components for anomalies," with a point of focus naming "logging of unusual system activities." CAIQ LOG-04.1 asks: "Is access to audit logs restricted to authorized personnel, and are records maintained to provide unique access accountability?" ISO 27001:2022 A.8.15 is titled simply "Logging."

Failure behavior is SOC 2 criterion A1.2 under the availability category: "The entity authorizes, designs, develops or acquires, implements, operates, approves, maintains, and monitors environmental protections, software, data backup processes, and recovery infrastructure to meet its objectives."

The video's second question is even closer to the source than the first four. "Can one customer's data ever reach another customer?" is a plain-language restatement of CAIQ IVS-06.1: "Are applications and infrastructures designed, developed, deployed, and configured such that CSP and CSC (tenant) user access and intra-tenant access is appropriately segmented, segregated, monitored, and restricted from other tenants?" On the substance of what gets asked, the video is accurate.

## The causal order in the video is reversed: the written description comes first

The opening line sets up a sequence where a buyer arrives and asks a person to talk. "Enterprise buyers don't ask to see your code. They ask someone on your team to explain the system. That's what a security review is."

A real enterprise security review does not begin with a conversation. It begins with a document request, and the first document is usually a SOC 2 Type II report. That report contains a written system description authored by the vendor, not the auditor, and the content of that description is governed by AICPA [DC section 200](https://www.ledgeraudits.com/blog/dc-200-guidelines), the 2018 Description Criteria for a Description of a Service Organization's System. DC section 200 runs to nine description criteria. DC1 requires the types of services provided and how customers use the system. DC2 requires the principal service commitments and system requirements. A separate criterion requires an explicit statement of the boundaries of the system, meaning what is in scope and what is not.

Alongside or instead of the report, the buyer sends a standardized questionnaire. [CAIQ v4.1.0](https://wolfia.com/blog/we-mapped-all-261-caiq-v4-questions-by-domain) carries 261 yes-or-no questions mapped to 207 controls across 17 domains. [HECVAT 4](https://er.educause.edu/articles/2025/2/hecvat-4-better-than-ever), released by EDUCAUSE on 10 February 2025 and now at revision 4.1.6, carries 321 questions across 7 sections. The Shared Assessments [SIG](https://sharedassessments.org/about-sig/) ships in a Lite form of roughly 126 questions and a Core form of roughly 855 questions across 21 risk domains.

All of that is written work, and it is finished before anyone schedules an architecture call. The live conversation the video describes is real, but it is the escalation path, not the entry point. It happens when the written answers contradict each other, when a control is marked as a customer responsibility that the buyer expected the vendor to own, or when the questionnaire answer is a bare "Yes" with no implementation description behind it. Treating the interview as the whole of a security review understates the paperwork and misplaces where a team actually fails first.

## "They don't ask to see your code" is half right, and the half that is wrong is contractual

The literal claim holds for the common case. No standard questionnaire asks a buyer's analyst to read your repository. CAIQ, HECVAT and the SIG are all control attestations, and SOC 2 is an auditor's opinion on controls rather than a code audit.

But the questionnaires do ask about code, and they ask in writing. CAIQ AIS-05.1 asks: "Does the testing strategy outline criteria to accept new information systems, upgrades, and new versions while ensuring application security, compliance adherence, and organizational speed of delivery goals?" AIS-05.2 asks: "Is testing automated when applicable and possible?" AIS-06.1 asks: "Are strategies and capabilities established and implemented to deploy application code in a secure, standardized, and compliant manner?" AIS-07.1 asks: "Are application security vulnerabilities remediated following defined processes?" TVM-06.1 asks whether measures exist "for the periodic performance of penetration testing by independent third parties."

Separately, large buyers do routinely ask for the code itself, just not to read it. [Source code escrow](https://en.wikipedia.org/wiki/Source_code_escrow) is the deposit of source with a third-party agent, released to the licensee on defined triggers such as the vendor's bankruptcy or failure to maintain the product. [ISACA's 2022 treatment of escrow](https://www.isaca.org/resources/news-and-trends/newsletters/atisaca/2022/volume-42/how-important-is-source-code-escrow) describes it as something to raise in the RFP at the time of procurement and then settle in the contract. Verification services exist specifically to confirm a deposit actually builds.

So the accurate version of the hook is narrower than what the banner says. A buyer will not read your code. A buyer will ask, in writing, how your code is tested, deployed and patched, and in a large deal may require the code be escrowed.

## "Agents are writing most of it" overstates the only first-party measurement available

The pivot in the transcript is a quantitative claim: "But now that agents are writing most of it, creating code faster than anyone can read, a team can ship a working product that no one can explain."

Anthropic's [2026 Agentic Coding Trends Report](https://resources.anthropic.com/2026-agentic-coding-trends-report) measures this directly and reports a smaller number. The report states that research from its Societal Impacts team "reveals that while developers use AI in roughly 60% of their work, they report being able to 'fully delegate' only 0-20% of tasks." It adds that "AI serves as a constant collaborator, but using it effectively requires thoughtful set-up and prompting, active supervision, validation, and human judgment—especially for high-stakes work."

Sixty percent of work touched is not the same as most of the code written autonomously, and a 0 to 20 percent full-delegation band is the opposite of code "creating faster than anyone can read." The same report is explicit that humans stay in the review loop, calling the shift one "from writing code to reviewing, directing, and validating AI-generated code," and noting that "even as AI capabilities expand, the human role remains central." The report does flag review capacity as a pressure point, predicting that organizations will "use AI agents to review large-scale AI-generated output, analyzing code for security vulnerabilities, architectural consistency, and quality issues that would overwhelm human capacity." That is a forward-looking prediction in the document, not a measured present state.

The video's underlying point survives the correction. If a growing share of implementation is delegated, fewer people hold the end-to-end picture. The percentage framing is the part that does not hold up against the primary source.

## The one claim with no published backing is the one the video builds its hook on

"If your answer is, I'd have to check, the buyer hears yes." The Whisper transcript renders this as "the buyer here is yes," which is a mistranscription of "hears yes"; the burned-in caption confirms the spoken line ends at "IF YOUR ANSWER IS, I'D HAVE".

No framework scores verbal hesitation. SOC 2 scores whether a control operated effectively over an observation period and the auditor's opinion is the output. CAIQ and HECVAT score written answers. There is no criterion in the TSC, in CCM v4, or in HECVAT 4 under which an engineer saying "I would have to check" converts to a finding. In practice an unanswered architecture question produces a follow-up request or a remediation item, not an adverse presumption. Treat this line as rhetoric rather than procurement mechanics.

The video names no AI model, so there is nothing to check against Anthropic's published lineup. For reference, the current models per the [live models overview](https://platform.claude.com/docs/en/docs/about-claude/models/overview) are Claude Fable 5.1, Claude Opus 5.5 (the recommended default), Claude Sonnet 5.5 and Claude Haiku 4.5, with Claude Opus 5 and Claude Sonnet 5 listed as legacy but still available. All accept text and image input and return text only.

## Key Takeaways

- **Verified:** The four questions in the transcript map to published criteria. Data location is CAIQ DSP-19.1 and ISO 27001:2022 A.5.23, access is SOC 2 CC6.1 and ISO A.8.3, logging is SOC 2 CC7.2 and CAIQ LOG-04.1 and ISO A.8.15, failure behavior is SOC 2 A1.2.
- **Verified:** "Can one customer's data ever reach another customer?" is a close restatement of CAIQ IVS-06.1 on tenant segmentation and segregation.
- **Correction:** A security review starts with documents, not an interview. The SOC 2 Type II report carries a vendor-written system description governed by AICPA DC section 200, and the questionnaire arrives alongside it. CAIQ v4.1.0 is 261 questions, HECVAT 4.1.6 is 321, SIG Core is roughly 855. The architecture call is the escalation when those answers leave gaps.
- **Partial correction:** Buyers will not read your repository, but questionnaires ask about your code in writing (CAIQ AIS-05, AIS-06, AIS-07, TVM-06), and large enterprise contracts often require source code escrow with a third-party agent.
- **Correction:** "Agents are writing most of it" overstates Anthropic's own measurement. The 2026 Agentic Coding Trends Report puts AI involvement at "roughly 60% of their work" with full delegation at "only 0-20% of tasks."
- **Unverified:** "The buyer hears yes" after a hesitation. No published criterion in the TSC, CCM v4 or HECVAT 4 treats a verbal non-answer as a finding. I checked all three.
- **Unverified:** The "five things big companies require" checklist named in the post description. prodblueprint.dev gates it behind a newsletter signup and the page is client-rendered, so the contents are not publicly readable.
- **Context:** The video names no AI model, so there is nothing to check against the current Claude lineup.

## Resources

- [2017 Trust Services Criteria (AICPA)](https://arpio.io/wp-content/uploads/2020/08/trust-services-criteria.pdf). Supplies the verbatim text for CC6.1, CC7.2 and A1.2, including the points of focus on restricting logical access and logging unusual system activity.
- [CAIQ v4.0.2 Consensus Assessments Initiative Questionnaire, completed example](https://configcat.com/assets/files/CAIQv4.0.2_STAR-Security-Questionnaire_ConfigCat.pdf). Supplies verbatim question text for IVS-06.1, DSP-19.1, LOG-04.1, AIS-05, AIS-06, AIS-07 and TVM-06.
- [We mapped all 261 CAIQ v4 questions by domain](https://wolfia.com/blog/we-mapped-all-261-caiq-v4-questions-by-domain). Establishes that CAIQ v4.1.0 holds 261 questions mapped to 207 controls across 17 domains.
- [HECVAT 4: Better than Ever (EDUCAUSE Review)](https://er.educause.edu/articles/2025/2/hecvat-4-better-than-ever). Establishes the 10 February 2025 release of HECVAT 4 and the merge of the Full, Lite and On-Premise workbooks into one conditional instrument.
- [About the SIG (Shared Assessments)](https://sharedassessments.org/about-sig/). Establishes the SIG as a standardized buyer-issued questionnaire used in vendor due diligence.
- [DC Section 200: The AICPA Description Criteria](https://www.ledgeraudits.com/blog/dc-200-guidelines). Establishes that the SOC 2 system description is written by the vendor against nine criteria covering services, commitments and system boundaries.
- [ISO 27001:2022 Annex A Control 8.15 Logging](https://www.isms.online/iso-27001/annex-a-2022/8-15-logging-2022/). Confirms the official titles of A.8.15 Logging, A.8.3 Information access restriction and A.5.23 cloud services.
- [2026 Agentic Coding Trends Report (Anthropic)](https://resources.anthropic.com/2026-agentic-coding-trends-report). Supplies the 60 percent involvement and 0 to 20 percent full-delegation figures and the statement that the human role remains central to review.
- [Source code escrow (Wikipedia)](https://en.wikipedia.org/wiki/Source_code_escrow) and [How Important Is Source Code Escrow (ISACA)](https://www.isaca.org/resources/news-and-trends/newsletters/atisaca/2022/volume-42/how-important-is-source-code-escrow). Establish that enterprise buyers do contract for access to source, through a third-party agent with defined release triggers.
- [Claude models overview](https://platform.claude.com/docs/en/docs/about-claude/models/overview). Establishes the current model lineup and that all current models return text output only.
