Skip to main content
The state of ai impact assessment
ScreenConnect Extensions: A Procurement Security Field GuideSoftware Supply Chain Security
5 min readFor Procurement Security Professionals

ScreenConnect Extensions: A Procurement Security Field Guide

Scope

This guide focuses on managing third-party extensions within IT management platforms, using the ScreenConnect and RMM+ incidents as examples. It's designed for procurement security professionals responsible for approving, contracting, and monitoring tools within privileged administrative software.

We'll explore what these incidents reveal about extension governance, API exposure, and patch dependency in your environment.

Key Concepts and Definitions

Extension (independently developed). Code created by a third party that operates within the platform's trust boundary. ConnectWise described RMM+ as an extension that allows external management tools to automate and control remote sessions via an API.

Extension API as command channel. These extensions expose an API capable of executing remote commands, protected by a passphrase set during setup. Treat this API as a remote code execution path guarded by a shared secret.

Fourth and Nth Party Management. The extension author is a fourth party. Your contract is with the platform vendor or MSP, but the extension author's code runs with the platform's reach into your endpoints.

Operator session hijacking. Blackpoint Cyber researchers reported that attackers can hijack authenticated operator sessions to push malicious code. Patching doesn't close this path.

Requirements Breakdown

No single standard names "remote management extensions," so map your obligations from existing frameworks.

  • ISO 27036 addresses information security in supplier relationships. Your extension author and platform vendor fall within its scope, requiring an understanding of what the supplier's components can access.
  • SR 23-4 expects risk management across the third-party relationship lifecycle, including Continuous Monitoring of Active Arrangements proportionate to criticality. An extension that can execute commands on endpoints should be classified as high criticality.
  • EBA Outsourcing Guidelines and the EBA Guidelines on Sound Management of Third-Party Risk apply if you're an EU institution. Sub-outsourcing visibility and Right to Audit provisions are relevant when a platform vendor's partner ecosystem touches Critical or Important Functions.
  • Vulnerability management obligations. CVE-2026-84869 was flagged by CISA as exploited in September, and Blackpoint Cyber confirmed the existing patch blocks the exploit. Organizations hit were likely unpatched.

Implementation Guidance

1. Build an extension inventory

ConnectWise found approximately 400 partner environments with at least one RMM+ family extension installed. Your first task is to produce a similar list for your tools.

  • Enumerate extensions on every remote management platform you or your MSPs operate.
  • Record the author, version, API exposure, and who configured it.
  • Flag on-premises instances separately. ConnectWise could disable RMM+ in identified environments but told on-premises customers to disable it themselves.

2. Gate extensions at Vendor Intake

Treat an extension as its own vendor, not a platform feature.

  • Require a Pre-Contractual Assessment of the extension author, including how API credentials are generated, stored, and rotated.
  • Ask if the API supports stronger security than a single passphrase: per-client keys, IP allow-listing, scoped permissions, or mutual authentication.
  • Use SIG Core as a baseline, then add extension-specific questions on code signing, update channels, and incident contacts.

3. Secure the API

  • Replace shared passphrases with unique, high-entropy secrets stored in a vault.
  • Restrict API reachability to known management hosts.
  • Log every command executed through the API and forward logs to your SIEM.
  • Alert on repeated login failures and unusual sign-ins, as highlighted by ConnectWise.

4. Protect operator sessions

Patching won't fix a hijacked session. Add controls around high-impact administrative actions: multi-factor authentication for operators, session timeouts, step-up approval for pushing code to many endpoints, and isolation of technician workstations. Treat technician machines as high-value assets.

5. Close the patch loop

Track vendor security advisories and CISA exploitation notices against your platform versions. Set an internal deadline for addressing exploited vulnerabilities and measure against it.

6. Contract for the next incident

  • Add Notification Timeline terms for extension-related events, not just platform-level breaches.
  • Require the vendor to disclose which extensions it can disable remotely and which it can't.
  • Include Termination Rights and a Wind-Down Plan for extensions that fail assessment.

7. Plan for clean-up, not just disablement

Disabling extensions and resetting credentials may not remove unauthorized software or access already established on endpoints. Your Vendor Breach Management playbook should include endpoint threat hunting for additional remote-access software.

Common Pitfalls

  • Assuming the platform vendor's assessment covers extensions. It rarely does.
  • Believing a patch ends the risk. Blackpoint Cyber's testing showed the patch blocks the exploit, but session hijacking remains a separate exposure.
  • Overlooking MSP concentration. ScreenConnect is widely used by managed service providers. One extension can reach many downstream customers. Run a Concentration Risk Assessment on your MSPs' tooling.
  • Waiting for root cause. Huntress hasn't seen evidence of a new vulnerability, and current telemetry points to compromised credentials or hijacked operator sessions. Don't wait for attribution before reviewing credentials and sessions.
  • Forgetting Access Revocation. Rotating the extension passphrase without revoking operator sessions leaves the door open.
  • Ignoring speed. Huntress reported 288 affected endpoints across 48 organizations targeted within 90 minutes. Your Incident Escalation path must be faster than a weekly review cycle.

Quick Reference Table

Control area What to verify Reference point
Extension inventory Author, version, API exposure, owner for every extension; on-prem separately ISO 27036; SR 23-4
Vendor Intake Extension author assessed as its own vendor SIG Core plus extension questions
API authentication Unique secrets, vaulted, rotated; beyond a single passphrase ISO 27036
API network exposure Allow-listed management hosts only Internal standard
Operator sessions MFA, timeouts, step-up approval for high-impact actions Internal standard
Technician workstations Treated as high-value, isolated Internal standard
Patch management CVE-2026-84869 patched; exploited-vulnerability deadline set CISA exploitation notices
Contract terms Notification Timeline, Right to Audit, Sub-Outsourcing Clause covering extensions EBA Outsourcing Guidelines
Response Threat hunting for persistence beyond disablement Vendor Breach Management playbook
Fourth and Nth Party Management Extension authors tracked as fourth parties EBA Guidelines on Sound Management of Third-Party Risk

Start with the inventory. If you can't list the extensions running inside your remote management tools today, every other control in this guide is guesswork.

Promotional banner for the CUI buildout guide

You Might Also Like