diff --git a/docs/sources/developers/plugins/publish-a-plugin.md b/docs/sources/developers/plugins/publish-a-plugin.md
index ca8092e53d1..3e3b51f3191 100644
--- a/docs/sources/developers/plugins/publish-a-plugin.md
+++ b/docs/sources/developers/plugins/publish-a-plugin.md
@@ -86,6 +86,7 @@ Before you submit your plugin, we ask that you read our guidelines and frequentl
 
 To speed up the time it takes to review your plugin:
 
+- Get familiar with our plugin [publishing and signing criteria](publishing-and-signing-criteria.md)
 - Check that your plugin is ready for review using the [plugin validator](https://github.com/grafana/plugin-validator).
 - Read our [6 tips for improving your Grafana plugin before you publish](https://grafana.com/blog/2021/01/21/6-tips-for-improving-your-grafana-plugin-before-you-publish/).
 - Refer to [plugin-examples](https://github.com/grafana/grafana-plugin-examples) to review best practices for building your plugin.
diff --git a/docs/sources/developers/plugins/publishing-and-signing-criteria.md b/docs/sources/developers/plugins/publishing-and-signing-criteria.md
index 948ce45d10f..277ba504c2f 100644
--- a/docs/sources/developers/plugins/publishing-and-signing-criteria.md
+++ b/docs/sources/developers/plugins/publishing-and-signing-criteria.md
@@ -19,6 +19,9 @@ Grafana plugins must adhere to the following criteria when being reviewed for pu
 - Abuse: plugins should not perform actions beyond the scope of the intended use.
   - Do not include hidden files
   - Do not manipulate the underlying environment, privileges, or related processes
+- Security:
+  - Should not access the filesystem
+  - Should not access environment variables
 
 ## Commercial