{"version":"2.1.248","anchor":"command-safety-lists-for-powershell-and-container-registries","canonical_anchor":"command-safety-lists-for-powershell-and-container-registries","heading":"Command-safety lists for PowerShell and container registries","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/command-safety-lists-for-powershell-and-container-registries","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Command-safety lists for PowerShell and container registries\n\nNew allowlists let read-only PowerShell and registry commands run without prompting; helm and prod paths flagged.\n\n**What**\n\nNew allowlists feed the check that decides whether a command is safe to run without prompting: read-only PowerShell cmdlets, PowerShell switch parameters, PowerShell executable paths probed on Windows, and known container and package registry hosts. A separate pattern flags paths mentioning helm, iam, prod, k8s or rbac as sensitive.\n\n**Evidence**\n\n`registry-1\\.docker\\.io`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}