The login request lands. A token is issued. Behind it sits a map of personal data—names, emails, phone numbers—flowing through your OpenID Connect (OIDC) implementation. Without a clear catalog of what Personally Identifiable Information (PII) you handle, you’re blind to where risk lives.
An OIDC PII catalog is an inventory: every PII attribute your identity provider and relying parties exchange, tied to the exact endpoints, claims, and scopes involved. Building this catalog means inspecting OIDC claims like email, profile, address, and linking them to your internal data model. It means tracking whether that data is stored, cached, or just passed downstream.
To construct an effective PII catalog in OIDC:
- Parse your authorization requests and inspect requested scopes.
- Map each OIDC claim to its PII classification level.
- Note storage location, retention period, and encryption status for each item.
- Record the flow of data between IdP, RP, and any API gateways.
- Update the catalog whenever scopes or claims change.
A complete OIDC PII catalog strengthens compliance with GDPR, CCPA, and internal governance. It also improves incident response—when a scope changes or a claim is exposed, you know exactly which data is at stake.
Integrating your PII catalog into CI/CD pipelines enables real-time detection of unauthorized claims and keeps your OIDC usage honest. Automating catalog updates ensures the inventory always matches reality.
If you run OIDC, your PII catalog is not optional. Without it, audit trails break and breaches become harder to contain.
See how this looks in practice. Build and view a live OIDC PII catalog in minutes with hoop.dev.