1-minute read
What a defender needs to know
An intruder used compromised credentials through a poorly configured third-party-managed gateway at a European bank, scanned thousands of systems and guessed administrator passwords over months. Automated requests scraped internal documentation and enumerated shares. The attacker later tried to exploit a remote-code-execution flaw on the central Windows Server Update Services (WSUS) configuration server, which handled software distribution. Palo Alto Networks Unit 42 says its own Cortex XDR product blocked the attempted execution. Its review of telemetry across thousands of endpoints and logs from dozens of servers found no additional presence or persistent backdoors. The bank rotated compromised credentials and reviewed exposed documentation.
Start with the provider-managed gateway: identify the accounts, authentication enforcement and internal routes it grants. Correlate months of gateway and VPN attempts with administrator login failures, broad scan bursts, documentation web requests and WSUS endpoint detections. Enforce strong authentication, rotate exposed credentials and restrict the provider account’s internal reach. Separate WSUS administration from that gateway segment while preserving approved update traffic for clients and any downstream servers. Test from the provider account that WSUS administration is inaccessible and update delivery still functions. The incident account leaves the WSUS vulnerability identifier and build unspecified, so use your actual server inventory and Microsoft advisories to choose patches.