My HubSpot API Key leaked! What should I do?

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

An API Key is a unique identifier that allows a developer to authenticate and access specific resources or services provided by an API, such as the HubSpot API. It is used to securely authorize and track API requests made by applications or users.

When it comes to understanding the HubSpot API Key, developers should be aware of the following main use cases:

Authentication: The HubSpot API Key is primarily used for authentication purposes, allowing developers to securely access and interact with the HubSpot API.
Data Access: Developers use the API Key to retrieve, update, and manipulate data within HubSpot, enabling integration with other systems and automation of various processes.
Integration: The API Key facilitates seamless integration of HubSpot with third-party applications, enabling developers to create custom solutions and enhance their marketing and sales workflows.

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

Using environment variables for storing sensitive information like HubSpot API keys is a good security practice for the following reasons:

Environment variables are not hard-coded into the code, making it less likely for them to be exposed accidentally through version control systems or code sharing.
Environment variables are stored outside of the codebase, providing an additional layer of security by separating sensitive information from the application logic.
Environment variables can be easily managed and rotated without the need to modify the code, allowing for better security controls and easier maintenance.

How to secure your secrets using environment variables

Language:
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Copy code
import os

hubspot_api_key_apikey = os.getenv('HUBSPOT_API_KEY_APIKEY')

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

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

Language:
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Copy code
import botocore 
import botocore.session 
from aws_secretsmanager_caching import SecretCache, SecretCacheConfig 

client = botocore.session.get_session().create_client('secretsmanager')
cache_config = SecretCacheConfig()
cache = SecretCache( config = cache_config, client = client)

hubspotapikey = cache.get_secret_string('HUBSPOTAPIKEY')

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

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

Language:
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Copy code
import hvac
import os

# Get the Vault URL and token from environment variables
VAULT_URL = os.getenv('VAULT_URL')
VAULT_TOKEN = os.getenv('VAULT_TOKEN')
VAULT_PATH = os.getenv('VAULT_PATH')

# Create connection
client = hvac.Client(url=VAULT_URL, token=VAULT_TOKEN)

# Read the secret
HUBSPOT_API_KEY = client.secrets.kv.v2.read_secret_version(path=VAULT_PATH)['data']['data']['HUBSPOT_API_KEY']

4. Code snippet to prevent HubSpot API Key hardcoding using CyberArk Conjur

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

Language:
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Copy code
import requests
import os


# CyberArk credentials
ID_TENANT_URL = os.getenv("ID_TENANT_URL")
PRIVATE_CLOUD_URL = os.getenv("PRIVATE_CLOUD_URL")
PAM_USER = os.getenv("PAM_USER")
PAM_PASS = os.getenv("PAM_PASS")


def get_auth_token() -> tuple[str, str]:
    url = f"{ID_TENANT_URL}/oauth2/platformtoken"
    response = requests.post(
        url,
        data={
            "grant_type": "client_credentials",
            "client_id": PAM_USER,
            "client_secret": PAM_PASS,
        },
    )  # Use verify=True in production
    if response.status_code == 200:
        data = response.json()
        return data["token_type"], data["access_token"]
    else:
        raise Exception(
            f"Failed to authenticate: {response.status_code} {response.text}"
        )


def get_account_id(account_name: str) -> str:
    token_type, access_token = get_auth_token()
    url = f"{PRIVATE_CLOUD_URL}/PasswordVault/API/Accounts"
    headers = {"Authorization": f"{token_type} {access_token}"}
    response = requests.get(url, params={"search": account_name}, headers=headers)
    if response.status_code == 200:
        accounts = response.json()["value"]
        return accounts[0]["id"]
    else:
        raise Exception(
            f"Failed to get account: {response.status_code} {response.text}"
        )


def get_secret(secret_name: str) -> str:
    token_type, access_token = get_auth_token()
    account_id = get_account_id(secret_name)
    url = (
        f"{PRIVATE_CLOUD_URL}/PasswordVault/API/Accounts/{account_id}/Password/Retrieve"
    )
    headers = {"Authorization": f"{token_type} {access_token}"}
    response = requests.post(
        url, json={"reason": "automatic retrieval"}, headers=headers
    )
    if response.status_code == 200:
        return response.text
    else:
        raise Exception(f"Failed to get secret: {response.status_code} {response.text}")


HUBSPOT_API_KEY = get_secret("HUBSPOT_API_KEY")

How to generate a HubSpot API Key?

To generate a HubSpot API Key, developers can follow these steps:

Log in to your HubSpot account.
Go to the "Settings" in the top right corner of the screen.
Under "Integrations" section, select "API Key".
Click on the "Generate API Key" button.
Give your API key a name and set the permissions for the key.
Click "Create" to generate the API Key.

Once the API key is generated, developers can use it to authenticate and access the HubSpot API for their applications.

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

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

1. Insecure storage: Storing the API Key in a plaintext file or hardcoding it in the source code can make it vulnerable to unauthorized access.
2. Weak access controls: Inadequate access controls on the system or repository where the API Key is stored can lead to unauthorized users gaining access.
3. Phishing attacks: Developers falling victim to phishing attacks and unknowingly disclosing their API Key to malicious actors.
4. Compromised third-party services: If the API Key is used in integrations with third-party services that have been compromised, it can lead to the key being leaked.
5. Lack of monitoring: Failure to monitor and detect unauthorized access or usage of the API Key can result in leaks going undetected.

What are the risks of leaking a HubSpot API Key

Leaking a HubSpot API Key can pose significant risks to your organization's data and security. It is crucial for developers to understand the potential consequences of such a breach:

Data Breach: A leaked HubSpot API Key can provide unauthorized access to sensitive customer data stored in HubSpot, leading to potential data breaches.
Unauthorized Access: Attackers can use a leaked API Key to gain unauthorized access to your HubSpot account, manipulate data, or perform malicious actions.
Financial Loss: A compromised API Key can result in financial loss due to unauthorized transactions, data loss, or damage to your organization's reputation.
Legal Consequences: Data breaches involving sensitive customer information can lead to legal consequences, including regulatory fines and lawsuits.
Reputation Damage: A security incident resulting from a leaked API Key can damage your organization's reputation and erode customer trust.

It is essential to implement robust secret management practices and regularly monitor for any potential leaks to mitigate the risks associated with exposing a HubSpot API Key.

HubSpot API Key security best practices

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

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

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

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

Steps to revoke the HubSpot API Key

Generate a new HubSpot API Key:

Log into your HubSpot 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 HubSpot 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 HubSpot 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.

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