SERVICES · LAS VEGAS NV

Charles Trinh — Security Architecture Review | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Charles Trinh — Security Architecture Review, Las Vegas NV
Charles Trinh — Security Architecture Review

Reviewing an architecture against what it must defend: trust boundaries, data paths, control placement, and the findings that survive an examiner rather than a checklist.

Draw the boundaries first

A review starts where trust changes: network segments, process isolation, tenant boundaries and third-party calls. A control placed outside a boundary does not control what crosses it.

Every boundary claim needs a configuration artefact with a date, because the diagram is a description and the config is the fact.

Trace one record

Trace a single record through the architecture and note where it is protected and where it is merely present. The second list is where findings live.

Map each control to the threat it addresses and to how you know it operates, rather than listing controls in the abstract.

Accepted risk needs a name

Record accepted risks with a person, a reason and an expiry. Undocumented acceptance becomes an assumption nobody can revisit, and it is the most common gap in a mature-looking programme.

Review acceptances monthly, since they accumulate quietly and expire unnoticed.

Report defects, not maturity

Findings are defects with owners and dates, not maturity levels with colours. A maturity score changes no behaviour; a dated defect list does.

Re-test the finding rather than closing it on assertion, because the closure is where reviews most often lie.

The review is a set of questions

A review is not a document review; it is a list of questions asked in a fixed order and answered with evidence. Where does trust change, what crosses that boundary, what enforces it, and how do you know it operates. The order matters because each question depends on the previous one, and a review that starts with controls has already assumed the boundary analysis it was supposed to perform.

Write the questions down and reuse them across systems, because a standard question set is what makes reviews comparable and what lets a second reviewer reproduce the first one's findings. An ad hoc review produces a report that cannot be compared to anything, which means the organisation cannot tell whether the architecture is improving.

Findings that survive an examiner

A finding is a sentence that names the system, the defect, the consequence and the evidence, with an owner and a date. A finding written as a recommendation is an opinion, and opinions do not get funded. The distinction is not pedantry: the defect list is what an examiner reads, and a list of recommendations reads as a programme that has not decided anything.

Where a finding cannot be remediated, the record is an accepted risk with a name, a reason and an expiry. Undocumented acceptance is the most common gap in an otherwise mature programme, and it is discovered when the person who accepted the risk has left and nobody can say why the system is configured as it is.

Reviewing third-party boundaries

Every external call is a trust boundary and the review has to cover what leaves, what returns and what the counterparty can infer from the traffic. A vendor integration that carries an identifier in a query string leaks the identifier to every proxy in the path, and the defect is not in the vendor's system. Review the integration the way you review an internal boundary, because the risk does not change with the invoice.

Where a counterparty cannot meet the standard, record the compensating control and its test. A compensating control without a test is a paragraph, and the paragraph is what gets quoted back at you when the incident review asks what was in place.

Re-review on change

A review has a shelf life measured in architecture changes rather than months. Tie the next review to the next material change rather than to a calendar, and record which changes trigger it so the trigger is not a judgement call under schedule pressure. A system reviewed annually that ships monthly has been reviewed once and changed twelve times.

Keep the previous finding list and compare. The value of a second review is largely in what the first one found and whether it stayed fixed, and the comparison is what distinguishes a programme from a series of documents.

Reporting upward

Report the defect count by severity, the age of the oldest defect and the count of accepted risks past expiry. Those three fit in a sentence and they are what an executive can act on. A maturity score or a heat map invites discussion of the scale rather than of the systems, and it is the most common way a security review produces no change.

Making the review repeatable

A review that depends on one reviewer is a review that stops when they leave. Write the question set down, keep the evidence templates with it, and have a second engineer run a review of a small system against the same set. The comparison between the two reports is the calibration, and it is the only way to know whether the questions are producing consistent findings rather than consistent prose.

Store the reports with the defects and the acceptances, so the history of a system is one folder rather than a search. When an examiner asks what changed after the last finding, the folder answers, and the answer is a dated list rather than a recollection.

Review the question set annually against the incidents that actually occurred. A question set that has never changed is a question set that has stopped learning, and the incidents are the only honest input.

What an examiner reads first

The first document examined is usually the risk analysis, and the second is the list of findings with their dates. If the two disagree about what the estate looks like, the disagreement is the finding that consumes the review. Keeping them generated from the same inventory is the cheapest way to keep them consistent, and the inventory is the artefact that both depend on.

Where a finding was closed, keep the retest result with the date. A closure without a retest is a claim, and the claim is what the reviewer will test first because it is the easiest thing to check.

Comparing reviews over time

The useful comparison is between the current finding list and the previous one, not between two maturity scores. A finding that has reappeared is a process defect in remediation; a finding that persists is a decision not taken. Both are visible in a two-column comparison and invisible in a score, which is why the comparison is worth keeping even when the reviews are informal.

Track how long each finding took to reach closure. The median is the remediation rate, and it is the number that predicts whether the next review will find the same things again.

The review should also record what it did not cover, with a reason. An explicit exclusion is defensible and an omission is a finding, and the difference is a sentence written at the time.

Finally, keep the review's evidence pack with the report. When the finding is challenged a year later, the configuration export that supported it is the answer, and it is almost never retained.

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 — security architecture review — 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

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.

TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh