output "storage_account" { description = "Where evidence goes." value = azurerm_storage_account.evidence.name } output "snapshot_resource_group" { description = "Where node disk snapshots go." value = azurerm_resource_group.evidence.name } output "capture" { description = "Set these, then run capture.sh from the Standard (t1) folder." value = <<-EOT export CLUSTER=${var.cluster_name} CLUSTER_RG=${var.cluster_resource_group} SNAPSHOT_RG=${azurerm_resource_group.evidence.name} EVIDENCE_ACCOUNT=${azurerm_storage_account.evidence.name} ./capture.sh EOT } output "verify" { description = "Checks, on a test pod you do not mind isolating." value = <<-EOT Run the capture command above against a test pod, then: az snapshot list -g ${azurerm_resource_group.evidence.name} --query "[?tags.incident==''].name" -o tsv kubectl get pod -n --show-labels # quarantine=true As someone who can delete blobs, such as Storage Blob Data Owner, the immutability policy must still refuse this: az storage blob delete --auth-mode login --account-name ${azurerm_storage_account.evidence.name} -c evidence -n ////pod.json Responders cannot list or read evidence. Someone with Storage Blob Data Reader on the account downloads the folder, then runs evidence-verify on it. EOT }