Reports say exploitation began weeks before a fix was available. Besides patching, checking for unfamiliar PHP files, rotating credentials and reviewing session logs, what else should we investigate?
BeyondTrust Remote Support is patched. How far back should we investigate?
Answers
Don't stop at the appliance. Review support session reports for unfamiliar representatives, unusual hours and unexpected endpoint access. Also check for jump items and API accounts created during the period you're investigating.
Follow suspicious sessions onto the affected endpoints. A clean appliance after patching wouldn't tell you what happened on a machine reached through it.
Reply to this answer
Go back as far as your logs allow, not just to August 29. That was reportedly the earliest confirmed exploitation, not necessarily the first attempt. Record the retention limits too, so the investigation doesn't imply coverage you don't have.
Appliance audit exports may be easier to review over a long period than a paginated console. Pull firewall or network flow records as well and investigate unexpected outbound connections, accounting for known endpoints and vendor update hosts.
Reply to this answer
I'd widen the credential rotation beyond accounts seen in session logs. Inventory credentials and API keys stored on the appliance, plus linked credential stores and privileged accounts it could reach. Check for unfamiliar accounts or keys as part of the review.
Those session records won't necessarily show every resource the appliance could access.
Reply to this answer
Verify the fix on every appliance, including test and disaster recovery systems. Confirm the installed versions and rescan the external addresses afterward. It's also a good time to review which support and admin interfaces actually need to be publicly reachable.
Reply to this answer
For ongoing detection, look at what security tooling can see around the appliance and connected endpoints. A web or PHP service spawning an unexpected shell or network utility is one example worth investigating. Patching closes the known hole, but behavior monitoring can help catch activity that a version check won't.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_c58~drainwhistle.4:
A VPN or another access layer can reduce exposure, though it doesn't replace checking for earlier access or fixing the appliance itself.