More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Azure ARM and Bicep Check

    1

    Your agent runs a scanner on your .bicep files, .bicepparam files, ARM JSON templates (including az bicep build output and nested templates) and *.parameters.json files.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Azure ARM and Bicep Check

    Azure ARM and Bicep Check

    Example session with this skill installed

    Check this project with azure-arm-bicep-check.

    • Read your context and instructions
    • Compiled the azure arm

    $ python3 scripts/check_azure.py examples/risky
    BLOCK infra/main.bicep:9 A03 SECRET_IN_TEMPLATE
    param sqlAdminPassword string = <redacted>
    Why: A password, key or connection string is written in the template or a parameter file: a @secure() parameter with a default value, a parameter, variable, property or app setting with a secret name and a literal value, or a connection string with AccountKey=, SharedAccessKey= or Password=. Everyone with the repository can use it, and the default of a secure parameter can also be read from the template and the deployment history.
    Safer: Remove the value and pass it at deploy time from Key Vault (getSecret() in a .bicepparam file or a Key Vault reference in a parameter file), use Key Vault references in app settings and managed identities instead of keys, and change the secret that was committed.

    BLOCK infra/main.bicep:13 A03 SECRET_IN_TEMPLATE
    BLOCK infra/main.bicep:21 A01 PUBLIC_BLOB_ACCESS
    BLOCK infra/main.bicep:32 A01 PUBLIC_BLOB_ACCESS
    BLOCK infra/main.bicep:50 A05 DATABASE_OPEN_TO_INTERNET
    BLOCK infra/main.bicep:113 A03 SECRET_IN_TEMPLATE
    BLOCK infra/main.bicep:132 A04 SECRET_IN_OUTPUT
    BLOCK infra/main.bicepparam:4 A03 SECRET_IN_TEMPLATE
    BLOCK infra/modules/jumpbox.bicep:17 A02 ADMIN_PORT_OPEN_TO_INTERNET
    REVIEW infra/legacy/redis.json:22 A12 HTTPS_ONLY_OFF
    REVIEW infra/legacy/redis.json:23 A11 TLS_BELOW_1_2
    REVIEW infra/main.bicep:11 A17 SECRET_PARAMETER_NOT_SECURE
    REVIEW infra/main.bicep:22 A11 TLS_BELOW_1_2
    REVIEW infra/main.bicep:58 A13 FIREWALL_ALLOWS_ALL_AZURE
    REVIEW infra/main.bicep:72 A15 PUBLIC_NETWORK_ACCESS
    REVIEW infra/main.bicep:76 A14 KEY_VAULT_PURGE_PROTECTION_OFF
    REVIEW infra/main.bicep:101 A12 HTTPS_ONLY_OFF
    REVIEW infra/main.bicep:104 A16 FTP_ALLOWED
    REVIEW infra/modules/jumpbox.bicep:30 A18 PORT_OPEN_TO_INTERNET

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 4 files, 4 with Azure template content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    allowBlobPublicAccess: true on one storage account, or one network security group rule with sourceAddressPrefix: '*' on port 22, is enough to leak every file or hand a VM to the bots that scan Azure address ranges. This skill finds those and eleven other Azure template mistakes before you deploy, and tells you how to fix each one.

    Your agent runs a scanner on your .bicep files, .bicepparam files, ARM JSON templates (including az bicep build output and nested templates) and *.parameters.json files. It parses Bicep itself (comments, ${...} strings, decorators, if conditions, for loops, existing and nested child resources), finds each resource by its type, follows parameters and variables to their literal values, and reports each finding at the property's line. It never calls Azure, runs bicep or deploys anything. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • A01: storage accounts and blob containers open to anonymous access
    • A02: SSH, RDP, database or all ports open to *, Internet or 0.0.0.0/0 in network security groups
    • A03: passwords and keys in @secure() defaults, properties, app settings, parameter files and AccountKey= connection strings
    • A04: listKeys() results and secure parameters returned as outputs
    • A05: SQL, PostgreSQL and MySQL firewall rules open to every address

    REVIEW

    • A11: TLS 1.0 and 1.1 allowed
    • A12: HTTPS-only off, the non-TLS Redis port and require_secure_transport off
    • A13: firewall rules open to all of Azure (Allow Azure services)
    • A14: Key Vaults without purge protection
    • A15: publicNetworkAccess Enabled on data services
    • A16: plain FTP allowed on App Service and Function apps
    • A17: secret parameters not marked @secure()
    • A18: other ports open to the internet

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example project, and the real report the scanner produces on the risky one

    Limits It reads your files as written. Values passed in at deploy time, registry modules (br:) and template specs, conditions, Azure Policy and subscription settings, and properties built with functions such as union() are not evaluated. Data services that leave public network access at the Azure default are not reported. NOT FLAGGED is not a guarantee.

    Static check of Bicep and ARM template text. Deploy-time parameter values, registry modules, Azure Policy, settings changed in the portal and the live state of resources are not checked. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert passwords and keys (NOTREAL, not-a-real-..., EXAMPLE) for the scanner to find. It is never deployed.

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads .bicep, .bicepparam and ARM JSON files as text. It never runs az or bicep and never calls Azure.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example set of Bicep and ARM templates, and the real report the scanner prints on the risky example.

    New in DevOps & Cloud