Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Audiences around the world may be captivated by dramatic stories of con men like the Tinder Swindler. But this type of fraud is the exception rather than the rule. Most criminals go to great lengths to stay hidden and minimize the risk of getting caught. Sometimes, though, a criminal needs to show their face — or at least, a face — to pass identity checks.

Supplemental document checks are often required for businesses that conduct Know Your Customer (KYC) or Know Your Business (KYB) checks. Even when compliance isn’t required, organizations often collect supplemental documents for their own business purposes, such as risk assessments. In business contexts, a supplemental document is a non-government-issued document that you collect to support a risk assessment.

The skimmer doesn’t go inside the iframe. It doesn’t need to. In every significant payment page compromise of the last decade, the malicious code sat on the merchant’s page, outside the payment component entirely, watching form submissions, intercepting keystrokes, reading values before they ever reached the provider’s sandbox. This is the architecture SAQ A-EP merchants live in.

U.S. state privacy compliance now operates in an environment that doesn’t stand still. The number of state laws keeps growing, and their requirements continue to evolve through new effective dates, amendments, and guidance. By January 2026 alone, Indiana, Kentucky, and Rhode Island added three more state privacy laws. This makes one thing clear. Compliance is no longer something you implement once and revisit periodically. It has to stay accurate as the requirements keep shifting.

The biggest ransomware attacks of 2025 have shown that this threat remains critical for organizations across all sectors. Incidents such as the Change Healthcare attack, which compromised the data of nearly 190 million individuals, and the attack on Jaguar Land Rover, which forced production lines to halt and caused losses amounting to hundreds of millions of dollars, show that a single incident can impact both operational continuity and information confidentiality.

Security vendors love the man-in-the-middle attack. It’s the boogeyman of every TLS marketing page. Some shadowy figure intercepting your traffic, reading your secrets, stealing your data. A man-in-the-middle attack is when an attacker positions themselves between two parties on a network to intercept the traffic flowing between them. In the context of TLS, that means an attacker who can present a valid certificate can read everything in plaintext and proxy it on to the real server.

AI accelerates discovery — but enterprise trust still depends on deterministic validation, remediation automation, and governance at scale. Last Friday, Anthropic launched Claude Code Security, powered by Opus 4.6, inside Claude Code. The demo is impressive: Frontier AI reasoning scanned open source codebases and surfaced over 500 previously unknown high-severity vulnerabilities — including subtle heap buffer overflows that had survived decades of expert review and fuzzing.

Connected products, whether IoT, IIoT, embedded, mobile, or other such devices, serve to either strengthen or undermine an organization’s security posture and reputation. As device ecosystems grow in complexity, manufacturers must secure embedded hardware, firmware, over-the-air (OTA) update mechanisms, companion mobile applications, cloud services and APIs, and RF interfaces. Each layer introduces distinct attack surfaces that adversaries actively target.

Listen to a NotebookLM podcast version of the blog: When Anthropic announced Claude Code’s new security scanning capabilities, following the announcement of OpenAI’s Aardvark, it marked an important moment for the industry. For the first time, expert-level security review is becoming embedded directly into the act of writing code. Subtle, context-dependent vulnerabilities can now be flagged as they are created. Zero-days can potentially be remediated before they ever make it into a build.

In many organizations, there is a dangerous unspoken rule: The SOC handles endpoints and networks; Engineering handles APIs. This silo creates a massive blind spot. We recently spoke with the Senior Manager of Security Engineering at a major insurance provider, who described this exact pain point.