Software inventory
Build a current view of installed software and versions as platform collection modules complete physical QA.
What the administrator needs to solve.
Without current software inventory, IT cannot reliably answer where an application is installed, which version is running or which endpoints need remediation.
How ZENQIX handles it.
ZENQIX is extending the endpoint record with normalized software observations that can support deployment, compliance and future vulnerability correlation.
Requested action and verified outcome stay separate.
What is currently in scope.
Installed software list
Version observation
Inventory refresh after action
Search/filter architecture
Future software compliance correlation
Availability by operating system.
Provider-backed physical QA pending.
Provider-backed physical QA pending.
Provider-backed physical QA pending.
Inspect the state the UI needs to expose.
This panel uses synthetic data. A genuine ZENQIX Endpoint screen can replace it only after sanitization and publication approval.
Security
- • No arbitrary installer execution from inventory collection
- • Bounded collection output
- • Tenant-scoped inventory access
Evidence
- • Observed application name
- • Observed version
- • Collection time
- • Endpoint association
Technical detail
- • Software inventory is a prerequisite for reliable deployment verification
- • Vulnerability correlation is a separate future layer
Technical questions for this capability.
Is software inventory generally available?
Not yet. It is presented as Preview until platform-specific physical acceptance is complete.
Does ZENQIX currently claim its own vulnerability intelligence database?
No. Future vulnerability correlation should use trusted external vulnerability intelligence rather than inventing a proprietary CVE research system.
Evaluate software inventory in your environment.
Use the capability matrix and the written acceptance checklist to confirm whether the current status matches your pilot needs.