Security Settings

You can customize the security settings of your LogicMonitor account to control user access to the portal. For example, you can suspend users after a specified number of inactivity days and configure an email domain allowlist. In addition, LogicMonitor provides the latest security recommendations to help secure your portal. For more information on securing your LogicMonitor platform, see LogicMonitor Best Practices.

LogicMonitor Security Recommended Actions

LogicMonitor displays all the recommended actions at the top of the Security page if your portal configuration does not match the latest LogicMonitor-released recommendations.

If you close the recommended action and save without incorporating it, then the same recommended action displays on the next session.

LogicMonitor can display the following recommended actions:

• Enable Two-Factor Authentication for all users who have disabled the Restrict Single Sign On
• Update to Suspend user after 90 (or less) days of inactivity
• Update to Disable tokens after 365 (or less) days of inactivity
• Disable Test Script
• Remove LMV1 tokens associated with OOB Administrator role
• Remove Bearer Tokens associated to Users with OOB Administrator role
• Remove API tokens LMV1/Bearer tokens associated to the lmsupport support user
• Update your Windows Collectors to run as non-adminstrator
• Update your Linux Collectors to run as non-root

Two-Factor Authentication

Two-factor authentication (2FA) provides an extra layer of security for accessing your LogicMonitor account. In addition, to a username and password, 2FA requires users to use a third-party application or an authentication token delivered using SMS, voice, or email to verify their identity.

You can globally apply 2FA for all users who log in to the portal for your LogicMonitor account. 2FA can also be applied on a per-user basis, however globally enabling 2FA forces all users to authenticate using 2FA regardless of the per-user setting.

Note: If you enable Single Sign On (SSO) for your LogicMonitor account, and SSO is not set to Restrict Single Sign On, users can choose to log in to their portals using SSO or 2FA. If SSO is set to strict access, users can only log in to LogicMonitor using SSO. To use 2FA with SSO, you must set this up with your SSO provider.

For more information about accessing your LogicMonitor account when 2FA is enabled, see Two-Factor Authentication Account Access.

Keep Me Signed In

An admin user can control the appearance and usage of Keep Me Signed In option on the Company Settings page. Also, the admin can control the duration of timeout from 0 to 999 days for users who chose to be kept signed in. 0 represents no limit; user session will last indefinitely. 

When an admin enables this, users can choose to use it while logging in. User sessions who had not checked the button while logging in will timeout after a certain time of inactivity. When the admin disables this, users whose  session is still active as they had checked Keep me Signed In would be forcefully logged out. User sessions who had not checked the button while logging in, will be exempt as their session will timeout eventually. 

Disable Unused Tokens

As a mitigation against risks related to the disclosure of previously generated and unused LMv1, Bearer, and Widget tokens, LogicMonitor has introduced a feature to auto-disable unused tokens after a set days of inactivity. Admin user with Manage Security permission can set the number of inactive days after which the unused token is auto-disabled.

When the unused token is disabled, LogicMonitor sends an email alert to the owner of the token about the disabled token and the reason for disabling it. A log of disabled token is maintained on the Audit Logs page.

Similarly, details of the disabled tokens are also available in the table for LMv1 API token, bearer, and widgets token. To access the details, navigate to Settings > User Access > Users and Roles and access the LMv1 API Tokens, Bearer Tokens, and Widgets Tokens tab. The details of the disabled token are greyed and cannot be edited.

To activate the disabled token, contact your administrator. For more information, see LMv1 API tokens, Bearer tokens, and Widgets tokens.

Requirements to Configure the Security Settings

To configure the Security settings, you need a LogicMonitor user with the “Manage” role for Security. For more information, see Users and Roles.

Configuring the Security Settings

1. In LogicMonitor, navigate to Settings > Security.
2. Toggle the Enable Remote Session switch to enable a remote session on an account-wide basis.
   For more information, see Remote Session.
3. Toggle the Enable Test Script switch to disable the Test Script option testing the script-based LogicModules.
   This switch is disabled by default.
4. Toggle the Enable Collector Debug switch to enable collector debug on an account-wide basis.
5. Toggle the Require Two-Factor Authentication for all Roles and Users switch to enable two-factor authentication on an account-wide basis.
   For more information, see Two-Factor Authentication.
   A message displays prompting you to select when to enforce authentication. You can enforce authentication immediately or eventually. This switch is enabled by default.
6. Toggle the Require Two-Factor Authentication for Remote Session switch to enable two-factor authentication on your remote session.
   You are required to toggle off the Require Two-Factor Authentication for all Roles and Users switch to use this option.
7. Toggle the Keep Me Signed In switch and in the Keep Me Signed In days field, enter the number of days you want to remain signed in. 
8. To suspend an account of a user after a defined number of days, enter a value in the Suspend user after days of inactivity on LM portal setting.
   Accepted values are whole numbers. The default days set is 90 days.
9. In the Disable Token (LMv1, Bearer, Widget) after X days of inactivity, enter the number of days after which you want to disable the inactive tokens. 
   The default days set is 365 days.
10. Select a timeout value for users from the User Session Timeout dropdown menu to log users out of the LogicMonitor portal after a specified time.
    Inactivity for the specified length of time results in a user account being logged out. The timeout period is applied to users not enabling the option to stay signed in when they log in to their LogicMonitor portal.
    The default timeout period is 4 hours.

11. In the IP allowlist table, enter a public Internet-facing IP address.
    You can identify addresses using any of the following formats:
    • Hostname (mycomputer.mybusiness.com)
    • IP address (192.168.1.1)
    • Network/mask (192.168.1.0/24)
    • Network range (192.168.1.100-255)
      LogicMonitor displays a warning if your current IP address is locked out after saving the list. If you are locked out of your account, contact Customer Success.
12. In the Email domain allowlist, enter the name of the required email domains for the primary email ID. You can enter multiple domain names by adding commas, for example, google.com, tomotom.com, and so on. By default, the field is blank.

13. Toggle the Allow Shared Reports switch to give access to reports to the users who are not logged in.

14. Toggle the Allow Scripts in Dashboard Text Widget switch to allow scripts in the Dashboard Text Widget.

15. Select Save.

The Security settings are applied globally for all users that log in to the portal.