[---

My LaunchDarkly Personal Token leaked! What should I do?

What is a LaunchDarkly Personal Token and how it is used?

A LaunchDarkly Personal Token is a unique authentication token that provides access to the LaunchDarkly platform for managing feature flags and controlling feature rollout.

LaunchDarkly Personal Token is used for the following main use cases:

Authentication: Developers use the Personal Token to authenticate themselves and access the LaunchDarkly platform securely.
API Access: The Personal Token is required to make authenticated API calls to interact with LaunchDarkly's features and data programmatically.
Secret Management: Developers can securely store and manage their Personal Token to ensure sensitive access credentials are protected and not exposed in code or configurations.

---]

[---

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

Using environment variables for storing sensitive information like LaunchDarkly Personal 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 outside of the code repository, making it less likely for the token to be leaked through version control.
Environment variables can be easily managed and rotated without changing the code, enhancing security maintenance.

How to secure your secrets using environment variables

---]

[---

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

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

---]

[---

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

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

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

---]

[---

How to generate a LaunchDarkly Personal Token?

To generate a LaunchDarkly Personal Token, follow these steps:

Log in to your LaunchDarkly account.
Click on your profile icon at the top right corner of the dashboard.
Select "Account settings" from the dropdown menu.
Go to the "Personal Access Tokens" section.
Click on the "Create Token" button.
Give your token a name and select the desired permissions for it.
Click on the "Create Token" button to generate the token.

Once the token is generated, make sure to copy and securely store it as it will not be displayed again for security reasons. You can use this token for authenticating API requests to LaunchDarkly services.

---]

[---

My LaunchDarkly Personal Token leaked, what are the possible reasons?

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

Improper storage: If the token was stored in a plaintext file or hardcoded in the code, it could have been easily accessed by unauthorized individuals.
Accidental exposure: Developers might have accidentally shared the token in public repositories, forums, or chat channels.
Phishing attacks: Hackers could have tricked developers into revealing their token through phishing emails or fake websites.
Insufficient access controls: If the token was shared with too many people or stored in a location with lax access controls, it could have been leaked.

What are the risks of leaking a LaunchDarkly Personal Token

When it comes to secret management, the security of your LaunchDarkly Personal Token is of utmost importance. Leaking this token can have severe consequences, as it grants access to your LaunchDarkly account and all the features and data within it. Developers must be aware of the risks associated with mishandling this token and take necessary precautions to prevent any leaks.

Unauthorized access to your LaunchDarkly account
Potential exposure of sensitive data and features
Risk of malicious activities being performed using your account
Compromise of your organization's security posture

It is essential for developers to understand the gravity of leaking a LaunchDarkly Personal Token and to implement best practices for secret management to mitigate these risks. Encourage them to follow secure coding practices, utilize secure storage mechanisms, and regularly audit and rotate their tokens to ensure the security of their accounts and data.

---]

[---

LaunchDarkly Personal Token security best practices

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

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

---]

[---

LaunchDarkly Personal 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 LaunchDarkly Personal Token was used by malicious actors

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

---]

[---

Steps to revoke the LaunchDarkly Personal Token

Generate a new LaunchDarkly Personal Token:

Log into your LaunchDarkly Personal 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 LaunchDarkly Personal 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 LaunchDarkly Personal 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