diff --git a/rules/S6988/metadata.json b/rules/S6988/metadata.json
new file mode 100644
index 0000000000..2c63c08510
--- /dev/null
+++ b/rules/S6988/metadata.json
@@ -0,0 +1,2 @@
+{
+}
diff --git a/rules/S6988/secrets/metadata.json b/rules/S6988/secrets/metadata.json
new file mode 100644
index 0000000000..bd5bbca5be
--- /dev/null
+++ b/rules/S6988/secrets/metadata.json
@@ -0,0 +1,64 @@
+{
+  "title": "MapBox secret access tokens should not be disclosed",
+  "type": "VULNERABILITY",
+  "code": {
+    "impacts": {
+      "SECURITY": "HIGH"
+    },
+    "attribute": "TRUSTWORTHY"
+  },
+  "status": "ready",
+  "remediation": {
+    "func": "Constant\/Issue",
+    "constantCost": "30min"
+  },
+  "tags": [
+    "cwe",
+    "cert"
+  ],
+  "extra": {
+    "replacementRules": [
+
+    ],
+    "legacyKeys": [
+
+    ]
+  },
+  "defaultSeverity": "Blocker",
+  "ruleSpecification": "RSPEC-6988",
+  "sqKey": "S6988",
+  "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"
+}
diff --git a/rules/S6988/secrets/rule.adoc b/rules/S6988/secrets/rule.adoc
new file mode 100644
index 0000000000..c496091efc
--- /dev/null
+++ b/rules/S6988/secrets/rule.adoc
@@ -0,0 +1,45 @@
+
+include::../../../shared_content/secrets/description.adoc[]
+
+== Why is this an issue?
+
+include::../../../shared_content/secrets/rationale.adoc[]
+
+=== What is the potential impact?
+
+MapBox secret access tokens are used to authenticate MapBox API calls. Each
+token is assigned one or more scopes that determine which API calls can be made
+using that token.
+
+Below are some real-world scenarios that illustrate some impacts of an attacker
+exploiting the access token.
+
+include::../../../shared_content/secrets/impact/data_modification.adoc[]
+
+include::../../../shared_content/secrets/impact/non_repudiation.adoc[]
+
+== How to fix it
+
+include::../../../shared_content/secrets/fix/revoke.adoc[]
+
+include::../../../shared_content/secrets/fix/vault.adoc[]
+
+=== Code examples
+
+:example_secret: sk.eyJ1IjoiZXhhbXBsZSIsImEiOiJFeEFtUGxFIn0.IsnG4xwWhubMpVzDrQfFWg
+:example_name: mapbox.access-token
+:example_env: MAPBOX_ACCESS_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
diff --git a/shared_content/secrets/impact/data_modification.adoc b/shared_content/secrets/impact/data_modification.adoc
new file mode 100644
index 0000000000..85e2d4a275
--- /dev/null
+++ b/shared_content/secrets/impact/data_modification.adoc
@@ -0,0 +1,10 @@
+==== Modification of application data
+
+Applications may rely on data that cannot be distributed with the application
+code. This may be due to the size of the data, or because the data is regularly
+updated. This data is downloaded by the application as it is needed.
+
+If an attacker can gain access to an authentication secret, they may be able to
+alter or delete this application data. This may cause parts of the application
+to misbehave or stop working. Maliciously altered data could also contain
+undesirable content which results in reputational damage.