Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

How we deployed post-quantum TLS without any code changes

In March, we announced our first major post-quantum milestone. Customers using a compatible browser could negotiate X25519MLKEM768 when connecting to the 1Password web app. This protected browser traffic from harvest-now, decrypt-later attacks (HNDL) without any customer action required. While this release raised the bar, it did not cover other ways customers connect to 1Password.

Your First Dark Web Scan Report, Explained

Most people don't hesitate to run a free security scan because they doubt it'll find anything. They hesitate because they don't know what the results will look like. Will it be 40 pages of raw data without context? A sales pitch disguised as a report? We'll walk through it screen by screen so you know exactly what to expect before entering a domain.

Why Retired IT Equipment Can Become a Cybersecurity Blind Spot

The security team at a mid-sized insurer spent eighteen months hardening everything that faced the internet. They rotated credentials, tightened their identity provider, and ran tabletop exercises until the incident playbook felt routine. Then a contractor bought a pallet of decommissioned laptops at a regional auction and found four of them still booting into a cached domain profile. Nothing had been breached. The data simply walked out through the loading dock, on equipment the company had already stopped thinking about.

Protecting Assets from Cyber-Physical Attacks

Our digital and physical worlds are now closely linked. This connection brings incredible efficiency, but it also creates new vulnerabilities. When digital systems control physical infrastructure, a security failure can have real, tangible consequences. Protecting your assets today means having a strategy that tackles threats in both these areas at the same time.

AI governance monitoring: how to prove your program is actually working

Ask a governance lead which of their AI controls actually ran last Tuesday at 2:14 p.m., when a specific agent touched a specific dataset, and the answer usually arrives as a policy document, an org chart, and a shrug. That gap between the controls a program claims to have and the controls that actually fired when an agent acted is where AI governance quietly fails. Policy documents describe intent. Model monitoring tracks accuracy and drift.

Two Reporting Clocks on One AI Product, Only One Running

An AI product sold in Europe is described as facing two incident reporting duties. One under product security rules and one under AI rules, with different triggers and different deadlines. ‍ Only one of them is running. Article 14 of the Cyber Resilience Act has applied since 11 September 2026. The AI duty moved, and coverage published in the last few weeks still describes it as live. ‍

AI Governance as a Condition of Writing Coverage

Insurers are subject to AI governance rules and they are also the party asking other organizations AI governance questions as a condition of coverage. More than twenty states have adopted the model bulletin that turns AI oversight into an operational requirement for carriers, and those same carriers now send AI questionnaires to their corporate insureds. ‍ The sector facing both is well covered. What follows from it is not, and it produces something an insured can use. ‍

Security Interviews Should Leave Room for What Remains Unknown

An incident story can sound impressively clear once everyone knows how it ended. The suspicious login becomes an obvious warning, the escalation looks inevitable, and the response appears to follow a straight path. A security interviewer needs to look earlier in the story, when the candidate had incomplete information and still had to choose what to do.