Banned and sanctioned software
Identify covered devices where software matching a relevant internal or jurisdictional watchlist was actually launched.
New Yaware module · In development
Software risk reports
Go beyond installed-software inventory: understand what is actually launched on covered devices, where it is used, and for how long.
Planned reports
Unsupported software
Prioritize applications and versions that may no longer receive vendor security or maintenance updates.
Upcoming support deadlines
Connect vendor lifecycle dates with active devices and teams to plan migration waves.
License review signals
Find usage patterns that may need a closer review of entitlements, editions, or contractual terms.
Migration readiness
Estimate the active user base, usage hours, and dependent teams before replacing a legacy system.
AI tools used by the team
See which AI services are launched on covered devices and where adoption is occurring.
AI data-risk signals
Identify AI-service usage that may need a policy or data-handling review without reading prompt content.
AI adoption
Understand where AI has become part of daily work and how usage changes over time.
Cost of risky software
Build a better replacement or remediation budget from active usage rather than installation counts alone.
Customer attestation
Prepare a bounded, verifiable overview of software coverage and status for a customer or auditor.
Shadow IT
Find applications and services used outside the organization’s approved technology catalog.
What these reports can—and cannot—show
Yaware plans to use metadata from compatible, active agents on covered devices: software names, versions, publishers, launch events, usage duration, and known coverage status. A report does not prove legal non-compliance, licensing status, or the content a person entered into a service. Findings should be reviewed against official sources, contracts, internal policy, and the report’s stated coverage.
