网络安全

邮件安全

通过过滤、SPF/DKIM/DMARC 和沙箱，拦截钓鱼邮件、冒充老板或供应商的诈骗邮件 (BEC) 及恶意附件。

现场常见问题

Email is still one of the main ways in. The kind that costs the most money has no malware at all: a message that looks like it's from your supplier in Thailand or China saying "we've changed our bank account". And a domain without DMARC is easy for someone else to send as, straight to your customers.

We split the job into three layers.

1. Protect your own domain

Set up SPF, DKIM and DMARC correctly, then move DMARC from p=none to quarantine and reject based on the reports. This usually takes several weeks, because you have to find every system that sends mail as you: the accounting package, the scanner, the HR system. Skip that step and your real email gets blocked.

2. Filter inbound mail

A secure email gateway, or an API-connected service for Microsoft 365/Google Workspace, filters spam, phishing and malicious links (re-checked at click time) and opens attachments in a sandbox before users see them. Good platforms also catch link-less BEC by looking at language and sender behaviour.

3. People and process

"External email" banners, a report-phishing button, and one rule: any change to a supplier's bank details is confirmed by phone on a number you already have. That last one costs nothing and stops more of this fraud than anything else. In offices that mix Lao, Thai and English, a fake email with slightly odd wording is harder to spot.

功能

SPF, DKIM and DMARC

Set up and driven by reports all the way to p=reject.

Anti-phishing and BEC

Catches executive impersonation and look-alike domains.

Attachment sandboxing

Opens files somewhere safe before delivery.

Time-of-click link checks

Catches links that were clean on arrival and turned bad later.

Microsoft 365 / Google Workspace

Via API or MX, no change of mail platform.

Report button and clawback

Pulls a bad message out of every inbox at once.

设计与实施

1
Audit DNS, domain settings and the current mail platform
2
Turn on SPF/DKIM and DMARC p=none to collect reports
3
Connect filtering via API or MX
4
Tune policy; turn on banners and the report button
5
Move DMARC to quarantine, then reject

适用场景

Finance teams receiving invoices from Thai and Chinese suppliers
Banks whose domains get spoofed to fool customers
Government agencies that want people to trust their email is genuine
Import/export firms doing deals with foreign partners by email

常见系统规模

Domain Protect

适用于: Where every organization should start

SPF, DKIM and DMARC setup
DMARC report analysis
Turn on the security already in M365/Google

获取报价

Advanced Filtering

适用于: 20–500 mailboxes

API or gateway email security
Sandboxing and time-of-click protection
BEC protection and report button

获取报价

Complete

适用于: High-risk organizations

Advanced filtering plus phishing simulations
DMARC p=reject with ongoing monitoring
A written payment-verification procedure

获取报价

我们供货并安装的品牌

Microsoft Google Workspace Fortinet Check Point Trend Micro Sophos Cisco Kaspersky ESET Proxmox

所有品牌名称和商标归其各自所有者所有。除非另有明确说明，提及某品牌并不代表与其存在合作关系。产品均通过正规分销渠道采购。

常见问题

What is DMARC and do I need it?

DMARC tells receiving servers what to do with mail that claims to be from your domain but fails SPF/DKIM. Since 2024 Gmail and Yahoo require it of bulk senders. Every organization should have it.

Microsoft 365 already filters email. Do I need more?

The baseline protection (EOP) is reasonable. Defender for Office 365 or a third-party layer adds sandboxing, link checks and better BEC defence. For finance staff and executives, we'd add it.

How do we stop payment-fraud emails?

Technology helps, but process matters more: every supplier bank-detail change is confirmed by phone using the number already on file, never the one in the email.