OpenAI Daybreak: Why aren’t my passport + Mac/iPhone passkeys enough? Requiring a separate physical security key feels excessive

API
1

I’m a heavy ChatGPT. Much of the work involves standard production engineering: PostgreSQL, Supabase/RLS, authentication, security boundaries, provenance, access controls, GitHub, etc.

I keep running into cybersecurity restrictions, so I’ve tried everything OpenAI asks to prove I’m a legitimate user.

I’ve verified my real identity with my U.S. passport. I use passkeys. My Mac and iPhone are both secured with their native biometric/device security. I’m on a paid account and I’m perfectly willing to have OpenAI know who I actually am.

Now I’m being told that Daybreak still requires a separate physical FIDO2 security key.

This is where I don’t understand the security model.

A modern Apple passkey is hardware/device-backed authentication protected by the security architecture of devices I already own. My computer locks. My phone locks. My account has a passkey. OpenAI has verified my government-issued identity. Yet apparently none of that is sufficient for Daybreak without buying and keeping track of another physical object that I can lose.

To make matters more confusing, my ChatGPT model selector currently gives me GPT-6 Astra, GPT-6 Sol, GPT-6 Luna, GPT-5.6 Sol, GPT-5.6 Terra, GPT-5.6 Luna and GPT-5.5. There is no “Daybreak Blue” or “GPT-5.5 Cyber” option visible. When using Astra, ChatGPT instead displays:

“This content can’t be shown. Daybreak isn’t available for Astra. Some cybersecurity requests may still be limited.”

I understand why OpenAI needs much stronger controls around advanced cyber capabilities. I actually support having a higher trust threshold for those capabilities.

What I don’t understand is why the trust threshold can’t recognize the combination of:

• verified government identity
• paid OpenAI account
• passkey authentication
• secured personal computer
• secured mobile device
• established account history

and allow that to satisfy the strong-authentication requirement without requiring a separate hardware token.

I’m not trying to anonymously access offensive cyber tooling. I’m trying to build a legitimate enterprise AI governance product, and ordinary security engineering sometimes falls into the same classifiers.

This isn’t just an inconvenience for me. I’m building a company and trying to make this work financially for my family. ChatGPT is one of my primary development tools. I want to give OpenAI whatever legitimate identity assurance it reasonably needs. I just don’t understand why a passport plus modern device-bound/passkey authentication still isn’t enough.

If anyone from OpenAI reads this: please consider allowing modern platform passkeys/device-bound credentials as an alternative to mandatory standalone FIDO2 keys for verified individual Daybreak users, or at least explain the threat model that makes the physical token materially safer in this situation.

And if I’m misunderstanding the current Daybreak enrollment process, I’d genuinely appreciate someone explaining what I’m missing.

2

I think you pinned it down: " why the trust threshold can’t recognize the combination" - it is that none of the surfaces are recognized combinations that can be transmitted. They are authentication methods to a third party, not to OpenAI.

You open a web browser. You go to the platform site’s playground and login. Usually right in with no login demand if you are cookied up with a session token. Perhaps normally with a challenge to check your email for a one-time use code or then with fallback to user/pass or even an email password reset. Then chat it up with an AI model in the site.

Where was strong authentication to anyone required and enforced as a setup?

Now: daybreak cyber models are behind that login, and nation-state adversaries will wage targeted campaigns against email accounts, web credentials, and the secured personal computer with remote access toolkits and 0-day exploits dropped in your email inbox…or admins that can simply cruise inboxes for fun.

Something you’ve got in hand, that authenticates to OpenAI, that OpenAI issued, satisfies to them the requirement “what you have” along with “what you (or anybody else) can know”. It is also where you are, can be separated from a high-visibility theft target laptop or phone you propose to use, and is not readily employed by an org full of users.

Thus, you using a Yubikey can be more justified a precaution than sending government ID scans off to unaccountable third parties performing “validation” that have never earned your trust.

The hardware’s expense should be disclosed first before jumping through those hoops, but it is about the same cost as one “find the exploit” call.

3

If only that was everything, they do not even specify beyond FIDO2, as far as I am aware, so people buy FIDO2 Capable Devices thinking it would work and multiple others and me end up having to contact support, because it in fact does not seem to work, maybe it only works with YubiKey who knows?

4

Yes, you need two authenticators: your phone is one or a tablet, and then this physical key. I’m only coming back here because I received another Trust Access blocker, and it’s simply a command looking to perform an audit on existing code; it’s not even a build…

5

It’s a bit silly that you need this key. Even banks got rid of physical tokens (formerly known as grasshoppers), and created a token system on their app. So there should be more than 2 solutions if they require 2 forms of verification: 1) a phone + 2) this physical key.