Hi, I can confirm this as well. We use a custom CTK-plugin (CryptoTokenKit), which works in Monterey, but not in Ventura. The issue seems be related to that the plugin doesn't show up as a smartcard reader, why that doesn't happen I can not answer. I can just point to the differences, works in Monterey but not in Ventura. This is how one can confirm, Monterey, $ > security list-smartcard com.xxx.xxx.ctk.sctoken:xxx <-- CTK-Plugin, shows up when smartcard is inserted. $ > system_profiler SPSmartCardsDataType xx Avalable SmarCards (keychain): com.apple.setoken: com.apple.setoken:aks: com.xxx.xxx.ctk.sctoken:xxx: < --- My certificate ---> Avalable SmarCards (token): com.apple.setoken: com.apple.setoken:aks: < --- My certificate ---> Now, same in Ventura, $ > security list-smartcard No smart card found. <-- CTK-Plugin, doesn't show up as smart card. Even though the smart card is inserted. $ > system_profiler SPSmartCardsDataType xx Avalable SmarCards (keychain): com.apple.setoken: com.apple.setoken:aks: com.xxx.xxx.ctk.sctoken:xxx: < --- NO certificate ---> Avalable SmarCards (token): com.apple.setoken: com.apple.setoken:aks: < --- My certificate Note how the smartcard is found, and the certificate is in the keychain when running Monterey, but not when running Ventura. This will effect anyone trying to use smartcard with a custom CTK-Plugin. Clearly something has changed, either you need to fix it, or you have to tell the developers how to fix it on their side. Please escalate this matter.