Integrate Microsoft Template Analyzer with Vulnesis. Scan Azure ARM templates and Bicep files for security misconfigurations and export SARIF findings for upload to Vulnesis.
Install & scan
$ dotnet tool install --global Microsoft.Azure.TemplateAnalyzer # Verify template-analyzer --version $ template-analyzer analyze-template template.json --output-file-format sarif --output-file analyzer-results.sarif
Run Template Analyzer in CI
Scan on every push and upload the report as a workflow artifact:
- name: Install Template Analyzer
run: dotnet tool install --global Microsoft.Azure.TemplateAnalyzer
- name: Analyze ARM templates
run: template-analyzer analyze-template template.json --output-file-format sarif --output-file results.sarif
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: templateanalyzer
path: results.sarif
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under Template Analyzer's own name and version. Written once per workflow, however many scanners you run:
publish:
name: Publish to Vulnesis
runs-on: ubuntu-latest
needs: [scan] # every scanner job, or its report is never published
if: always() # or one failing scanner suppresses all the others
permissions:
contents: read
actions: read # required to list the run's artifacts
env:
VULNETIX_ORG_ID: ${{ secrets.VULNETIX_ORG_ID }}
VULNETIX_API_KEY: ${{ secrets.VULNETIX_API_KEY }}
steps:
- uses: actions/checkout@v5
- name: Install Vulnesis CLI
run: |
curl -fsSL https://cli.vulnes.is/install.sh | sh -s -- --install-dir "$HOME/.local/bin"
echo "$HOME/.local/bin" >> "$GITHUB_PATH"
- name: Publish scanner reports
env:
GITHUB_TOKEN: ${{ github.token }}
run: vulnetix gha upload --org-id "$VULNETIX_ORG_ID" --jsonAfter the run, vulnetix gha status reports what was actually recorded.
How Vulnesis compares: better together
Vulnesis does not replace Template Analyzer. Keep running it. Vulnesis sits on top of Template Analyzer (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
| Capability | Vulnesis | Template Analyzer |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✗ |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✗ |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✓ Core: security analysis of Azure ARM and Bicep templates (encryption, HTTPS-only, network/access misconfig) with line numbers + remediation |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✗ |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ✗ |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✗ |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25 registries) | ✗ |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ✗ |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✗ |
| The Vulnesis orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ✗ |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnesis LEV | ✗ |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✗ |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ✗ |
| Safe Harbour autofix | ✓ Resolves + applies the nearest safe version | ✗ |
| End-of-life policy | ✓ Flags/blocks past-EOL runtimes & packages | ✗ |
| SSVC / risk-based policy | ✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets | ✗ |
✓ full · ~ partial · ✗ not covered
What Template Analyzer does well
- Native Azure IaC coverage for both ARM templates (.json) and Bicep files, from Microsoft itself
- SARIF output with correct per-rule severity in the level property, for clean CI and security-tooling integration
- Customizable/extensible JSON-authored rules (Rules/BuiltInRules.json) so orgs can enforce only relevant checks
- Free and open-source, purpose-built for Azure security best-practice and misconfiguration detection
Where Vulnesis adds to it: Vulnesis consumes Template Analyzer's SARIF output and merges its Azure ARM/Bicep misconfiguration findings into a single deduplicated, prioritised queue with exploit-intel, SSVC, versioned VEX and autofix across all scanner types. Better together: Template Analyzer stays the Azure IaC checker; Vulnesis orchestrates and prioritises its results alongside every other scanner.
No migration, no rip-and-replace. Template Analyzer keeps doing what it does best; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.
Centralise Template Analyzer results in Vulnesis
Upload Template Analyzer SARIF, JSON output to the Vulnesis platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.