Securing Non-Human Identities - Enhancing OAuth and Permissions

Cloudflare is enhancing security for non-human identities with scannable API tokens and improved OAuth visibility. These updates help prevent credential leakage and ensure least-privilege access. Developers can now manage permissions more effectively, reducing risks associated with unauthorized access.

Cloud SecurityMEDIUMUpdated: Published:
Featured image for Securing Non-Human Identities - Enhancing OAuth and Permissions

Original Reporting

CFCloudflare BlogΒ·Justin Hutchings

AI Summary

CyberPings AIΒ·Reviewed by Rohit Rana

🎯Basically, Cloudflare is making it safer for apps to use tokens without leaking sensitive information.

What Happened

Cloudflare has announced significant updates to enhance security for non-human identities, particularly focusing on automated revocation of API tokens, improved OAuth visibility, and resource-scoped permissions. These changes aim to help developers implement a least-privilege architecture and protect against credential leakage.

Understanding Identity: Principals, Credentials, and Policies

In modern development, identities are not just people; they include agents, scripts, and third-party tools. To secure these non-human identities, it is crucial to manage their lifecycle effectively. This involves:

  • The Principal: The identity itself, such as a developer or an automated agent.
  • The Credential: The proof of identity, like an API token.
  • The Policy: The rules governing what that identity can do.

When these elements are not managed together, security vulnerabilities can arise, leading to potential data loss or service disruptions.

Leaked Token Detection

One of the most common ways credentials are leaked is through public repositories. GitGuardian reported over 28 million secrets were exposed on GitHub last year, with AI accelerating the rate of these leaks. Cloudflare has partnered with GitHub to create a system that identifies leaked tokens and automatically revokes them, acting as a proactive measure against misuse.

How It Works

Cloudflare has developed a new token format that is easily scannable by credential scanning tools. When a token is detected in a public repository, GitHub verifies its authenticity and notifies Cloudflare to revoke it. This rapid response helps prevent unauthorized access before any damage can occur.

Cloudflare has also revamped the OAuth consent process. Users can now see which third-party applications are requesting access to their accounts, along with the specific permissions being requested. This transparency is vital for maintaining least-privilege access and ensuring users are aware of what data is being accessed.

Fine-Grained Resource-Level Permissioning

In addition to scannable tokens and improved OAuth, Cloudflare is introducing resource-scoped permissions. This allows organizations to limit access to specific resources, enhancing security by ensuring that even verified identities only access what they need.

Getting Started

Existing users are encouraged to roll their API tokens to the new scannable format. Cloudflare's improvements are designed to help developers and organizations protect their environments from credential leaks and unauthorized access effectively.

πŸ”’ Pro Insight

πŸ”’ Pro insight: These enhancements reflect a growing need for robust identity management in cloud environments, especially as automated agents proliferate.

CFCloudflare BlogΒ· Justin Hutchings
Read Original

Related Pings