Skip to content
Anchorage from the coastline, Chugach mountains behind the city

Anchorage, Alaska

IT and security for shops that don’t have an IT department.

Zero Trust is a one-person, veteran-owned practice. You work with Chris — not a ticket queue — on support, hardening, and access that is verified every time.

“I do not trust the internet, and neither should you.”

— Chris — Zero Trust

Based in

Anchorage

Practice size

One person

Veteran-owned

Retired U.S. Army Cyber Defender

The model

Trust is earned, not assumed

How it works

Talk. Scope. Do the work.

  1. 01

    Talk

    A real conversation about how you work, what’s already in place, and what actually hurts. No discovery theater.

  2. 02

    Scope

    A short written plan: what I’ll do, what it costs, and what you will be able to see when it’s done.

  3. 03

    Do the work

    You work with me — not a queue. When something breaks later, you still know who to call.

A small office network rack with neatly dressed cables

Self-check

Five questions before we talk.

Honest answers, no scoreboard for its own sake. The point is to see where implicit trust is still doing the work that controls should do.

Five questions

A quick posture check

0/5 answered

  1. 01Is multi-factor authentication required on email and admin accounts?

  2. 02Do you know who has administrator access — and can you name why each person has it?

  3. 03Have you restored a backup in the last 90 days, not just taken one?

  4. 04When someone leaves, are their accounts and vendor logins cut the same day?

  5. 05If ransomware hit tonight, is there a named person and a first-hour plan?

Chris on a snowmachine in the Alaska mountains

Anchorage, on purpose

Local when it matters. Remote when that’s enough.

On-site work stays in Anchorage. The Valley is case by case. Consults, assessments, and project work happen remote so I can keep this a one-person practice — not a travel schedule. Same timezone. Same weather. No flying in from Seattle to bill you for the flight.

Read the approach

Questions

Straight answers.

Why is it called Zero Trust?+

It is a security model, not a warning about my character. The old idea was that people inside the office are safe. That was never true on a laptop, a shared password, or a guest Wi-Fi. We assume nothing is allowed until we check. The slogan is the translation: I do not trust the internet, and neither should you. You should not have to take my word for it either — you get the work in writing.

Do I need a retainer?+

No. Many clients start with a scoped project — a hardening pass, a Microsoft 365 cleanup, a backup that can actually restore. Retainers exist for shops that want an ongoing pair of hands. We decide that after the first conversation, not before.

Do you travel?+

On-site work is Anchorage. The Mat-Su Valley is case by case. Consults, assessments, pentests, and project work are remote unless a local visit is actually required. I do not take jobs that mean flying to Fairbanks or the rest of the state.

Are you a large MSP?+

No. Zero Trust is one person on purpose. You get Chris, not a tier-1 queue. That means capacity is finite. If I’m not the right fit or I’m booked, I’ll say so.

What if we already have IT help?+

That’s common. I can sit alongside an existing provider, a part-time staffer, or a vendor who set things up years ago and left. The goal is a clearer picture and fewer implicit trusts — not a turf war.

Do you sell software or hardware?+

I recommend tools when they earn their place. I don’t run a product quota. If a free control does the job, that’s the recommendation.

Start with a conversation.

Tell me what’s in place and what’s failing. I’ll tell you if I can help — and if I can’t, I won’t waste the hour.