[---

My CARTO API Access Token leaked! What should I do?

What is a CARTO API Access Token and how it is used?

An API Access Token for CARTO is a unique string of characters that acts as a credential to authenticate and authorize access to CARTO's API services.

Here are the main use cases for CARTO API Access Token:

Authentication: The Access Token is used to authenticate and authorize requests made to the CARTO API. It serves as a proof of identity for the user or application accessing the API.
Authorization: The Access Token determines the level of access and permissions granted to the user or application. It controls which resources and actions can be accessed within the CARTO platform.
Secure Communication: The Access Token ensures secure communication between the user or application and the CARTO API. It helps protect sensitive data and prevent unauthorized access to resources.

---]

[---

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

Using environment variables for storing sensitive information like API access tokens is a good security practice because:

Environment variables are not stored in your codebase or version control system, reducing the risk of exposure.
Access to environment variables can be restricted to authorized users, limiting the potential for unauthorized access.
If a breach occurs, changing the environment variable is easier and faster than updating code and redeploying.
Environment variables are typically encrypted and not easily accessible to unauthorized users.

How to secure your secrets using environment variables

---]

[---

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

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

---]

[---

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

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

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

---]

[---

How to generate a CARTO API Access Token?

To generate a CARTO API Access Token, developers can follow these steps:

Log in to your CARTO account
Go to your account settings
Click on the "Your API Keys" section
Generate a new API key by clicking on the "New API Key" button
Provide a name for the API key and select the appropriate permissions
Click on the "Create API Key" button

Once the API key is generated, developers can use it to authenticate their requests to the CARTO API by including it in the Authorization header of their HTTP requests.

---]

[---

My CARTO API Access Token leaked, what are the possible reasons?

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

Improper storage: If the access token is stored in a publicly accessible location or in a code repository, it can be easily leaked.
Accidental exposure: Developers may inadvertently include the access token in code snippets or logs that are shared publicly.
Weak authentication: If the access token is not securely generated or managed, it can be easily guessed or brute-forced by attackers.
Third-party breaches: If a third-party service or tool that has access to the access token is compromised, the token can be leaked.

What are the risks of leaking a CARTO API Access Token

Developers need to understand the risks associated with leaking a CARTO API Access Token. Here are some specific risks:

Unauthorized access to sensitive data: A leaked API Access Token can be used by malicious actors to gain unauthorized access to sensitive data stored on CARTO's servers.
Abuse of services: Attackers can use the leaked token to abuse CARTO's services, leading to increased costs for the organization and potential service disruptions for legitimate users.
Reputation damage: If a data breach occurs due to a leaked API Access Token, it can damage the organization's reputation and erode customer trust.
Legal implications: Depending on the nature of the data accessed using the leaked token, the organization may face legal consequences such as fines or lawsuits.

---]

[---

CARTO API Access Token security best practices

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

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

---]

[---

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

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

---]

[---

Steps to revoke the CARTO API Access Token

Generate a new CARTO API Access Token:

Log into your CARTO API Access 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 CARTO API Access 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 CARTO API Access 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