Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Proton66 Part 1: Mass Scanning and Exploit Campaigns

Trustwave SpiderLabs continuously tracks a range of malicious activities originating from Proton66 ASN, including vulnerability scanning, exploit attempts, and phishing campaigns leading to malware infections. In this two-part series, SpiderLabs explores the malicious traffic associated with Proton66, revealing the extent and nature of these attacks.

Amazon EC2 Instance Metadata Targeted via Server-Side Request Forgery (SSRF)

CVE Trends, Vulnerabilities of SSRF On March 25, 2024, the National Security Agency (NSA) and the Cybersecurity and Infrastructure Security Agency (CISA) issued a joint cybersecurity advisory about an increasing yet commonly overlooked web application vulnerability, Server-Side Request Forgery (SSRF).

Strategies to Mitigate Risks in AI-Driven Medical Note Systems

AI isn't just changing how healthcare works-it's redefining how care is delivered. With medical note systems powered by AI, clinicians are finally getting a break from endless documentation. But with that freedom comes a new set of challenges: accuracy, data safety, and the delicate balance between tech and human judgment. If you're adopting or managing these tools, it's not just about innovation-it's about protecting what matters most. Read on to discover the key strategies every healthcare leader must know to implement AI documentation systems responsibly and effectively.

Chinese APT Exploits Ivanti CVE-2025-22457 with Malware

A newly disclosed vulnerability in Ivanti Connect Secure (ICS) VPN appliances has been weaponized in the wild by a Chinese nation-state threat actor, UNC5221. Tracked as CVE-2025-22457, this critical stack-based buffer overflow vulnerability allows unauthenticated remote attackers to execute arbitrary code, posing a significant risk to enterprise networks.

How RemOps Improves Security Without Slowing Down Engineering Teams

You’ve heard it a hundred times – security is everyone’s responsibility. But when security starts slowing things down, it’s usually engineering teams that feel the pain. Nobody wants to be the one responsible for shipping vulnerabilities into production, but at the same time, nobody wants security to be the reason releases grind to a halt. This is the dilemma DevSecOps was supposed to solve – bringing security into the development process without breaking everything.