Azure Blob Storage command protection

Reviews Azure CLI storage commands including upload, list, copy, and deletion.

command.storage.azure-blob · v1.0.0 · Data and resilience

By HOL Guard TeamBuilt-in coverageCommand coverage
Try this coverage Install GuardView exact source Azure Blob Storage command protection documentation About project-maintained coverage
0
Protection rules
6
Permission checks
6
Mapped commands
6

Overview

What this coverage does

Reviews Azure CLI storage commands including upload, list, copy, and deletion.

Key facts

Catalog ID
command.storage.azure-blob
Version
v1.0.0
Kind
Command coverage
Category
Data and resilience
Protection rules
6
Permission checks
6
Mapped commands
6
Maintainer
HOL Guard Team(project-maintained)
Source commit
ff3d4eb
Protection model
Built-in coverage
Built-in coverage

This coverage is built into the native Guard runtime.

Stated limits

  • Coverage is limited to the reviewed operations and the surrounding Guard policy.
  • A maintainer profile is not a security certification or an official upstream endorsement.

Use cases

Reviewed workflows that reference this coverage

Browse all use cases

Command mapping

Every command this extension recognizes, with the catalog default floor Guard applies before workspace policy. Search the table, then open an operation for safe variants and the permission ID.

6 operations · 5 reviewed by default · 1 allowed by default These are catalog defaults, not your workspace policy.

6 operations5 reviewed1 allowed
Default floor

Showing 6 of 6 operations

  • Reviewed Guard intercepts the command for review before it runs.Critical
    • az storage blob delete
    Azure Blob Storage deletion
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies azure blob storage deletion operations.
    Documented safe variants
    Azure Blob Storage deletion helpAzure Blob Storage deletion dry runskip this operation when they are the documented preview or help form.
    Permission ID
    command.storage.azure-blob.permission.deletion
  • Reviewed Guard intercepts the command for review before it runs.High
    • az storage container create
    Azure container create
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies azure container create operations.
    Documented safe variants
    Azure container create helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.storage.azure-blob.permission.container-create
  • Reviewed Guard intercepts the command for review before it runs.High
    • az storage blob copy start
    Azure blob copy
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies azure blob copy operations.
    Documented safe variants
    Azure blob copy helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.storage.azure-blob.permission.copy
  • Reviewed Guard intercepts the command for review before it runs.High
    • az storage blob download
    Azure blob download
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies azure blob download operations.
    Documented safe variants
    Azure blob download helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.storage.azure-blob.permission.download
  • Reviewed Guard intercepts the command for review before it runs.High
    • az storage blob upload
    Azure blob upload
    Default floor
    Reviewed by default. Guard intercepts the command for review before it runs.
    Detector mode
    review
    What it matches
    Identifies azure blob upload operations.
    Documented safe variants
    Azure blob upload helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.storage.azure-blob.permission.upload
  • Allowed Guard recognizes the command and does not intercept it unless workspace policy tightens it.Low
    • az storage blob list
    Azure blob list
    Default floor
    Allowed by default. Guard recognizes the command and does not intercept it unless workspace policy tightens it.
    Detector mode
    disabled
    What it matches
    Identifies azure blob list operations.
    Documented safe variants
    Azure blob list helpskip this operation when they are the documented preview or help form.
    Permission ID
    command.storage.azure-blob.permission.list

Tool state mapping

No per-tool overrides are declared. Command defaults above resolve through the workspace Guard policy unless a later policy layer changes them.

Runtime identity

Catalog ID
command.storage.azure-blob
Guard enforcement ID
command.storage.azure-blob
Source path
contributions/extensions/command.storage.azure-blob.json
Contribution digest
sha256…7cc3be

Action classes

Azure storage destructive command

Technical profile

No independent profile published

This extension has no current independent technical profile. Catalog facts and any legacy launch remain separate and are not presented as profile evidence.

FAQ

Frequently asked questions

Reviews Azure CLI storage commands including upload, list, copy, and deletion. The listing declares 6 rules and 6 permission checks. 6 operations · 5 reviewed by default · 1 allowed by default. Coverage is limited to these reviewed operations and the surrounding Guard policy.

Built-in coverage: This coverage is built into the native Guard runtime. Enabling state is always controlled through Guard policy, never from this directory.

This listing is maintained by the HOL Guard project itself as part of the native runtime catalog.

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.

6 operations · 5 reviewed by default · 1 allowed by default. Examples: az storage blob delete (reviewed by default); az storage container create (reviewed by default); az storage blob copy start (reviewed by default); az storage blob download (reviewed by default); az storage blob upload (reviewed by default); az storage blob list (allowed by default). These are catalog defaults, not your workspace policy.

This coverage is built into the native Guard runtime. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the command coverage for command.storage.azure-blob in Guard's policy surface.

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 6 rules and 6 permission checks.

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Yes — community coverage is accepted through public pull requests with recorded provenance. Project-maintained listings like this one are extended by the HOL Guard team; propose new operations through the hol-guard repository.

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.