Skip to content
VETERAN-OWNED · NEBRASKA-BASED
IT professionals working on laptops in a dim collaborative workspace

Email security for the attacks that actually land.

Email security for Lincoln and Omaha: most Midwest businesses don’t lose money to exotic zero-days — they lose it to phishing, business email compromise, and mailbox takeovers. SAINT hardens Microsoft 365 and Google Workspace email, layers Huntress Managed ITDR for post-compromise identity threats, runs Huntress SAT for phishing resilience, and coordinates response when something gets through. Gateway add-ons (including Check Point Avanan where scoped) are selective — not every tenant needs another logo.
BEC / account-takeover playbooks with Huntress ITDR
M365 Defender & Google phishing controls tuned, not default
DMARC / DKIM / SPF and payment-verification culture
Huntress SAT phishing simulations for your users

How we defend email

  • 01

    Tenant hardening (M365 & Google)

    Anti-phishing policies, spoofing protection, external sender tags, safe links/attachments where licensed, forwarding-rule audits, and admin consent workflows that block casual OAuth abuse.
  • 02

    Identity threat detection (Huntress ITDR)

    Catches account takeover, malicious OAuth consent, suspicious mailbox rules, and follow-through that gateway filters miss after a user is already phished.
  • 03

    Awareness that changes behavior

    Huntress Managed SAT — phishing simulations and training tied to real campaigns, not annual checkbox videos nobody remembers.
  • 04

    Authentication & DNS hygiene

    SPF, DKIM, and DMARC brought to enforcement when ready — with monitoring so legitimate mail doesn’t break when you tighten policy.
  • 05

    Selective email gateway depth

    When a dedicated email security layer is warranted, we scope it (including Check Point Avanan where it fits the engagement). We won’t stack redundant gateways without a design reason.
  • 06

    Compromise response

    Session revocation, password resets, inbox/forwarding rule cleanup, partner and bank notification guidance, and Huntress SOC coordination — generic playbooks, no drama theater.

Frequently asked

Is this only for Microsoft 365?+
No. We harden both Microsoft 365 and Google Workspace. Mixed environments are common — we treat email and identity as one risk surface.
What should we do if we suspect business email compromise right now?+
Call (531) 625-2113. Typical first moves: revoke sessions, reset credentials, audit forwarding and inbox rules, check recent mail flow and OAuth apps, then notify finance partners if payment instructions may have been altered. Do not “wait and see.”
Do you guarantee no phishing will get through?+
No honest provider does. We reduce likelihood and blast radius with layered controls, training, and fast response — and we won’t pretend a single filter makes you immune.
How does this relate to cyber insurance?+
Carriers routinely ask about MFA, email filtering, phishing training, and incident response. Our email program maps to those questions — use /tools/insurability for a self-check, then we’ll evidence the controls for renewal.
Do you always deploy Check Point Avanan?+
No. Avanan (and similar gateways) are selective — scoped when a dedicated email layer is warranted. Many tenants are better served by hardening native M365/Google controls plus Huntress ITDR and SAT. We won’t invent a “standard Avanan for everyone” package.
Is there a written playbook if we suspect compromise tonight?+
Yes — start with our public BEC first-actions guide at /blog/security/business-email-compromise-what-to-do, then call (531) 625-2113 so we can execute containment with you.
My email was hacked in Lincoln or Omaha — do you actually respond locally?+
Yes. Lincoln is a primary market (Hickman-based team, no storefront). Omaha-metro is a core service area. Suspected compromise: (531) 625-2113. If email is simply down rather than compromised, start at /it-support or /blog/operations/email-down-lincoln-omaha — outages use 531-625-2111.
What if our email was compromised or hacked?+
Treat a compromised email account, a hacked email account, or email compromised by a changed payment request as business email compromise until you know otherwise. Call (531) 625-2113. Typical first moves: revoke sessions, reset credentials, audit forwarding and inbox rules, and check recent mail flow and OAuth apps. If a payment instruction may have changed, notify finance partners out of band — not by replying to the suspect thread. Ordered steps while you dial: /blog/security/business-email-compromise-what-to-do. If mail is simply down and not compromised, start at /it-support or /blog/operations/email-down-lincoln-omaha. Outages use 531-625-2111. We do not guarantee a filter will stop every phish.
Is this different from Microsoft 365 or Google Workspace management?+
Those pages are tenant administration (licenses, identity, devices). This page is the email-threat program: BEC, phishing, DMARC, SAT, compromise response. Most clients need both — we don’t make you pick a silo.

Lincoln & Omaha — how this actually shows up locally

  • Email hacked in Lincoln, Nebraska? Outage vs compromise.

    Lincoln businesses still lose money to invoice-redirect emails and mailbox forwarding rules nobody audits. We harden M365/Google, layer Huntress ITDR, and respond when a payment request looks wrong. If Outlook simply won’t send, that’s an IT outage — call 531-625-2111. Suspected compromise: (531) 625-2113. Hickman-based; not a Lincoln storefront.

    Lincoln, NE hub
  • BEC defense for Omaha professional services and clinics.

    Omaha law, insurance, healthcare, and construction offices are prime BEC targets — lots of wires, lots of vendors. We treat email as a finance-risk system: MFA, forwarding audits, SAT, and identity threat detection. Multi-site tenants get one program, not a different filter per office.

    Omaha, NE hub

Ready to see where you stand?

Not sure where you stand? Take the free self-assessment at /assessment (NIST CSF, HIPAA, CISA CPG, FTC Safeguards, GDPR), or book a short call for a written plan. No fake certifications.

30 minutes. NIST-aligned report. No obligation.

How a job with SAINT actually starts

This page is one part of the stack. The desk behind it is the same small team for the computers, the security tools, and the building. Lincoln is the day-to-day market. Omaha is next. The rest of Nebraska is scheduled.

SAINT Technology Services is the trade name of SAINT Management Group LLC. We are veteran-owned and based in Hickman, Nebraska. There is no Lincoln storefront and no Omaha headquarters. If someone needs a person on site in Lincoln, the drive is short. Omaha is a planned trip. We say that up front so you are not picturing a downtown office we do not have.

Most of the businesses we sit with are small or mid-size: a clinic, a shop, a professional office, a contractor, a school, a city department, a plant, or a nonprofit. The common thread is that one or two people are tired of being the unofficial IT department. If you already have an IT person and you want to keep them, that is co-managed IT. We write down who owns which tickets. We do not show up to replace someone who is doing the job.

Managed IT, when that is the fit, is a monthly program: monitoring, patching, a help desk, and cloud administration for Microsoft 365 or Google Workspace when those are in scope. The rate is a documented fixed monthly number once the environment is scoped. We do not publish a sticker price on the website, because a five-person office and a fifty-person office are not the same job. The first-response target during business hours is 15 minutes. Outages and security incidents have a 24/7 line. Those are the same targets already stated on the managed IT page, not a new offer.

The help desk is for the ordinary stuff that stops a workday. A laptop that will not join the network, a shared mailbox nobody can open, a printer that quit, a new hire who needs accounts before Monday. You call (531) 625-2111 or you write the desk. If the problem is an active compromise, use the incident path on this site. Do not wait on a newsletter.

Cybersecurity on an engagement is Huntress or Guardz, not a pile of overlapping tools and not a claim that we are a certified auditor. Huntress is the 24/7 SOC path: endpoint detection, identity threat detection, log correlation, and security awareness training when those pieces are in scope. Guardz is the all-in-one path some smaller offices prefer. We pick one lane with you. Email security sits next to that, because business email compromise is how a lot of Midwest shops actually lose money: a changed bank account, a mailbox rule, a fake invoice. We look for those. We do not promise that nobody will ever click.

Physical security is the same team as the network, not a separate vendor you have to introduce us to. That covers cameras, door access, and a look at the building. Verkada, UniFi Protect, and Salient are products we deploy when they fit the site. A jobsite is a different layout than a clinic hallway, and the jobsite security page is where that scope lives. The SAINT Security Box is a custom enclosure we build when a camera needs power and protection that a catalog mount does not give you. We do not invent camera counts or coverage percentages.

Backups are only useful if someone has restored them. The backup and disaster recovery work is monitoring the jobs, keeping a copy that ransomware cannot simply encrypt with everything else, and testing a restore on a schedule you can see. 'We have backups' is not the same sentence as 'we restored a file last quarter.' If you want the checklist version of that, it is on the backup page and in the operations notes.

The network work is design and upkeep: UniFi where that is the right stack, Fortinet when you need that firewall, Wi-Fi that reaches the back office, and a diagram your next IT person can read. Business fiber, when you want it, is ALLO service we provision as an authorized agent. Availability is an address check. We do not publish carrier price lists or promise a speed. Hosted voice, Teams voice, and analog or PRI lines are quoted the same way: one ticket path, after we know the address and what you have now. Failover internet is a design for a second path. The carrier still delivers the circuit.

Website design and website management are on this site as their own pages. Domain management and domain security cover the registrar, DNS, and the locks that keep someone from walking off with the name. None of that is bundled into managed IT unless we wrote it into the scope.

Assessments and the free tools are there so you can see a gap before you buy anything. The domain security scan, the insurability check, the downtime calculator, the breach check, and the short quizzes for NIST CSF, HIPAA, CISA, the FTC Safeguards Rule, and GDPR are educational. They are not a certification and they are not a legal opinion. A security risk assessment, a physical security assessment, a vendor assessment, or a critical infrastructure walk-through is a scoped job with a written result. If a page says the work is advisory, that is what it is.

AI, when it is in scope, is governance and setup. Readiness, a written policy, vendor questions, training for the people who will actually use Copilot or Gemini, and a fractional chief AI officer when an office wants that seat part-time. We will tell you when the honest answer is to leave a feature off. We will not dress up a prompt as a transformation.

A first conversation is short. You call (531) 625-2111 or you book a time. We ask what is breaking, what you already pay for, and who has the admin passwords. Then we look. The output is a written plan: what to keep, what to fix, and what can wait. You can stay with your current provider. We would rather say that on the first call than discover it after a quote. If you want a partner to resell or refer work, that conversation lives on the partner program pages, separate from a customer assessment.

Lincoln pages are the detailed local versions. Omaha pages are the second set. If you are comparing those two, start with the city that matches the building you care about most, then open the service under it. The phone number does not change. Desk line: (531) 625-2111.

If you have more than one building, say so on the first call. A Lincoln office and an Omaha office can sit on one agreement, with the same help desk and a note about which site gets the scheduled visit. A clinic with a guest network and a clinical network is a different drawing than a single retail floor. We would rather see that before we name a tool.

Compliance language on this site is narrow on purpose. HIPAA-aligned IT for a small clinic means identity, email, backups, and a business associate agreement when we touch systems that hold patient information. It does not mean SAINT certifies you. CJIS-aware work for a city or sheriff's office means the access and logging questions in that policy, not a badge. CMMC-aware work for a shop that touches defense contracts means the control list and the evidence, not a rubber stamp. FTC Safeguards and PCI show up the same way: we implement the technical pieces we scoped, and we tell you what we did not take on.

You should leave a first call knowing three things: who answers (531) 625-2111, what is in the monthly scope, and what is a separate project. Projects are the one-time jobs: a camera install, a firewall cutover, a move, a website, a fiber order. The monthly program is what keeps running after the project truck leaves. If a salesperson ever blurs those two, ask for it in writing. We will put it in writing either way.

Bring what you already have. A list of vendors, the admin login for Microsoft 365 or Google Workspace, and a rough count of people and sites is enough to start. You do not need a network diagram. If the last IT company will not hand over passwords, say that. It happens, and it changes the first week of work more than any product choice does.

If you already know the service, use the links on this page. If you do not, start with the solutions list, Lincoln, or Omaha, then call (531) 625-2111 or book a time.