rage.fail

azure-vmss-capacity-trigger

derived azure emits CanTrigger

match (effective permission)

{ "action": "Microsoft.Compute/virtualMachineScaleSets/write", "scope_type": "resource|resourceGroup|subscription|mg" }

emit

target type	`Compute`
source	`<principal>`
target	`<scale set>`
permissions	`Microsoft.Compute/virtualMachineScaleSets/write`

Narrative

{principal.name} can raise capacity of {vmss.name} (virtualMachineScaleSets/write), forcing new instances to boot the model as its MI.

Raw rule rules/derived/azure/vmss.yaml

id: azure-vmss-capacity-trigger
emits: CanTrigger
match_effective_permission:
  action: Microsoft.Compute/virtualMachineScaleSets/write
  scope_type: resource|resourceGroup|subscription|mg
emit:
  target_type: Compute
  source: <principal>
  target: <scale set>
  permissions:
  - Microsoft.Compute/virtualMachineScaleSets/write
  note: Increasing capacity (or setting an autoscale profile) creates new instances that boot the model
    and assume the MI - detonates poisoned config.
  narrative: '{principal.name} can raise capacity of {vmss.name} (virtualMachineScaleSets/write), forcing
    new instances to boot the model as its MI.'