[---

My PGP Private Key leaked! What should I do?

What is a PGP Private Key and how it is used?

A PGP Private Key is a secret cryptographic key used in Pretty Good Privacy (PGP) encryption to decrypt messages that have been encrypted with the corresponding public key.

When it comes to PGP Private Keys, developers should understand the following main use cases:

Encryption: PGP Private Keys are used to encrypt sensitive data, ensuring that only the intended recipient with the corresponding Public Key can decrypt and access the information.
Signing: PGP Private Keys are also used for digitally signing messages or files. This allows the recipient to verify the authenticity and integrity of the sender, ensuring that the content has not been tampered with during transit.
Authentication: PGP Private Keys can be used for authentication purposes, allowing users to prove their identity in secure communications or transactions. By signing messages with their Private Key, users can demonstrate that they are the legitimate sender.

---]

[---

1. Code snippets to prevent PGP Private Key hardcoding using environment variables

Using environment variables for storing sensitive information like PGP Private Keys in code is considered a secure practice for the following reasons:

Environment variables are not hardcoded in the codebase, reducing the risk of accidental exposure through version control systems or code reviews.
Environment variables are typically stored outside of the codebase and are not accessible to unauthorized users who may have access to the code repository.
Environment variables can be easily managed and rotated without the need to modify the code, providing a flexible and secure way to update sensitive information.
Environment variables are commonly used in production environments and are supported by most deployment platforms, making it a convenient and widely accepted method for storing sensitive information.

How to secure your secrets using environment variables

---]

[---

2. Code snippet to prevent PGP Private Key hardcoding using AWS Secrets Manager

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

---]

[---

3. Code snippet to prevent PGP Private Key hardcoding using HashiCorp Vault

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

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

---]

[---

How to generate a PGP Private Key?

To generate a PGP Private Key, developers can follow these steps:

Install a PGP software such as GnuPG or OpenPGP on your computer.
Open the PGP software and navigate to the key generation option.
Choose the type of key you want to generate (RSA or DSA).
Enter your name and email address as the key identity.
Set a secure passphrase to protect your private key.
Generate the key pair (public and private keys).

---]

[---

My PGP Private Key leaked, what are the possible reasons?

There are several reasons why a PGP Private Key might have been leaked:

Accidental exposure: Developers may accidentally share their private key through code repositories, emails, or other communication channels.
Insufficient protection: If the private key is not properly protected with strong encryption and access controls, it may be vulnerable to theft or unauthorized access.
Malware or hacking: Malicious actors may use malware or hacking techniques to steal private keys from developers' computers or systems.
Social engineering: Attackers may use social engineering tactics to trick developers into revealing their private key or other sensitive information.
Weak key management practices: Poor key management practices, such as storing private keys in insecure locations or using weak passwords, can also lead to key leakage.

What are the risks of leaking a PGP Private Key

Leaking a PGP Private Key can have serious consequences and risks that developers need to be aware of. Here are some specific risks associated with leaking a PGP Private Key:

Unauthorized access: If a PGP Private Key is leaked, unauthorized individuals may gain access to sensitive information encrypted with that key.
Data breaches: Leaking a PGP Private Key can lead to data breaches, compromising the confidentiality and integrity of data.
Identity theft: Hackers could potentially use a leaked PGP Private Key to impersonate the key owner, leading to identity theft and fraudulent activities.
Loss of trust: A leaked PGP Private Key can damage the reputation and trustworthiness of the individual or organization associated with the key.
Legal implications: Depending on the nature of the leaked information, there could be legal consequences for the key owner and their organization.

---]

[---

PGP Private Key security best practices

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

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

---]

[---

PGP Private 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 PGP Private Key was used by malicious actors

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

---]

[---

Steps to revoke the PGP Private Key

Generate a new PGP Private Key:

Log into your PGP Private 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 PGP Private 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 PGP Private 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