[---

My LaunchDarkly SDK Key leaked! What should I do?

What is a LaunchDarkly SDK Key and how it is used?

The LaunchDarkly SDK Key is a unique identifier used by developers to authenticate their application with the LaunchDarkly feature management platform, allowing them to control feature flags and other configuration settings.

Here are the main use cases for the LaunchDarkly SDK Key:

Access Control: The SDK Key is used to authenticate the application with LaunchDarkly's feature management platform, allowing the application to retrieve feature flags and configurations.
Feature Flag Evaluation: The SDK Key is essential for the application to evaluate feature flags and determine which features should be enabled or disabled based on user targeting rules and conditions.
Data Collection: The SDK Key is used to collect data on feature flag evaluations, allowing developers to analyze and optimize feature flag usage for better performance and user experience.

---]

[---

1. Code snippets to prevent LaunchDarkly SDK Key hardcoding using environment variables

Using environment variables for storing sensitive information like LaunchDarkly SDK Key is a secure practice because:

Environment variables are stored separately from your codebase, reducing the risk of accidental exposure through version control or sharing of code.
Environment variables are not visible in the code itself, making it harder for attackers to access the sensitive information.
Environment variables can be easily managed and updated without the need to modify the code, improving the overall security posture of the application.

How to secure your secrets using environment variables

---]

[---

2. Code snippet to prevent LaunchDarkly SDK Key hardcoding using AWS Secrets Manager

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

---]

[---

3. Code snippet to prevent LaunchDarkly SDK Key hardcoding using HashiCorp Vault

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

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

---]

[---

How to generate a LaunchDarkly SDK Key?

To generate a LaunchDarkly SDK Key, follow these steps:

Log in to your LaunchDarkly account.
Click on the "Account settings" tab in the top right corner.
Under the "Projects" section, select the project for which you want to generate the SDK Key.
Click on the "SDK Keys" tab on the left-hand side menu.
Click on the "Generate SDK Key" button.
Give your SDK Key a name and description for easy identification.
Click on the "Generate key" button to create the SDK Key.

Once you have generated the SDK Key, you can use it in your application to connect to LaunchDarkly and access feature flags and other feature management capabilities.

---]

[---

My LaunchDarkly SDK Key leaked, what are the possible reasons?

There are several reasons why a LaunchDarkly SDK Key might have been leaked:

Improper handling of sensitive information: Developers may accidentally expose the SDK Key by hardcoding it in their code or including it in publicly accessible configuration files.
Weak access controls: Inadequate access controls on repositories or servers where the SDK Key is stored can lead to unauthorized access and potential leakage.
Insufficient security measures: Lack of encryption or other security measures to protect the SDK Key can make it vulnerable to theft or interception.
Human error: Mistakes such as sharing the SDK Key in public forums, emails, or chat messages can also result in its unintended disclosure.

What are the risks of leaking a LaunchDarkly SDK Key

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

Unauthorized Access: If the LaunchDarkly SDK Key is leaked, it can be used by unauthorized individuals to gain access to your LaunchDarkly account and potentially compromise your application.
Data Breach: Leaking the SDK Key can lead to a data breach, where sensitive user data or other confidential information stored in your application could be exposed.
Financial Loss: A security breach resulting from a leaked SDK Key can have financial implications, such as loss of revenue, legal fees, and damage to your organization's reputation.
Reputation Damage: The trust and reputation of your organization can be severely impacted if a security incident occurs due to a leaked SDK Key, leading to loss of customers and business opportunities.

It is essential for developers to implement robust security measures to protect sensitive information like the LaunchDarkly SDK Key, including proper secret management practices and regular security audits to detect any vulnerabilities before they can be exploited.

---]

[---

LaunchDarkly SDK Key security best practices

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

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

---]

[---

LaunchDarkly SDK Key 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 SDK Key was used by malicious actors

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

---]

[---

Steps to revoke the LaunchDarkly SDK Key

Generate a new LaunchDarkly SDK Key:

Log into your LaunchDarkly SDK Key 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 SDK Key:

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 SDK Key.
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