Starting Soon! Want to secure workload access to LLMs like ChatGPT? Join Our Webinar | Today at 1 pm. PT

Aembit Earns Prestigious Runner-Up Spot at RSA Innovation Sandbox Contest! Watch the Announcement

RSAC™ Innovation Sandbox FINALIST 2024 banner
Aembit is an RSA Conference Innovation Sandbox finalist! Read the news

Dear API Vendors: Use Secure Authentication, Ditch API Keys

Open Letter to API Vendors

Dear API Vendors,

I am writing to you today to plead for digital security and integrity. In recent years, the proliferation of APIs has transformed how we interact with technology, enabling seamless integration and innovation across various platforms and services. While much progress has been made in user authentication over the years, service and API authentication has generally gotten little attention. As the demand for API access continues to grow, so does the urgency of adopting more secure authentication methods.

Specifically, I urge you to reconsider the widespread support for API keys and instead prioritize the adoption of more robust and secure authentication mechanisms, such as workload identity federation. While API keys have long been the de facto method for authenticating API requests, they inherently pose significant risks to the security of your systems and your customers’ data.

The Risks of Using and Leaking API Keys

Unauthorized and Overprivileged Access: API keys, often issued with broad permissions, can grant unauthorized users or systems unrestricted access to sensitive data and functionalities. In the event of a key compromise, attackers can exploit this access to infiltrate systems, compromise user accounts, and exfiltrate confidential information.

Credential Exposure: API keys are frequently transmitted in plaintext within HTTP headers or URLs, making them susceptible to interception by malicious actors. Moreover, developers may inadvertently expose API keys in publicly accessible code repositories or configuration files, increasing the risk of credential exposure.

Lack of Accountability: API keys lack the transparency necessary for effective access control and auditing. Without mechanisms to track and monitor API key usage, organizations struggle to maintain accountability and identify anomalous activities, leaving them vulnerable to insider threats and unauthorized access.

Operational Challenges of Managing API Keys

Key Generation and Distribution: Generating and distributing unique API keys to developers, applications, and third-party integrators is time-consuming and error-prone. 

Key Rotation and Expiry: Managing key rotation schedules and ensuring that all keys are updated on time is challenging, particularly in large-scale environments with numerous interconnected systems and services.

Access Control and Permissions: Maintaining granular access control and permissions for each API key requires careful management of access policies and configurations. Organizations must define and enforce access control policies to ensure that each key is assigned the appropriate level of access based on the user or workload’s role and responsibilities.

Auditing and Monitoring: Tracking and auditing key usage across multiple systems and services can be complex, particularly without centralized logging and monitoring solutions.

Revocation and Deletion: When employees leave the organization or applications are decommissioned, revoking and deleting any associated API keys is essential to prevent unauthorized access and data breaches. However, identifying and deactivating inactive or obsolete keys can be challenging, especially without comprehensive inventory management and tracking mechanisms.

Compliance and Regulatory Requirements: Organizations operating in regulated industries must adhere to strict compliance and regulatory requirements governing the management and protection of sensitive data, including API keys. Ensuring compliance with industry standards such as PCI DSS, HIPAA, and GDPR adds complexity to key management processes.

Scalability and Performance: As organizations scale their operations and infrastructure, managing many API keys becomes increasingly complex and resource-intensive. Key management systems must be designed to scale effectively and handle high volumes of key generation, distribution, rotation, and monitoring without impacting performance or reliability.

Embracing More Secure Authentication Methods

Given the structural security risks and operational challenges, I implore API vendors to transition away from API keys and adopt more secure and manageable authentication methods. Workload identity federation offers several advantages over traditional API keys, including:

Short-Lived Tokens: Workload identity federation generates short-lived authentication tokens with limited lifespans, reducing the risk of unauthorized access and credential exposure.

Dynamic Credential Generation: Unlike static API keys, workload identity federation dynamically generates credentials based on the requester’s identity and permissions, minimizing the risk of credential misuse and unauthorized access.

Automated Credential Rotation: Workload identity federation automates credential rotation, ensuring that tokens are regularly refreshed to maintain security and compliance.

By embracing more secure authentication methods like workload identity federation, API vendors can enhance the security posture of their platforms, protect user data from unauthorized access, and uphold the trust and confidence of their customers.

I urge API vendors to prioritize security and adopt modern authentication mechanisms that align with industry best practices. Let’s work together to create a safer and more secure digital ecosystem.


Kevin Sapp

Co-Founder and CTO, Aembit

You might also like

Aembit Workload IAM extends RBAC by grouping and isolating non-human resources and policies within an organization or tenant.
As organizations emphasize safeguarding non-human identities, you must balance immediate security measures with long-term oversight and compliance.
Sticky note security now plagues application and service connections, necessitating a shift to more mature workload access safeguards.