Update website with recent changes. (CSCC requirements) (#1810)

* Added 2.0 upgrade instruction (#1769)

* Added 2.0 upgrade instruction

* Addressed PR comment

* Updated broken urls

* Added missing gsuite scope (#1772)

* Update upgrade.md (#1774)

* Added compute engine disk resource (#1779)

* Update CSCC doc (#1778)

* versioned 2.1

* revert branch to stable

* Updated generated configuration files

* update versioning (#1791)

* Added space between comment and function

* Updated app.yaml file

* updates

* updates

* fixed version redirect issues

* Update forsetisecurity.org-dev faqs for VM instances security updates… (#1799)

* Update forsetisecurity.org-dev faqs for VM instances security updates issue#830

* Changes to PR comments Update forsetisecurity.org-dev faqs for VM instances security updates issue#830

* Update CSCC notifier documentation to list the additional requirements for CSCC (#1808)

* Update doc to list the additional requirements for CSCC

* Update how to enable API

* Fixing issue 1801 where links to GitHub for latest are broken. (#1807)

_docs/_latest/configure/notifier/index.md

@@ -171,9 +171,18 @@ notifier:
             webhook_url: https://hooks.slack.com/services/foobar
 ```
 
-### CSCC Notification
-
-Forseti Security can configured to send violations to [Cloud Security Command Center (Cloud SCC)](https://cloud.google.com/security-command-center/).
+### Cloud SCC Notification
+
+Forseti Security can configured to send violations to
+[Cloud Security Command Center (Cloud SCC)](https://cloud.google.com/security-command-center/).
+
+As Cloud SCC is in alpha, you must meet the following additional requirements:
+* Your organization is enrolled in the [Cloud SCC alpha program](https://services.google.com/fb/forms/commandcenteralpha/).
+* Your Forseti project has been whitelisted to Cloud SCC access. You should
+send the Forseti `project name, id and number` to your Cloud SCC contact.
+* Enable the `Cloud Security Command Center API` for the Forseti project via
+the Cloud Console.
+* Add the `securityCenter.editor` role to the Forseti server's service account. 
 
 1. Open `forseti-security/configs/forseti_conf_server.yaml`.
 1. Navigate to the `notifier` > `violation` > `cscc` section.

_faq/installation_and_deployment/forseti VM instance security updates.md

@@ -0,0 +1,16 @@
+---
+title: How do I keep Forseti VM instances (client and server) up-to-date with security patches? 
+order: 7
+---
+{::options auto_ids="false" /}
+
+
+[GCE](https://cloud.google.com/compute/docs/images) VM instances have the 
+[unattended-upgrades](https://wiki.debian.org/UnattendedUpgrades) tool to automatically update the operating system, software, or security patches from the [Debian security](https://www.debian.org/security/) repository.
+
+However, kernel patches do not take effect until your VM instance is restarted.
+By default, GCE does not automatically restart running instances.So you must either restart your instances manually to update the kernel, or [apply the mechanism provided by the unattended-upgrades tool to automatically do the restart](https://wiki.debian.org/UnattendedUpgrades#Automatic_call_via_.2Fetc.2Fapt.2Fapt.conf.d.2F20auto-upgrades).
+
+Automatic updates from Debian security do not upgrade instances between major versions of the operating system.
+Debian also has a relevant guide: https://www.debian.org/doc/manuals/securing-debian-howto/index.en.html
+

_includes/site/layout/docs/tabs.html

@@ -64,7 +64,7 @@
     </div>
     <div class="edit-on-github visible-lg-inline-block visible-md-inline-block">
       {% assign filename = page.path | split:"/" | last | downcase %}
-      <a class="icon github" href="{{ site.github.repository_url }}/edit/forsetisecurity.org/{{ page.path }}">
+      <a class="icon github" href="{{ site.github.repository_url }}/edit/forsetisecurity.org-dev/{{ page.path | replace_first: "_docs/latest/", "_docs/_latest/" }}">
         Edit this page
       </a>
     </div>