soc 2 · type ii · evidence
Charles Trinh — SOC 2 Readiness, Las Vegas NV

Readiness for a SOC 2 Type II examination: scoping, the trust criteria that matter, control design, and the evidence a service auditor will sample.
Type I versus Type II
Type I describes design at a point in time; Type II describes operation over a window, and nearly all enterprise buyers now require Type II.
The window is the hard part, because it means the controls must have been operating before the period started.
Plan backwards from the window: nothing you build in month two can evidence month one.
Scoping by service, not by company
Scope to the services that touch customer data, and say plainly what is excluded.
An over-broad scope multiplies evidence work without improving the report a buyer reads.
Exclusions with documented reasoning are normal and accepted; silent exclusions are findings.
The controls buyers actually read
Access control, change management, monitoring, incident response and vendor management cover most of what is examined.
Design them to be evidenced cheaply, because a control that requires heroics to prove will not survive a full window.
Automate the evidence where possible: tickets, logs and exports beat narrative descriptions every time.
Evidence collection discipline
Collect continuously into a repository, indexed by control and period, rather than assembling at the end.
Sampling means the auditor picks; you do not get to choose the examples, so consistency matters more than a good sample.
A missed month is not repairable after the fact, which is why collection starts before the window opens.
Common failure modes
Policies signed once and never reviewed, access reviews performed without decisions recorded, and incidents closed without a written review.
Each fails on operation rather than design, and each is cheap to fix before the window starts.
Read your own policy and ask whether the last twelve months match it; that gap is the finding.
Vendor and subservice organisations
Carry-in from subservice organisations needs a complementary report, and their window may not align with yours.
Ask for their report and bridge letter before you commit to a start date.
A vendor without a report becomes your scope problem, and the auditor will say so.
Cost and timeline
A first Type II on a small estate runs four to six months of preparation plus the observation window.
The dominant cost is internal effort in evidence and policy upkeep, not the audit fee.
Budget the owner's time explicitly, because readiness without an owner becomes a document nobody maintains.
What I do
I design the control set, build the evidence repository, and run a pre-audit sample against the criteria in scope.
I do not issue the report and I do not sell a GRC platform; I make the examination boring.
The deliverable is a control matrix with owners, evidence sources and a realistic window start date.
Measuring readiness
The useful test is a random sample: pick five controls and try to evidence them for last month without asking anyone.
If that takes more than an hour, the repository is not ready regardless of what the matrix says.
Run that test monthly between now and the window, because it is the only one that predicts the outcome.
Where to start
Pick the five controls you are least confident about and attempt to evidence them for last month.
Whatever you cannot produce is the first project, and it is likely to be access review or change approval.
Everything after that is repetition with better tooling.
How I do it
- One trace of a real case, timestamps at every hop, before any document is written.
- A findings list naming the defect, the system, the owner and the date — reviewed monthly.
- No attestation I did not test, and no template sold as an assessment.
The window is the product
A Type II report is a statement about a period, so the start date matters more than any individual control design decision.
Organisations that start the window before collection habits settle spend the first month producing evidence they cannot find later.
Set the window start after two clean months of collection, and say so to the buyer rather than promising a date that the evidence cannot support.
Carve-outs and subservice organisations
A subservice organisation's report has its own window and its own exceptions, and neither aligns automatically with yours.
The complementarity claim has to be true at the level of the specific control you are relying on, not at the level of the vendor relationship.
Read the exceptions section of their report before relying on it, because the exception is where the control you inherited is described as failing.
Scope mistakes that cost a quarter
Adding a system to scope is cheap; removing one after the window opens is not, because the evidence must cover it from the start.
The usual mistake is including a marketing site or a staging environment because someone assumed completeness was safer.
Name the systems, the data they hold and the reason each is in or out, then freeze the list in writing before the period starts.
Tooling versus habit
A GRC platform organises evidence; it does not create it, and the platform will happily index an empty month.
Adopt tooling after the habit exists, because tooling applied first produces dashboards that describe a process nobody runs.
The habit is simple: one owner, one repository, one monthly check that last month is complete.
Reading the criteria honestly
Each criterion asks a question about operation, and answering it requires an artefact rather than a paragraph.
Map the artefact to the criterion before the auditor does, and note the exceptions you already know about.
The exception you disclose is survivable; the exception they discover is the finding that lengthens the report.
What the report is for
The report is a sales artefact as much as a control artefact, and its scope should match what the buyer will read.
Ask the buyer which criteria and which services matter before scoping, because over-delivering on an unread section is expensive.
Publish a short bridge explaining scope and exceptions for the sales team, so the report is not misdescribed downstream.
Exception handling as a control
Every organisation has months where a control misses, and the difference between a finding and a footnote is whether the miss was caught and corrected.
Record the exception, the compensating step, the date it was resolved and who verified the resolution.
An auditor sampling that month finds a documented correction rather than an unexplained gap, and the report reads very differently as a result.
What the auditor will ask in the first week
The first request is almost always a list, and the list names the system, the period and the artefact. What the auditor is measuring in that first week is not the quality of the control but the speed and consistency of the answer, because a repository answers in minutes and a scramble answers in days. Organisations that fail the first week usually fail on access reviews, because the review happened but the decisions were never recorded, and a review without decisions cannot be sampled.
The second request is for the policy that governs the control, and the question behind it is whether the policy describes what actually happens. A policy written for an audit that describes a monthly review while the operation runs quarterly is not a documentation defect; it is evidence that the control does not operate as claimed. The safest policy is the one written last, after the process has settled, because it describes reality rather than intention and it needs no interpretation during the examination.
The third request is the exception register, and this is where an organisation with a good process distinguishes itself from one without. Every window has exceptions, and an auditor who is told about them up front treats them as context, while an auditor who discovers them in a sample treats them as findings. Keeping that register current costs an hour a month and changes the character of the entire examination, which is the cheapest trade in the whole readiness programme.
Proof
- ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
- 67 public hostnames, 51 serving, one AWS account
- 104 clearinghouse enrolments across 53 jurisdictions
- USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
- AWS Business Associate Addendum active since 18 August 2026
Where this work is delivered
Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.
How an engagement runs
1. Trace one real case
Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.
2. Written findings
A findings list naming the defect, the system, the owner and the date.
3. Monthly review
Review the list monthly and check whether the dates held.
Frequently asked
What is this service?
This page describes charles trinh — soc 2 readiness, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the Security and Compliance category at trinh.io.
Where is the work delivered?
Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.
What does it cost?
Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.
Who is Charles Trinh?
A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.
How does an engagement start?
With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.
Engagement
Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io
Talk to Charles
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
Record
Profile
Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.
Selected engineering scale
- Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
- FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
- Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
- X12 005010 pipelines across eight transaction sets.
- Designed, built, deployed and operated end to end by one person.
Credentials and standards work
- Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
- USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.
Technical environment
AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.