Introspectus
Start Free Trial

HR Reporting OLD

HR Reporting

What is HR Reporting and how does it work?

Current Human Resources (HR) reporting tools require company staff to correctly record the start and end times of each day. This is often manually recorded at the end of each week or fortnight and may be difficult to compile retroactively.

Timekeeping software, if used, may need to be dedicated to workstations or specifically invoked to record a timestamp.

Time spent working away from the office, after hours or on weekends, is not recorded or may be overstated.

Cyber Securuty Professionals Working
Woman using a computer

Why is HR Auditing important?

Inaccurate time sheets result in incorrect payments of salaries, overtime, and entitlements.

Requiring software to monitor workstation logons and logoff is also problematic as staff members do not have to log on and log off a workstation at the start and the end of the day.

Time spent working on the computer away from the office and after hours may be overstated.

Introspectus Key Features

What's the solution?

Introspectus addresses the challenges facing HR Management. We record the start time and end time of each application window. This includes the associated application details. This information is collected to produce a summary of a staff member’s day. It includes when they started and finished using their workstation.

The report identifies actual time spent per user on the computer in 15-minute increments – differentiating between corporate and non-corporate applications. It highlights periods of activity over a 24-hour period and recognises a staff member’s usage of an application through local machines and remote entry. As a decision maker within your organisation you can:

  • Produce a report of all user computer activity which can be compared to your HR records to identify anomalies within your HR logs.
  • Identify which staff are working long hours without appropriate breaks or recognition.
  • Identify actual hours worked from home.
Assessor HR Reporting

Record Work Hours

Because computers are such an integral part of employment, most users log on at the start of each day and may do a final check of e-mail at the end of each day before shutting down for the evening. Introspectus timestamps all this activity, providing work hour information that can be used in conjunction with other time-keeping systems.

Extended Hours & Work From Home

While current HR reporting tools seldom record work performed out of hours and on weekends, Introspectus records all ‘Active Window’ activity when staff are working from home on work provided Laptops or connecting to work via Terminal Services / Citrix.

Monitor Organisational Change

Introspectus assists organisational change with daily information on the take up of technologies that your organisation is seeking to embrace. By monitoring how many new applications are used and the extent to which terminated Applications are relinquished, the success of organisational change can accurately be determined.

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.