[---

My Intercom Access Token leaked! What should I do?

What is a Intercom Access Token and how it is used?

An Intercom Access Token is a unique alphanumeric code that grants access to Intercom's API for authentication and authorization purposes.

Intercom Access Token is used for:

Authenticating API requests: Developers use the Access Token to authenticate and authorize their API requests to the Intercom platform, ensuring secure communication between their application and Intercom services.
Accessing user data: The Access Token allows developers to access and retrieve user data from Intercom, enabling them to provide personalized experiences and interactions within their applications.
Performing administrative tasks: Developers can use the Access Token to perform administrative tasks such as managing users, conversations, and other resources within the Intercom platform, helping them streamline and automate various processes.

---]

[---

1. Code snippets to prevent Intercom Access Token hardcoding using environment variables

Using environment variables for storing sensitive information like an Intercom Access Token is a secure practice because:

Environment variables are not hard-coded in the codebase, reducing the risk of exposure in case of a code leak.
Environment variables are stored outside of the codebase and are not accessible to users or other third parties who may have access to the code.
Environment variables can be managed securely on the server or deployment platform, allowing for easy rotation and updates without changing the code.

How to secure your secrets using environment variables

---]

[---

2. Code snippet to prevent Intercom Access Token hardcoding using AWS Secrets Manager

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

---]

[---

3. Code snippet to prevent Intercom Access Token hardcoding using HashiCorp Vault

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

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

---]

[---

How to generate a Intercom Access Token?

To generate an Intercom Access Token, developers need to follow these steps:

Log in to the Intercom Developer Hub.
Go to the "Access Tokens" section.
Click on the "Generate Access Token" button.
Provide a name for the token to easily identify its purpose.
Choose the appropriate scope for the token, such as read-only or read-write access.
Click on the "Generate Token" button to create the Access Token.

Once the Access Token is generated, developers can use it to authenticate API requests to Intercom on behalf of their application.

---]

[---

My Intercom Access Token leaked, what are the possible reasons?

There are several reasons why an Intercom Access Token might have been leaked:

Improper storage: Storing the Access Token in plain text in code, configuration files, or version control systems can lead to accidental exposure.
Weak access controls: Allowing unauthorized access to systems or repositories where the Access Token is stored can result in leakage.
Phishing attacks: Social engineering attacks that trick individuals into revealing their Access Token can also lead to leaks.
Third-party integrations: Integrating with third-party services that do not have robust security measures in place can expose Access Tokens to potential leaks.

What are the risks of leaking a Intercom Access Token

When it comes to Intercom Access Tokens, it is crucial for developers to understand the risks associated with leaking such sensitive information. Here are some specific risks to be aware of:

Unauthorized Access: If an Intercom Access Token is leaked, unauthorized individuals may gain access to sensitive data and functionalities within the Intercom platform.
Data Breaches: Leaking an Intercom Access Token can potentially lead to data breaches, compromising the confidentiality and integrity of user information stored in Intercom.
Reputation Damage: A security incident resulting from a leaked Access Token can severely damage the reputation of the developer or organization responsible for the application.
Financial Loss: In some cases, a security breach caused by a leaked Access Token can result in financial losses due to legal fines, compensation to affected users, and loss of business opportunities.

Therefore, it is imperative for developers to prioritize the secure management and protection of Intercom Access Tokens to prevent these risks and safeguard the integrity of their applications and user data.

---]

[---

Intercom Access Token security best practices

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

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

---]

[---

Intercom Access 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 Intercom Access Token was used by malicious actors

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

---]

[---

Steps to revoke the Intercom Access Token

Generate a new Intercom Access Token:

Log into your Intercom Access 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 Intercom Access 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 Intercom Access 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