vulnerability · remediation · evidence
Charles Trinh — Vulnerability Management, Las Vegas NV

Finding, triaging and actually closing vulnerabilities in a regulated estate: coverage, severity against exploitability, remediation windows and the evidence trail.
Coverage before tooling
A scanner that covers eighty percent of the estate produces a confident number that is wrong.
Enumerate assets first, including the ones nobody has scanned because they were temporary.
The unmanaged asset is the finding, not the CVE list.
Severity versus exploitability
CVSS alone produces a list sorted by anxiety rather than by risk.
Combine severity with exposure, exploit availability and whether the component is reachable.
Document the triage logic, because it is the part that gets questioned.
Remediation windows
Publish windows by severity and actually meet them, or the policy becomes decorative.
Track the exception explicitly with an owner and an expiry.
The metric that matters is median time to close by severity, not total open count.
Patching in clinical environments
Some systems cannot be patched on demand, and the constraint is usually a vendor certification rather than the operating system.
Compensating controls, segmentation and monitoring are legitimate answers if recorded as such.
Pretending the constraint does not exist is how patches get deferred indefinitely.
The evidence trail
For each closed item: what was found, when, what was done, who verified and when.
A dashboard showing zero open criticals proves nothing without that trail.
Keep it exportable, because it will be requested.
Exceptions and risk acceptance
A formal acceptance with a name, a reason and an expiry is a control.
An accepted risk without a date is a decision nobody will revisit.
Review acceptances monthly, because they accumulate quietly.
Dependency and container scanning
Image layers contain the majority of real findings in containerised estates.
Pin base images and rebuild on a cadence rather than patching in place.
Track base image age as a first-class metric.
What I do
I build coverage inventory, triage logic, remediation windows and the evidence export.
I do not sell scanning; I make the output actionable and defensible.
The deliverable is a weekly list with owners and a monthly trend that survives scrutiny.
Reporting that changes behaviour
Report median time to close, exception count and oldest open critical.
Total open count invites arguments about severity rather than action.
Two numbers, trended monthly, are enough.
Where to start
Reconcile your asset inventory against what the scanner actually sees.
The difference is the first project and it is usually larger than expected.
Everything else improves once coverage is honest.
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.
Mean time to close, honestly measured
Time to close measured from discovery is easy to game by discovering late, so measure from the date the package was published.
Report the median and the oldest item rather than the average, because one neglected critical can hide inside a mean.
Publish the trend monthly, and treat a flat trend as evidence that the window is aspirational.
Compensating controls that are real
Segmentation and egress filtering genuinely reduce exploitability; a note saying the system is behind a firewall does not.
Record the compensating control, the mechanism and the test that proves it, and review it at the next cycle.
When the vendor finally ships a patch, the compensating control is retired deliberately rather than forgotten.
Inventory drift
The estate changes between scans, and the difference between the inventory and the scanner's view is the exposure.
Reconcile monthly against cloud APIs and the hypervisor rather than against a list somebody maintains.
Every asset without a scanner tag is a finding with a name, and the name is the team that created it.
Severity in context
A critical in a library that is never loaded is a different decision from a critical in the authentication path.
Carry reachability in the triage, and record the reasoning for anything deferred.
The record is what makes a deferred critical defensible rather than invisible.
Vendors and the upgrade treadmill
Clinical systems lag on patching, and the lag is contractual rather than technical.
Ask for the vendor's patch cadence and support window at purchase, and record both in the register.
Where the windows do not align with yours, write the compensating control rather than the exception.
Reporting to people who do not read reports
One number, one trend and one named owner is what survives an executive agenda.
Report median time to close and the oldest open critical, and name the system it sits in.
Everything else is available on request and should not be presented by default.
The queue is the product
A weekly queue with owners, dates and severity in context is what turns scanning into remediation.
Every item carries the system, the owner and the decision, and nothing sits in the queue without one.
Items without an owner age indefinitely, and the ageing is visible in the oldest-open metric before it is visible anywhere else.
Closing the loop
Closing means verified rather than patched, and verification is a rescan or a query that shows the package version changed.
Record the verification with the closure, and sample the closures each month.
An unverified closure is a number that improves while the exposure stays where it was.
Making remediation a schedule rather than a hope
The difference between a vulnerability programme that works and one that reports is whether each open item sits in somebody's calendar. A queue without dates is a list of intentions; a queue where every item has an owner and a target date is a schedule, and a schedule can be interrogated. The weekly conversation should be short because it only covers items that are late or disputed, and long only when the triage logic is being challenged, which is the conversation worth having.
Triage disputes are the healthiest signal in the programme, because they mean severity is being read in context rather than copied from a scanner. The disputes should be recorded with the reasoning, since the same debate recurs with each new item of the same class, and a recorded decision turns a repeated argument into a rule. That record is also what an examiner reads when asking why a critical remained open for six weeks while a medium was closed in two days.
The final element is the monthly view for whoever owns the risk. Two numbers, the median time to close by severity and the age of the oldest open critical, with the system named. A flat trend over three months is evidence that the published windows are decorative, and the fix is either a resourcing decision or a change to the policy, both of which are decisions somebody can make. Reporting the total open count instead invites a conversation about severity and produces no decision at all.
What to do when the fix is not available
A finding with no vendor patch needs a decision rather than a queue entry, and the decision should be recorded where the next reviewer will find it. The options are narrow: remove the component, isolate it until the patch arrives, monitor it more closely, or accept the exposure with a date. Choosing one and writing it down converts an open critical into a managed risk, and leaving it in the queue undecided converts it into a number that grows older every week without anybody noticing until an examiner asks.
Isolation is the option most often available and least often used, because it requires somebody to map the network path and confirm the component cannot reach the data. That mapping takes an afternoon and produces a compensating control that is testable, which is worth more than a hope that the vendor ships soon. The test is straightforward: attempt the path and confirm the refusal, then repeat it when the patch finally lands and the control is retired.
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 — vulnerability management, 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.