[---

My FullContact API Key leaked! What should I do?

What is a FullContact API Key and how it is used?

The FullContact API Key is a unique alphanumeric code that serves as a secure authentication token for accessing the FullContact API, allowing developers to retrieve and manage contact information from various sources.

Here are the main use cases for the FullContact API Key:

Accessing FullContact API Endpoints: The API Key is used to authenticate and authorize access to FullContact's API endpoints, allowing developers to retrieve information about contacts, enrich contact data, and perform other operations.
Integration with Third-Party Applications: Developers can use the FullContact API Key to integrate FullContact's services with their own applications or third-party platforms, enabling them to leverage contact data and insights provided by FullContact.
Data Enrichment and Personalization: By utilizing the FullContact API Key, developers can enhance their contact databases with additional information, such as social profiles, job titles, and demographic data, to personalize user experiences and improve data quality.

---]

[---

1. Code snippets to prevent FullContact API Key hardcoding using environment variables

Using environment variables for storing sensitive information like API keys, such as the FullContact API Key, is a secure practice for the following reasons:

Environment variables are not hard-coded in the codebase, making it less likely for the key to be exposed in version control systems or shared publicly.
Environment variables are stored outside of the codebase and can be managed separately, reducing the risk of unauthorized access to the key.
Environment variables are only accessible to the specific process that needs them, limiting the exposure of the key to other parts of the system.

How to secure your secrets using environment variables

---]

[---

2. Code snippet to prevent FullContact API Key hardcoding using AWS Secrets Manager

Using AWS Secrets Manager to manage FullContact 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 FullContact API Key from AWS Secrets Manager.

---]

[---

3. Code snippet to prevent FullContact API Key hardcoding using HashiCorp Vault

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

Using CyberArk Conjur to manage FullContact 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 FullContact API Key from CyberArk Conjur.

---]

[---

How to generate a FullContact API Key?

To generate a FullContact API Key, developers need to follow these steps:

Go to the FullContact website and sign up for an account.
Once logged in, navigate to the API section in the dashboard.
Click on the option to create a new API Key.
Follow the prompts to generate the API Key.
Make sure to securely store the API Key as it will be required for making API requests.

---]

[---

My FullContact API Key leaked, what are the possible reasons?

There are several reasons why a FullContact API Key might have been leaked:

Improper storage: If the API key is stored in plain text in code repositories or configuration files, it can easily be exposed through a data breach or unauthorized access.
Weak access controls: If the API key is not properly protected with strong access controls and permissions, it can be accessed by unauthorized users or malicious actors.
Shared keys: If the API key is shared with multiple developers or stored in shared environments without proper segregation, the risk of leakage increases.
Logging and debugging: If the API key is inadvertently logged or exposed in error messages or debugging information, it can be leaked unintentionally.
Third-party integrations: If the API key is used in third-party integrations or services that are not secure, it can be compromised through vulnerabilities in those systems.

What are the risks of leaking a FullContact API Key

When it comes to secret management, it is crucial for developers to understand the risks associated with leaking a FullContact API Key. Here are some specific risks:

Data Breach: If a FullContact API Key is leaked, it can potentially lead to unauthorized access to sensitive user data stored on the FullContact platform.
Financial Loss: Hackers or malicious actors could exploit a leaked API Key to make unauthorized requests, leading to financial loss for the organization.
Reputation Damage: A data breach or misuse of the API Key can tarnish the reputation of the organization, leading to loss of trust from customers and partners.
Legal Consequences: Depending on the nature of the data exposed or the misuse of the API Key, there could be legal implications and regulatory fines imposed on the organization.

It is essential for developers to prioritize secure handling of API Keys, including proper storage, encryption, and access control mechanisms to prevent unauthorized access and potential leaks.

---]

[---

FullContact API Key security best practices

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

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

---]

[---

FullContact 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 FullContact API Key was used by malicious actors

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

---]

[---

Steps to revoke the FullContact API Key

Generate a new FullContact API Key:

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