Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

A Short History of Crypto Customer Data Leaks, and What They Teach

In August 2026, Trezor told about 13,700 US customers that their names, email addresses, phone numbers and shipping addresses had been stolen in a breach at ShipMonk, a logistics company that had once handled its orders. Weeks later the number rose to roughly 80,700, after the company found the stolen records also covered orders placed between late 2019 and mid-2021. Customers who had bought a wallet five years earlier, and long since forgotten the delivery, were suddenly on a list in the hands of an extortion group.

How to reduce DLP false positives

DLP false positives bury real incidents under benign alerts and push teams to switch off the controls they bought. Most of that noise is configuration. Classify sensitive data before enforcement, pair content matches with identity and destination context, phase policies from simulation to blocking, and read override reasons as a tuning signal. Track the trend per policy, and you can show an auditor what the controls do.

Stop accidental data leaks at the source: Configuring DLP in MSP Central

Although a user syncing corporate passwords to a personal cloud account isn't the same as a malicious attack, it is still a massive security risk. When everyday browser features like autofill, third-party cookies, and cloud syncing aren't actively managed, your clients' sensitive data is left vulnerable. In this tutorial, we cover how to set up data leakage prevention (DLP) configurations for your clients using MSP Central.

How Regulated Data Leaks Through AI, One Paste at a Time

A support coordinator has a difficult letter to write. The customer record is open in one tab, a consumer AI assistant in another, and the deadline is this afternoon. She selects the record, copies it, pastes it into the prompt box, and asks for a polite draft. Thirty seconds later she has a good letter and a regulatory problem, and nobody in the organization knows about either. ‍ The sequence below traces that single action through to its consequences.

Phishing Exposes Employee Data at 86% of Fortune 100 Companies

A new report from SpyCloud has found that phishing attacks have exposed employee data at 86% of Fortune 100 companies over the past 12 months, with the technology, airline and automotive sectors being hit the hardest. The researchers also found that 78% of organizations experienced an increase in phishing volume over the past year. Additionally, 84% of respondents named AI-assisted phishing as their top concern, followed by business email compromise (BEC) attacks.

The 5 Questions Every Leak Investigation Needs to Answer

In this video, you will learn the five questions every data leak investigation must answer to be defensible — what the data is, where it originated, who accessed it, where it spread, and the fastest containment step — and why the visibility gap in most security stacks makes those questions impossible to answer instantly. You will also learn how combining DSPM baseline inventory with real-time data lineage replaces the high-stress scramble with surgical containment and audit-ready proof, so you move from "I think we're safe" to "here is the proof.".

Major Security Event: Fortinet VPN Credentials and Configuration Data Exposed for 73,000 Devices

A large-scale credential compromise campaign known as FortiBleed has exposed verified administrator credentials for more than 73,000 internet-facing Fortinet FortiGate firewalls. As of mid-June 2026, the dataset is reportedly circulating within criminal underground communities. Researchers estimate that approximately 50% of all internet-reachable FortiGate devices may be affected across 194 countries, making this one of the most significant Fortinet security incidents to date.

When an Endpoint Forgets to Ask, "Who Are You?": Inside the ServiceNow June 2026 Data Exposure

On June 5, 2026, ServiceNow quietly pushed a security update to hosted customer instances. The fix, described in an internal knowledge base article, addressed a flaw that let unauthenticated users gain more access to ServiceNow-hosted data than they were ever supposed to have. No password. No credentials. The remediation itself tells the whole story: ServiceNow changed an endpoint configuration to restrict access to authenticated users only. Read that again.

CISA's GitHub Leak Is a Preview of the MCP Security Problem Every CISO Is About to Inherit

America's cybersecurity agency left its production credentials sitting in a public GitHub repo for six months. The same failure pattern is now being automated by AI agents in every enterprise running Cursor, Claude Desktop, or Copilot.