LINUX HARDENING

Linux and systemd Hardening, Las Vegas NV

Linux and systemd Hardening, Las Vegas NV — Las Vegas NV
Linux and systemd Hardening, Las Vegas NV

Baseline hardening for systems that carry clinical traffic: unit-level isolation, least privilege, patch cadence, and the audit trail that proves it.

Baseline before tuning

A documented baseline that every host meets is worth more than a sophisticated configuration on half of them.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Unit-level isolation

systemd gives you sandboxing per service; using it converts a compromised process into a contained one.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Least privilege in practice

A service account with a shell and a home directory is an account waiting to be used as a foothold.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Patch cadence and evidence

The patch policy is a schedule; the evidence is the list of hosts and the date each was last patched.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Authentication and access

Key-based access, no shared accounts, elevation logged with a reason and a name.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Logging and retention

Local logs that rotate away before an investigation are logs that never existed.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Configuration drift

Drift is normal and must be detected rather than prevented; the control is the diff, reviewed on a schedule.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

Restore, not backup

An untested restore is an assumption; the drill result is the control.

In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.

Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.

The baseline is the control

A documented baseline that every host meets beats a sophisticated configuration on half of them. The question an auditor asks is not what the hardest host looks like; it is how many hosts deviate and how you know.

Drift is normal and should be detected rather than prevented. The control is the diff, reviewed on a schedule, with an owner for each deviation and a decision to accept or correct it.

Patch cadence is a schedule; the evidence is the list of hosts with the date each was last patched. A policy without that list cannot be distinguished from an intention.

Unit-level isolation is free and rarely used

systemd can sandbox a service per unit: restricted filesystem view, no new privileges, private temporary directories, a read-only root for services that do not write there. Using it converts a compromised process into a contained one, and the cost is a handful of directives.

Service accounts deserve the same treatment. An account with a shell and a home directory is a foothold; one with a dedicated UID, no shell and no writable paths outside its data directory is a boundary.

Logs that rotate away before an investigation are logs that never existed. Ship them off-host, retain them for the window the business needs, and prove the retention by querying for something old.

Access that leaves a record

Key-based access, no shared accounts, and elevation that is logged with a reason and a name. The shared root password is the finding that appears first in every review of a small estate, and it exists because it was once convenient.

Break-glass access should exist and be loud: a documented path, a recorded reason, an automatic expiry and a review afterwards. An organisation with no emergency path invents an informal one, and the informal path never appears in the log.

Test the revocation: remove a user, confirm their key fails on the next attempt rather than at the next audit. A revocation that takes effect at review time is not a revocation.

Patch management that survives an audit

The policy is a cadence and a risk classification; the evidence is a list of hosts with the date each was last patched and the exceptions with their owners. The list is what an examiner reads, and a policy without it cannot be distinguished from an intention.

Automate the patch and alert on the host that has not reported. A fleet patched by hand is a fleet with one host permanently three releases behind, and it is always the host nobody remembers.

Reboot deliberately. A kernel update that waits for a maintenance window nobody schedules is a vulnerability with a date attached, and the window should be written into the runbook rather than negotiated each time.

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. Las Vegas, Nevada 89101.

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 linux and systemd hardening, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the Cloud and Operations 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

Available for architecture review, conformance work and fractional leadership. Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more.

Talk to Charles

702-559-3489 · charles@trinh.io

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
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

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.