siem · detection · log retention

Charles Trinh — SIEM and Log Management, Las Vegas NV

Charles Trinh — SIEM and Log Management, Las Vegas NV
Charles Trinh — SIEM and Log Management

Security monitoring in a healthcare estate: log sources that matter, retention that satisfies both security and audit, detection rules that do not drown the analyst, and the review that turns alerts into action.

Sources before rules

A SIEM with the wrong sources detects nothing useful; start with identity, endpoints, clinical application access and network egress.

Include the systems that hold PHI, because access anomalies there are the findings that matter clinically.

Ingest the cloud control plane and the backup platform; the two most damaging events in healthcare estates both show up there first.

Retention and cost

Retention must cover the investigation window and the audit window, which are often different lengths.

Tier storage: full fidelity for the security window, aggregate or cold for the audit window.

Record the retention decision and who made it, because it will be questioned after an incident.

Rules that earn their place

Every rule needs an owner, a documented rationale and a response. A rule nobody has responded to in a year is noise that trains the analyst to ignore the console.

Start with a small set of high-fidelity detections rather than a default content pack that fires hundreds of times a day.

Tune on real data: measure false positive rate per rule and retire the worst offenders.

Triage and escalation

Define what an analyst does with each alert class, and who is called when it is real.

Document the decision, including the decision that it was benign, because the pattern is the intelligence.

Measure time to acknowledge and time to decide, not alert counts.

Integrity and access

Logs must be tamper-resistant and access to them audited; an attacker who can edit logs removes the evidence.

Restrict write access to the pipeline, and keep an immutable copy for the security window.

Review SIEM access quarterly; it is often wider than intended.

Using it beyond security

The same pipeline answers availability questions and audit questions, and that is how it earns its cost.

Agree cross-team queries in advance so the data is retained in the shape others need.

Report monthly on what was detected, what was decided and what changed.

How I do it

One trace of a real case with 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.

Start from the questions, not the product

A SIEM is a query engine with a cost model, and the organisations that get value from it are the ones that wrote down the questions they need answered before they bought it. Who accessed this record, from where, at what time. Who created an account, who approved it, when was it last used. What changed in the cloud account, and who changed it. Starting from questions determines the sources, the fields, the retention and the parsing, and it produces a system that answers an investigation rather than a system that collects everything and answers nothing.

Write the ten questions that would be asked after an incident in this estate, and test that each one can be answered today in under an hour with the data currently retained. Whatever cannot be answered is the roadmap, and the gaps are usually a missing source, a missing field or a retention window that closes before the investigation begins. This test is uncomfortable for a week and it is the only honest measure of whether the investment is working, which is why it should be repeated on a schedule rather than performed once during procurement.

Detection content that survives a busy week

Every rule produces alerts and every alert consumes analyst attention, so the value of the programme is the ratio of decisions to alerts rather than the count of either. Start with a small set of detections with clear responses attached, measure the false positive rate per rule over a month, and retire the ones that never produce a decision. A rule that has never been actioned in a year is not a detection; it is noise with a signature, and it teaches the analyst to skim which is the failure mode that lets a real signal through.

Write the response next to the rule when the rule is written, because a detection without a documented action is an interesting fact rather than a control. The response should say who does what, how quickly, and what the benign explanation usually looks like. When the rule fires and the response is not obvious, that is a rule design problem rather than an analyst problem, and the fix belongs in the rule rather than in a training session. Review the detection library quarterly against what actually happened in the estate over that quarter.

The evidence angle

The same pipeline answers audit questions that are otherwise answered by a person reading a report: who accessed patient records outside their assignment, who approved a change, when was a policy modified. Building those queries in advance, and retaining the fields they need, converts a recurring audit exercise into a saved search. The organisations that do this find that the security investment is justified by the audit savings alone, before any incident happens, which is a much easier budget conversation than the alternative.

Where a control depends on logs, the log query is the evidence, and it should be dated and stored with the control. A control described as monitored while the retention is seven days and nobody has run the query is an assertion. Attaching the query result to the control, with the date it was last run and who ran it, is the difference between a policy and an artefact, and it is the difference an examiner will ask about.

The pipeline that nobody owns

The log pipeline itself is a system with availability requirements, and it fails in ways that look like nothing happening: a collector stops, a parser drops a field, a source changes its format and the events arrive unreadable. Monitor the pipeline's own health, with an alert when a source stops sending and a daily count of events per source compared with the previous week. The comparison catches the quiet failures, since a source that has stopped entirely is easy to see and a source that is sending a tenth of its usual volume is not, and the reduced volume is usually the sign of a problem at the source rather than at the collector.

Name an owner for the pipeline separately from the analysts, because the people reading alerts are not the people who notice that the ingest is degraded. That owner is responsible for the source inventory, the parsing changes and the capacity forecast, and they should be challenged quarterly on the three questions that matter: which sources are missing, which are late, and which have changed format. An organisation that can answer those three has a pipeline it can trust; one that cannot is reading alerts from an unknown subset of its estate and does not know it.

Why the query is the deliverable

The deliverable of a security monitoring programme is not a dashboard; it is the ability to answer a specific question about the estate within an hour, with evidence, for a named incident. Everything else, the sources, the parsing, the retention and the rules, exists to make that possible. Organisations that measure themselves on the number of detections optimise for a number that nobody outside the team understands; organisations that measure on questions answered in time can show the board exactly what the investment bought.

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 — siem and log management, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the AV and IT Infrastructure 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