Start Free Trial

Frequently Asked

Questions

Below you'll find answers to some common questions about Introspectus Software Assurance

Software Assurance FAQs

Software Assurance

FAQs

The Introspectus Software Assurance module provides organisations with clear visibility into how software is installed, used, and licensed across their IT environment.

It helps organisations understand actual software usage so they can optimise licensing, reduce unnecessary costs, and maintain compliance with vendor agreements.

Software Asset Management is really about getting control of what your business actually owns, uses, and pays for when it comes to software.

It saves you real money. Most organisations are paying for software licences they don’t use, or buying new ones when spare ones are sitting idle. Software Assurance programs typically uncovers 20 to 30 percent in savings on software spend. That’s money straight back to the bottom line.

It keeps you out of strife with vendors. Microsoft, Oracle, IBM and similar organisations run audits regularly, and the fines for being under-licensed can run into the millions. SAM means you know exactly where you stand before the auditors come knocking, not after.

It tightens up your cyber security. You can’t protect what you don’t know you’ve got. Unmanaged software, and out-of-date applications are common methods used by hackers to compromise organisations. SAM gives you a detailed register of what’s running across the business so IT can patch, update, or disable software before it become a problem.

It helps you make smarter decisions. When you can see what’s actually being used versus what’s not, you can negotiate better deals at renewal time, retire software nobody touches.

It’s becoming a compliance must-have. Frameworks like ISO 27001, the Essential Eight, and various privacy obligations all expect you to know what software you’re running. SAM meets these requirements.

The bottom line for the executive table: SAM isn’t an IT housekeeping job. It’s a financial control, a risk management tool, and a security measure rolled into one. Organisations that ignore it tend to overspend, get caught short in audits, and carry hidden cyber risk they can’t even see.

Software Assurance helps organisations understand how software is used across their environment.

Key insights include:

  • Which applications are installed across devices
  • How frequently applications are used
  • Where licences may be unused or duplicated
  • Opportunities to reallocate or reduce licences
These insights help organisations optimise software investments and improve asset management.

By analysing real usage data, Software Assurance identifies applications that are rarely used or no longer required.

This allows organisations to reassign licences, remove unused software, or adjust licensing agreements, helping to reduce unnecessary spending while ensuring employees still have access to the tools they need.

Yes. The module provides clear reporting on software installation and usage, helping organisations demonstrate compliance with vendor licensing requirements.

This visibility can help organisations prepare for vendor audits and reduce the risk of unexpected compliance issues.

The module is valuable for several teams across an organisation, including:

  • IT teams managing software assets and applications
  • Procurement teams responsible for software purchasing
  • Finance teams monitoring technology spending
  • Governance and compliance teams ensuring licence compliance

By providing reliable insights into software usage, Software Assurance supports better decision-making across the organisation.

Yes. Software Assurance can operate independently or alongside the other Introspectus modules.

When used together with Assessor and Workforce, organisations gain a broader view of their environment from cyber security posture to workforce activity and software usage enabling more informed technology and operational decisions.

Software Assurance is designed to be straightforward to deploy and operate. Once installed, it automatically collects software usage data across endpoints and generates clear reports.

This allows organisations to quickly gain visibility into their software environment and begin optimising licence management.

How Introspectus Helps

Each agent compares the current patch list against what is actually installed on its device. Any gap between what has been released and what is deployed is immediately surfaced. Critically, Introspectus pays particular attention to the timing of patch deployment not just whether a patch is present, but when it was applied.

This temporal dimension is central to Essential Eight compliance, where the difference between a patch applied on day two versus day thirty can mean the difference between maturity levels, and between an environment that was protected and one that was exposed.

This combination of daily patch intelligence, severity-based filtering, agent-level validation, and deployment timing analysis gives organisations a real-time, evidence-based view of their operating system patch posture mapped directly to the ISM controls applicable to the Essential Eight patch operating systems strategy.

The Challenge with Patch Operating Systems

The visibility gap here is particularly consequential. A patch may be approved and scheduled, yet never successfully applied due to a failed deployment, a device that was offline during the maintenance window, a reboot that was deferred, or a system that exists outside managed channels entirely.

Organisations that rely solely on deployment tooling to confirm patch status are measuring intent, not reality. The ACSC is explicit on this point: organisations need to confirm patches have been applied successfully, not merely that they were dispatched.

Patch Operating Systems Overview

Within the Essential Eight framework, patching operating systems is a core and non-negotiable control. The ACSC sets clear expectations: patches for internet-facing infrastructure must be applied within 48 hours when identified as critical or where working exploits exist, and within two weeks for standard releases.

Patches for workstations, servers, and network devices must be applied within one month, with tighter timeframes applying in high-threat environments. Critically, the ACSC also mandates that vulnerability scanning occurs at least daily for internet-facing systems and at least fortnightly for workstations and non-internet-facing infrastructure not to replace patching, but to confirm it has actually occurred.

How Introspectus Works

From this inventory, Introspectus performs targeted web intelligence gathering. For each application identified, the platform locates the top five authoritative sources of patch and release information vendor security advisories, release notes, and vulnerability databases and retrieves that content into a central repository.

Aletheia, Introspectus’s AI analysis agent, then reads and analyses this content to extract the intelligence that matters for application patching: the latest available version, whether a release addresses a security vulnerability, the severity of that vulnerability, and all information relevant to the Essential Eight application patching requirements. This structured intelligence is mapped directly to the applicable ISM controls, producing defensible, audit-ready evidence of an organisation’s application patch compliance posture.

The Challenge with Patch Applications

A critical and frequently overlooked problem is the visibility gap. Organisations may believe their applications are current when, in reality, patches have silently failed, devices have missed deployment windows, or software has been installed outside of managed channels entirely.

Without continuous inspection at the endpoint level, these gaps go undetected until an audit or, worse, a breach.

Patch Applications Overview

Within the Essential Eight standard, patching applications is a dedicated and non-negotiable control. The ACSC specifies clear timeframes: critical vulnerabilities in internet-facing services must be addressed within 48 hours, commonly used applications such as office productivity suites, web browsers, email clients and PDF software must be patched within two weeks of release, and all other applications within one month.

For organisations in high-threat environments, the bar is higher still. Meeting these requirements consistently across hundreds of distinct applications deployed across thousands of endpoints is not achievable through manual effort alone.