My CircleCI Personal API Token leaked! What should I do?

What is a CircleCI Personal API Token and how it is used?

A CircleCI Personal API Token is a unique identifier that allows access to the CircleCI API for a specific user, enabling them to automate workflows and interact with CircleCI resources securely.

Here are the main use cases for the CircleCI Personal API Token:

Authenticate and access the CircleCI API: Developers use the Personal API Token to authenticate their requests to the CircleCI API, allowing them to interact with their CI/CD pipelines programmatically.
Automate CI/CD workflows: The API token is commonly used to automate various CI/CD workflows, such as triggering builds, retrieving build information, and managing project settings.
Integrate with third-party tools: Developers can use the Personal API Token to integrate CircleCI with other tools and services, enabling seamless automation and collaboration within their development environment.

1. Code snippets to prevent CircleCI Personal API Token hardcoding using environment variables

Using environment variables for storing sensitive information like a CircleCI Personal API Token is a secure practice because:

Environment variables are not hard-coded in the codebase, reducing the risk of accidental exposure.
Environment variables are stored separately from the code and are not included in version control systems, adding an extra layer of security.
Environment variables can be managed and rotated easily without changing the code, enhancing security maintenance.
Access to environment variables can be restricted based on user roles and permissions, limiting exposure to unauthorized users.

How to secure your secrets using environment variables

2. Code snippet to prevent CircleCI Personal API Token hardcoding using AWS Secrets Manager

Using AWS Secrets Manager to manage CircleCI Personal API Tokens is a secure way to handle sensitive data. Here are code snippets in five different programming languages that demonstrate how to retrieve the CircleCI Personal API Token from AWS Secrets Manager.

3. Code snippet to prevent CircleCI Personal API Token hardcoding using HashiCorp Vault

Using HashiCorp Vault for managing CircleCI Personal API Tokens is a great way to enhance security. Here are code snippets in five different programming languages for securely handling a CircleCI Personal API Token using HashiCorp Vault.

Remember to replace the VAULT_ADDR and VAULT_TOKEN with your Vault server address and authentication token. The snippets assume that the CircleCI Personal API Token is stored under the api_key field within Vault. The specifics of the Vault path and field names should be adjusted to match your Vault setup.

4. Code snippet to prevent CircleCI Personal API Token hardcoding using CyberArk Conjur

Using CyberArk Conjur to manage CircleCI Personal API Token is a secure way to handle sensitive data. Here are code snippets in five different programming languages that demonstrate how to retrieve the CircleCI Personal API Token from CyberArk Conjur.

How to generate a CircleCI Personal API Token?

To generate a CircleCI Personal API Token, follow these steps:

Log in to your CircleCI account.
Go to your account settings.
Click on "Personal API Tokens" in the sidebar menu.
Click on the "Create New Token" button.
Give your token a name and set the scope of the token.
Click on the "Create Token" button.
Your new API token will be generated. Make sure to copy and securely store it as it will not be displayed again.

My CircleCI Personal API Token leaked, what are the possible reasons?

There are several reasons why a CircleCI Personal API Token might have been leaked:

Improper storage: If the token is stored in a publicly accessible repository or in a file that is not properly secured, it can be easily accessed by unauthorized users.
Accidental exposure: Developers may inadvertently include the token in code snippets, configuration files, or logs that are shared publicly, leading to its exposure.
Phishing attacks: Hackers may use social engineering techniques to trick developers into revealing their API tokens through fake emails or websites.
Insufficient access controls: If the token is shared with team members who do not have a legitimate need for it, there is a higher risk of it being leaked.

What are the risks of leaking a CircleCI Personal API Token

Leaking a CircleCI Personal API Token can pose significant risks to the security of your project and organization. It is crucial for developers to understand the potential consequences of such a breach:

Unauthorized Access: An attacker could use the leaked API token to gain unauthorized access to your CircleCI account, potentially compromising sensitive information and resources.
Data Breach: If the API token is exposed, it could lead to a data breach, exposing confidential data, such as code repositories, build configurations, and deployment pipelines.
Financial Loss: An attacker with access to your CircleCI account could incur significant costs by running malicious or resource-intensive builds, leading to financial losses for your organization.
Reputation Damage: A security incident resulting from a leaked API token can tarnish the reputation of your organization, leading to loss of trust from customers, partners, and stakeholders.

CircleCI Personal API Token security best practices

Avoid embedding the secret directly in your code. Instead, use environment variables or secrets managers‍
Secure storage: store the CircleCI Personal API Token in a secure location, such as a password manager or a secrets management service.
Regular rotation: periodically rotate the API key to minimize the risk of long-term exposure.
Restrict permissions: apply the principle of least privilege by only granting the key the minimum necessary permissions.
Monitor usage: regularly check the usage logs for any unusual activity or unauthorized access attempts.
Implement access controls: limit the number of users who have access to the secret and enforce strong authentication measures.
Use a secrets manager: utilize secret management tools like CyberArk or AWS Secrets Manager for enhanced security.

By adhering to the best practices, you can significantly reduce the risk associated with CircleCI Personal API Token usage and improve the overall security of your CircleCI Personal API Token implementations.

Exposing secrets on GitHub: What to do after leaking Credential and API keys

CircleCI Personal API Token leak remediation: what to do

What to do if you expose a secret: How to stay calm and respond to an incident [cheat sheet included]

How to check if CircleCI Personal API Token was used by malicious actors

Review Access Logs: Check the access logs of your CircleCI Personal API Token account for any unauthorized access or unusual activity. Pay particular attention to access from unfamiliar IP addresses (if you haven’t set up a specific allow list) or at odd hours.
Monitor Usage Patterns: Look for anomalies in the usage patterns, such as unexpected spikes in data access or transfer.
Check Active Connections and Operations: Review the list of active connections and recent operations on your database. Unusual or unauthorized operations might indicate malicious use.
Audit API Usage: If possible, audit the usage of your API key through any logging or monitoring services you have integrated with CircleCI Personal API Token. This can give insights into any unauthorized use of your key.

Steps to revoke the CircleCI Personal API Token

Generate a new CircleCI Personal API Token:

Log into your CircleCI Personal API Token account.
Navigate to the API section and generate a new API key.

Update Services with the new key:

Replace the compromised key with the new key in all your services that use this API key.
Ensure all your applications and services are updated with the new key before deactivating the old one.

Deactivate the old CircleCI Personal API Token:

Once the new key is in place and everything is functioning correctly, deactivate the old API key.
This can typically be done from the same section where you generated the new key.

Monitor after key rotation:

After deactivating the old key, monitor your systems closely to ensure that all services are running smoothly and that there are no unauthorized access attempts.

How to understand which services will stop working

Inventory of services: keep an inventory of all services and applications that utilize your CircleCI Personal API Token.
Communication and documentation: Ensure that your team is aware of which services are dependent on the key. Maintain documentation for quick reference.
Testing: before deactivating the old key, test your services with the new key in a staging environment. This helps in identifying any services that might face issues post rotation.
Fallback strategies: Have a fallback or emergency plan in case a critical service fails after the key rotation. This might include temporary measures or quick rollback procedures.

In summary, the remediation process involves identifying potential misuse, carefully rotating the key, and ensuring minimal disruption to services. Being proactive and having a well-documented process can greatly reduce the risks associated with a compromised API key.

What about other secrets?

GitGuardian helps developers keep 350+ types of secrets out of source code. GitGuardian’s automated secrets detection and remediation solution secure every step of the development lifecycle, from code to cloud:

On developer workstations with git hooks (pre-commit and pre-push);
On code sharing platforms like GitHub, GitLab, and Bitbucket;
In CI environments (Circle CI, Travis CI, Jenkins CI, GitHub Actions, and many more);
In Docker images.

payment_intent

nullable object

The PaymentIntent object for errors returned on a request involving a PaymentIntent.

Show

child attributes

CLIENT LIBRARIES

$ gem install stripe

STRIPE-RUBY

$ pip install stripe

STRIPE-PYTHON

$ composer require stripe/stripe-php

STRIPE-PHP

MAVEN
<dependency>
  <groupId>com.stripe</groupId>
  <artifactId>stripe-java</artifactId>
  <version>24.16.0</version>
</dependency>

GRADLE
compile "com.stripe:stripe-java:24.16.0"

STRIPE-NODE

$ npm install --save stripe

STRIPE-NODE

$ go get github.com/stripe/stripe-go/v76

STRIPE-NODE

$ nuget install Stripe.net

STRIPE-NODE

SHOW

This is placeholder code

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents

Table of Contents