fix(query): fn for SQL Server Database Without Auditing - ARM #7590
Conversation
…0694--FN-SQL_Server_Database_Without_Auditing--ARM
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 19562607 | Triggered | Generic Password | 59a513d | assets/queries/common/passwords_and_secrets/test/positive53.json | 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.
Reason for Proposed Changes
dbTypesarray, a search of the resource´schildresources proceeds aiming to find one with a valid type such as "auditingSettings" , those being registered in the "types" array, and , in case they have astateset toenabled, we can be sure auditing is not missing and the flag is avoided.dbTypesarray there should be theMicrosoft.Sql/serverstype and in thetypesarray there should be theMicrosoft.Sql/servers/auditingSettingstype.Proposed Changes
dbTypesandtypesarrays. With this the negative tests started to flag due to being dependent on aMicrosoft.Sql/serversthat itself triggered the query flag.I submit this contribution under the Apache-2.0 license.