Layered controls for access, integrity, and long-term resilience.
NSATS Mail applies a layered security architecture that focuses on encrypted access, sender authentication, abuse prevention, and an approach designed to adopt post-quantum cryptography as standards evolve. This page summarizes how security controls are applied across the service.
Security layers
Email security is implemented as complementary controls. Each layer addresses a specific class of risk.
Encrypted access (SSL/TLS)
All connections to NSATS Mail are protected using SSL/TLS encryption. This secures credentials and mailbox traffic while in transit between user devices and NSATS Mail systems.
Post-quantum security architecture
The service is designed to adopt cryptographic methods intended to remain robust as future computing capabilities evolve. This reduces long-term dependence on a single generation of cryptography.
Sender authentication
DKIM and DMARC support domain-based sender verification, helping recipient systems distinguish legitimate mail from spoofed or impersonated messages.
Operational security controls
In addition to cryptographic protections, NSATS Mail applies operational controls that support reliability and abuse prevention.
Spam filtering
Automated filtering reduces unsolicited and malicious messages before they reach the inbox. Filtering is applied continuously to maintain mailbox integrity.
Anti-abuse enforcement
Acceptable-use policies and automated monitoring are enforced to prevent misuse, including unsolicited bulk sending, account compromise, and automated abuse.
Service continuity
Security controls are designed to remain active across infrastructure upgrades and cryptographic transitions, supporting continuity of protection over time.
Security scope and limitations
This section clarifies how security is applied and where responsibility boundaries exist.
What is protected
Account access in transit, mailbox traffic in transit, sender authenticity signals, and service-level controls designed to reduce abuse, spoofing, and impersonation attempts.
What is not implied
Security controls do not imply immunity from all threats and do not guarantee protection beyond the scope of the controls described on this page.
User responsibility
Users remain responsible for password hygiene, device security, and compliance with acceptable-use policies. Account protection depends on both service controls and user practices.