diff --git a/plans/tier0.fmf b/plans/tier0.fmf
index 13f8bcb..f184c31 100644
--- a/plans/tier0.fmf
+++ b/plans/tier0.fmf
@@ -8,6 +8,8 @@
 #   trigger=build
 ---
 summary: Tier 0 test plan
+context:
+  component: gcc-toolset-15-gcc
 environment+:
   WITH_SCL: gcc-toolset-15-env
 discover:
diff --git a/rpminspect.yaml b/rpminspect.yaml
new file mode 100644
index 0000000..f20f2f5
--- /dev/null
+++ b/rpminspect.yaml
@@ -0,0 +1,23 @@
+badfuncs:
+    # GCC doesn't use the "forbidden" functions as such. Just some of its
+    # sanitizers can instrument those functions which leads to false
+    # positives in the badfuncs test.
+    ignore:
+      - /usr/lib*/libasan.so.*.*.*
+      - /usr/lib*/libtsan.so.*.*.*
+
+specname:
+    # In GCC toolsets builds, the spec file name and the package may not
+    # be exactly the same, the package is prefixed with gcc-toolset-NN-.
+    # Let's ignore the prefix.
+    match: suffix
+    primary: filename
+
+runpath:
+    # Although gcc-toolset sanitizers link gcc-toolset libraries from
+    # /opt/..., they themselves are placed in /usr. The runpath test
+    # doesn't like this difference. Explicitly allow it.
+    allowed_paths:
+      - /opt/rh/gcc-toolset-15/root/usr/lib
+      - /opt/rh/gcc-toolset-15/root/usr/lib/../lib64
+      - /opt/rh/gcc-toolset-15/root/usr/lib64