Mimecast Customer Care - Browser Support Matrix

This article outlines the framework of the supported environment for Mimecast end-user applications, administrative portals, and Large File Send access key generation pages. It is intended for Administrators.

Considerations

Consider the following when considering your browser installation:

• We strongly encourage you to update your browser to a supported version for security purposes.
• The minimum screen resolution is 1024px x 768px.
• Results may vary if you use Zoom to adjust your view to levels other than 100%.
• Beta versions of web browsers are not supported.

Browser Support Matrix

The following browsers are supported for the listed applications:

Application	Google Chrome	Microsoft Edge	Safari Mac OS (v8 or later)	Firefox (v3 or later)	Safari iOS
Mimecast Community	✓	✓	✓	✓	✓
Administration Console *	✓	✓	✓	✓	✓
Connect Application	✓	✓	✓	✓	✓
Mimecast Personal Portal	✓	✓	✓	✓	✓
Secure Messaging	✓	✓	✓	✓	✓
Large File Send	✓	✓	✓	✓	✓
Targeted Threat Protection	✓	✓	✓	✓	✓
Mimecast Awareness Training	✓	✓	✓	✓	✓
Browser Isolation **	✓	✓	✓	✓	✓
Aware	✓	✕	✕	✓	✕

Safari is not supported with our token refresh in authO.

Firefox might work, but it's not officially supported.

*	If you need to use content editor features such as cut and paste, script access to the clipboard should not be disabled.
**	Mobile browsers for both email and web security are not supported. When an IOS web security customer tries to access a suspicious site, we proxy the site instead of opening the link in an isolated container.

TLS and SSL Protocols

This section references the protocols and cipher suites that Mimecast supports. It is not a detailed explanation of the workings of TLS and SSL.

Our web applications are accessed using Hypertext Transfer Protocol Secure (HTTPS). Technically, HTTPS is not a protocol, but the result of layering HTTP on top of Transport Layer Security (TLS) or Secure Sockets Layer (SSL) adds the security of these protocols to cleartext HTTP communications. Using these cryptographic protocols doesn't guarantee the connection is secure. As such, we only support specific protocol versions and ciphers.

The quality of the protection provided by SSL relies on the private key (the basis for the security) and the certificate (which conveys the server's identity to its visitors). We use an SSL certificate issued by Verisign, a reputable Certificate Authority (CA), with a 2048-bit RSA key. We no longer support SSLv3 for inbound browser connections. Instead, one of the following TLS versions should be used:

• TLS v1.2: The most secure protocols that have no known security issues. However, many servers and client systems do not currently support these protocols.

Cipher Suites

TLS / SSL cipher suites enforce the actual security of the encrypted session. We support several strong cipher suites with a minimum of 128 bits, guaranteeing your secure connection cannot be decrypted if intercepted.

The following cipher suites are not supported:

• Anonymous Diffie-Hellman (ADH) suites: It provides no authentication.
• NULL cipher suites: It has no encryption.
• EXPORT cipher suites: It uses trivial encryption.
• WEAK cipher suites: They typically use less than 128-bits.
• Rivest Cipher 4 (RC4): It is insecure.

Also, we can not support any connections using the RC4 cipher, and the Mimecast API will reject these. Therefore, we strongly recommend you update your operating system and browsers to more recent secure versions to maintain security.