No. 07Week of September 23, 2026This week’s briefing
Tradecraft

Format6 published

Explainers

One question, answered well, with sources. Updated when the facts change.

Explainer

Carrier-native authentication, explained: how a SIM can sign a login

Carrier-based authentication verifies a user through their mobile operator instead of sending them a code. The simplest form checks that a request comes from the SIM tied to a phone number; stronger forms use cryptographic keys held in the SIM to sign the request.

Explainer

The FCC’s SIM-swap rules: what carriers now have to do

The FCC’s 2023 order (FCC 23-95) requires US wireless carriers to authenticate customers securely before moving their number to a new SIM or provider, to notify customers of SIM change and port-out requests, and to offer account locks. It does not regulate how banks or apps use SMS codes.

Explainer

SIM swap attacks, explained

A criminal persuades, tricks or bribes a mobile carrier into moving a victim’s phone number to a SIM they control. From then on the victim’s calls and texts, including one-time passcodes, go to the attacker.

Explainer

Are synced passkeys phishing-resistant?

Yes. A passkey is bound to the website it was created for, so it can’t be entered on a look-alike site. NIST’s 800-63-4 update accepts synced passkeys at AAL2. The main new risk is the account that syncs them, which needs strong protection of its own.

Explainer

Why OTP bots keep working against bank customers

An OTP bot is an automated calling or messaging service that impersonates a bank or other service and persuades the victim to read out or type in a one-time passcode, which the criminal uses at the same moment to log in or approve a payment.