Security compliance question for Auth0

Hi auth0 gurus -

My company is using auth0 as part of our cloud environment, which a couple of our security sensitive end-customers are using. One of our customer’s security team has asked us a specific question about auth0 and I’m hoping someone from this community can help me answer it:

Here is their question:

”Can you have someone from auth0 confirm that it is just an OIDC/OAuth2 endpoint, and that it doesn’t accept/store arbitrary POSTs of data to it? To us it looks like it’s an OIDC/OAuth2 responder only, but we’re concerned that there could be other APIs under other paths that might result in data being stored on auth0 servers.”

Their goal is to confirm there’s no mechanism through which their proprietary data could possibly be written to / stored by Auth0 in any way. Can someone confirm this ?

Thanks for the help!!! :slight_smile:

Joe

Hi @joe.pringle

Welcome to the Auth0 Community!

You are asking whether Auth0 can formally confirm that its endpoints are OIDC/OAuth 2.0 protocol endpoints only, and that no path accepts or stores arbitrary data written by a customer or an end user.

[Summary]

Auth0’s core authentication endpoints process identity data only, but Auth0 does provide documented Management API and metadata features that let tenant administrators and applications write data, so a formal written statement from Auth0 is needed to cover the full “no write path” claim.

[Root Cause]

The primary customer-facing endpoints, /authorize, /token, /userinfo, and /v2/logout, implement OpenID Connect, OAuth 2.0, and SAML protocols. These endpoints process identity attributes (such as email address, name, and identity provider connection), JWTs and opaque refresh tokens, and hashed credentials. They are not designed to accept arbitrary application data. Other Auth0 APIs, however, are authenticated and documented, and they can write data in specific ways.

[Solution]

:globe_with_meridians: 1. Protocol Endpoints (Transient Transactional Data)

The endpoints that end-users directly interact with—such as /authorize, /oauth/token, /userinfo, and /v2/logout—act as a transactional runtime engine. They do not serve as a general-purpose database for proprietary application data.

The data processed in these paths is strictly limited to:

  • Identity attributes: Basic user profile data (e.g., email address, name, sub identifier, and the connection provider) required to validate identity.

  • Token material: Issuing short-lived JSON Web Tokens (JWTs) and managing opaque, securely hashed refresh tokens.

  • Credentials: User passwords, which are strictly hashed utilizing bcrypt/Argon2 and salted before storage, or WebAuthn/FIDO2 public key credentials for passkeys.


:gear: 2. The Management API Surface (Persistent Configuration Data)

It is crucial to note that Auth0’s Management API (/api/v2/) contains numerous endpoints that persistently write and store data on behalf of your tenant. These endpoints are designed for Machine-to-Machine (M2M) and administrative operations and manage:

  • User Accounts: Persistent user profile records.

  • Branding & Templates: Storing custom HTML page templates, email provider settings, and localization assets.

  • Extensions & Custom Logic: Storing Rules, Custom Database Scripts, Hooks, and Auth0 Actions code.

  • Audit Logs: Storing real-time tenant log history (e.g., successful logins, blocked attempts, and configuration changes).

Metadata Storage Recommendations

While Auth0 offers custom metadata storage within user profiles via app_metadata (which cannot be edited by the end-user) and user_metadata (user-editable), we strongly recommend against storing any proprietary, highly sensitive, or regulated customer data (such as financial records, PHI, or PII beyond basic identity) in these fields.


:locked: 3. Compliance and Security Trust Center

For formal compliance evaluations and security audits (such as SOC 2 Type II, ISO 27001, or PCI-DSS Attestation of Compliance), we recommend utilizing Auth0’s dedicated trust and security channels:


:open_book: Additional Reference Materials

I hope this clarifies the taxonomy of Auth0’s endpoints and provides your security team with the exact resources they need. Please let us know if we can assist you with any further security reviews!

Have a great one,
Gerald

Thanks so much Gerald - really appreciate the response. Is there a way to prevent the use of the user_metadata field or otherwise make it so it isn’t editable by end-users?

Hi @joe.pringle

Happy I was able to provide some useful information!

Both the user_metadata and app_metadata fields are meant to be used as means to add information about the user, which can be done either by the application, an Admin, an Action Flow etc. These will not contain additional information about the users unless explicitly added. It is not possible to make the user_metadata field non editable by users, but if such a field is required, the app_metadata fulfils this need.

In addition, within the Auth0 dashboard under User Management → Users → click on any user and navigate to the Raw JSON tab, you will find user information such as their last login, authentications, creation date etc. These are only visible to tenant Admins or tenant members with a set of accesses that allows them to view this information, more details regarding tenant level roles can be found here: Dashboard Access by Role

Hope this helped!
Gerald