[---

My SonarQube Token leaked! What should I do?

What is a SonarQube Token and how it is used?

SonarQube Token is a unique authentication key generated by SonarQube for secure access to its APIs and services, used to authenticate and authorize requests made to the SonarQube server.

When using SonarQube, the Token is primarily used for:

Authentication: SonarQube Tokens are used to authenticate and authorize access to the SonarQube server, allowing developers to interact with the platform securely.
Integration: SonarQube Tokens are often used in continuous integration and deployment pipelines to automate code analysis and quality checks, ensuring that the code meets predefined standards before deployment.
API Access: Developers can use SonarQube Tokens to access the SonarQube API programmatically, allowing for custom integrations, reporting, and analysis of code quality metrics.

---]

[---

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

Using environment variables for storing sensitive information like SonarQube tokens in your code is a secure practice for the following reasons:

Environment variables are not hard-coded in the codebase, reducing the risk of accidental exposure.
Environment variables are stored outside of the code repository, making it harder for unauthorized users to access them.
Environment variables can be easily managed and rotated without the need to modify the code.
Environment variables are typically encrypted at rest by the operating system, adding an extra layer of security.

How to secure your secrets using environment variables

---]

[---

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

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

---]

[---

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

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

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

---]

[---

How to generate a SonarQube Token?

To generate a SonarQube token, follow these steps:

Login to your SonarQube account.
Click on your user icon in the top right corner and select "My Account" from the dropdown menu.
Go to the "Security" tab.
Click on the "Generate Tokens" button.
Provide a name for your token and click on "Generate" to create the token.

Make sure to copy and securely store the generated token as it will be needed for authentication when accessing SonarQube APIs or integrating with other tools.

---]

[---

My SonarQube Token leaked, what are the possible reasons?

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

Improper storage: If the token is stored in a plaintext file or hardcoded in the code, it can be easily accessed and leaked.
Accidental exposure: Developers may inadvertently include the token in their code when sharing code snippets or pushing code to a public repository.
Weak access controls: If the token is not properly protected with access controls, unauthorized users may gain access to it.
Compromised systems: If the system where the token is stored is compromised, attackers may be able to extract the token.

What are the risks of leaking a SonarQube Token

When it comes to SonarQube Tokens, it is crucial for developers to understand the risks associated with leaking these tokens. Here are some specific risks:

Unauthorized Access: If a SonarQube Token is leaked, unauthorized individuals may gain access to sensitive information and resources within SonarQube.
Data Breaches: Leaking a SonarQube Token can potentially lead to data breaches, compromising the security and integrity of the system.
Reputation Damage: A security incident resulting from a leaked SonarQube Token can tarnish the reputation of the developer and the organization they work for.
Financial Loss: In some cases, leaking a SonarQube Token can result in financial losses due to potential legal actions, fines, or loss of business.

---]

[---

SonarQube Token security best practices

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

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

---]

[---

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

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

---]

[---

Steps to revoke the SonarQube Token

Generate a new SonarQube Token:

Log into your SonarQube 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 SonarQube 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 SonarQube 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