+1.855.SYNCDOG (1-855-796-2364)

Frequently Asked Questions

Q. What platforms is Secure.Systems™ available for?

A. Secure.Systems is available on iOS, and Android devices.


Q. Do you have to have your smartphone managed by an EMM to use Secure.Systems™?

A. No, unlike Android for Work or Samsung KNOX, an EMM is not required to manage the Secure.Systems™ workspace. Secure.Systems™ is EMM-agnostic and can be used with an EMM solution or as a standalone solution.


Q. Can I add applications to my instance of Secure.Systems™ workspace?

A. Yes, any natively developed iOS or Android application can be applied to Secure.Systems™.  The application will need to be placed within the framework of Secure.Systems™ by a SyncDog engineer.


Q. If I have 3rd party applications I use for business on my smartphone can they be protected by Secure.Systems™?

A. Yes, for 3rd party business applications not embedded into the secure workspace, Secure.Systems™ provides the ability to wrap the application in encryption for protecting data at rest and in transit.


Q.  How does Secure.Systems™ work with my corporate e-mail system?

A. Secure.Systems™ provides applications for e-mail, calendar, and contacts connectivity.  Currently Secure.Systems™ supports Microsoft Exchange and Office 365 implementations out of the box.  Custom installations can be completed for mail systems like Lotus Notes and others.


Q. How secure is Secure.Systems™?

A. Secure.Systems™ provides AES 265 bit encryption for all data at rest and in transit between the smartphone and the enterprise network.


Q. Does Secure.Systems™ require a VPN Solution?

A. No, Secure.Systems™ does not require a 3rd party VPN solution to connect to the network securely.  The Secure.Systems™ workspace connects to the secure management server via a relay in the DMZ using an AES 256 bit encrypted SSL tunnel between the device and the management server behind the firewall.


Q. Can Secure.Systems™ be hacked?

A. All software can, in theory, be hacked, but Secure.Systems™ has taken all methods that are available today to protect against hacking. The client is protected, among other methods, with code obfuscation and runtime memory heap protection.


Q. Is Secure.Systems™ vulnerable to a man-in-the-middle attack?

A. No, Secure.Systems’™ secure transport methodology protects against MIM attacks.


Q. Does Secure.Systems™ store encryption keys in the local key store of the device?

A. No, Secure.Systems™ uses a multi-part key structure which disseminates the key in various places, but is also composed of several key components in order to be fully secure.


Q. How many applications can be put into Secure.Systems™?

A. There is no limit to the number of applications which can be embedded into Secure.Systems™.  The only limit would be based on the maximum physical storage capacity of the device.


Q. Can I store and retrieve documents in Secure.Systems™?

A. Yes, Secure.Systems™ provides both the ability to store and sync documents with a network drive or desktop, as well as open and edit the documents, spreadsheets or slide decks in an Office Suite within Secure.Systems™ workspace. 


Q. Can I use my smartphone to view internal LAN pages on my company intranet?

A. Yes, Secure.Systems™ provides a secure browser which does not connect to the internet directly via the device, but by the secure connection on the secure management server through the encrypted SSL tunnel.


Q. Can I run Secure.Systems™ on multiple devices?

A. Yes, the Secure.Systems™ device client can be installed on multiple devices and will sync content between the devices so you can start an e-mail on your iPhone and finish it on your iPad.


Q. Can I have multiple mailboxes on an instance of Secure.Systems™?

A. No, currently Secure.Systems™ can only support a single connection to Microsoft Exchange or Office 365. Multiple mailbox functions are on the Secure.Systems™ roadmap and will be available in a future release.


Q. Can I run multiple instances of Secure.Systems™ on a single device?

A. Multiple versions of Secure.Systems™ can be made available if required.


Q. How many users can be supported by Secure.Systems™?

A. Secure.Systems™ and the secure management server have been designed to scale according to the size of the deployment.  When implemented, the secure management server and the secure relay can be installed in multiple locations and geographies to maximize the capacity and provide redundancy for the deployment.


Q. What applications are available with Secure.Systems™?

A. Along with E-mail, Calendar and Contacts, Secure.Systems™ also includes a secure browser, an Office Suite for documents, and access to files and docs. Along with a secure camera and maps application, Secure.Systems™ also includes File Manager which allows user to Manage, View, Edit, Copy and/or delete files synced between a device and backend, and a Briefcase which is a shared workspace for centralized distribution and access to files and docs. Integrations are also available with OneDrive, Box and DropBox.


Q. Can you copy data from Secure.Systems™ to an application on the device?

A. No, you are not able to copy and paste data from the Secure.Systems™ application to other device applications running outside of the secure workspace.  You are able to use copy and paste between applications running within the secure workspace.


Q. Can you take screenshots of screens within Secure.Systems™ and save on the device?

A. No, screen captures are disabled when you are running within Secure.Systems™.


Q. Can I wipe the device or specific data from the device?

A. Secure.Systems™ has an over the air function to wipe the Secure.Systems™ workspace from the device.  This is a management command from the secure management console which can only be accessed by a qualified administrator and will wipe Secure.Systems™ and all data from the device.


Q. Can I wipe data from the device if the device is not connected to the network?

A. Secure.Systems includes a policy for a feature called “Time Bomb”.  When enabled the administrator will define a period of time (i.e. 30 days) and if the Secure.Systems™ client on the device has not checked in with the secure management server the Secure.Systems™ client on the device will automatically wipe itself.