Product Manager
Community ManagerWill access to the lmsupport account be affected by the new security mandates?
No. Requiring two-factor authentication (2FA) or enabling RestrictSSO will not impact LogicMonitor’s ability to access customer portals via an active lmsupport account. If you encounter any issues, please open a
support ticket so that it can be addressed as a priority. Additionally, any phone number associated with the LMSupport account is not utilized for 2FA.
What authentication methods can be used?
The following authentication methods are available for 2FA:
Will LogicMonitor support other 2FA apps than Authy?
Yes. LogicMonitor is currently upgrading its 2FA processing infrastructure to support additional 2FA applications such as Okta, Google Authenticator, and Authy, alongside other ToTP applications. This upgrade is on track to be completed by the end of August 2024. In the meantime, customers can enable 2FA and authenticate via voice, SMS, or email. For further details on 2FA Account Access, please refer to this page
How will the 2FA mandate impact shared user accounts for use cases such as shared reports or NOC dashboards?
In order to align with security best practices, LogicMonitor does not recommend using shared accounts. For use cases which require broader access, such as shared reports or NOC dashboards, and where a phone may not be available, user accounts can be configured to authenticate via Single Sign-On (SSO), or utilize 2FA via email for authentication.
How can I bulk add or update users to prepare for enabling 2FA?
LogicMonitor's API can be used to perform bulk tasks or programmatically manage your account. If you need assistance with bulk actions related to this mandate, please contact LogicMonitor Support.
Please refer to the below additional documentation for relevant endpoints for leveraging the API:
https://www.logicmonitor.com/swagger-ui-master/api-v3/dist/#/Users/addAdmin https://www.logicmonitor.com/swagger-ui-master/api-v3/dist/#/Roles/addRole https://www.logicmonitor.com/swagger-ui-master/api-v3/dist/#/Users/patchAdminById
How will LogicMonitor verify phone numbers for compliance reporting?
Phone Numbers are not verified by LogicMonitor, however customers’ phone numbers will need to be both in your possession and match the number set on your user account, to successfully authenticate via 2FA using phone number options. Phone numbers are no longer required for 2FA setup with portal V209, and users can now use an email account to get 2FA codes.
If the customer is using SAML is 2FA still mandatory ? Any suggestions on the approach?
SAML users are out of scope for mandatory 2FA, as they authenticate through their IdP. However, to follow best practices, we strongly recommend that their IdP requires 2FA.
If the customer enables 2FA for a local user, will the dashboard work after implementing 2FA?
Yes it will work; The customer will need to configure a valid e-mail address or phone number on the user account, and use their preferred 2FA option to authenticate.
With our new mandate for valid phone numbers, are SSO users required to have a phone number?
For 2FA, yes, which predates the email 2FA availability. The phone requirement was a hold over, which is going away per DEV-173012.
Will data collection be affected by moving to non-root accounts?
The Linux Collector service account is not typically used to retrieve data from remote devices. Data Collection from core LogicModules will not be affected as most devices monitored via Linux collectors are using either SSH, SNMP, or other credentials set under device properties during normal circumstances. However, if there are any custom modules, it is advisable for customers to review them to ensure they do not require root permissions.
How am I going to remotely monitor domain controllers without credentials?
Credentials will still be needed, however limited to an account without the Administrator group. One time admin credential will be required to move from admin to non-admin. Post that, to monitor and for data collection etc. explicit credentials (non-admin) can be maintained (as wmi.user and wmi.pass) or if not maintained, data collection etc. will occur through service account.
Will LogicMonitor provide a detailed list of requirements for access?
Yes. LogicMonitor provides comprehensive documentation to guide you through the required configurations and permissions for access. Here are the key resources:
How will this affect cross-domain trusts for monitoring?
Cross-domain monitoring should be possible by whitelisting the necessary domains in the trusted hosts list.
Can collectors still be run as a local service account?
Yes, collectors can still use local service accounts. We advise against using the local account (NTAuthority). Per the mandate, we encourage the use of a local non-admin service account, if you would like to use a local account. The collector installer itself will allow for this for the time being.
Will I need to update LogicModules before or after making changes to the collectors?
No, core LogicModules won’t be affected by the changes, and will not require any updates. However, if there are any custom modules, it is advisable for customers to review them to ensure they do not require administrator permissions.
If I’m an MSP, how do I delegate this to each of my accounts?
For MSP accounts, collectors are usually installed in the individual domains of each customer. Therefore, you will need to obtain the end customer’s approval and assistance to make any changes to the permissions related to the monitoring account. We recommend providing a list of collector IDs that will need to be migrated so these efforts can be coordinated. If you require assistance identifying which collectors are using administrator accounts, please contact LogicMonitor Support Team.
Are there instructions for organizations that have 400+ windows servers? Does this complicate onboarding of new Windows Servers, since the same process would need to be completed for each new server being monitored?
Please use the process outlined in the WinRM guidance to automate via GPO: https://www.logicmonitor.com/support/configuring-winrm-for-windows-collector#h-automating-winrm-non-admin-configuration
For making the SDDL changes in the least privilege documentation, for the WMI Namespace Security, and Windows Service permissions, do these steps need to be performed on each of the collectors, on all monitored servers, or just once from a single server?
For non-domain based setups, the steps can be completed on each machine. For Domain based setups, it is convenient to complete it via a GPO policy.
For the Windows admin mandate, does this also apply to accounts specified with wmi.user/wmi.pass?
The first target is to move the Collector service user (user account under which collector service runs) to a non-administrator account.
When we allowed access to the WMI user on SCManager, we were able to query several windows services, but not various application services. Are the same steps to be followed for each service? Is it expected to get access to services other than SCManager? How are we able to query several services after enabling access on SCManager?
The current script gives permissions to services not just under SCManager, but also to other services which are fetched currently in our script: $Services = Get-Service | Select-Object Name (basically Win32_Services), and also two (2) services, logicmonitor-agent and logicmonitor-watchdog. If any specific service is not covered in the above pool, then for that we have provided manual steps, which need to be followed on all the resources involved. Please see this supporting documentation for further details.
Can you provide me with active API tokens that are currently built using the lmsupport user account?
You can find details on active API tokens and their last usage information in the UI display tabs for "LMv1," "Bearer," and "Widget" tokens. Follow these steps:
For the usage details of those API tokens, refer to the audit logs. For more information, visit API Tokens.
How do I get better logging of systems that are connecting to LogicMonitor via the API to find where I need to make updates?
You can use the LM Portal Audit Log to determine the source IP address and API detail information. This will help you track down where to look for updates, or where the token might be utilized. For more information, please visit the Audit Logs Report.
If LogicMonitor team members built an API token with the lmsupport account on our behalf, how do I know if it is still needed?
You can check the “API Tokens” tab under “Users & Roles” in the LogicMonitor Portal, and review the “Last Used” date. If this field is empty or shows a non-recent date, you can consider disabling and later deleting the token, once it's confirmed to be non-impacting..
How am I supposed to programmatically create and deploy collectors or user accounts without administrator rights to the API?
LogicMonitor only requires customers to migrate to a token that is not under the lmsupport user account, or using the default administrator role. Customers can still create roles specific to their needs which allow managing permissions for both collectors and user operations. This way, you can programmatically create and deploy collectors or user accounts, while adhering to security best practices.
Will LogicMonitor introduce an automation API token type?
Currently, an “API Only” user can be created and assigned API tokens. For more details, please visit LogicMonitor Users and Roles.