# Security
For Modyo, security is a fundamental priority. For this reason, we have developed this page that will serve as a comprehensive guide to ensure the secure installation of Modyo.
Both Modyo Cloud and Enterprise Cloud, our cloud solutions, offer an excellent level of security by default. In addition, platform administrators have the ability to implement additional measures to strengthen the protection of their organizations.
This guide presents the most relevant recommendations for achieving this objective.
# Password policy
In this section, you can set the password security policy for team members. The available options are:
- Minimum password length value: This value determines the minimum length a password must have; it must be between 12 and 128 characters.
- Require at least one lowercase letter from Latin alphabet (a to z): This option ensures that the password contains at least one lowercase letter.
- Require at least one uppercase letter from Latin alphabet (A to Z): This option ensures that the password contains at least one uppercase letter.
- Require at least one of these special characters: This option requires that team members' passwords contain at least one of the symbols that the checkbox itself lists in parentheses. The default set is
! @ # $ % ^ & * ( ) _ + º - = [ ] { } | " . ' ¿ / ¡ : ;, and the list you see on screen is always the one your installation validates.
When saving this configuration, existing users will have to comply with these conditions when changing their password.
Attention
When you enable Require at least one of these special characters, the password is also limited to that alphabet: only letters from a to z, uppercase or lowercase, digits, and the symbols on the list are accepted. Any other character causes the password to be rejected, even if it is long and meets all the other conditions. This includes accented vowels, ñ, and symbols such as ~, <, or >.
# Lockout after failed login attempts
In addition to the password policy, Modyo protects the login process against brute force attacks. After 10 consecutive failed attempts, the user is temporarily locked out for 15 minutes, and the error message tells them how long is left before the lockout is lifted:
Consecutive failed logins limit exceeded. Your account has been temporarily disabled. Please wait 14 minutes for your account to be unlocked.
This protection applies both to team members signing in to the admin panel and to end users signing in to a realm. The lockout is released only by waiting: there is no manual unlock action in the panel, you have to wait for the time to elapse.
Tip
This temporary lockout is different from the inactive status of the User inactivity period policy. If a team member reports being unable to sign in, check which of the two cases applies: the failed attempts lockout clears on its own after 15 minutes, whereas the inactive status remains until the user reactivates their account or a team member with the Admin Team permission activates it again.
# Expiration of panel links and codes
Besides the session, several links and codes that Modyo sends by email or shows on screen have their own expiration time. These times are fixed: they are not configured from the panel.
| Link or code | How long it lasts |
|---|---|
| Password recovery link | 3 days from the moment the email is sent. |
| Account activation link, in the welcome email | 1 week from the moment the email is sent. |
| Reactivation link for an account marked as inactive | 10 minutes from the moment the email is sent. |
| Two-factor authenticator setup link | 5 minutes from the moment the screen is opened. |
| Confirmation link for a new email address | 5 minutes from the moment the email is sent. |
Once the time is up, the link stops working: the platform sends the person back to the login screen with an error message. The fix is always to request a new one, never to forward the old email.
Attention
All these links share the same single-use code. Every time a new one is generated, for example when password recovery is requested a second time, the previous one is invalidated immediately, even if it was still within its time window. If a team member requests several emails in a row, only the link in the last one they received works.
# Request limits and temporary lockouts
Beyond the password policy and the login lockout, Modyo limits how often a team member can request a recovery email or change the sensitive data in their profile. These limits are fixed and are not configured from the panel either.
# Password recovery requests
The recovery screen always answers with the same message, whether the username exists or not and whether the email is sent or discarded:
If a valid username has been entered, you will receive a temporary password to your email.
Underneath, two limits apply:
- Two requests in a row for the same team member, less than 10 seconds apart, cause the second one to be discarded and no email to be sent.
- When more than three requests pile up for the same team member, the following ones are discarded for 24 hours, counted from the last accepted request.
In both cases the person sees the success message and the email never arrives. This is the most frequent cause of the "I asked for the recovery and nothing arrived" report.
# Sensitive data changes from the profile
The Profile screen asks for the current password before changing the password, the email address, or the username, and before removing the authenticator. Two more limits apply there:
- One password change every 24 hours: once a team member changes their password, they cannot change it again from their profile for the next 24 hours. If they try, the platform sends them back to the profile with the message The number of password change request has exceeded the maximum permitted. The clock also starts when the password was set from a recovery link.
- Three failed attempts and a 15-minute lockout: changing the password, changing the email or the username, and removing the authenticator share the same attempt limit. Only an attempt with a wrong or empty current password counts as failed. When three failed attempts pile up, the next one is rejected even if the password is correct, with the message You've reached the limit tries to change sensitive data on your profile. Your session will be closed for safety reasons. The platform closes the team member's session, and it may also log them out on all of their devices.
The lockout lasts 15 minutes and clears only by waiting: there is no action in the panel to release it earlier. While it lasts, any attempt to change this data or to remove the authenticator is rejected, even with the correct password, and the session is closed again. The lockout does not prevent signing in again. Once the time is up, the team member gets their attempts back.
Tip
This lockout is different from the Lockout after failed login attempts, which triggers after 10 attempts on the login screen. The profile one triggers after 3 failed attempts, with the session already open, and its visible effect is that the person is thrown out of the platform on the next attempt, even if this time they type their current password correctly. If someone reports that "the panel kicked me out while I was changing my email" or "while I was removing my authenticator", this is why.
# Session expiration policy
In this section, you can configure how long a session will remain active. Both fields are fixed option lists: you choose one of the available values, you do not type a free-form time.
Session expiration: At the end of the selected time, Modyo automatically closes the user's session. The options range from 15 minutes up to the maximum session duration your installation allows, which is 1 week by default: 15 minutes, 30 minutes, 1 hour, 2 hours, 12 hours, 1 day, and 1 week. The 2 weeks, 1 month, and 3 months options only appear when your installation's maximum reaches them, and if that maximum does not match any option, it also appears as the last one on the list. If your installation's maximum is lowered, sessions last at most that maximum, even if the account has a higher value saved.
User idle period: When a user is inactive, the session is automatically closed after the selected time has elapsed. Navigation, keyboard, and mouse actions are considered user activities. This option protects the user if they leave their workstation unattended. To be able to choose a value, first check the Enable user idle period box; the options are 5 minutes, 15 minutes, 30 minutes, 1 hour, and 6 hours.
This session closing is measured in minutes and only ends the open session. Do not confuse it with the User inactivity period policy, which is measured in days and marks the user as inactive so that they cannot sign in again.
# Sign-in notice from a new device
Every time a team member enters the panel from a browser or a device they had not used before, Modyo automatically sends them an email with the subject New Sign-in to your Modyo account. The email states the account and the email address used to sign in, the browser and the operating system, the date of the sign-in, and the IP address, and it includes a button to change the password right away in case the access was not theirs.
This notice is part of the platform: there is no option to turn it on, turn it off, or word it differently. It is not sent on the very first sign-in of a newly created team member either, because at that point there are no previous accesses to compare against.
Modyo decides that a device is new by comparing the fingerprint of the current access with the fingerprints of that same team member's previous accesses, the same information you see in the Devices tab of their record in Team.
Tip
Getting this email does not by itself mean that someone else entered the account. The fingerprint changes when using another browser, updating it, clearing cookies, or signing in from another computer, so the same team member can receive the notice for perfectly legitimate accesses. Before escalating, compare the device and the IP address in the email with the Devices tab and with the Activity logs.
# User inactivity period policy
With the Enable user inactivity policy box checked, which is the default, Modyo changes to inactive the status of team members who go longer than the selected Inactivity period without interacting with the platform. The change does not happen at the exact moment the period is reached, but at whichever of these two moments comes first:
- In the automatic review that Modyo runs once a week. This review also closes the team member's open sessions.
- When the team member tries to sign in after the period has been reached and their credentials are valid.
The account owner never becomes inactive, even if they exceed the period.
Once the user is marked as inactive, they cannot log in while the policy remains enabled. The default inactivity period is 90 days, and you can change it to:
- 30 days
- 90 days
- 180 days
- 360 days
If you check the Send reactivation email on user deactivation by inactivity box, which is enabled by default, the user receives an email every time they try to sign in while inactive, and from that email they can reactivate their account. The weekly review does not send this email.
Attention
When you save the settings after enabling or disabling the policy, all team members marked as inactive become active again, including the ones you marked manually. If the policy remains enabled, those who still exceed the period become inactive again in the next weekly review or when they try to sign in.
Tip
Any team member with the Admin Team permission can change a user's status between inactive and active using the Login suspended for inactivity checkbox.
You can locate this option when editing a user in the Team section, in the Edit tab. If you select the checkbox, the user is marked as inactive and their open sessions are closed. When you clear it, the user is active again and the inactivity period starts counting again from that moment. In the Team list, the Suspended filter lets you see which users are inactive.
# HTTP access control (Cross-Origin Resource Sharing CORS)
The Cross Origin Resource Sharing section defines which domains can access Modyo resources. It has three controls:
- Enable CORS: turns the feature on. When you check it, the custom domains of your apps are included automatically, without you having to list them.
- Allow all origins: adds the
*wildcard to the list of allowed origins, so that any domain can consume your public information in JSON format. When you check it, Modyo asks for confirmation with the notice "If enabled, all domains will have access to your public JSON information. Would you like to continue?". - Alternative origins: text field to grant access to external domains. Write them separated by commas, for example,
http://api.mydomain.com, http://mysubdomain.mydomain.com. Wildcards are not accepted in this field: if you include a*, the configuration is not saved. From each entry, Modyo keeps only the scheme, the domain, and the port, and discards paths.
When you are done, click Save.
The origins in this section apply to the administration API, the Channels menus API, and the payments API. The other APIs have their own CORS: the content API uses each space's, in the Security section of its settings, and the Customers API uses each realm's, in the Security section of its settings. In addition, the menus API of an app with an active custom domain always accepts calls from that domain, even if CORS is disabled.
Attention
Allow all origins is enabled from this same screen, with no need to open a support ticket or make any other change to your installation. Because it puts your account's public information within reach of any domain, reserve it for development or testing environments and, in production, list the domains in Alternative origins.
Tip
The automatic inclusion covers the primary domain of each app. If you publish an app on an alternative domain, or if the origin making the calls uses a different scheme or port, add it in Alternative origins, because the origin comparison is exact.
# Content Delivery Token (JWT - JSON Web Token)
Modyo signs user JWTs with the Private content JSON Web Signature (JWS) key so they can access private content through the API. It is not a shared secret, but an elliptic curve key pair that Modyo uses to sign tokens with the ES256 algorithm. The key is created along with the account, does not expire, and only changes when you click Generate new JWS key.
Attention
If you generate a new key, all requests for private content must go through Modyo. This is because JWTs signed by Modyo with the old key will no longer be valid.
The Content delivery token TTL (in seconds) field defines how long each JWT that Modyo issues lasts, not the key. The default is one hour (3600 seconds) and the minimum is 10 seconds. While a token is still valid, Modyo can hand it out again with the same expiration, so the one your app receives may last less than that time; when it expires, the content API rejects it and you have to request a new one. It is recommended to avoid a very short duration, as it may affect the platform's performance.
# Two-factor authentication (2FA)
Two-step authentication adds a layer of security to your account and reduces the risk of unauthorized access. When activated, each time team members log in, they will have to enter their password and a dynamic key provided by the Google Authenticator application from their phones.
Each team member can activate two-step authentication from their profile. In addition, the administrator can force two-step authentication for all team members.
By enabling mandatory two-step authentication for team members, the next time a member logs in, they will be required to set up their two-step authentication device. Once set up, you must log in using your password and the code provided by Google Authenticator.
Attention
The Set Time Zone Automatically Option must be active when using two-factor authentication on your mobile device.
# Enable two-factor authentication for a user
To enable two-factor authentication for a user and neutralize the risk of compromised passwords, follow these steps:
- Click your avatar at the bottom of the side menu and select Profile.
- In the right column of your Profile, under Setup authenticator, click the Setup authenticator button.
- Scan the code that appears on the screen with your mobile device to link your authenticator with Modyo Platform. This adds an entry in the app with your account domain and your username.
- Enter the 6-digit code shown by the app in the Current code field and click Save.
Once you have two-factor authentication enabled, the button will say Remove authenticator. To remove the authenticator, click that button, type your password in the Current password field of the window that opens, and click Remove authenticator. If the password is wrong, you see the message The authenticator could not be removed. Please check your current password. and the authenticator stays in place. Failed attempts count toward the profile attempt limit.
# Delete authenticator for a user
If the authenticator is lost or stolen, it will not be possible to access the account. In this case, a Modyo Platform administrator can help by removing the authenticator linked to the user by following these steps:
- In the side menu, expand Settings and click Team.
- Click on the member's name.
- In the top bar, click on the more options button, represented by three dots, and select Remove authenticator.
To see this option you need the Admin Team permission, which Admin Settings also includes. The option is only available when the member has an authenticator set up, and it cannot be used on your own user: you remove your own authenticator from your Profile, where your current password is required. When it finishes, you see the message Authenticator removed successfully. and the action is recorded in the Activity logs as User updated.
Attention
If you have activated the option to force authentication, the next time the user tries to log in, they will need to initialize the authenticator first. Once the authenticator is active, the user can proceed with the login process.
# SVG images
The Enable use of SVG images section defines whether your account accepts SVG files. It is disabled by default, and only team members with the Admin Security permission can change it.
To allow SVG file uploads, follow these steps:
- In the side menu, expand Settings and click Security.
- Scroll down to the Enable use of SVG images section.
- Check the Allow use of SVG box.
- Click Save.
While the box is unchecked, any attempt to upload or update an SVG file in Media is rejected with the message Can't upload or update SVG files due to configured security policies. The rejection applies both in the panel and through the admin API, and it also reaches the SVG files that already exist in the account: while the box stays unchecked, you cannot save changes to their title, alternative text, description, or tags either.
Attention
The panel itself warns you that "The use of SVG images can leave you vulnerable to XSS attacks and may be insecure". An SVG is an XML document that can carry scripts and external references inside, and the browser interprets it with the same privileges as the page that displays it. Enable it only if your teams need this format and you control the origin of the files they upload.
# Best practices
# Important concepts
- Limit access: Reduce the chances of a malicious actor gaining access to the system.
- Containment: Configure the system in a way that minimizes possible damage if it is breached by a malicious actor.
- Preparation and knowledge: Maintain backups and procedures to be prepared in the event of potential disasters.
- Trusted sources: Avoid implementing widgets or code from untrustworthy sources. Ensure that all dependencies loaded on the site come from reliable sources.
# Local vulnerabilities
- Make sure that the computers of all administrator users are free of spyware, malware, or viruses.
- Make sure that access always comes from updated computers and through reliable and updated web browsers.
# Update Modyo regularly
We recommend that you update Modyo periodically to ensure that your installation has the latest security fixes and that all security patches are up to date. These patches are designed to be applied without causing significant interruptions to the workflow.
In addition, we recommend that you perform major version upgrades at least twice a year. This will not only keep you on the latest supported version, but will also provide you with the latest features and functionalities.
# Set up a strong password in the admin panel
The Administration Panel is Modyo's most powerful management tool. Through it, you can have control over various configurations and actions that are fundamental to the operation of Modyo. In addition, it provides you with administrative access to all the organizations defined on the platform.
We recommend that you set a secure password and change it regularly, for example, after every major platform update.
# Enable transport layer security (TLS)
Forcing connections to be TLS only in your installation ensures that all incoming and outgoing traffic is encrypted. In addition, we recommend using only modern versions of the protocol, in particular versions 1.2 or 1.3.
# Differentiate subdomains
Differentiating subdomains is essential, as there are multiple places where Modyo supports HTML development. If not activated, the HTML of sites developed on Modyo can become an entry point for attacks that could affect other Modyo components through the cross-site scripting (XSS) technique.
# Review the backup processors
Running backup processes on a regular basis is very important in a secure Modyo implementation.
In the case of Cloud and Enterprise Cloud, this is done automatically. For Enterprise On Premise, each customer's operations team is responsible for carrying out this activity.
Modyo backups cover both the database and file shared directories, where static content is stored.
# Using an exit proxy server
Modyo can establish communications with the Internet, especially with regard to identity providers or integration Webhooks. To manage and control these outbound communications, it is essential to implement an outbound proxy server or to set up a Network Address Translation (NAT) scheme in which the source IP addresses are not exposed.
# Restrict public ports of entry
Modyo users must access exclusively through port 443, behind a load balancer that distributes traffic to the different instances of the platform.
Traffic between the load balancer and the platform instances can use ports 443 or 80, depending on the internal security of the network. For example, in isolated, protected networks such as Amazon AWS VPCs, internal traffic may not need to be encrypted.
# Activity logs
The platform keeps a record of all actions performed by administrator users within it, and also of those it runs on its own, with no person behind them: the latter are recorded with System as the author. You can review these logs in the Activity logs section.
We recommend that you review these logs periodically to verify the correct behavior of users within the system. Activity logs are also available through Modyo's administrative API.
# Review administration permissions
The administrators of an organization or site have a high level of access to content and settings that must be private. Impersonating one of these administrators can pose a major security risk. For this reason, we recommend keeping a small and very controlled number of users with a general administration role and ensuring that these users keep additional levels of protection active, such as the second factor of authentication.
In addition, administrators can generate tokens to access the platform's management APIs. These tokens are often used to automate common administrative tasks, so it is important to ensure that they are only used within secure systems that guarantee their protection.
# Report a vulnerability
If you think you have identified a security vulnerability in Modyo, please help us by reporting the problem.
Modyo offers secure and confidential channels for reporting security incidents through our support center (opens new window) or by sending an email to security@modyo.com.
Your collaboration is fundamental to maintaining the integrity and security of the platform.