Device Posture Reports

The Insights → Device Posture Reports screen helps you monitor the effectiveness of your device posture enforcement policies. This feature provides visibility into posture check results across users, devices, and policies—enabling you to detect recurring compliance issues, identify frequently failing attributes, and evaluate endpoint health over time.

Reports on this screen are automatically generated as long as your posture check policies are active and devices are sending telemetry through the Timus Connect Agent or integrated EPP solutions.

📍 To access this screen, go to Insights → Device Posture Reports

The screen is divided into three main sections:

  • Overview – A summary of pass/fail trends, top failing devices, and the most frequently violated attributes
  • Devices – Detailed run results for a selected endpoint, including pass/fail outcomes and attribute logs
  • Posture Checks – Aggregated results grouped by posture check policy, with drill-down options to investigate devices or attributes

Need help setting up your posture check policies or integrating external data sources?

Go to Device Posture Checks Guide

Go to Third Partner Integrations Guide


📊 Analyze Overall Posture Trends

The Overview tab provides a high-level summary of posture performance across your environment.

  • Most Failed Devices – Devices with the highest number of failed posture checks
  • Most Failed Attributes – Attributes that failed most frequently (e.g., OS mismatch, agent not installed)
  • Total Pass/Fail Rate – A visual chart summarizing overall compliance status
  • Pass Trend – A time-based graph showing changes in pass rate over the selected period
  • Check Summary Table, including:
    • Title of each posture check
    • Number of runs
    • Total checks performed
    • Average number of devices per run
    • Overall pass/fail rates

Use this view to identify widespread issues—such as common misconfigurations or telemetry gaps—before they impact your posture enforcement strategy.


Review Results for a Specific Device

The Devices tab allows you to drill into posture check results for a specific endpoint.

  1. Select a device using the dropdown at the top right.
  2. Choose a date range to filter the results.
  3. Once applied, you’ll see:
    • Total Runs: Number of posture checks executed for this device
    • Pass Rate and Fail Rate
    • A results table including:
      • Date and time of each run
      • Result (Passed / Failed)
      • Number of passed and failed attributes
      • Details link to explore further

Run Details

Click Details to view the full Device Posture Check Report for that run. It includes:

  • Data Source (e.g., Timus Connect, Bitdefender)
  • Attribute checked (e.g., Firewall, OS)
  • Condition and expected Pass Value
  • Actual Value received from the device
  • Result (Passed / Failed)

This detailed view helps you pinpoint the exact reason for failure—such as outdated antivirus, unsupported OS, or missing telemetry.


Evaluate Posture Check Policies

The Posture Checks tab displays results grouped by posture check policy, giving you a policy-centric view of enforcement success.

  1. Select a posture check from the dropdown.
  2. Choose a date range to filter the dataset.
  3. View policy-level metrics such as:
    • Total Runs
    • Attributes Checked
    • Pass Rate / Fail Rate
    • Pass Trend chart for visual monitoring

You’ll also see a run-level table with:

  • Date and time
  • Number of devices evaluated
  • Devices that passed / failed
  • A ••• menu with two options:
    • View Devices – Opens a list of affected devices and their results
    • View Attributes – Shows each attribute checked during the run

View Devices Associated with a Posture Check

This screen shows:

  • Device name
  • Failed attribute(s)
  • Pass / Fail per device

View Attribute-Level Results

This screen shows:

  • Data Source
  • Attribute name
  • Device Name the check was applied to
  • Condition, Pass Value, Actual Value
  • Result (Passed / Failed)

These breakdowns are useful for detecting systematic errors in posture configurations or integration gaps in endpoint telemetry.

Updated

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.