The NYDFS Cybersecurity Regulation sets strict security requirements for financial services, covering access control, data protection, and breach notification. If your applications use OpenID Connect (OIDC) for authentication, you need to prove every handshake meets those rules. This means enforcing strong encryption, keeping audit logs for all login events, and implementing continuous monitoring for signs of compromise.
OIDC builds on OAuth 2.0, adding an identity layer with standardized endpoints to retrieve user profile data. Under NYDFS guidelines, you must make sure the ID token and access token are encrypted in transit, validated against your identity provider's public keys, and stored only when necessary. Any mismatch in signature verification can be considered a control failure.
Token expiration is another compliance point. Short-lived tokens reduce exposure if a credential leaks. Your OIDC configuration should align with NYDFS’s requirement to minimize retained sensitive data. This includes setting strict refresh token policies and revoking sessions after inactivity.