Introspectus
Start Free Trial

Cookie Policy OLD

Cookie Policy

This Website (referred to in these “terms of use” as the website) is owned and operated by Introspectus Pty Ltd, who is referred to in this Cookie Policy as “we”, “us”, “our” and similar grammatical forms.

Our Cookie Policy explains what cookies are, how we use cookies, how third-party partners may use cookies on our Websites and your choices regarding cookies.

General information about visits to our Websites is collected by our computer servers, with small files “cookies” that our Websites transfers to your computer’s hard drive through your Web browser (if you allow the delivery of “cookies”). The “cookies” are used to follow the pattern of movements of users by letting us know which pages on our Websites are visited, in what order and how often and the previous website visited and also to process the items you select if you are making purchases from our Websites. The anonymous non-personal information that we collect and analyse is not personal information as described in the Privacy Act.

Why do we use “cookies” and other web use tracking technologies?
  1. When you access our Website, small files containing a unique identification (ID) number may be downloaded by your web browser and stored in the cache of your computer. The purpose of sending these files with a unique ID number is so that our Website can recognise your computer when you next visit our Website. The “cookies” that are shared with your computer can’t be used to discover any personal information such as your name, address or email address they merely identify your computer to our Websites when you visit us.
  2. We can also log the internet protocol address (IP address) of visitors to our Website so that we can work out the countries in which the computers are located.
  3. We collect information using “cookies” and other tracking technologies for the following reasons:
    • to help us monitor the performance of our Website so that we can improve the operation of the Website and the services we offer;
    • to provide personalised services to each user of our Website to make their navigation through our Website easier and more rewarding to the user;
    • to sell advertising on the Website in order to meet some of the costs of operating the Website and improve the content on the Website; and
    • when we have permission from the user, to market the services we provide by sending emails that are personalised to what we understand are the interests of the user.
  4. Even if you have given us permission to send you emails, you can, at any time, decide not to receive further emails and will be able to “unsubscribe” from that service.
  5. In addition to our own cookies, we may also use various third-parties cookies to report usage statistics of the Website, deliver advertisements on and through the Website, and so on.
What are your choices regarding cookies?

If you are unhappy about having a cookie sent to you, you can set your browser to refuse cookies or choose to have your computer warn you each time a cookie is being sent. However, if you turn your cookies off, some of our services may not function properly.

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.