Secure BeyondTrust playbook for self-hosted appliances

Secure your self-hosted Remote Support or Privileged Remote Access appliance with a step-by-step PDF. We built this method on our own ScreenConnect server; this edition applies the same method to BeyondTrust appliances.

$79

One-time payment. Instant PDF download. No refunds.

  • For self-hosted Remote Support (RS) and Privileged Remote Access (PRA) only.
  • BeyondTrust-specific instructions, with preparation and testing.
  • Rollback steps so you can reverse your changes.
  • Free email support on the solution.

Why review BeyondTrust security now?

BeyondTrust reported exploitation involving self-hosted appliances in 2026. Its February advisory covers Remote Support and Privileged Remote Access. Its October disclosure confirms Remote Support zero-day exploitation. If you run your own appliance, verify the patches and follow the vendor's investigation guidance before treating the incident as resolved.

  • February: CVE-2026-1731 allows remote command execution without authentication. BeyondTrust observed exploitation against internet-facing self-hosted environments that remained unpatched before February 9 (BT26-02).
  • October disclosure: BeyondTrust dates zero-day exploitation of CVE-2026-102764 to August 29, against one BeyondTrust-hosted and one self-hosted Remote Support instance. The vulnerability allows remote file operations (incident timeline, BT26-05).
  • PRA distinction: BeyondTrust found no exploitation path in its PRA testing for the October vulnerability. It released a precautionary patch because PRA shares the affected code and recommends immediate installation (vendor guidance).

Read the free guide for the timeline and vendor response steps: BeyondTrust Remote Support attacks in 2026.

What we saw on our own ScreenConnect server

Our experience started with a different remote-support product.

We found rogue unattended sessions on our own on-premises ScreenConnect server. After we applied the method, we saw no new rogue sessions and no brute-force login attempts.

That is an observation from one server. It does not prove the changes caused the result.

The BeyondTrust attacks prompted us to apply the same method to RS and PRA in this edition, using BeyondTrust's documentation for the product-specific instructions.

We have not run this method on BeyondTrust. We still patch our own server and follow the vendor’s guidance, and you should too.

What is in the BeyondTrust playbook?

You get instructions for applying the method to a self-hosted RS or PRA appliance, from preparation through testing. Use the fit check before making changes. Work through the steps, check that your support work still functions, and use the rollback instructions if you need to reverse a change.

  • Our ScreenConnect experience and the limits of that evidence
  • The 2026 BeyondTrust attacks and vendor response guidance
  • A fit check for your deployment
  • A preparation checklist before you make changes
  • The step-by-step method for self-hosted appliances
  • Product-specific instructions for RS and PRA
  • Checks to confirm your support work still functions
  • Rollback instructions
  • Ongoing maintenance
  • A checklist for suspected compromise

Is the BeyondTrust playbook right for your deployment?

It fits if you run your own BeyondTrust Remote Support or Privileged Remote Access appliance and want a step-by-step way to secure it on top of the vendor patches. It is not for BeyondTrust SaaS or other BeyondTrust products, and it does not clean up an intrusion. Check these points before you buy.

  • Self-hosted RS and PRA only. That includes virtual appliances you run in your own cloud account.
  • Keep patching. Apply the vendor's required updates and follow its investigation guidance. The playbook is an extra layer.
  • It does not remove an existing compromise. If you suspect an intrusion, preserve evidence and contact BeyondTrust support. You may need incident response and a clean redeployment.
  • No refunds. Confirm that you run a self-hosted RS or PRA appliance before purchasing.

Secure BeyondTrust Playbook

$79

One-time payment. No refunds.

  • For self-hosted RS and PRA only
  • PDF, instant download
  • Free email support on the solution: support@threatlistpro.com
  • Updates to this edition through the same download link

FAQ

Have you run this method on BeyondTrust?

No. We built the method on our own on-premises ScreenConnect server after finding rogue unattended sessions. We have seen no new rogue sessions or brute-force login attempts since applying it. That is one server's observation. This edition applies the same method to BeyondTrust appliances using vendor documentation.

Does this cover BeyondTrust SaaS?

No. This edition is only for self-hosted BeyondTrust Remote Support or Privileged Remote Access appliances, including virtual appliances in your own cloud account. BeyondTrust patches its SaaS service for you. Check how your deployment is hosted before you buy, because there are no refunds.

Does this replace patching or remove an existing compromise?

No. Keep applying BeyondTrust's patches and follow its investigation guidance. The playbook adds a security layer on top of them. It does not remove an existing compromise, and applying it won't tell you whether one exists. If you suspect an intrusion, preserve evidence and contact BeyondTrust support first.

Can I get help applying the playbook?

Yes. Your purchase includes free email support on the solution in the PDF. Write to support@threatlistpro.com with questions about applying the steps to your setup. The playbook also covers testing and rollback so you can check your changes and reverse them if you need to.

What do I get for $79?

You get the Secure BeyondTrust Playbook as an instant PDF download after checkout. You pay $79 once. There are no refunds. Updates to this edition use the same download link. Free email support on the solution is included at support@threatlistpro.com. Check the self-hosted scope before buying.

Also from ThreatListPro: the ThreatListPro blocklist for VPN brute force protection. It is a separate product: 5.4M+ IPv4 addresses, checked for new attackers every 6 hours.

Sources