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 Riot Games API Key leaked! What should I do?

What is a Riot Games API Key and how it is used?

The Riot Games API Key is a unique authentication token provided by Riot Games that allows developers to access and interact with the Riot Games API, enabling them to retrieve game data and build applications related to Riot Games' products.

Here are the main use cases for the Riot Games API Key:

  • Accessing Game Data: Developers use the API key to access game data such as player statistics, match history, and in-game items for integration into their applications or websites.
  • Authentication: The API key is used for authentication purposes to verify the identity of the developer accessing the Riot Games API and to ensure secure communication between the developer's application and Riot Games servers.
  • Rate Limiting: The API key helps in enforcing rate limits set by Riot Games to prevent abuse of their API resources. Developers need to include the API key in their requests to ensure they stay within the allowed usage limits.

---]

[---

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

Using environment variables for storing sensitive information like Riot Games API Key in your code is a good security practice for the following reasons:

  • Environment variables are not hard-coded in the codebase, making it more difficult for attackers to access them.
  • Environment variables are stored outside of the code repository, reducing the risk of accidental exposure or leakage.
  • Environment variables can be easily managed and updated without changing the code, enhancing security and flexibility.
  • Environment variables are specific to the environment in which the code is running, limiting access to authorized users and systems.

How to secure your secrets using environment variables

--

---]

[---

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

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

--

---]

[---

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

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

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

--

---]

[---

How to generate a Riot Games API Key?

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

  1. Go to the Riot Games Developer Portal website.
  2. Sign in with a Riot Games account or create a new one if needed.
  3. Create a new application by providing the necessary information such as the application name, description, and the API services you will be using.
  4. Once the application is created, you will be provided with an API Key that you can use to access the Riot Games API.
  5. Make sure to keep your API Key secure and avoid sharing it publicly.

---]

[---

My Riot Games API Key leaked, what are the possible reasons?

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

  • Improper storage: If the API key is stored in a publicly accessible repository or hardcoded within the application code, it can be easily accessed by unauthorized parties.
  • Accidental exposure: Developers might inadvertently include the API key in error messages, logs, or other forms of output that are visible to external users.
  • Insufficient access controls: If the API key is shared with team members who do not have a need-to-know or if access permissions are not properly configured, there is a higher risk of leakage.
  • Compromised systems: If the systems where the API key is stored are compromised by attackers, they can potentially gain access to the key and misuse it.
  • Third-party dependencies: If the API key is included in third-party libraries or services that are not adequately secured, it can be exposed through vulnerabilities in those dependencies.

What are the risks of leaking a Riot Games API Key

Developers need to be aware of the risks associated with leaking a Riot Games API Key. Here are some specific risks related to this API Key:

  • Unauthorized Access: If the API Key is leaked, unauthorized individuals could gain access to sensitive data and resources within the Riot Games system.
  • Financial Loss: Leaking the API Key could lead to financial losses, especially if malicious actors use it to perform unauthorized transactions or access paid services.
  • Reputation Damage: A leaked API Key can damage the reputation of both the developer and Riot Games, leading to a loss of trust from users and partners.
  • Legal Consequences: Depending on the circumstances, leaking an API Key could result in legal action being taken against the responsible party, leading to potential fines or lawsuits.

It is crucial for developers to understand the importance of securely managing and protecting API Keys to prevent these risks from occurring.

---]

[---

Riot Games API Key security best practices

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

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

---]

[---

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

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

---]

[---

Steps to revoke the Riot Games API Key

Generate a new Riot Games API Key:

  • Log into your Riot Games 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 Riot Games 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 Riot Games 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