User Authentication and Networking
What forms of user authentication does Suitcase TeamSync use?
Suitcase TeamSync uses a custom web-based authorization mechanism. Suitcase TeamSync does not have support for Active Directory, LDAP, or Kerberos authentication.
What are the security requirements for Extensis passwords?
Passwords must be a minimum of 8 characters. There are no limitations or requirements on the types of characters that can be used.
Extensis.com passwords do not expire; nevertheless, it is recommended that you change your password regularly.
How long do Suitcase TeamSync user sessions last?
Login sessions on https://secure.extensis.com/ and https://manage.extensis.com/ expire after 30 minutes. Suitcase Fusion client sessions expire after 30 days; when Suitcase Fusion connects to the Extensis network to synchronize its cloud-based libraries, the session length is reset.
What network ports and URLs does Suitcase Fusion require access to?
For full Suitcase TeamSync functionality, Suitcase Fusion requires TCP and UDP ports 80 and 443 to be accessible on the following URLs:
How are user permissions handled in Suitcase TeamSync?
Suitcase TeamSync provides strict permissions to regulate access to administration functions and read/write access to cloud-based libraries. Access to font libraries is set on a per-user basis; there are no group- or role-based permissions.
Data Transmission and Storage
What user data does Extensis store for Suitcase TeamSync?
How is user data protected during transit?
User data, including libraries, sets, and fonts, are sent over HTTPS-secured connections.
Can Suitcase TeamSync sync fonts from an on-premises server?
Suitcase TeamSync can only sync with the Extensis cloud network. There is no functionality for connecting to an on-premises server.
Maintenance and Updates
How are updates to Suitcase TeamSync handled?
The Suitcase Fusion application is updated by the end user. The Suitcase TeamSync service is updated by the Extensis DevOps team; production updates are deployed into Amazon Web Services when we have changes.
How long are service logs kept and who has access to them?
Logs for troubleshooting and technical support purposes are kept for 14 days. Logs are archived indefinitely in Amazon Web Services storage and accessible by the Extensis DevOps team.
What is your procedure in case of a data breach?
Responses by the Extensis Incident Response Team can include or proceed through the following stages: identification, severity classification, containment, eradication, recovery and root cause analysis resulting in improvement of security controls. The Incident Response Team will respond as per the more detailed Incident Response Plan published and maintained by the Extensis DevOps Manager.