[---

My Buildkite API Token leaked! What should I do?

What is a Buildkite API Token and how it is used?

A Buildkite API Token is a unique authentication key that allows access to the Buildkite API, which is used to automate and manage pipelines and workflows in the Buildkite platform.

When it comes to the Buildkite API Token, developers should be aware of the following main use cases:

Authentication: The Buildkite API Token is used for authenticating requests made to the Buildkite API. It serves as a way to verify the identity of the user or application accessing the API.
Authorization: The API Token is also used to grant specific permissions and access levels to certain resources within the Buildkite platform. Developers can control what actions can be performed using the token.
Integration: The Buildkite API Token is crucial for integrating Buildkite with other tools and services. By using the token, developers can automate processes, trigger builds, and retrieve information from Buildkite programmatically.

---]

[---

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

Using environment variables for storing sensitive information like API tokens in your code is a secure practice for the following reasons:

Separation of Concerns: Environment variables are stored outside of your codebase, reducing the risk of accidental exposure through version control or code sharing.
Access Control: Environment variables can be restricted to specific users or processes, limiting access to the sensitive information.
Easy Revocation: If an API token needs to be revoked or changed, it can be done at the environment variable level without modifying the code.
Scalability: Using environment variables allows for easy deployment and scaling of applications without compromising security.

How to secure your secrets using environment variables

---]

[---

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

Using AWS Secrets Manager to manage Buildkite 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 Buildkite API Token from AWS Secrets Manager.

---]

[---

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

Using HashiCorp Vault for managing Buildkite API Tokens is a great way to enhance security. Here are code snippets in five different programming languages for securely handling a Buildkite 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 Buildkite 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 Buildkite API Token hardcoding using CyberArk Conjur

Using CyberArk Conjur to manage Buildkite 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 Buildkite API Token from CyberArk Conjur.

---]

[---

How to generate a Buildkite API Token?

To generate a Buildkite API Token, follow these steps:

Log in to your Buildkite account.
Click on your profile icon in the top right corner and select "Account settings".
In the left sidebar, click on "API Access".
Click on the "Create API Access Token" button.
Give your token a name and select the scopes for the token (read-only, read-write, etc.).
Click on the "Create Token" button.

Your API Token will be generated and displayed on the screen. Make sure to copy and securely store this token as it will be needed to authenticate API requests to Buildkite.

---]

[---

My Buildkite API Token leaked, what are the possible reasons?

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

Improper storage: Storing the API token in plain text in a configuration file or code repository can lead to accidental exposure.
Weak access controls: Inadequate access controls on the repository or server where the token is stored can result in unauthorized access.
Sharing credentials: Sharing the API token with unauthorized individuals or including it in public code repositories can lead to leaks.
Logging sensitive information: Printing or logging the API token in logs or error messages can expose it to unauthorized parties.
Phishing attacks: Falling victim to phishing attacks that trick developers into revealing their API tokens can also result in leaks.

What are the risks of leaking a Buildkite API Token

When it comes to the Buildkite API Token, it is crucial for developers to understand the risks associated with leaking this sensitive information. Here are some key points to consider:

Buildkite API Token grants access to Buildkite's API, allowing for interaction with sensitive data and resources.
Leaking the API Token can lead to unauthorized access to your Buildkite account and potentially compromise the security of your builds and pipelines.
An attacker with access to your API Token can view, modify, or delete your pipelines, trigger builds, and access any other resources accessible through the API.
Exposing the API Token in code repositories, configuration files, or other public places can result in serious security breaches and data leaks.
Developers should follow best practices for secret management, such as storing API Tokens securely, using environment variables, and restricting access to sensitive information.

---]

[---

Buildkite API Token security best practices

Avoid embedding the secret directly in your code. Instead, use environment variables or secrets managers‍
Secure storage: store the Buildkite 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 Buildkite API Token usage and improve the overall security of your Buildkite API Token implementations.

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

---]

[---

Buildkite 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 Buildkite API Token was used by malicious actors

Review Access Logs: Check the access logs of your Buildkite 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 Buildkite API Token. This can give insights into any unauthorized use of your key.

---]

[---

Steps to revoke the Buildkite API Token

Generate a new Buildkite API Token:

Log into your Buildkite 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 Buildkite 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 Buildkite 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.

Hide

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