Az storage from js #13
Conversation
|
It's ok. Now ajv-format requires ajv |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://mango-mushroom-0effeca03-13.westeurope.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://mango-mushroom-0effeca03-13.westeurope.azurestaticapps.net |
|
| Secret | Commit | Filename | Detected At | |
|---|---|---|---|---|
| Microsoft Azure Storage Account Key | 6e9301c | create-az-storage.sh | 10:20 November 21st, 2021 | View secret |
🛠 How to resolve this
-
Understand the implications of revoking this secret by examining where it is used in your code.
-
Replace and store your secret safely. Learn here the best practices
-
Revoke and rotate this secret
-
If possible, rewrite your git history to remove all evidence of the secret leak. Please beware this is not a trivial operation. You might completely break other contributing developers’ workflow and you risk accidentally deleting work in progress.
💡 To avoid such incidents in the future, consider following these best practices for managing and storing secrets including API keys and other credentials.
You are seeing this because you or someone else has authorized GitGuardian to scan pull requests
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://mango-mushroom-0effeca03-13.westeurope.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://mango-mushroom-0effeca03-13.westeurope.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://mango-mushroom-0effeca03-13.westeurope.azurestaticapps.net |
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://mango-mushroom-0effeca03-13.westeurope.azurestaticapps.net |
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 2123825 | Microsoft Azure Storage Account Key | 6e9301c | create-az-storage.sh | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://proud-field-0ddb7da10-13.centralus.1.azurestaticapps.net |
…component.html, and delete unnecessary workflow files
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 2123825 | Triggered | Microsoft Azure Storage Account Key | 6e9301c | create-az-storage.sh | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
No description provided.