A11ey
Former Employee
Joined 2 years ago
User Profile
User Widgets
Contributions
Important Security Announcement
Hello LM Community! Important Security Announcement As part of our ongoing commitment to enhancing security for our customers, LogicMonitor will be requiring stronger security measures to protect your account. This page is to serve as both an announcement and a landing page for resources you may need. Your account will need to be in compliance with the following security mandates by December 31, 2024, to avoid any disruptions to your service. Please review the items below and take appropriate actions to ensure a secure experience with LogicMonitor. Security Mandates Two-Factor Authentication (2FA) Two-Factor Authentication Summary: Two-factor authentication (2FA) provides an extra layer of security for accessing any LogicMonitor account. With this upcoming change, users not using SSO (Single Sign-On) will be required to use 2FA. This means, in addition to a username and password, users will need to verify their identity using a third-party application such as Authy, an authentication token delivered via SMS/voice, or authenticate via email. Quick Reference Guide (QRG) Supporting Documentation: Linux Collectors Least Privilege Migrating Linux Collectors Installation Process Summary: Previously, LogicMonitor required collectors to use root credentials to collect data from the resources it monitored. As part of our commitment to increasing security standards, and meeting the feedback of our customer base, with the release of GD 36, we have introduced the capability of collectors to run using non-root credentials. We ask that customers promptly change to non-root credentials, which will improve security and reduce risk. Moving forward, LogicMonitor is requiring all Linux collectors to be migrated to run under non-root users. Our enhanced migration process allows this transition without uninstalling the collector or losing any data. Customers can follow either the prompt-based or silent migration processes to complete the transition. Quick Reference Guide (QRG) Supporting Documentation: Windows Collectors Least Privilege Summary: Originally, LogicMonitor required Windows collectors to run using administrator (admin) credentials to collect data from the resources it monitored. As part of our commitment to the highest security standards, we have continued to invest in security features and risk mitigation for our customers. We have now extended the capabilities of collectors to utilize non-administrator (non-admin) credentials for data collection. Moving forward, LogicMonitor is requiring all Windows collectors to be migrated to utilize non-administrator accounts to monitor their systems. Our enhanced migration process allows this transition, without uninstalling the collector or losing any data. Customers can follow the prompt-based migration processes to complete the transition to non-administrator accounts. Non-admin essentially means moving away from an excessively privileged account for monitoring. Update on the Windows Collectors Least Privilege Security Mandate: What happens at the end of the year if collectors are still using administrative privileged accounts for the collector service and query user? Based on our customers’ unique environmental landscape and needs, if the collector is still configured to use accounts with Administrative privileges on December 31, 2024, we will not prevent collectors from communicating with LogicMonitor. We do however strongly recommend you utilize non-administrator accounts to monitor your systems as our migration process allows this transition, without uninstalling the collector or losing any data. We understand that 100% compliance with a non-admin is not possible, if the technology you’re monitoring REQUIRES administrative privileges. Logic Monitor is currently reviewing the best options in order to limit the attack surface in these scenarios, while also minimizing disruptions. Once we have refined the solutions that best fit customers’ unique circumstances, we will provide ample timing for our customers to implement any required changes.The goal of this security mandate is not to dictate how customers manage Windows accounts, but rather to help our customers better adopt security best practices (Principle of Least Privilege), as it relates to the collector service user and collector query user. Quick Reference Guides (QRG) Supporting Documentation / How To Guides Migrating Windows Collectors Setting up non-Admin for WMI on Windows API Tokens Summary: Roles within the LogicMonitor platform define the permissions and configurations that determine a user's interactions. The administrator role, in particular, grants permissions across all areas of the platform, enabling administrators to perform any action, including those that are security-sensitive. REST API tokens are used to authenticate requests to the REST API, allowing users to programmatically manage their LogicMonitor resources, dashboards, devices, reports, services, alerts, collectors, datasources, scheduled downtime (SDTs), and more. To enhance security and maintain the integrity of our systems, we disabled the ability for customers to create API tokens using LMSupport user accounts or the default administrator role. This restriction helps prevent unauthorized access and potential misuse of elevated permissions, ensuring that API keys are generated and managed within a controlled and secure framework. The combination of out-of-box (OOB) admin permissions with the use of an API token poses significant risks, potentially leading to unauthorized actions and disruptions within a LogicMonitor portal. Below are the conditions which will be enforced by the Security Mandate for API tokens: Tokens generated on LMSupport user account Tokens generated on a user that has the out of the box “Administrator” role, even if that role was re-named. Action: Please migrate to a new API token, created under a new user or role, which has appropriate permissions for how the API is being called. Quick Reference Guide (QRG) Supporting Documentation: API Tokens API Best Practices Guide (coming soon!) LogicMonitor Security Best Practices LogicMonitor Security Best Practices If you have any questions or need assistance, please contact our Technical Support Team.LogicMonitor Security Best Practices
At LogicMonitor we take the protection of customer data and cybersecurity very seriously. Security is a team effort and partnership between LogicMonitor and our valued customers. Below we have provided our recommended guidance on security best practices, and how to keep your LogicMonitor portals secure, including the 2FA authentication enablement. General Security LogicMonitor Security Corporate site: LogicMonitor’s Security corporate site provides resources for our customers who are interested in reviewing our security white papers or accessing SOC2 Type 2 and SOC3 reports. Security Best Practices: This comprehensive document offers invaluable security guidance and best practices which LogicMonitor strongly recommends be diligently followed. It also provides critical insights into how LogicMonitorsecures customer accounts, such as regular updates to strong, unique passwords and not sharing account information. Configuring Multi & Single Sign On Single Sign-On Integration Setup Guide: Single Sign-On (SSO) is a powerful mechanism for enforcing robust authentication measures, including 2FA, while simultaneously mitigating the risk of password-related issues. This guide outlines the prerequisites and initial setup steps for SSO, including how to restrict account access to SSO user accounts. Multi Sign-On Integration Setup Guide: Multi-sign on augments security by requiring multiple authentication factors. This document empowers administrators to add multiple tenants (Identity Providers), and manage users directly from their Identity Provider (IdP). Microsoft Azure Active Directory (AD) IdP for Single Sign-On (SSO) Setup Guide: Customers interested in utilizing Microsoft Azure Active Directory (AD) IdP for SSO will find this guide invaluable. It provides step-by-step instructions for integrating Azure with LogicMonitor. Additional Tools to Increase Security Account IP Whitelisting: Customers looking to restrict access to their accounts, based on specific IP addresses or subnets, can refer to point five (5) in the "Configuring the Portal Settings" section document for detailed guidance. Role Based Access Control settings: Role-Based Access Controls offer a powerful means of restricting access to security features or entire product sections for specific user groups. This document explains the numerous configurations available at the role level, ensuring that your security posture aligns seamlessly with your business requirements. Preparing for two-factor authentication (2FA) Remote Session Access Control: In preparation of implementing 2FA, this document comprehensively explains the Access Controls available for the Remote Session feature, allowing for enhanced security through customizable access restrictions or feature disabling. 2FA Setup Guide: This guide provides step-by-step instructions on configuring 2FA at various levels. LogicMonitor strongly recommends customers who are not currently using 2FA or employing Single Sign-On (SSO), without enabling the "Restrict to SSO" option, proactively enable 2FA for their non-SSO user accounts. User Reporting for 2FA: The User Report serves as a vital tool in securing your account with 2FA. It facilitates the identification of user accounts that do not currently utilize 2FA or lack associated phone numbers, which could potentially disrupt user access, if not addressed before 2FA is activated. See also 2FA FAQ’s & User Reports.LogicMonitor Introduces Edwin AI to Enhance Observability
LogicMonitor has unveiled Edwin AI, a new artificial intelligence designed to significantly boost observability capabilities. Edwin AI integrates with LogicMonitor's existing platform, leveraging machine learning and advanced analytics to provide deeper insights, predictive capabilities, and more efficient monitoring of IT environments. This innovation aims to simplify IT operations, enhance performance, and proactively address issues before they impact business operations. Edwin AI represents a major step forward in the application of AI to IT infrastructure management, promising to streamline processes and improve overall system reliability. For more details, visit the official press release here.LM User Group Dinner Series Kick Off
Exciting news alert! 🎉 We're pumped to let you know that in May - June 2024, we're kicking off a series of User Group Founding Member events with TopGolf dinners in Dallas, Atlanta, New York, Chicago and Charlotte! These gatherings are going to be the bomb - think networking, delicious food, and juicy discussions about YOUR success and the future of LM User Groups. Join our LogicMonitor Leaders, Marc Degenkolb (Vice President of Sales), Brian Youngblood (VP of Corporate Sales), Steven Kahn (VP of Enterprise Sales), and Kristen Engelhardt (VP of Customer & Product Enablement), to learn more about this exciting development. This dinner is a prime opportunity to network with industry peers, indulge in great food, delve into the LM User Group program, and connect with like-minded LM customers passionate about Hybrid Observability and AIOps. But here's the deal: space is limited to just 10 per location, so don't snooze on this. Secure your spot pronto! Click on the location above where you're keen to attend, and fill out the registration form. Easy peasy! Let's make these events epic together! If you're not in one of these first-round cities, no worries! Just drop us a line below with your interest and location, and we'll add your city for a future event!. Catch you soon! 🌟
Groups
Inner Circle
Welcome to the Customer Showcase, sponsored by “The Inner Circle “. Feel free to peruse this Customer Story Showcase to read more about what our customers are doing out in the world and how LogicMonitor is supporting their journeys.LM User Groups
Welcome to the Customer User Group! Join below to get updates! We are just kicking off this space, and we invited you to post ideas and ask questions.Open Beta
Open Beta Process During this open beta period, we are asking that your team members flip the toggle and explore all the new features and functionality while attempting to complete their workflows in the new UI. Any identified bugs or feedback on critical functionality loss will help us to ensure your success and value in this new offering. *Please note, depending on what’s discovered, users can always toggle back to the current UI and continue with their work. Identified bugs or Feedback can be submitted through the following routes: Bugs: Please submit directly through the “Submit a Support Ticket” option using your instance. The more specific you can be on where you experienced the bug, the better. Functionality Feedback: Please submit through the “Feedback” option in your LogicMonitor instance and include “New UI” in the Subject line to ensure it’s routed appropriately.Roche Community
Welcome to the Roche Diagnostics sub-community on LogicMonitor! Connect with fellow Roche Diagnostics users here to share insights, best practices, and optimize monitoring strategies tailored to your specific needs. Let's collaborate and leverage LogicMonitor's capabilities to enhance operational efficiency and drive success.
