Threat researchCisent
A European bank: the attacker came in through a vendor's gateway
Unit 42 investigated an intrusion that began on a device managed by a third party without strict authentication, and that went on for months before anyone noticed.

On October 13, 2026, Unit 42, the threat research team at Palo Alto Networks, published the case of a European bank that an attacker entered through an external gateway managed by a third party, one that wasn’t configured to enforce strict authentication. Using compromised credentials, the intruder logged in to internal systems. The report doesn’t name the bank or the vendor, and doesn’t explain how those credentials were obtained.1
What happened
The unauthorized VPN access attempts spanned several months.1 According to Cyber Security News’s summary, they continued until the bank’s security team noticed unusual activity on its central IT system.2
Once inside, the attacker scanned hosts and networks across a wide range of protocols, interacted with thousands of systems and ran several password-guessing campaigns focused on administrator accounts. It also copied pages and attachments from internal systems and went through operational and network shares.1
Finally, it tried to exploit a remote code execution vulnerability in the Windows update service on the central configuration management server. The bank’s security tool detected the attempt and contained it before it escalated, and the investigation found no further attacker presence or backdoors.1
Why it matters
Unit 42 describes an opportunistic attacker that didn’t behave like a sophisticated actor, and warns that a lack of sophistication doesn’t make an attacker harmless.1 The case leaves two lessons. The door wasn’t one of the bank’s devices but a third party’s, with weaker access rules than the bank’s own. And the noise lasted for months: VPN attempts, scans and passwords tried over and over.
Where Cisent comes in
Sentinel Defense detects, assesses and blocks attacks in real time alongside the EDR, the firewall and every connected source. A scan or a password campaign shows up while it’s happening, not months later. It acts on its own only where an action can be undone, such as blocking an attacking IP or an intrusive connection, and asks before anything with impact, such as isolating a machine.
Sources
Unit 42, Palo Alto Networks, “The Noise Inside the Network: How an Unsophisticated Attack Exposed a Third-Party Risk”, October 13, 2026. https://unit42.paloaltonetworks.com/noise-inside-network-third-party-risk/↩︎
Cyber Security News, “Attackers Breach European Bank Through Third-Party Gateway and Target WSUS Server”, October 14, 2026. https://cybersecuritynews.com/attackers-breach-european-bank/↩︎