diff --git a/rules/S6990/metadata.json b/rules/S6990/metadata.json
new file mode 100644
index 00000000000..2c63c085104
--- /dev/null
+++ b/rules/S6990/metadata.json
@@ -0,0 +1,2 @@
+{
+}
diff --git a/rules/S6990/secrets/metadata.json b/rules/S6990/secrets/metadata.json
new file mode 100644
index 00000000000..cd524a80ef2
--- /dev/null
+++ b/rules/S6990/secrets/metadata.json
@@ -0,0 +1,56 @@
+{
+  "title": "Ubidots API secrets 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-6990",
+  "sqKey": "S6990",
+  "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/S6990/secrets/rule.adoc b/rules/S6990/secrets/rule.adoc
new file mode 100644
index 00000000000..0dc80bd781f
--- /dev/null
+++ b/rules/S6990/secrets/rule.adoc
@@ -0,0 +1,49 @@
+
+include::../../../shared_content/secrets/description.adoc[]
+
+== Why is this an issue?
+
+include::../../../shared_content/secrets/rationale.adoc[]
+
+=== What is the potential impact?
+
+Ubidots API keys and tokens are used to programmatically access the Ubidots API.
+A compromised key can be able to access the API on behalf of a legitimate user
+and affect the confidentiality and integrity of the data stored on the service.
+
+Below are some real-world scenarios that illustrate some impacts of an attacker
+exploiting the secret.
+
+:secret_type: token
+
+include::../../../shared_content/secrets/impact/data_compromise.adoc[]
+
+== How to fix it
+
+include::../../../shared_content/secrets/fix/revoke.adoc[]
+
+include::../../../shared_content/secrets/fix/vault.adoc[]
+
+=== Code examples
+
+:example_secret: BBFF-I6yfPQkcRB2JgSzzmPd0VO75YFJwHL
+:example_name: Ubidots-api-key
+:example_env: UBIDOTS-KEY
+
+include::../../../shared_content/secrets/examples.adoc[]
+
+//=== How does this work?
+
+//=== Pitfalls
+
+//=== Going the extra mile
+
+== Resources
+
+=== Documentation
+
+* Ubidots documentation - https://help.ubidots.com/en/articles/570026-api-authentication[API Authentication]
+
+include::../../../shared_content/secrets/resources/standards.adoc[]
+
+//=== Benchmarks