How to Respond to an RDP Brute-Force Attack in Healthcare
A Remote Desktop Protocol (RDP) brute-force attack involves repeated attempts to guess account credentials. In a healthcare environment, even unsuccessful attempts deserve prompt attention: an exposed remote-access service can put clinical systems, electronic protected health information (ePHI), and patient care at risk.
Use your incident response plan, involve both security and clinical leadership, and treat suspicious activity as a potential compromise until your investigation establishes what happened. A series of failed attempts alone does not prove an attacker accessed a system, but it may reveal exposed Remote Desktop Protocol access or a compromised password.
How should healthcare teams contain an RDP brute-force attack?
Activate your incident response process and assign clear responsibilities for technical containment, clinical continuity, evidence handling, and communications. Use a trusted, out-of-band channel—such as phone calls—for coordination if you suspect an attacker can monitor organizational systems or email.
- Restrict the exposed path. Block unauthorized RDP traffic at the firewall, remote-access gateway, or other control point. If RDP is not needed, disable it. If it is needed, limit access to approved sources and authorized users.
- Protect accounts and sessions. Disable or restrict accounts with suspicious activity, terminate unauthorized sessions, and revoke relevant remote-access sessions or credentials where your identity systems support it. Coordinate changes so you do not disrupt essential clinical work.
- Isolate affected endpoints when warranted. Use endpoint detection and response (EDR) or network controls to isolate a suspected compromised host from other systems while preserving evidence. Prioritize systems that could enable lateral movement or expose ePHI.
- Escalate proportionately. If activity is widespread, involves privileged accounts, or appears linked to malware or data theft, expand the response to affected network segments and engage your incident-response provider, leadership, and relevant legal or privacy teams.
CISA recommends isolating affected systems and warns that powering devices down can destroy evidence stored in volatile memory. Weigh containment against clinical needs and evidence preservation; document decisions and actions. See the CISA StopRansomware Guide for containment and recovery considerations.
How can hospitals preserve evidence and determine whether an RDP login succeeded?
Preserve evidence before routine cleanup, log rotation, password resets, or system rebuilds erase useful information. Record the incident timeline, affected hostnames, account names, source IP addresses, time zone, and response actions. Export relevant logs to a secure location with access controls, and retain the original records where possible.
Review authentication logs from the affected endpoints, domain controllers, remote-access gateways, VPNs, identity providers, and security monitoring tools. On Windows systems, Security event 4625 records a failed logon; event 4624 records a successful logon. For an RDP session, event 4624 logon type 10 indicates a RemoteInteractive logon. Review the account, source address, timestamp, and other event details, then correlate them with gateway records and endpoint telemetry. Microsoft explains these events in its documentation for event 4624 and event 4625.
A successful authentication is important evidence, but it does not by itself establish what the account accessed or whether PHI was viewed, acquired, or disclosed. Check for unexpected sessions, privilege changes, new accounts, remote administration activity, file access, unusual data transfers, and suspicious processes. Preserve EDR alerts, firewall records, relevant application and database logs, and available network telemetry to build a fuller timeline.
Do not assume that turning off a system is the safest first step. If a device may contain useful live evidence, consult qualified responders about preserving it. NIST’s Guide to Integrating Forensic Techniques into Incident Response discusses volatile data, evidence collection, and documenting investigative actions.
How should clinical teams protect patient care during system downtime?
Coordinate technical containment with clinical operations before isolating systems that support patient care. Clinical leadership should identify affected services, dependencies, and immediate safety risks, then activate the organization’s downtime procedures when needed. Avoid changes that could unexpectedly interrupt access to medication, diagnostic, scheduling, or patient-record systems.
Use approved downtime workflows to support essential functions, communicate system status to care teams, and track orders and documentation that must be reconciled after restoration. Restrict access to any temporary records containing patient information and follow established procedures for secure handling and later entry into restored systems.
HIPAA’s Security Rule requires covered entities and business associates to have contingency procedures that address emergencies affecting systems containing ePHI. HHS describes contingency planning as including data backup, recovery, and continued operation of critical processes in emergency mode in its Summary of the HIPAA Security Rule. Use your organization’s tested downtime and emergency-mode procedures to guide clinical operations during the incident.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhich RDP access controls and account security measures should be applied?
After immediate containment, address the conditions that made repeated RDP attempts possible. Review every RDP-enabled endpoint and gateway, identify which systems need remote access, and remove access that is unnecessary. Avoid exposing RDP directly to the public internet; use a controlled remote-access path and limit which users and devices can connect.
- Require multi-factor authentication. Apply MFA to remote access, especially for privileged and high-impact accounts. Where feasible, favor phishing-resistant methods. A password alone should not be the only barrier to remote access.
- Apply an account lockout policy carefully. Set thresholds and lockout durations that help resist password guessing while accounting for the risk that an attacker could deliberately lock out clinical or administrative users.
- Use least privilege and unique accounts. Limit RDP access to users who need it, use separate administrator accounts for privileged work, remove stale access, and avoid shared accounts where individual accountability is needed.
- Monitor and maintain access systems. Centralize authentication logs, alert on unusual attempts and successful remote logons, keep operating systems and remote-access components updated, and use EDR to detect suspicious activity on endpoints.
- Segment the network. Limit which remote users and systems can reach sensitive servers, clinical environments, and backup infrastructure. Restrict unnecessary ports and protocols.
CISA, FBI, and HHS recommend securing and monitoring RDP, restricting its use, applying MFA, enforcing account lockouts, and reviewing RDP login attempts in their joint advisory on Daixin Team ransomware activity. HIPAA’s current Security Rule requires appropriate safeguards for access, audit controls, and authentication; it does not name one specific RDP configuration as universally required. HHS summarizes those standards in its HIPAA Security Rule guidance.
How can healthcare organizations recover affected systems safely?
Do not restore a compromised system until responders have contained the attack, assessed its scope, and removed the attacker’s access. Investigate whether the attacker created accounts, changed remote-access settings, installed malware, altered security tools, or reached other systems. Reset affected credentials from a trusted device or environment, and review privileged and service accounts for signs of compromise.
Restore from verified data backups that are known to predate the compromise and have not been altered or reached by the attacker. Where feasible, rebuild affected systems or restore them in a clean, segmented environment rather than returning potentially compromised devices directly to production. Before reconnecting systems, apply security updates, confirm access controls, check system integrity, and validate that monitoring is working.
Prioritize recovery based on patient safety and operational dependencies. Test restored systems and data with the teams that rely on them, then reconnect services in a controlled sequence. Continue monitoring authentication logs, EDR alerts, and network activity for signs that the attacker or malware remains. HHS identifies backup, restoration, emergency-mode operations, and contingency planning as elements of the Security Rule in its HIPAA Security Rule summary.
What should organizations assess about potential PHI exposure and notification obligations?
An RDP brute-force attempt does not automatically establish a reportable HIPAA breach. The organization must determine whether there was an impermissible use or disclosure of PHI, whether the information was unsecured, and whether an exception or an applicable risk assessment changes the notification analysis. Involve your privacy officer and legal counsel promptly; preserve the evidence supporting the decision.
For an impermissible use or disclosure of PHI, the Breach Notification Rule generally presumes a breach unless the covered entity or business associate demonstrates a low probability that the PHI was compromised through a risk assessment. HHS says the assessment considers the nature and extent of the PHI, who received or used it, whether it was actually acquired or viewed, and how effectively the risk was mitigated. Review the HHS Breach Notification Rule guidance for the rule and its exceptions.
When notification is required for a breach of unsecured PHI, covered entities must notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery. Notification to HHS is due without unreasonable delay and within 60 days when a breach affects 500 or more individuals; breaches affecting fewer than 500 individuals may be reported to HHS annually, within 60 days after the end of the calendar year in which they were discovered. Media notice may also be required when a breach affects more than 500 residents of a state or jurisdiction. Business associates must notify the covered entity as required by the rule and their business associate agreement. Check the HHS notification requirements, as well as applicable state laws and contractual obligations.
Effective response connects rapid containment with careful evidence preservation, continuity of patient care, secure recovery, and a documented PHI assessment. Use the incident to reduce unnecessary RDP exposure, strengthen account protections, and test your downtime and recovery plans.
FAQs
What should a healthcare organization do first after detecting RDP brute-force activity?
Activate the incident response process, notify security and clinical operations leads, and restrict the suspicious RDP access path without disrupting essential care. Preserve relevant authentication logs and assess whether any account or endpoint shows signs of a successful login.
How can responders tell whether an attacker successfully logged in through RDP?
Review Windows Security event 4624 for successful logons and check whether the logon type is 10, which indicates a RemoteInteractive logon. Correlate the account, source address, and time with gateway, identity-provider, endpoint, and application records. A successful login does not by itself prove that PHI was accessed.
Should affected clinical systems be shut down or isolated?
Not automatically. Isolate a suspected compromised system when needed to limit further access or spread, but coordinate with clinical leadership to protect patient care. Consult incident responders before powering down a device that may contain volatile evidence, unless immediate safety or containment needs require it.
When might an RDP incident require HIPAA breach notification?
Notification may be required if the investigation finds a breach of unsecured PHI and the organization cannot establish an applicable exception or demonstrate a low probability that the PHI was compromised through the required risk assessment. The incident’s discovery alone does not settle the notification question; promptly involve privacy and legal staff and follow HHS requirements and applicable state laws.
Table of Contents
- How should healthcare teams contain an RDP brute-force attack?
- How can hospitals preserve evidence and determine whether an RDP login succeeded?
- How should clinical teams protect patient care during system downtime?
- Which RDP access controls and account security measures should be applied?
- How can healthcare organizations recover affected systems safely?
- What should organizations assess about potential PHI exposure and notification obligations?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today