Enforce standard authentication for external data source connections. Use when integrating, configuring, or reviewing connections from AI systems to external databases, APIs, or data services.
How this skill is triggered — by the user, by Claude, or both
Slash command
/prodsec-skills-ge-core:authenticationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
External data sources MUST require that the principal (user or service) connecting to them is identified and authenticated. The authentication MUST use standard protocols.
External data sources MUST require that the principal (user or service) connecting to them is identified and authenticated. The authentication MUST use standard protocols.
| Protocol | Use Case |
|---|---|
| OAuth 2.1 / OIDC | Web APIs, REST services, cloud data sources |
| SPIFFE/SPIRE + mTLS | Service-to-service connections within infrastructure |
| SAML | Federated enterprise data sources |
| Kerberos | On-premise databases and services (Active Directory environments) |
| Client certificates (mTLS) | Machine-to-machine data source access |
api_keys/avoid-api-keys)npx claudepluginhub redhatproductsecurity/prodsec-skills --plugin prodsec-skills-ge-coreEnforces authorization checks for external data source access in AI systems, covering read/write/delete permissions and least privilege principles.
Maps client type, trust level, and token lifetime to the correct API credential scheme. Use when designing or auditing API authentication.
Provides auth patterns for API keys, OAuth, and token management. Use when implementing or reviewing service authentication and credential handling.