SECURITY

Charles Trinh — Security Awareness Training Programme | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading SECURITY AWARENESS — role-based content, realistic phishing and measured behaviour change
Charles Trinh — Security Awareness Training Programme

A training programme that satisfies a checklist is not the same as staff who recognise the errors that actually reach them. I build training around the phishing and handling patterns a healthcare organisation really encounters, with measurement that changes behaviour and not just completion.

Completion is not competence

Most healthcare organisations can produce a completion rate of 98 per cent for annual security training and still have staff who click a phishing email claiming to come from the billing office. Completion measures that the content was assigned and the course opened. It does not measure whether anyone would act differently when a real email arrives on a busy Tuesday. The gap between those two things is where the programme has to be measured.

The controls I build are measured by behaviour: the rate at which simulated messages are clicked and reported, the share of staff using MFA on their accounts and the time to report a suspicious email. Those numbers say more about risk than a completion percentage, and they can be tracked month on month. I put them in front of leadership alongside the completion rate, so the difference becomes visible.

The content is role-based, because a clinician in a patient portal, a biller handling payer emails and an executive handling board materials face different risks. One module for everyone is the cheapest training to buy and the least effective to operate. The programme is built from a handful of targeted modules assigned by role, with a short core everyone completes in the first month.

Content matters less than the examples

Staff dismiss generic awareness modules that talk about passwords and padlocks. What works is material in the organisation's own language, about its own services and vendors. A simulation mimicking a real payer portal or a real EHR notification tests behaviour against the exact message a staff member would see in the wild. The sender domain and the formatting are as important as the message itself.

I choose examples from incidents and close calls inside the organisation or its peer group, with identifiers removed. Real events make the risk concrete, and the sanitised story stands on shared understanding more than a thousand slides of abstract threats. The person who clicked the simulation and reported it afterwards becomes a better teacher than a vendor-produced video, provided the atmosphere is safe.

The content is short. A module of five minutes ending with one clear behaviour to change gets remembered; a forty-minute mandatory course is clicked through while the reader does something else. I write the modules myself, test them on a few real staff members and rewrite anything that invites the response that this is obvious and a waste of a working morning.

Phishing simulation with an ethical boundary

Phishing simulation is a control, not an opportunity to trap people. I design simulations testing a specific behaviour, varied enough not to be recognised by pattern and never used to punish anyone. The objective is to create a reporting reflex and to identify the services and messaging patterns the organisation should audit more closely. Any simulation that targets an individual by name or role for retribution is out of bounds.

The programme runs at a pace staff do not resent. Fortnightly simulations are common in mature organisations and monthly is usually enough for a small one. Each round is followed by a short debrief, covering what happened and what to do next time, delivered to people who clicked and, in sanitised form, to the whole organisation. The debrief turns a click into a learning event rather than a badge of shame.

Click rates fall over time and then plateau. The plateau is where the programme needs to change the content, the channel or the underlying control, such as a phishing-resistant MFA on the account the simulation targets. Reporting rates should keep rising; a fall in reporting is a sign the programme has become background noise and the people are simply ignoring the simulation.

Training that supports the controls it depends on

Awareness is part of a control set, not a standalone activity. If staff are trained to spot suspicious links and the email gateway does not warn them, the programme is relying on a human control that should have a technical partner. I help reduce that reliance by adding email authentication, link protection and MFA, and the training then explains what those controls do. Training on top of strong controls is a multiplier; training instead of controls is a liability.

Where the organisation has a security risk analysis, the training plan references specific risks on the register. If the register says misconfigured storage is a risk, the training includes the sharing pattern that leads to it. Training that mirrors the register is more defensible and more useful than a generic compliance module, and it survives the question of why a particular module was chosen.

I also train the access and incident-reporting behaviours: who to call, what to preserve, how to report a suspected incident and what not to do to the evidence. Staff trained to preserve the wrong thing create hours of rework for the incident team. A short list with the internal numbers on a card is more effective than a paragraph buried in a policy document.

Measurement that actually changes the programme

I set up a simple dashboard: completion rate, phishing click rate, phishing reporting rate, average report time, help-desk tickets tagged as suspected phishing and failed logins per user. Each has a target and an owner. The programme is reviewed quarterly against those numbers and the next quarter's content adjusted accordingly. A dashboard nobody reviews is not a control, so the review is scheduled and minuted.

The reporting side is often the weak link. Staff who report a suspicious email and get no response will stop reporting. I help define the response process, including an acknowledgement the reporter sees, so the feedback loop stays intact and people trust the channel enough to keep using it. A quick reply from a named person is the cheapest way to keep reporting rates up.

Some staff need a second channel. Clinicians on shared workstations, front-desk staff handling records orally and staff in remote offices sometimes need differently formatted content. The programme accommodates them rather than sending the same module to everyone. The clinic notice board and the shared workstation login screen are two places where a one-page reminder reaches people the email campaign never does.

Procurement and contract language for training vendors

Many organisations buy awareness content from a vendor, and the contract shapes what the programme can do. I review the licence terms for simulation, the rights to modify content and the data it collects on staff behaviour. A platform that keeps click data in its own cloud and exports only summaries deprives the organisation of the data it needs to measure the programme. The organisation should own its behavioural data at the same standard it applies to any other ePHI system.

The content rights matter as much. A vendor that allows the organisation to edit modules and mix its own scenarios gets a better programme than one that locks the library. The organisation's own phishing patterns, its own vendor notices and its own clinical vocabulary are what make training effective, and the contract should allow their use. A licence prohibiting editing is a licence to buy a generic product rather than a training programme.

The exit terms are the third concern. Training history is employee performance data under many state and employment rules, and it often needs to be retained. A vendor that deletes the history on termination can leave the organisation unable to show that a departing employee was trained at the time of an incident. I write the export and retention obligations into the contract and test the export before the relationship ends.

Why year two goes quiet

The first campaign works because the content is new. In year two staff recognise the pattern, the simulations stop being interesting and the click rate plateaus or rises. The year-two failure is treating a plateau as a ceiling rather than a signal. I change the simulation themes, the channels and the timing, and I move the organisation from generic awareness to specific risk patterns that staff have not seen. A programme repeating the same campaign in year two wastes its budget.

The other year-two failure is staff turnover. New staff arrive and the onboarding includes the compliance module but not the campaign. By mid-year the newest employees are the highest-risk group and appear in the click data without anyone noticing the cause. I connect the training programme to onboarding so every new starter receives the campaign and is enrolled in the simulation cycle from their first week. That integration is the largest measurable improvement in most programmes.

Finally, the sponsor changes. A programme that relied on one executive's attention rarely survives their departure. I write the programme's charter with role-based ownership so it transfers to whoever holds the role, and I report results to a standing committee rather than to an individual's inbox. The committee becomes the programme's institutional memory when the people change, the budget is renegotiated and the campaigns move on to their next cycle.

Programme ownership and renewal

A training programme needs an owner. In mid-sized healthcare that is often the compliance officer or the head of information security. I write the owner's responsibilities: setting targets, approving simulations, reviewing results and deciding whether a staff member needs additional training. I also draft the policy text, so HR and security agree on what happens after repeated clicks and nobody invents a sanction on the day.

Annual refresher training remains required by HIPAA, and I integrate it into the ongoing programme rather than treating it as a separate event. The owner is left with a calendar, the course content, the simulation schedule, the dashboard and a one-page summary for leadership. The calendar is the artefact that keeps the programme from becoming an annual scramble and it is the first thing a buyer asks to see.

For small organisations the programme is often the best value control they have, because well-informed staff catch the mistakes no tool would. It pairs naturally with Linux systemd hardening, which reduces the attack surface the training is meant to guard against. The deliverables are the role-based modules, the simulation programme, the reporting workflow and the dashboard, each with an owner and a target.

The evidence pack an assessor opens

HIPAA training evidence is usually a spreadsheet of names and dates, and it rarely answers the question an assessor actually asks. The assessor wants to know that staff received training, understood it and that the organisation measured the result. I assemble a pack with the course completion, the simulation results per campaign and the reporting rates over the year, so the programme is visible rather than summarised in a percentage.

The pack also shows what happened after the training. If the click rate fell and the reporting rate rose, that is evidence the programme changed behaviour. If completion is 100 per cent and the click rate is unchanged, the pack says so honestly, because an assessor will spot the gap underneath the number and the explanation is better given in the pack than during an interrogation.

The pack is kept per role as well as overall, because a clinician's risk differs from a biller's. An assessor who sees that the highest click rate is in the newest cohort can be shown the onboarding fix that addressed it. That narrative, present in the evidence, is the difference between a compliance record and a programme someone is running.

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 awareness training programme — 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