Secure Messaging

Learning Center

Back to top

Search Results


This page includes answers to common FAQs around installation of and hosting a Secure Messaging portal. If your question is not answered here, try reviewing the documentation available on this site. If your question is still unanswered, please contact Secure Messaging support:

Where is the Secure Messaging Platform webapp hosted?

The Secure Messaging Platform Web app is currently hosted on Microsoft Azure servers in three locations: U.S.-West, U.S.-East, and EU-North. The Azure traffic manager will direct your browser to the closest available location; from there, every location is load-balanced with at least two active nodes. This means your session is directed to the most available (least busy) location. This also means that all six nodes would have to go down at once for the Secure Messaging Web app to be unavailable.


What is the Secure Messaging physical infrastructure environment, in high-level terms

Infrastructure is comprised of Azure virtual machines; Azure app services; Azure SQL databases.


Can Secure Messaging be hosted in any country using a local cloud provider if an MS Azure server is not available?

Hosting in new regions is contingent on the sales of that region. I.e., if the scale of the deployment justifies locating a server there.


Can an organization host the platform on internal servers provided that access is provided as required?

On-premise hosting is not available.


Which SSO services is Secure Messaging compatible with?

Common SSO environments include SAML 2.0, an XML-based open standard data format for exchanging authentication and authorization data between parties (in particular, between an identity provider and a service provider), and OAuth 2.0, which allows secure authorization in a simple and standard method from web, mobile, and desktop applications.

Cirius Secure Messaging seamlessly integrates with such SSO deployments (whether SAML 2.0 or OAuth 2.0) without requiring new identities for users. As well, Secure Messaging quickly and seamlessly integrates into existing email environments, including Outlook, Office 365, and Gmail, along with DLP engines and archiving systems. Because integration into your existing environment is seamless and the learning curve is minimal, new users can be up and running with Secure Messaging in minutes.


Our backup software blocks level database change. How does that work with secure messaging?

Secure Messaging does not require database changes.


What is my procedure for recovering an Exchange database in the event of disaster so that all secure messages are present and retain seamless expected functionality?

Recovering the exchange database will have no impact on the Secure Messaging service.


Does Secure Messaging work with Outlook on a Microsoft Exchange server?

Yes. There are no changes to the Exchange server required when using the Outlook add-in.


Does the Secure Messaging Outlook client work on terminal servers / remote desktop servers / Citrix environments?

Yes, terminal services/remote desktop/Citrix environments are fully supported. There is a special Enterprise Edition version of the Secure Messaging Office add-in for these environments, which can be found here:


Does Secure Messaging Platform integrate with S/Mime

Secure messaging works with any mail server, in any configuration, and supports a mix of on-premise and cloud email.


Does Secure Messaging comply with Apple’s IPv6-only network services policy?

Yes. The Secure Messaging iOS app has been tested and works with IPv6.


Does Secure Messaging have SSAE16 SOC 2, Type 2 certification or similar?



Are you fully N+1 in all components and services?

Yes, on all business critical environments


What controls and methodologies do you use to protect client information from your own employees, both physical and virtual?

All data at rest is encrypted with unique client keys; system access is restricted to key personnel performing scheduled maintenance tasks; Additionally, we engage KPMG for yearly infrastructure security and penetration testing.


What is the Secure Messaging continuity plan and ETA from disaster declaration to return of service?

We rely on geographical data replication and, in the event of a disaster, we should have the service restored within ‘n’ hours.  Our SLA can also be reviewed at