Skip to main content

How to Upgrade Riscosity on Azure

Updated

Overview

Upgrading Riscosity on Azure involves 2 required steps and 1 optional step:

  • Riscosity Certificate Manager Upgrade (Required)
  • Riscosity Stack Upgrade (Required)
  • Riscosity Proxy Upgrade (Optional, only required if you are using the Riscosity Proxy)

 

Riscosity Certificate Manager Upgrade

  • Login to the Azure console.
  • In the search bar specify: ‘Template specs’, and proceed to the ‘Template specs’ dashboard.
  • Select the Riscosity Certificate Manager template spec.
  • You should now be in the ‘Overview’ menu of the Riscosity Certificate Manager template spec. Select ‘+ Create new version’.
  • You should now be in the menu titled ‘Create new template spec version’. In the ‘Basics’ tab update the ‘Version’ value, and then proceed to the ‘Edit Template’ tab.
  • Since you are updating the Riscosity Certificate Manager, the presumption is that Riscosity has provided you with a new ARM template for the Riscosity Certificate Manager. Please paste that template into the ‘Template Content’ area, and provide the non-sensitive parameters directly into the template as default values. For sensitive parameters, you once again have the choice to either store them unencrypted directly in the template or in a secondary location of your choosing. Proceed to the ‘Review + Save’ tab. Then select ‘Save Changes’ to create the new template spec version.
  • Return to the Azure console home. In the search bar specify: ‘Template specs’, and proceed to the ‘Template specs’ dashboard. Select the Riscosity Certificate Manager template spec.
  • You should once again be in the ‘Overview’ menu of the Riscosity Certificate Manager template spec. Select ‘Deploy’ to redeploy the template spec.
  • You should now be in the ‘Deploy’ menu of the template spec. If necessary, fill in the sensitive parameter values then select ‘Next’. Then select ‘Create’ to redeploy the Riscosity Certificate Manager.

 

Riscosity Stack Upgrade

  • Login to the Riscosity web application. To access the web application either use the public IP of its application gateway or its host name.
  • You should now be on the homepage for the Riscosity web application. In the top-right corner of the screen, click on your user account icon. Then select ‘Check for DB updates’. You will be redirected to the ‘Database status’ menu. Select ‘Check for Updates’ to bring up the ‘Database Update’ modal window. If there are updates available, a button labelled ‘Update’ will appear. Select the button to update the Riscosity web application database. If this button does not appear, then your database is already up-to-date.
  • Login to the Azure console.
  • In the search bar specify: ‘Template specs’, and proceed to the ‘Template specs’ dashboard.
  • Select the Riscosity Stack template spec.
  • You should now be in the ‘Overview’ menu of the Riscosity Stack template spec. Select ‘+ Create new version’.
  • You should now be in the menu titled ‘Create new template spec version’. In the ‘Basics’ tab update the ‘Version’ value, and then proceed to the ‘Edit Template’ tab.
  • Since you are updating the Riscosity Stack, the presumption is that Riscosity has provided you with a new ARM template for the Riscosity Stack. Please paste that template into the ‘Template Content’ area, and provide the non-sensitive parameters directly into the template as default values. For sensitive parameters, you once again have the choice to either store them unencrypted directly in the template or in a secondary location of your choosing. Proceed to the ‘Review + Save’ tab. Then select ‘Save Changes’ to create the new template spec version.
  • Return to the Azure console home. In the search bar specify: ‘Template specs’, and proceed to the ‘Template specs’ dashboard. Select the Riscosity Stack template spec.
  • You should once again be in the ‘Overview’ menu of the Riscosity Stack template spec. Select ‘Deploy’ to redeploy the template spec.
  • You should now be in the ‘Deploy’ menu of the template spec. If necessary, fill in the sensitive parameter values then select ‘Next’. Then select ‘Create’ to redeploy the Riscosity Stack.
  • It is time to re-scale your Riscosity web application. Return to the Azure console home. In the search bar specify: ‘Virtual machine scale sets’, and proceed to the ‘Virtual machine scale sets’ dashboard. Select the RiscosityPortalScaleSet.
  • You should now be in the ‘Overview’ menu of the RiscosityPortalScaleSet. Select ‘Availability + scale’ > ‘Scaling’ from the left pane.
  • You should now be in the ‘Scaling’ menu of the RiscosityPortalScaleSet. Increase the ‘Instance count’ from 1 to 2. Make sure to select ‘Save’ in the top-left of the menu after doing so.
  • Select ‘Instances’ from the left pane. Wait for the second instance to appear. Then wait for it to reach the ‘Running’ state. Once it is in the ‘Running’ state, click on its name to be redirected to the ‘Overview’ menu of the instance. In this menu, a ‘Health state’ should be available. Wait for this ‘Health state’ to reach ‘Healthy’. Once the ‘Health state’ has reached ‘Healthy’ you can proceed.
  • Return to the Azure console home. In the search bar specify: ‘Virtual machine scale sets’, and proceed to the ‘Virtual machine scale sets’ dashboard. Select the RiscosityPortalScaleSet.
  • You should once again be in the ‘Overview’ menu of the RiscosityPortalScaleSet. Select ‘Availability + scale’ > ‘Scaling’ from the left pane.
  • You should now be in the ‘Scaling’ menu of the RiscosityPortalScaleSet. Decrease the ‘Instance count’ from 2 to 1. Make sure to select ‘Save’ in the top-left of the menu after doing so.
  • Select ‘Instances’ from the left pane. If it has not yet disappeared, wait for the second instance to disappear.

Riscosity Proxy Upgrade

  • Once a Riscosity Stack update is finished, you can proceed with updating the Riscosity Proxy. This process has been streamlined in order to make it as simple as possible.
  • First, login to the Riscosity web application. To access the web application either use the public IP of its application gateway or its host name. When you login, you must do so with a user account belonging to the organization that you have made the proxy owner.
  • From the left pane select ‘Integrations’.
  • You should now be in the ‘Integrations’ menu. Select ‘Configure’ under ‘Azure Accounts’.
  • You should now be in the ‘Integrations > Azure Accounts’ menu. To update your Azure account(s), select the ‘Edit’ button next to each entry you wish to update. A modal window titled ‘Edit Azure Account’ should pop up. This modal window will allow you to edit the name of the account or the ‘Valid Client Secret for App Registration’. When you are finished making your changes, you can click ‘Save’ to submit them.
  • From the left pane select ‘APIs’ > ‘Azure Governance’. You should be redirected to the ‘APIs > Azure Governance’ menu.
  • To update the Riscosity Proxy expand the ‘General’ section.
  • Select ‘Install / Update’. A modal window titled ‘Edit Proxy’ should pop up. If Riscosity has provided a new ‘Slingshot Image ID’ and / or ‘Base Proxy Image ID’ please provide them here. You can then simply click ‘Install / Update’ to initiate the update of the Riscosity Proxy. When the Riscosity Proxy is fully updated its status will return to ‘INSTALLED’. During the update there will be no service interruption to the proxy.
  • 9. To update a proxy tunnel expand the ‘Proxy Tunnels’ section.
  • 10. Select ‘Install / Update’ for the proxy tunnel you wish to update. A modal window titled ‘Edit Proxy Tunnel’ should pop up. If Riscosity has provided a new ‘Analyzer Image ID’ and / or ‘Forwarder Image ID’ please provide them here. You can then simply click ‘Install / Update’ to initiate the update of the proxy tunnel. When the proxy tunnel is fully updated its status will return to ‘INSTALLED’. During the update there will be no service interruption to the proxy.
  • 11. To update a VNet connection expand the ‘VNets’ section.
  • 12. Select ‘Install / Update’ for the VNet you wish to update. A modal window titled ‘Edit VNet’ should pop up. Simply click ‘Install / Update’ to initiate the update of the VNet. When the VNet is fully updated its status will return to ‘INSTALLED’.
  • 13. To update an activated domain’s VNet associations expand the ‘Domains’ section.
  • 14. Select ‘Associations’ for the activated domain you are interested in. A modal window titled ‘Edit VNet Associations’ should pop up. Simply click ‘Update’ to initiate the update of all the VNet associations. When the VNet associations are fully updated you will be able to click on the ‘Associations’ button again. Please do so. The ‘Edit VNet Associations’ modal window should pop up again. If all the VNet associations appear green, then the update was a success.
Powered by Zendesk