Frequently Asked Questions
Security & Protection
Will MTE protect us if the network is already compromised?
Yes — that’s the specific problem MTE was built for. Traditional security assumes the network can be trusted; MTE assumes it cannot be. Every payload is protected before it enters the network, so a compromised router, an intercepting proxy, a malicious insider, or a hostile network segment changes nothing about whether the data is readable. Intercepted data is rendered unusable at the point of capture.
What happens to the data if someone intercepts it?
It becomes useless. MTE replaces sensitive data with one-time, self-verifying tokens. There is no key to steal, no session to hijack, and no ciphertext that can be harvested and decrypted later. An attacker who captures the traffic holds data they cannot read, reuse, or replay.
Does MTE protect against “harvest now, decrypt later”?
Yes. This is one of the threats MTE was designed around. Because the data is protected with one-time tokens rather than long-lived keys, captured traffic has no value to an adversary holding it for future decryption — even a future quantum machine.
What about data at rest?
Eclypses protects data in transit, complementing mature data protection at rest controls from major ERP application and storage vendors.
Does MTE replace our existing security stack?
No, and it isn’t designed to. MTE operates underneath the tools you already run — including Zscaler, CrowdStrike, and Palo Alto Networks — protecting the data payload those platforms cannot reach. Customers add MTE without replacing a vendor or re-architecting their perimeter.
How strong is your encryption ?
Eclypses leverages the latest quantum-resistant algorithm from NIST, now standardised as FIPS 203 + the Eclypses Cryptographic Library is certified to FIPS 140-3.
Performance & Integration
Will MTE slow us down?
No perceptible impact. Current MTE Relay performance averages around 1ms latency on benchmark infrastructure under heavy load, representing roughly a 90% latency reduction versus earlier releases. It operates natively at the application layer rather than adding an encryption wrapper on top of the transport stack.
What extra network overhead and latency is there ?
Eclypses generates a stream of micro-tokens rather than encrypting monolithic data files, creating less overhead than traditional encryption schemes. There is also minimal latency in network transmission for data protected with Eclypses: ~1-2 ms, typically imperceptible to a human.
Will it break what we already run?
MTE is delivered as a containerized deployment — a sidecar or relay layer alongside your existing services. It does not require changes to your back-end systems, network configuration, or transport protocols. For environments where even minimal relay latency is undesirable, MTE can be embedded directly into the application.
How much integration effort is required?
Substantially less than a typical security deployment. Our upcoming ezMTErelease reduces integration from roughly 70 functions to 11, with standardized interfaces across 11 language platforms. Both ezMTE and MTE Relay run on the same FIPS 140-3 validated cryptographic core.
How does it scale?
Deployment scales horizontally via Docker and Kubernetes. A representative production topology we support — a public-facing banking API handling 15–20 million requests per month — runs on an initial cluster of 10 containers, with the same architecture extending to hyperscale.
Does it work in our cloud environment?
Yes. MTE is available through the AWS, Azure, and Oracle Cloud marketplaces, with Google Cloud Marketplace generally available. It is also deployable to on-premises and air-gapped environments.
What additional infrastructure is required to protect data with Eclypses?
Eclypses scales horizontally with the infrastructure of the asset it is protecting, is natively containerised and operates from a minimal footprint in a modern microservices environment.
Can I protect data for Operational Technology with Eclypses?
Eclypses scales from the core to the cloud and can be installed to protect data in minimised PLC environments.
Compliance & Audit
Can we prove to an auditor that we did this correctly?
Yes, and the evidence is built into the product rather than assembled after the fact. MTE is validated to FIPS 140-3 by an independent NIST-accredited testing laboratory, and is aligned with ML-KEM / FIPS 203, the NIST post-quantum standard. Each deployment emits cryptographically signed, tamper-evident log records — supporting audit trails aligned with FedRAMP, HIPAA, GDPR, and the EU AI Act without manual reconstruction.
Does MTE address the recent federal post-quantum mandates?
Directly. MTE uses ML-KEM (FIPS 203), the standard named in the June 2026 Executive Order on advanced cryptographic attacks, and is already deployed in production within a federal agency. It supports cryptographic agility, which is increasingly a stated requirement rather than a preference.
Is there a reference customer we can speak with?
Yes. MTE is in production at the U.S. Department of Transportation / NHTSA, protecting a designated High Value Asset. Following deployment, that application went from thousands of detected vulnerabilities to zero on the agency’s detection scans. The NHTSA CISO has confirmed his team is available to discuss their testing outcomes and use cases directly with prospective customers.
What compliance frameworks does MTE support?
FedRAMP, HIPAA, PCI DSS, SOX, SOC 1 & 2, ISO 27001, GDPR, CMMC, and the EU AI Act. Because MTE reduces key management overhead, it also tends to simplify compliance scope rather than expand it.
How do I contact Eclypses?
The Eclypses team can be reached by emailing contact@eclypses.com.
