A SIEM that produces four hundred alerts a week and closes none of them is a logging bill, not a security control.
Charles Trinh designs SIEM and detection operations from Las Vegas, Nevada: source inventory, retention, alert tuning, the runbook behind each detection, and the metric that shows whether anyone acts on it.

The value of a SIEM is set by what it ingests. Identity, endpoint, network, cloud control plane and application logs each answer a different question.
A source inventory with owner, format and retention turns an expensive platform into a usable one.
Every detection needs a runbook: what it means, what to check, who decides, and what the disposition options are. Without that, the queue grows until it is ignored.
Tuning is continuous. The metric is not alert volume; it is the percentage of alerts triaged and the time to disposition.
Retention is a cost and a legal question. The design states what is kept, for how long, where, and who can search it without a ticket.
For regulated work, the same log answers the audit question and the incident question, so it must be tamper-resistant and time-synchronised.
A small team can run a managed detection service well if the sources and runbooks are right. Buying the platform and the analysts without that foundation produces the same noise, at a higher price.
The decision is about coverage hours and the ability to act, not about brand.
Detection is only half of a control; the other half is what a person does in the first ten minutes. A tabletop exercise with the real on-call roster, a real alert and a stopwatch exposes the gaps faster than any tool review.
The usual findings are unglamorous: nobody knows who may authorise taking a system offline, the phone tree points to a number that no longer exists, and the legal contact is not in the same document as the technical one.
Running it once a quarter, with the findings written down and closed, is what turns a policy into a capability. It also gives the board a defensible answer to the question of whether anyone has tested the plan.
Coverage is best expressed as a list of questions the organisation wants to be able to answer, with the log source that answers each one. If a question has no source, that is a gap with a cost, not an opinion.
It starts with a scoping call of thirty to forty-five minutes. The point is not to sell; it is to establish what decision has to be made, what constrains it, and whether this is the right kind of work for one architect rather than a team. If it is not, the call ends with a referral.
If it is, the next artefact is a written plan: scope, sequence, price and the evidence each step will produce. Nothing starts before that plan is agreed in writing, and nothing in it is a surprise later. Plans change, and when they do the change is written down with its effect on price and date.
Delivery runs in weekly checkpoints. Each one ends with something that exists: a document, a design, a working system, a test result. That is deliberate, because a programme that reports progress without artefacts is a programme that cannot be audited, handed over or defended.
Two shapes. A fixed price for a defined deliverable - an assessment, a design, a due-diligence report - where the scope is clear enough to price honestly. Or a monthly seat for continuing advisory work, with a set number of days and a standing slot for decisions.
Invoices are monthly, net fifteen, and the terms are the same for every client. There is no percentage of savings, no success fee and no commission from a vendor, because an advisor paid by the seller is not an advisor.
Nothing formal. What helps is a one-page description of the problem in your own words, the names of the systems involved, the deadline that is driving the timing, and who else has to agree before anything changes.
If a vendor proposal is already on the table, send it. Reading someone else proposal is often the fastest way to find the question nobody asked, and it costs nothing to look.
Every engagement leaves a record: the map, the decisions, the trade-offs that were rejected and why. That record is what makes a change of staff survivable, what an auditor reads, and what a buyer inspects. It is also the part most consultancies keep for themselves.
The record settles arguments. When a decision is questioned a year later, the note that states what was known, what was chosen and what it would cost to change is usually the only thing that ends the discussion.
Las Vegas organisations often have a small security function and a national provider, which makes the runbook and the escalation path the deciding factors.
Scope is a fixed number of hours per month or a defined project, agreed in writing before work starts. Every engagement carries a written plan, a weekly checkpoint, and a closing pack that states what was built, what was verified and what is left.
Charles Trinh is a Las Vegas-based technology architect and fractional CTO/CIO serving health systems, payers, enterprises and government programmes in Nevada and nationally. Every discipline below is offered in ten engagement forms - consultant, architect, advisor, contractor, specialist, expert, services, support, solutions and consulting - so an engagement can be a review, a build, a retainer or an interim role.
The full catalogue, every discipline in all ten engagement forms, sits on the Las Vegas, Nevada services index. Delivery is remote-first from Las Vegas with on-site coverage across Clark County, and the same ten disciplines carry to engagements anywhere in the United States and in 264 countries.
Serving customers in Columbus, Ohio, United States and worldwide.
Teams searching for SIEM help near Las Vegas usually have a platform and no process; the process is what this engagement builds.
No. The design and the runbooks; operation can be internal or managed.
Yes, starting with the source inventory and the alert dispositions.
Twelve months hot search is common; the requirement drives it.
Yes, control plane and data plane separately.
Four to eight weeks including runbook authoring.
trinh.io · Services · Las Vegas, Nevada · charles@trinh.io · 702-559-3489