1-minute read
What a defender needs to know
Elastic Security Labs confirmed 23 findings involving remote monitoring and management (RMM) tool abuse between April and September 2026. ScreenConnect was the product named most often. The number counts findings, not ScreenConnect installations or distinct affected organizations. An agent can carry a remote session even when its software is signed and familiar to IT.
Compare installed RMM agents, services and deployment history on supported endpoints with your approved support-tool list and deployment tickets. For an unexplained agent or session, preserve installer activity, service creation and process starts, then match them with RMM console session history, controlling account and support ticket. Restrict enrollment and console access to approved administrators and remove unauthorized installations through your managed software process. Ask the tool owner for console-side history when endpoint logs alone cannot identify the operator. A signed binary tells you who published the software, not who requested access to your workstation.
Elastic separately describes abuse of trusted cloud applications and identity flows. For Microsoft Entra, review Identity > Applications > Enterprise apps > Consent and permissions > User consent settings. Microsoft recommends limiting user consent to verified-publisher applications; its microsoft-user-default-low policy also limits eligible permissions to those classified as low impact. Agree on the allowed policy with the identity team, save it, and use designated test accounts to check both an allowed request and one requiring administrator consent. A policy change affects future consent only: existing app grants remain in force. Review enterprise-app permissions and revoke unauthorized grants separately. Keep Entra consent observations separate from the 23 RMM findings.
