Create rule S7001: Detect Azure App Service Secrets APPSEC-1846

rules/S7001/metadata.json

@@ -0,0 +1,2 @@
+{
+}

rules/S7001/secrets/metadata.json

@@ -0,0 +1,56 @@
+{
+  "title": "Azure App Service deployment passwords should not be disclosed",
+  "type": "VULNERABILITY",
+  "code": {
+    "impacts": {
+      "SECURITY": "HIGH"
+    },
+    "attribute": "TRUSTWORTHY"
+  },
+  "status": "ready",
+  "remediation": {
+    "func": "Constant\/Issue",
+    "constantCost": "30min"
+  },
+  "tags": [
+    "cwe",
+    "cert"
+  ],
+  "defaultSeverity": "Blocker",
+  "ruleSpecification": "RSPEC-7001",
+  "sqKey": "S7001",
+  "scope": "All",
+  "securityStandards": {
+    "CWE": [
+      798,
+      259
+    ],
+    "OWASP": [
+      "A3"
+    ],
+    "CERT": [
+      "MSC03-J."
+    ],
+    "OWASP Top 10 2021": [
+      "A7"
+    ],
+    "PCI DSS 3.2": [
+      "6.5.10"
+    ],
+    "PCI DSS 4.0": [
+      "6.2.4"
+    ],
+    "ASVS 4.0": [
+      "2.10.4",
+      "3.5.2",
+      "6.4.1"
+    ],
+    "STIG ASD 2023-06-08": [
+      "V-222642"
+    ]
+  },
+  "defaultQualityProfiles": [
+    "Sonar way"
+  ],
+  "quickfix": "unknown"
+}

rules/S7001/secrets/rule.adoc

@@ -0,0 +1,73 @@
+
+include::../../../shared_content/secrets/description.adoc[]
+
+== Why is this an issue?
+
+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: deployment password
+
+:service_name: Azure App Service
+
+include::../../../shared_content/secrets/impact/infrastructure_takeover.adoc[]
+
+include::../../../shared_content/secrets/impact/data_compromise.adoc[]
+
+include::../../../shared_content/secrets/impact/data_modification.adoc[]
+
+include::../../../shared_content/secrets/impact/malware_distribution.adoc[]
+
+include::../../../shared_content/secrets/impact/financial_loss.adoc[]
+
+== How to fix it
+
+include::../../../shared_content/secrets/fix/revoke.adoc[]
+
+include::../../../shared_content/secrets/fix/vault.adoc[]
+
+=== Code examples
+
+==== Noncompliant code example
+
+In general, never disclose the "PublishSettings" file, or any data coming from it. It looks like that:
+
+[source,xml]
+----
+<publishData>
+    <publishProfile 
+        profileName="example" publishMethod="MSDeploy" 
+        publishUrl="example.net:443" 
+        msdeploySite="example"
+        userName="$example"
+        userPWD="6kkBCdit4ZTfs01By2RJjgRon9ly9yqetEBZhlz8MfDhn5qKrb5yhQRnMliM" <!-- Noncompliant -->
+        destinationAppUrl="https://example.net"
+        SQLServerDBConnectionString=""
+        mySQLDBConnectionString=""
+        hostingProviderForumLink=""
+        controlPanelLink="https://portal.azure.com"
+        webSystem="WebSites">
+        <databases/>
+    </publishProfile>
+</publishData>     
+ ----
+
+//=== How does this work?
+
+//=== Pitfalls
+
+//=== Going the extra mile
+
+== Resources
+
+include::../../../shared_content/secrets/resources/standards.adoc[]
+
+//=== Benchmarks