đź“… Webinar - Delivering Security on Your Terms: An Intro to Self-Hosted

Save my spot!

đź“… Webinar - Delivering Security on Your Terms: An Intro to Self-Hosted

Save my spot!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
.

[---

My Yousign API Key leaked! What should I do?

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

The Yousign API Key is a unique identifier that allows developers to authenticate and access the Yousign API services securely. It should be kept confidential and not shared with unauthorized users to prevent unauthorized access to sensitive information.

When using the Yousign API Key, developers should understand its main use cases:

  • Authentication: The Yousign API Key is used to authenticate and authorize access to the Yousign API, allowing developers to interact with the e-signature platform securely.
  • Integration: Developers use the Yousign API Key to integrate Yousign's e-signature functionality into their applications, enabling users to sign documents electronically.
  • Tracking and Monitoring: The Yousign API Key can also be used to track and monitor API usage, providing insights into how the e-signature functionality is being utilized within the application.

---]

[---

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

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

  • Environment variables are not hard-coded in the codebase, reducing the risk of exposing the sensitive information in case of a breach or unauthorized access to the code repository.
  • Environment variables are stored separately from the code and are not included in version control systems, providing an additional layer of security.
  • Environment variables can be easily managed and updated without the need to modify the code, making it convenient to rotate API keys regularly for enhanced security.
  • When deployed, environment variables are typically stored in secure locations and are not accessible to users or unauthorized parties, minimizing the risk of exposure.

How to secure your secrets using environment variables

--

---]

[---

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

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

--

---]

[---

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

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

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

--

---]

[---

How to generate a Yousign API Key?

To generate a Yousign API Key, follow these steps:

  1. Log in to your Yousign account.
  2. Go to the API section in your account settings.
  3. Click on the "Generate API Key" button.
  4. Copy and securely store the generated API Key for future use.

---]

[---

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

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

  • Improper storage: If the API Key is stored in plain text in code repositories or configuration files that are publicly accessible, it can be easily leaked.
  • Weak access controls: If the API Key is shared with individuals who do not have a legitimate need to access it, there is a higher risk of it being leaked.
  • Logging and debugging: If the API Key is accidentally included in logs or error messages, it can be exposed to unauthorized users.
  • Phishing attacks: If developers fall victim to phishing attacks or social engineering tactics, their credentials, including API Keys, can be compromised.
  • Third-party integrations: If the Yousign API Key is shared with third-party services or libraries that have security vulnerabilities, it can lead to a leak.

What are the risks of leaking a Yousign API Key

As a security trainer, it's important for developers to understand the risks associated with leaking a Yousign API Key. The Yousign API Key is a sensitive piece of information that, if exposed, can lead to serious security breaches and potential unauthorized access to your Yousign account. Here are some specific risks of leaking a Yousign API Key:

  • Unauthorized access to your Yousign account: If an attacker gains access to your API Key, they can impersonate your account and perform actions on your behalf without your knowledge.
  • Data breaches: Leaking your API Key can expose sensitive data stored in your Yousign account, such as signed documents and personal information of users.
  • Financial loss: Attackers can misuse your API Key to perform malicious actions that may result in financial loss for your organization.
  • Reputation damage: A security breach due to a leaked API Key can tarnish your organization's reputation and erode trust with customers and partners.

It's crucial for developers to follow best practices in secret management and detection to prevent the leakage of sensitive information like API Keys. This includes securely storing API Keys, limiting access to them, rotating them regularly, and monitoring for any unauthorized usage. By raising awareness about the risks of leaking a Yousign API Key, developers can better protect their applications and data from potential threats.

---]

[---

Yousign API Key security best practices

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

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

---]

[---

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

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

---]

[---

Steps to revoke the Yousign API Key

Generate a new Yousign API Key:

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

---]

Environment Variables
Environment Variables
Environment Variables

charge

nullable string

For card errors, the ID of the failed charge.

payment_method_type

nullable string

If the error is specific to the type of payment method, the payment method type that had a problem. This field is only populated for invoice-related errors.

doc_url

nullable string

A URL to more information about the error code reported.

request_log_url

nullable string

A URL to the request log entry in your dashboard.

charge

nullable string

If the error is specific to the type of payment method, the payment method type that had a problem. This field is only populated for invoice-related errors.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

charge

nullable string

If the error is specific to the type of payment method, the payment method type that had a problem. This field is only populated for invoice-related errors.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

payment_intent

nullable object

The PaymentIntent object for errors returned on a request involving a PaymentIntent.

setup_intent

nullable object

The SetupIntent object for errors returned on a request involving a SetupIntent.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

Hide
Show
child attributes

type

enum

For some errors that could be handled programmatically, a short string indicating the error code reported.

CLIENT LIBRARIES

$ gem install stripe
$ pip install stripe
$ composer require stripe/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"
$ npm install --save stripe
$ go get github.com/stripe/stripe-go/v76
$ nuget install Stripe.net
SHOW
{{this.title}}
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
{{clipboardIconText}}
This is placeholder code