[---

My Tableau Personal Access Token leaked! What should I do?

What is a Tableau Personal Access Token and how it is used?

A Tableau Personal Access Token is a secure authentication method that allows users to access Tableau Server resources without entering their password. It provides a more secure way of accessing Tableau data and resources.

Tableau Personal Access Token is used for:

Authenticating and accessing Tableau Server or Tableau Online APIs
Automating tasks and workflows by integrating Tableau with other applications
Securing access to Tableau resources without exposing sensitive login credentials

---]

[---

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

Using environment variables for storing Tableau Personal Access Tokens in code is a secure practice because:

Environment variables are not hard-coded in the codebase, reducing the risk of accidental exposure in version control systems.
Environment variables are stored outside of the codebase, making it harder for attackers to access sensitive information.
Environment variables can be easily managed and rotated without the need to modify the code, enhancing security and reducing the risk of unauthorized access.

How to secure your secrets using environment variables

---]

[---

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

Using AWS Secrets Manager to manage Tableau Personal 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 Tableau Personal Access Token from AWS Secrets Manager.

---]

[---

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

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

Using CyberArk Conjur to manage Tableau Personal 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 Tableau Personal Access Token from CyberArk Conjur.

---]

[---

How to generate a Tableau Personal Access Token?

To generate a Tableau Personal Access Token, follow these steps:

Log in to your Tableau Online or Tableau Server account.
Click on your profile icon in the top right corner and select "My Account".
In the left-hand menu, click on "Settings".
Under the "Personal Access Tokens" section, click on "Create New Personal Access Token".
Enter a name for your token and set the token expiration date.
Click on "Create" to generate your Personal Access Token.
Copy the token and securely store it as it will not be visible again.

---]

[---

My Tableau Personal Access Token leaked, what are the possible reasons?

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

Weak or easily guessable token: If the token was not strong enough or followed a predictable pattern, it could have been easily guessed or brute-forced by attackers.
Improper storage: Storing the token in plain text files, code repositories, or insecure databases can lead to unauthorized access if these resources are compromised.
Sharing or exposing the token: Sharing the token in public forums, code snippets, or inadvertently exposing it in logs or error messages can lead to its leakage.
Phishing attacks: Developers falling victim to phishing attacks or social engineering tactics could inadvertently disclose their Tableau Personal Access Token to malicious actors.
Unintentional exposure: Misconfigurations, insecure integrations, or vulnerabilities in the application or infrastructure could inadvertently expose the token to unauthorized parties.

What are the risks of leaking a Tableau Personal Access Token

When it comes to Tableau Personal Access Tokens, it is crucial for developers to understand the risks associated with leaking this sensitive information. Here are some specific risks to consider:

Unauthorized Access: If a Tableau Personal Access Token is leaked, it can be used by unauthorized individuals to access sensitive data and dashboards within Tableau.
Data Breaches: Leaking a Tableau Personal Access Token can lead to data breaches, where confidential information stored in Tableau may be exposed to malicious actors.
Impact on Business Operations: A security breach resulting from a leaked Tableau Personal Access Token can have severe consequences on business operations, reputation, and financial stability.
Legal and Compliance Issues: Failure to protect Tableau Personal Access Tokens can result in legal and compliance issues, especially if the leaked information includes sensitive customer data.

It is important for developers to prioritize the security of Tableau Personal Access Tokens and implement best practices for secret management and detection to prevent any potential leaks and mitigate the risks outlined above.

---]

[---

Tableau Personal Access Token security best practices

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

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

---]

[---

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

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

---]

[---

Steps to revoke the Tableau Personal Access Token

Generate a new Tableau Personal Access Token:

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