Update RSPEC

rules/S7149/secrets/metadata.json

@@ -1,5 +1,5 @@
 {
-  "title": "SECRET_TYPE should not be disclosed",
+  "title": "Doppler auth tokens should not be disclosed",
   "type": "VULNERABILITY",
   "code": {
     "impacts": {

rules/S7149/secrets/rule.adoc

@@ -7,21 +7,12 @@ include::../../../shared_content/secrets/rationale.adoc[]
 
 === What is the potential impact?
 
-// Optional: Give a general description of the secret and what it's used for.
-
 Below are some real-world scenarios that illustrate some impacts of an attacker
 exploiting the secret.
 
-// Set value that can be used to refer to the type of secret in, for example:
-// "An attacker can use this {secret_type} to ..."
-:secret_type: secret
-
-// Where possible, use predefined content for common impacts. This content can
-// be found in the folder "shared_content/secrets/impact".
-// When using predefined content, search for any required variables to be set and include them in this file.
-// Not adding them will not trigger warnings.
+include::../../../shared_content/secrets/impact/data_compromise.adoc[]
 
-//include::../../../shared_content/secrets/impact/some_impact.adoc[]
+include::../../../shared_content/secrets/impact/financial_loss.adoc[]
 
 == How to fix it
 
@@ -31,20 +22,13 @@ include::../../../shared_content/secrets/fix/vault.adoc[]
 
 === Code examples
 
-:example_secret: example_secret_value
-:example_name: java-property-name
-:example_env: ENV_VAR_NAME
+:example_secret: dp.ct.bAqhcVzrhy5cRHkOlNTc0Ve6w5NUDCpcutm8vGE9myi
+:example_name: doppler-auth-token
+:example_env: DOPPLER_AUTH_TOKEN
 
 include::../../../shared_content/secrets/examples.adoc[]
 
-//=== How does this work?
-
-//=== Pitfalls
-
-//=== Going the extra mile
-
 == Resources
 
 include::../../../shared_content/secrets/resources/standards.adoc[]
 
-//=== Benchmarks