Reports That Help Increase IT Operations

Tripwire Enterprise includes a comprehensive library of tailorable reports and online dashboards providing valuable performance metrics and trends that help you manage IT operations. Tripwire's focused reports provide configuration change details improving troubleshooting and remediation, while trend reports provide management the information they need to improve processes and enforce C/CM policies–reducing the frequency of outages and improving MTTR.

Use the tabs below to view sample reports most helpful for IT availability. You may also download the Tripwire Enterprise Report Catalog, with samples of all available reports.

Detailed Waivers
For each specified node and test, this report provides a complete listing of all applicable waivers and related details such as waiver start and end dates, reason for the waiver, and who is responsible for remediation.

Usage: Security and IT operations can use this report to manage waivers and remediation more effectively and with less effort.

Detailed Test Inventory
For each specified test, this report provides a test definition that includes details such as test description, type, severity and weighting.

Usage: This report makes it easy for management to generate and share formal test documentation, as well as view this information offline.

Test Results by Node
For each specified node, this report shows both a summary and a detailed breakdown of the latest test results. The report can also be configured to only display failed tests and associated remediation steps.

Usage: This report functions as a prescriptive "punch list" that system administrators can use to expedite necessary remediation tasks.

Report Linking
Report Link Criteria provides the ability to link certain reports allowing for the ability to "drill-down" or link from a report being viewed to a subsequent report with an increased level of detail. For example, one may want to link from a Change Process Compliance report, to a Changed Elements report for a list of unapproved changes, then to a Detailed Changes report on a particular element.

Frequently Changed Elements
List details about the most frequently changed elements for the specified set of nodes.

Usage: Management report very useful for identifying those elements that change on a regular basis as part of normal business processes. The resulting data can be used to manage and tune Tripwire Enterprise rules and actions for more efficient integrity checks. Typically run once a week until rules are tuned for specific environments, then once a month.

Last Node Checked Status
This report displays last check status information for the specified nodes over a period of time defined by the user. It optionally includes information regarding failed, checked, and unchecked nodes.

Usage: Management report used to ensure that nodes are being checked as scheduled without any failures occurring. Typically run monthly or more frequently if needed.

Missing Elements
This report displays element names specified by the user that are not present for the specified nodes. Alternatively, it can display rules that have no elements for the specified nodes.

Usage: Management report allows users to pick either rules or element names and determine whether or not they are missing on a target set of nodes. This report helps Tripwire Enterprise administrators configure Tripwire Enterprise to monitor for and detect configuration drift that could affect availability.

Unchanged Elements
This report lists elements or rules that have no changes over the specified period of time for the set of nodes specified by the user.

Usage: Management report used to check for elements that were expected to change over a period of time but did not do so. Used to ensure C/CM policies are being followed.

Change Process Compliance
This report identifies authorized and unauthorized changes to specified nodes over a period of time. An authorized change is associated with a valid change request ticket ID.

Usage: Management report to help operations identify when and who is circumventing change processes.

Change Variance
This report shows the total number of rules and elements associated with detected changes on specified nodes. As appropriate, you can limit report output to specific nodes, rules, and/or element names.

Usage: This report is typically executed immediately after deployment of a patch or other software package. To determine which new element versions should be promoted, you may review the report for inconsistencies across the updated systems, which can then be investigated for potential impacts on availability.

Change Window
This report indicates the number of detected changes for a specified monitored system(s) that have occurred inside and outside a defined change window.

Usage: Changes outside the change window can potentially affect service quality through downtime or restricted system access. Numerous changes outside change windows are an indicator of processes circumvention, which has been shown to be directly responsible for poor availability. This report is typically run before and after a change window.

Changed Elements
This report lists all changed elements identified by the specified criteria. Report output specifies exactly which attributes changed for each element.

Usage: Typically run ad hoc to help operations identify what changed if/when there is a service affecting problem, improves troubleshooting by identifying and isolating system changes in order to reduce Mean Time To Repair (MTTR). Eliminates the "deniability factor" when investigating unauthorized changes.

Changes by Severity
This report shows the total number of changes detected on one or more nodes (or node groups) that fall within a specified range of severity levels.

Usage: Categorizes changes, helping operations staff identify changes with potentially adverse impact on service quality. Typically run daily.

Detailed Changes
This report compiles comprehensive change information for elements on specified nodes.

Usage: Typically run ad hoc to help operations identify what changed if/when there is a service affecting problem, improves troubleshooting by identifying and isolating system changes in order to reduce MTTR.

Device Inventory
This report identifies the make, model, and version of specified nodes.

Usage: Management report showing devices being monitored helping to insure correct systems and nodes are being controlled. Typically run monthly, potentially more frequently depending on process maturity.

Elements
This report lists all elements identified by the specified criteria, e.g., all elements associated with a rule. Optionally, the report can also identify the package associated with each element.

Usage: By identifying the elements, operations can ensure that the proper systems, files, settings, configurations, etc. are being monitored ensuring any availability affecting changes are detected.

Frequently Changed Nodes
This report ranks the most frequently changed nodes that meet the specified criteria. The report includes the total number of changes for each node, as well as the totals for each type of change (additions, removals, or modifications).

Usage: Management report used to identify nodes that could potentially cause availability problems due to frequent changes.

Monitoring Policy
This report identifies the components associated with each file system, registry, database server, and directory server rule in your Tripwire Enterprise implementation.

Usage: Management report used to insure that the right rules are applied to the correct systems and devices.

Nodes with Changes
For the specified criteria, this report identifies the number of nodes that have changed over a given period of time.

Usage: Management report giving a synopsis of systems or devices that have changed vs. unchanged providing information needed to enforce change and configuration management policies.

Reference Node Variance
This report identifies all elements that differ between one node (the reference node) and another (the compare node). In a single report, the reference node may be compared with one or more nodes.

Usage: Used to identify configuration drift, which can lead to system instability, failure and ultimately downtime.