SecurityInsight settings · Settings > Sign-in & Azure resources
Update ring
| Key | SI_UpdateRing |
|---|---|
| Where | Settings > Sign-in & Azure resources > Licence and updates |
| Type | int |
| Default | Not set: the ring the installation recorded at install time (from its resource-group name), until the updater records the ring it updates by |
| Edition | pro |
What it does
The update ring this installation belongs to: 0 = development, 1 = internal test, 2 = early release, 3 = broad. It is shown in the header (UPDATE RING) and recorded with the installation, so the ring is known from the day it is installed -- also before the updater job has run.
When set
The header shows this ring and setup records it as the installation's ring. Once the updater job has run, the header shows the ring the updater actually updated by -- which ring an installation receives releases on is decided by the update service, not by this setting.
When blank or default
Left blank, the default applies: Not set: the ring the installation recorded at install time (from its resource-group name), until the updater records the ring it updates by
Risk and how to reverse it
Affects how the jobs sign in or which Azure resources they use. A wrong value stops the affected jobs at their next run (nothing is changed or deleted); a broader identity or right gives the jobs more access than they need. Reversible: correct it and run again.
Requires
A SecurityInsight Pro licence.
Recommended
Keep the default. Change it when: Once, when the installation's ring is not shown, or was recorded wrongly at install time.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack