Compliance guides

What the frameworks ask of your inbox.

No product makes you compliant. Every framework still requires technical controls, and email is where most incidents start. These guides map each obligation to the control and the evidence.

Guides by framework

CybersäkerhetslagenSweden’s Cybersecurity Act (SFS 2025:1506): who is covered, the security measures, incident reporting to FRA, and where email fits.Read
DORADORA ICT risk management, major-incident reporting and third-party risk, mapped to the email layer, plus what a DORA buyer should ask Sentaro.Read
EU AI ActEU AI Act deployer duties after the 2026 Omnibus: AI literacy, prohibited practices, transparency and high-risk dates, and why shadow AI makes them hard.Read
GDPREmail security under GDPR: Article 32 security of processing, the 72-hour breach clock in Article 33, and Sentaro as your processor.Read
ISO 27001 and SOC 2Which ISO/IEC 27001:2022 Annex A controls and SOC 2 Common Criteria email security evidences, and Sentaro’s own certification status.Read
NIS2What NIS2 Article 21 and Article 23 ask of the email layer, and the control, evidence and detection Sentaro supplies.Read
NIS2 incident reportingThe NIS2 24-hour, 72-hour and one-month reporting workflow, step by step, and the evidence email detection supplies at each step.Read

Putting the controls in place

The guides explain what each framework asks. The solution page covers the control itself.

Email security for compliance teamsThe email-layer control, continuous evidence and incident detection that NIS2, DORA, SOC 2, ISO 27001 and GDPR ask for, with a guide per framework.Read

See what it catches on your own traffic.

Connect Microsoft 365 or Google Workspace over API in about four minutes.

Speak to sales Start free