We Travel PC

Security is the foundation,
not a feature.

We Travel PC is a security-first technology partner in Fargo, North Dakota. This page explains how we protect the businesses we serve, and how to reach us if you find something we should know about.

The baseline: layered protection

No single product stops everything, so we do not rely on a single product. Every layer below is table stakes in the environments we look after. If a provider stops here, they are selling you the checklist.

Email protection

Inbound mail is screened for phishing, impersonation, and malicious attachments before it reaches an inbox. Our own domains enforce strict sender authentication so no one can convincingly pretend to be us.

Web and DNS filtering

Malicious and lookalike sites are blocked at the DNS layer, before the page ever loads. It is quiet protection that works everywhere a device goes, not just in the office.

Endpoint detection, watched 24/7

Every protected computer runs detection tooling backed by a round-the-clock security operations team. If something suspicious happens at 3 a.m., it gets looked at, at 3 a.m.

Identity and multi-factor

Multi-factor authentication is our baseline, not an upsell. We review sign-in policies regularly and close the gaps that attackers actually use.

Patching and updates

Operating systems and the software on top of them are kept current on a schedule, with reporting to prove it, so known vulnerabilities get closed instead of collecting dust.

Backups that restore

Nightly, encrypted, and periodically test-restored. A backup you have never restored from is a hope, not a plan.

Where we go past the baseline

This is the part that does not fit on a checklist, and the reason clients stay.

Attacks get investigated, not just deleted

When a serious phishing attempt targets someone we protect, blocking it is the start, not the end. We trace where it came from, how it was built, and who else was in its path, then turn the findings into an anonymized case study. Every business we serve gets smarter from an attack on any one of them.

Identity, graded over time

Most break-ins today are sign-ins with stolen credentials, not hacks. So we map how every account in an organization can be signed into: where multi-factor is thin, which legacy doors are still unlocked, which exceptions have outlived their reason. Then we close the gaps and keep score over time. The industry calls this identity security posture management. We call it knowing where the keys are.

Logs that actually get read

Sign-in and activity logs from the environments we protect are collected centrally and reviewed by a person, not just stored. When something odd happens, we can answer what happened, when, and from where, with evidence. That is the difference between an incident report and a shrug.

A person in your corner

There is no tier one, no call center, no "your ticket has been escalated." When something matters, you talk to Michael: the same person who set up your systems, reads your alerts, and actually knows your business. The protection itself never sleeps. The layers above run around the clock, and a 24/7 security operations team watches every protected computer regardless of who is on vacation.

It is also a quiet security advantage. Fewer hands in your systems means fewer doors into them. Access is one accountable person you know by name, not a rotating bench of technicians. And we have run cloud-first for years ourselves, with no aging server in a closet, living by the same rules we set for the businesses we protect.

Hacked, and not sure who to call?

If your business has been hit by ransomware, a compromised email account, a drained bank account, or anything that feels wrong, reach out. The first conversation is free, whether or not you ever become a client. No contract, no sales pitch, no judgment.

We will help you understand what likely happened, what to do in the next 24 hours, and who else you may need to involve. Bad days are easier with someone calm who has seen this before.

michael@wetravelpc.com · or reach us through wetravelpc.com

Don't take our word for it

Security claims are cheap, so here are ours in a form you can check. Run any of these from your own machine against this very domain.

dig TXT _dmarc.wetravelpc.io +short
"v=DMARC1; p=reject; ..."
Mail pretending to be us is rejected outright, not filed in spam.
curl -sI https://wetravelpc.io | grep -i strict
strict-transport-security: max-age=31536000
Browsers are told to only ever speak HTTPS to this domain.
curl https://wetravelpc.io/.well-known/security.txt
Contact: mailto:michael@wetravelpc.com
A standard, machine-readable way to report a vulnerability (RFC 9116).
dig TXT wetravelpc.io +short | grep spf
"v=spf1 ... ~all"
Only servers we authorize may send mail as this domain.

Already with us?

Your client portal has your invoices, coverage, and reports in one place, behind multi-factor sign-in. Same security standard we describe on this page.

Sign in to the portal →

Thinking about working with us?

We keep our client list intentionally small. Most of the businesses we protect have been with us for years, and new ones usually arrive by referral.

The first conversation is about fit. We want to understand how your business runs, what worries you, and whether we can genuinely make things calmer and safer. If we are not the right match, we will tell you straight and point you in a good direction.

Start with an email: michael@wetravelpc.com, or say hello at wetravelpc.com.

Found a security issue?

If you believe you have found a vulnerability in one of our systems or a website we operate, we want to hear from you, and we will treat a good-faith report with respect and urgency.

Email michael@wetravelpc.com with enough detail for us to reproduce the issue. Please give us a reasonable window to fix it before sharing it publicly, and do not access, alter, or retain data that is not yours. We will not pursue action against research conducted in good faith within these guidelines.

You will hear back from a person, usually within one business day. Machine-readable details live at /.well-known/security.txt, per RFC 9116.