MBITS brings together deep technical expertise, practical industry experience and a shared commitment to disciplined delivery.
Our team combines engineering rigour with a strong understanding of governance, risk and operational complexity. This enables us to work confidently within enterprise and government environments where stability, accountability and security are critical.
We focus on delivering infrastructure and platform outcomes that are clear, supportable and defensible not just implemented, but properly engineered and sustained.
Our culture reflects long-term thinking, structured execution and practical decision-making grounded in real operational experience.
DIRECTOR, VARLEY GROUP
Jeff provides strategic oversight and governance experience that strengthens MBITS’ long-term capability.
Jeff joined Varley in 1993 and became Managing Director in 1995. Under his leadership, the Group has evolved from a family-owned engineering business into a globally recognised enterprise operating across multiple sectors and international markets.
His leadership is defined by disciplined growth, commercial clarity and long-term strategic planning. Varley’s 140-year engineering heritage reinforces a culture of accountability, resilience and structured delivery principles that align closely with MBITS’ approach to infrastructure and technology services.
Jeff is also a strong advocate for cyber security and operational resilience, recognising the importance of secure, well-governed systems in increasingly complex digital environments.
FOUNDER AND DIRECTOR, MBITS
MBITS was founded by Eugene Nolan to address the growing complexity and operational risk within modern IT environments.
With more than 30 years of experience in the technology sector, Eugene has held senior roles across large corporate organisations, including Intel Corporation, as well as managed service providers supporting enterprise and government clients.
This breadth of experience informs MBITS’ practical, execution-focused approach. Eugene combines deep technical capability with a strong understanding of governance, risk management and the operational realities faced by organisations operating at scale.
Since relocating to Australia in 2001, Eugene has led infrastructure programs, platform transitions and secure environment deployments across diverse industries. His leadership remains hands-on and outcome-focused, ensuring that strategy translates into disciplined implementation.
MBITS operates with the support and strategic backing of the Varley Group, providing long-term stability, governance strength and access to experienced operational leadership.
Together, we share a commitment to:
Our people are defined not by titles, but by experience and by a consistent focus on building infrastructure that stands up to operational and governance scrutiny.
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 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.
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.
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.
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.
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.