[---

My Jira API Token leaked! What should I do?

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

An API token in Jira is a unique and secure string of characters that allows a developer or application to authenticate and interact with Jira's REST API without using a password.

When it comes to Jira API Tokens, developers should understand the following main use cases:

Authentication: Jira API Tokens are used to authenticate and authorize API requests made to the Jira platform. They serve as a secure way to access Jira resources without exposing the user's password.
Integration: Developers use Jira API Tokens to integrate Jira with other tools and services, allowing for automated interactions and data exchange between systems.
Automation: Jira API Tokens enable developers to automate workflows and processes within Jira, such as creating issues, updating information, or generating reports programmatically.

---]

[---

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

Using environment variables for storing sensitive information like Jira API tokens is a secure practice for several reasons:

Environment variables are not hard-coded in the codebase, reducing the risk of accidental exposure or leakage.
Environment variables are stored outside of the code repository, providing an additional layer of protection against unauthorized access.
Environment variables can be easily managed and updated without the need to modify the code, making it simpler to rotate API tokens regularly for enhanced security.

How to secure your secrets using environment variables

---]

[---

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

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

---]

[---

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

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

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

---]

[---

How to generate a Jira API Token?

To generate a Jira API Token, follow these steps:

Log in to your Jira account.
Click on your profile icon and select "Account settings".
Under the "Security" section, click on "API token".
Click on "Create API token".
Enter a label for your token to easily identify it.
Click on "Create" and your API token will be generated.

Make sure to copy and securely store your API token as it will not be displayed again. You can use this token to authenticate your requests when using the Jira API.

---]

[---

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

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

Weak or compromised credentials: If the Jira API Token was created using weak or compromised credentials, it could have been easily guessed or stolen by malicious actors.
Improper storage: Storing the Jira API Token in an insecure location, such as in plain text in a configuration file or hardcoding it in the code, can lead to leaks if the file or code is accessed by unauthorized parties.
Accidental exposure: Developers may inadvertently expose the Jira API Token by including it in code snippets shared in public forums, repositories, or during code reviews.
Phishing attacks: Hackers may use phishing techniques to trick developers into revealing their Jira API Tokens, posing as legitimate entities requesting the information.
Insufficient access controls: Inadequate access controls on systems or repositories where the Jira API Token is stored can result in unauthorized access and potential leaks.

What are the risks of leaking a Jira API Token

When it comes to the risks of leaking a Jira API Token, developers must understand the following implications:

Unauthorized Access: If a Jira API Token is leaked, it can be used by malicious actors to gain unauthorized access to sensitive data and perform actions within the Jira platform.
Data Breach: Leaking a Jira API Token can lead to a data breach, compromising the confidentiality and integrity of the information stored in Jira.
Reputation Damage: A data breach resulting from a leaked API Token can damage the reputation of the organization, leading to loss of trust from customers and stakeholders.
Financial Loss: In addition to reputational damage, a data breach can also result in financial loss due to potential legal implications, fines, and costs associated with remediation.

It is crucial for developers to be vigilant and follow best practices for secret management to prevent the leakage of sensitive information like Jira API Tokens. Implementing secure coding practices, using encryption, and regularly auditing access controls are essential steps in safeguarding against such risks.

---]

[---

Jira API Token security best practices

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

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

---]

[---

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

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

---]

[---

Steps to revoke the Jira API Token

Generate a new Jira API Token:

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