Tool integration

CycloneDX .NET integration guide

Official CycloneDX .NET global tool for generating SBOM from NuGet projects

Get a Free API Key

Integrate CycloneDX .NET with Vulnesis. Generate a CycloneDX SBOM from your .NET/C# NuGet project and upload to Vulnesis.

CLI toolCycloneDX

Install & scan

$ dotnet tool install --global CycloneDX
$ dotnet-CycloneDX . -o . -json

Run CycloneDX .NET in CI

Scan on every push and upload the report as a workflow artifact:

- name: Setup .NET
  uses: actions/setup-dotnet@v4
  with:
    dotnet-version: '8.0.x'

- name: Restore dependencies
  run: dotnet restore

- name: Install CycloneDX .NET tool
  run: dotnet tool install --global CycloneDX

- name: Generate SBOM
  run: dotnet-CycloneDX . -o . -json

- name: Upload report
  uses: actions/upload-artifact@v6
  with:
    name: cyclonedx-dotnet
    path: bom.json
    if-no-files-found: warn

Then one publish job hands every artifact in the run to Vulnesis, recorded under CycloneDX .NET'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" --json

After the run, vulnetix gha status reports what was actually recorded.

How Vulnesis compares: better together

Vulnesis does not replace CycloneDX .NET. Keep running it. Vulnesis sits on top of CycloneDX .NET (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.

CycloneDX .NET is strongest at its core category and also carries features in License Compliance, SCA, just as Vulnesis spans categories.

CapabilityVulnesisCycloneDX .NET
Security coverage
SAST (static code analysis)✓ Built-in rules + Semgrep augmentation✗
SCA / dependencies✓ 40+ ecosystems, transitive graph~ Enumerates transitive NuGet dependencies with hashes but does no vulnerability scanning itself
DAST (dynamic testing)~ Ingests DAST results; no native dynamic engine✗
Container & image✓ Image CVEs, base image, Dockerfile✗
IaC / misconfiguration✓ Terraform, k8s, CloudFormation✗
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~ Optional GitHub license resolution to SPDX IDs (auth required; master-branch refs only)
SBOM generation✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable✓ Core: aggregate CycloneDX BOM of all NuGet project/solution dependencies, spec 1.0-1.7, JSON/XML
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 CycloneDX .NET does well

Where Vulnesis adds to it: Vulnesis ingests cyclonedx-dotnet output (or generates its own CycloneDX 1.7 + SPDX 2.3 for .NET) and adds the layer this tool omits: cross-scanner dedup, exploit-intel prioritisation (EPSS/KEV/ESS/CWSS/LEV), reachability, immutable versioned VEX + audit, EOL and SSVC policy, and Safe Harbour autofix PRs. Better together: the official tool provides trusted NuGet inventory, Vulnesis does the risk triage on top - it does not replace the generator.

No migration, no rip-and-replace. CycloneDX .NET 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 CycloneDX .NET results in Vulnesis

Upload CycloneDX .NET CycloneDX 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.

CycloneDX .NET documentation ↗  ·  Source repository ↗

Wire CycloneDX .NET into your CI/CD pipeline →