Configuration - 3.2
Vulnerability fixes
- SQL Injection, XSS, Path Traversal, and RCE vulnerabilities, among others identified in specific parts of the product, were fixed.
- The versions of third-party dependencies were updated to reduce vulnerabilities and strengthen the security of the platform.
More control and flexibility in multifactor authentication (MFA)
The new version of the system expanded multifactor authentication with a new method and more administrator control over which factors the organization accepts.
In addition to e-mail verification, it is now possible to use an authenticator app (TOTP), and the login automatically guides users to the right path.
In the previous version of the system, it was possible to enable MFA and configure allowed IP ranges, but it was not possible to choose which verification methods the organization would accept.
From version 3.2 onwards, the administrator can define, in the authentication parameters, which MFA methods are available to users, choosing between e-mail verification and authenticator app verification (TOTP).
With MFA enabled, at least one method must remain active, and the system does not allow saving the configuration without any method selected. The choice is respected throughout the system: methods that are not enabled are no longer displayed either at login or in the user's MFA setup.
Guided login based on the available method
From version 3.2 onwards, after the user enters their username and password, the system considers the methods enabled by the organization and those the user has already set up. Check out the possible paths below:
- With a single method available, the user goes straight to verification, with no selection screen.
- With more than one method available, the user chooses which one to use for that login, without changing their saved preferences.
- With no method set up, the user is directed to the MFA method setup and completes the login only after setting it up.
When MFA is not enabled or access comes from an allowed IP range, login proceeds normally, without requesting the second factor.
New audit trail structure
The audit trail now has a new structure that broadens the coverage and security level of change records. With it, all changes made to data are audited automatically, without depending on record-by-record configuration.
With this improvement, the trail becomes more complete and reliable, making it easier to prove what was changed, by whom, and when.
The information is stored in a segregated way and protected against tampering, and access is faster, with text search, filters, and grouping of changes by operation.
This new structure was designed to meet the compliance requirements of FDA 21 CFR Part 11.
This feature is available only to customers on the Regulated plan. Customers on other plans continue to use the current audit trail.
Copy data between environments
Now, through Refresh, it is possible to copy data from one environment to another within the same account directly from the Manage account panel.
This makes it simpler to keep a test or staging environment updated with production information, without depending on a manual request to support.
The customer chooses, among the account's environments, the source and destination of the copy, and schedules the date on which it should occur, respecting a minimum lead time. The number of available copies varies according to the contract type: Enterprise accounts are entitled to one copy per month, and Regulated accounts, to one copy per week.
While the request is pending, it is possible to cancel it, as long as the reason is provided in advance of the scheduled date; after this deadline, cancellation is no longer allowed.
A history brings together all copies already requested, with the status of each one and their creation and execution dates.
New environment storage view
The Manage account panel now displays a summary of the storage used by the environment. Two indicators show how much has already been consumed: one for file space and another for the space occupied in the database. The color varies according to the usage level, making it easier to identify higher consumption.
Additionally, the database tables that take up the most space are listed, with the size and percentage of each one.
This way, there is more visibility into how the environment's space is being used.
Support for new languages
Starting with this version, the system supports the following languages: Hindi, Swedish, Norwegian, and Greek.
Swedish and Norwegian are supported in both environment types (ANSI and UTF-8), while Hindi and Greek are restricted to the UTF-8 environment.
See the latest improvements made to this component: