[---

My Mapbox Token API leaked! What should I do?

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

The Mapbox Token API is a service that allows developers to securely manage and authenticate access to Mapbox services by providing unique access tokens.

Here are three main use cases for the Mapbox Token API:

Securing Access to Mapbox Services: Developers can use the Mapbox Token API to generate and manage access tokens that are required to authenticate and authorize access to Mapbox services, such as maps, geocoding, and routing functionalities.
Preventing Unauthorized Access: By using the Mapbox Token API, developers can ensure that only authorized users and applications are able to access Mapbox services, thereby preventing unauthorized access and protecting sensitive data.
Monitoring and Auditing Access: The Mapbox Token API allows developers to monitor and audit access to Mapbox services by tracking the usage of access tokens. This helps in identifying any suspicious activity and ensuring compliance with security policies.

---]

[---

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

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

Environment variables are not hard-coded in the codebase, reducing the risk of exposure in case of a code leak or breach.
They are stored outside of the code repository, making it harder for unauthorized users to access the sensitive information.
Environment variables can be easily managed and updated without altering the code, providing flexibility and security in case the token needs to be changed.

How to secure your secrets using environment variables

---]

[---

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

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

---]

[---

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

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

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

---]

[---

How to generate a Mapbox Token API?

To generate a Mapbox Token API, follow these steps:

Sign in to your Mapbox account or create a new account if you don't have one.
Once logged in, navigate to the account settings.
Click on the "Access tokens" tab.
Click on the "Create a token" button.
Give your token a name and set the appropriate permissions for the token.
Click on the "Create token" button.

Your Mapbox Token API will be generated and displayed on the screen. Make sure to keep this token secure and do not share it publicly.

---]

[---

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

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

Improper storage: If the token was stored in a publicly accessible location such as a GitHub repository or a shared drive, it could have been easily accessed by unauthorized parties.
Hardcoded in source code: If the token was hardcoded directly into the source code of an application, it could have been exposed during code reviews or through decompilation of the application.
Accidental exposure: Developers may have inadvertently included the token in error messages, logs, or other output that was accessible to external users.
Insufficient access controls: If the token was shared with individuals who did not have a legitimate need to access it, there is a higher risk of it being leaked.
Phishing attacks: Hackers may have used social engineering techniques to trick developers into revealing the token through phishing emails or other means.

What are the risks of leaking a Mapbox Token API

Developers must understand the risks associated with leaking a Mapbox Token API, as it can have serious consequences. Here are some key points to consider:

Unauthorized Access: If a Mapbox Token API is leaked, unauthorized individuals or systems could potentially gain access to sensitive location data and other information stored on the Mapbox platform.
Financial Loss: Leaking a Mapbox Token API could result in financial loss, as attackers could use the token to incur charges on the account associated with the API.
Reputation Damage: A data breach resulting from a leaked Mapbox Token API could damage the reputation of the developer or organization responsible for the security lapse.
Legal Consequences: Depending on the nature of the data exposed through the leaked API, there could be legal repercussions, such as violations of data protection regulations.
Service Disruption: If unauthorized parties gain access to a Mapbox Token API, they could potentially disrupt the services relying on the API, causing downtime and inconvenience for users.

---]

[---

Mapbox Token API security best practices

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

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

---]

[---

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

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

---]

[---

Steps to revoke the Mapbox Token API

Generate a new Mapbox Token API:

Log into your Mapbox Token API 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 Mapbox Token API:

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 Mapbox Token API.
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