[---

My Linear Personal API key leaked! What should I do?

What is a Linear Personal API key and how it is used?

A Linear Personal API key is a unique alphanumeric code that grants access to a specific user's account and allows them to interact with Linear's API for personal use.

Linear Personal API key is used for the following main use cases:

Authentication: Developers use the API key to authenticate and access Linear's API endpoints securely.
Integration: The API key is used to integrate Linear's functionality into other applications or services.
Authorization: Developers can use the API key to authorize specific actions or permissions within Linear's platform.

---]

[---

1. Code snippets to prevent Linear Personal API key hardcoding using environment variables

Using environment variables for storing sensitive information like API keys is a secure practice because:

Environment variables are not hard-coded in the codebase, reducing the risk of exposure.
Environment variables are stored outside of the code repository, making it harder for attackers to access them.
Environment variables can be easily managed and rotated without changing the code.
Environment variables are specific to the environment in which the code is running, providing an additional layer of security.

How to secure your secrets using environment variables

---]

[---

2. Code snippet to prevent Linear Personal API key hardcoding using AWS Secrets Manager

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

---]

[---

3. Code snippet to prevent Linear Personal API key hardcoding using HashiCorp Vault

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

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

---]

[---

How to generate a Linear Personal API key?

To generate a Linear Personal API key, follow these steps:

Log in to your Linear account.
Click on your profile icon in the top right corner and select "Settings".
Under the "API keys" section, click on "Generate new key".
Give your API key a name and select the permissions you want to assign to it.
Click on "Generate key" to create your Linear Personal API key.

You can now use this API key to authenticate and access Linear's API endpoints for your personal account.

---]

[---

My Linear Personal API key leaked, what are the possible reasons?

There are several reasons why a Linear Personal API key might have been leaked:

Improper storage: If the API key was stored in a public repository or in a file that was accessible to unauthorized users, it could have been easily leaked.
Weak access controls: If the system or application that was using the API key did not have proper access controls in place, it may have been compromised by an attacker.
Phishing attacks: Developers may have unknowingly shared their API key in response to a phishing email or message, leading to its leakage.
Insufficient encryption: If the API key was transmitted over insecure channels or stored without encryption, it could have been intercepted by malicious actors.

What are the risks of leaking a Linear Personal API key

Developers need to understand the risks associated with leaking a Linear Personal API key. Here are some specific risks:

Unauthorized access to sensitive data: If a Linear Personal API key is leaked, attackers could potentially gain unauthorized access to sensitive information stored in the Linear account.
Abuse of API capabilities: Attackers could abuse the API capabilities associated with the key, potentially causing disruptions or unauthorized actions within the Linear platform.
Financial implications: Leaking a Linear Personal API key could lead to financial losses, especially if attackers use the key to perform costly actions or transactions.
Reputation damage: A security breach resulting from a leaked API key could damage the reputation of the developer or organization responsible for the key, leading to loss of trust from users and stakeholders.

---]

[---

Linear Personal API key security best practices

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

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

---]

[---

Linear Personal API key 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 Linear Personal API key was used by malicious actors

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

---]

[---

Steps to revoke the Linear Personal API key

Generate a new Linear Personal API key:

Log into your Linear Personal API key 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 Linear Personal API key:

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 Linear Personal API key.
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