how to stop packagecloud in an emergency

README.md

@@ -81,6 +81,7 @@ The aim of this project is to have a quick guide of what to do when an emergency
 * [Start a psql console in the staging environment](howto/staging-environment.md#run-a-psql-console-in-staging-environment)
 * [Force a failover with postgres or redis](howto/manage-pacemaker.md#force-a-failover)
 * [Use aptly](howto/aptly.md)
+* [Disable PackageCloud](howto/stop-or-start-packagecloud.md)
 ### Work with the Database

howto/stop-or-start-packagecloud.md

+# PackageCloud [SCRAM](https://en.wikipedia.org/wiki/Scram) Button
+
+In the event that a malicious or compromised package is deployed
+to our package repo, we must stop PackageCloud immediately
+to prevent users from downloading the compromised package.
+
+This can be done via Marvin, our friendly GitLab Cog bot.
+
+If you have access to Marvin, you can call this by simply typing 
+the following into Slack:
+
+```
+!chef-job-start stop-packagecloud
+```
+
+Once we have resolved the issue or compromised package, we can 
+restart PackageCloud in a similar way.
+
+```
+!chef-job-start start-packagecloud
+```