Gartner®: Avoid Mobile Application Security Pitfalls

GET REPORT

Gartner®: Avoid Mobile Application Security Pitfalls

GET REPORT
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
.

[---

My Bunny.net API Key leaked! What should I do?

What is a Bunny.net API Key and how it is used?

An API key is a unique code issued by Bunny.net that allows developers to authenticate and access the Bunny.net API for managing content delivery services.

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

  • Authentication: The Bunny.net API Key is primarily used for authenticating and authorizing requests made to the Bunny.net API. It serves as a secure way to ensure that only authorized users can access and interact with the Bunny.net services.
  • Access Control: The API Key is crucial for controlling access to specific resources and functionalities within the Bunny.net platform. By using the API Key, developers can define and enforce access levels, permissions, and restrictions for different users or applications.
  • Monitoring and Tracking: The Bunny.net API Key is also utilized for monitoring and tracking API usage and activity. It allows developers to track who is making requests, when the requests are made, and what actions are being performed, enabling better visibility and control over API operations.

---]

[---

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

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

  • Environment variables are not hard-coded in the codebase, reducing the risk of accidental exposure.
  • Environment variables are stored outside the code repository, keeping the sensitive information separate and secure.
  • Environment variables can be easily managed and updated without the need to modify the code, enhancing security and flexibility.
  • Environment variables are typically not accessible to unauthorized users or third-party services, adding an extra layer of protection.

How to secure your secrets using environment variables

--

---]

[---

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

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

--

---]

[---

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

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

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

--

---]

[---

How to generate a Bunny.net API Key?

To generate a Bunny.net API Key, developers can follow these steps:

  1. Log in to the Bunny.net dashboard.
  2. Click on the user icon in the top right corner and select "API Keys" from the dropdown menu.
  3. Click on the "Create API Key" button.
  4. Enter a name for the API Key and select the permissions you want to grant to it.
  5. Click on the "Create API Key" button to generate the key.

Once the API Key is generated, developers can use it to authenticate and access the Bunny.net API for various functionalities like managing storage, CDN configurations, and more.

---]

[---

My Bunny.net API Key leaked, what are the possible reasons?

There are several reasons why a Bunny.net 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 need to know or if it is not properly protected with access controls, it can be leaked.
  • Phishing attacks: Developers may fall victim to phishing attacks where they unknowingly provide their API Key to malicious actors.
  • Insufficient monitoring: Without proper monitoring and logging mechanisms in place, it may be difficult to detect unauthorized access to the API Key.

What are the risks of leaking a Bunny.net API Key

Developers need to be aware of the risks associated with leaking a Bunny.net API Key. Here are some specific risks:

  • Data Breaches: If an API Key is leaked, unauthorized users may gain access to sensitive data stored on Bunny.net servers.
  • Financial Loss: Attackers could potentially use the leaked API Key to incur charges on the account associated with it, leading to financial loss for the organization.
  • Reputation Damage: A data breach or misuse of the API Key can damage the reputation of the organization, leading to loss of trust from customers and partners.
  • Legal Consequences: Depending on the nature of the leaked data and the impact of the breach, the organization may face legal consequences and regulatory fines.

---]

[---

Bunny.net API Key security best practices

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

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

---]

[---

Bunny.net 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 Bunny.net API Key was used by malicious actors

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

---]

[---

Steps to revoke the Bunny.net API Key

Generate a new Bunny.net API Key:

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