CodeSecDays 2024 - Join GitGuardian for a full-day exploration of cutting-edge DevSecOps solutions!

Save my spot!

CodeSecDays 2024 - Join GitGuardian for a full-day exploration of cutting-edge DevSecOps solutions!

Save my spot!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
.

[---

My PlanetScale Token leaked! What should I do?

What is a PlanetScale Token and how it is used?

A PlanetScale Token is a unique identifier used to authenticate and authorize access to PlanetScale's database services securely.

Developers use the PlanetScale Token for the following main use cases:

  • Access Control: The PlanetScale Token is used to authenticate and authorize access to the PlanetScale database, ensuring that only authorized users can interact with the database.
  • Automated Deployment: Developers can use the PlanetScale Token to automate the deployment of database changes and updates, streamlining the development and deployment process.
  • Monitoring and Logging: The PlanetScale Token can be used to enable monitoring and logging features, allowing developers to track database performance, identify issues, and troubleshoot any potential problems.

---]

[---

1. Code snippets to prevent PlanetScale Token hardcoding using environment variables

Using environment variables for storing sensitive information like PlanetScale Token in your code is a secure practice because:

  • Environment variables are not hard-coded in the codebase, making it less likely for the sensitive information to be exposed accidentally.
  • Environment variables are stored outside the code repository, adding an extra layer of security as they are not accessible to unauthorized users who may have access to the codebase.
  • Environment variables can be managed and rotated easily without the need to modify the code, reducing the risk of exposing sensitive information during the development or deployment process.

How to secure your secrets using environment variables

--

---]

[---

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

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

--

---]

[---

3. Code snippet to prevent PlanetScale Token hardcoding using HashiCorp Vault

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

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

--

---]

[---

How to generate a PlanetScale Token?

To generate a PlanetScale Token, developers can follow these steps:

  1. Log in to the PlanetScale dashboard.
  2. Go to the "Settings" section.
  3. Click on "API Tokens" in the sidebar menu.
  4. Click on the "Generate Token" button.
  5. Give the token a name and set the desired permissions.
  6. Click on "Generate Token" to create the token.

For more information and detailed instructions, developers can refer to the PlanetScale documentation on API Tokens.

---]

[---

My PlanetScale Token leaked, what are the possible reasons?

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

  • Improper storage: If the token was stored in plain text in a code repository or configuration file that is accessible to unauthorized users, it could have been easily leaked.
  • Weak access controls: If the system or platform where the token was stored did not have proper access controls in place, it could have been accessed by unauthorized individuals.
  • Phishing attacks: If a developer fell victim to a phishing attack and unknowingly shared their credentials or token with an attacker, the token could have been leaked.
  • Insufficient monitoring: Without proper monitoring and logging mechanisms in place, it may be difficult to detect unauthorized access to sensitive tokens, leading to potential leaks.
  • Human error: In some cases, a developer may accidentally expose a token by including it in a public code snippet, sharing it in an insecure communication channel, or making a mistake during configuration.

What are the risks of leaking a PlanetScale Token

As a security trainer, it is important for developers to understand the risks associated with leaking a PlanetScale Token specific to this token. Below are some key points to consider:

  • Leaking a PlanetScale Token can expose sensitive data stored in the database to unauthorized parties.
  • Unauthorized access to the database can lead to data breaches, data manipulation, or data loss.
  • A leaked PlanetScale Token can be used by malicious actors to access and manipulate the database, potentially causing irreversible damage to the application and its users.
  • Exposure of the PlanetScale Token can also lead to reputational damage for the organization, loss of customer trust, and legal implications.

It is crucial for developers to follow best practices in secret management and detection to prevent the leakage of sensitive tokens like the PlanetScale Token. This includes securely storing tokens, restricting access to them, rotating them regularly, and monitoring for any unauthorized access or usage.

---]

[---

PlanetScale Token security best practices

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

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

---]

[---

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

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

---]

[---

Steps to revoke the PlanetScale Token

Generate a new PlanetScale Token:

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

---]

Environment Variables
Environment Variables
Environment Variables

charge

nullable string

For card errors, the ID of the failed charge.

payment_method_type

nullable string

If the error is specific to the type of payment method, the payment method type that had a problem. This field is only populated for invoice-related errors.

doc_url

nullable string

A URL to more information about the error code reported.

request_log_url

nullable string

A URL to the request log entry in your dashboard.

charge

nullable string

If the error is specific to the type of payment method, the payment method type that had a problem. This field is only populated for invoice-related errors.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

charge

nullable string

If the error is specific to the type of payment method, the payment method type that had a problem. This field is only populated for invoice-related errors.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

payment_intent

nullable object

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

setup_intent

nullable object

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

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

CLIENT LIBRARIES

$ gem install stripe
$ pip install stripe
$ composer require stripe/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"
$ npm install --save stripe
$ go get github.com/stripe/stripe-go/v76
$ nuget install Stripe.net
SHOW
{{this.title}}
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
{{clipboardIconText}}
This is placeholder code