Identity & Access Management
1 | Does the solution support Single Sign-On integration? | Yes, Maytech support Single Sign-On and ADFS integrations. Maytech's customers can sign in to their accounts using their existing corporate Active Directory credentials or any other identity provider (i.e. Duo, Okta, OneLogin, etc.). | ||||||
2 | Does the solution distinguish user roles and admin roles within the application? | FTP-Stream: All users except admin are jailed to their home folders and cannot see files or folders outside. To exchange confidential files with customers give each login a distinct home folder. Account owners can add new secondary admins who can help to manage FTP-Stream account and Billing admin, who helps with payments and invoices. In Quatrix there are several user roles that determine what actions can be performed in the account. The account owner is the top administrator of the account that has access to all Quatrix features and can purchase more users for the account. Admin has the same rights as the account owner with the exception of tracking and paying invoices for the account. Pro users can browse folders and share to any of your users or to their contacts who don't need a licence to download (normally your employees). Associate users can only use your service to share files back to your Pro Users - great for external partners who need to regularly feed data into your organisation. Jailed users are jailed to the Projects Shared With Me folder. They are not able to use the Share Form or otherwise share files outside of the designated workflow. Read more about Roles and permissions. | ||||||
3 | How are user passwords stored in the system? | Passwords are individually salted and stored in a database, encrypted one way. | ||||||
4 | Does your organisation have a documented password policy? If YES, describe the controls (e.g. minimum length, complexity, expiration period). | Yes. ISMS OP 30 - Password Management Policy: The following are general recommendations for creating a Strong Password. A Strong Password should:
A Strong Password should not:
With the optional Extended Authentication module, customers can set a password policy, including: Users can / cannot change their passwords, must change their passwords on the first login, must periodically change their passwords, must use strong passwords. | ||||||
5 | Can we request a custom password policy to be applied to Customer users? | Yes, the administrator of FTP-Stream account can set a password policy for his/her account to specify complexity requirements and rotation periods for his users' passwords. It provides a possibility to allow users change their passwords, to set a number of failed login attempts, to set the minimum password length, to force password change on the first login or after a specified period and to specify password construction requirements. The following options are available for configuring the password policy: Quatrix supports strong passwords. | ||||||
6 | What is the password reset process? | There are several ways of changing the password in FTP-Stream and Quatrix:
The user or admin can change their password on the Login page. Follow these steps:
| ||||||
7 | Does the solution support multi-factor authentication? | Yes, all Maytech's file sharing products offer Two-Factor Authentication (2FA) as an additional module. Administrators can elect to have their 2FA codes sent in one of two ways:
| ||||||
8 | Do Maytech provide audit and monitoring of access to the system and data? | Yes. Comprehensive audits logs are available and all user activity is tracked. | ||||||
9 | How does the solution authenticate users to prevent unauthorized access? | Username and strong password, and 2FA. | ||||||
10 | Within the application, and the supporting infrastructure, describe how administrator actions are logged and recorded, including details of how long these audit logs are stored for. | Where Maytech are instructed to access any data (regardless of whether it is personal data or otherwise), all such access is logged with information identifying the Maytech's personnel accessing the data and setting out the date and time of access. Access logs are maintained for 12 months and can be downloaded and stored by the Customer at that time. | ||||||
11 | What is your review processes, manual or automated, for event and application logs generated within the solution? | Maytech’s approach to log management is controlled by ISMS OP 22 - Logging and Audit Trails Policy.
All audit entries are time-stamped with entries recorded as GMT dates and times. Clock synchronisation is uniform on all servers to ensure timestamps are consistent across all logs to avoid any time discrepancies which may cause issues for any subsequent forensic activities. All logs are reviewed periodically (minimum at least monthly) to identify any unauthorized access to the systems. Retention of audit files is for at least 12 months. | ||||||
12 | If required, what methods and formats are available for a Customer to export a copy of data? | The account owner has access to all the data, so can take a copy of it at any time. |