32 docs tagged with "Compliance"

This document outlines a dataview created to verify the applied workaround and installation of necessary patches to mitigate and detect Active Directory privilege escalation attacks. It provides a comprehensive overview of computer accounts with non-compliant sAMAccountNames and details about patch statuses.

This document outlines a PowerShell script designed to verify the installation of necessary patches to mitigate and detect Active Directory privilege escalation attacks. It checks for the presence of specific patches, monitors registry settings, and identifies non-compliant computer accounts, ultimately enhancing security compliance for domain controllers.

This document describes a monitor that detects agents based on the presence of the "Compliance Management Installer Key" and ensures that deployment is enabled. It highlights the importance of not excluding any locations or computers from this monitoring process.

This document provides an overview of a Bitlocker monitoring script that identifies target machines based on specific conditions related to Bitlocker settings and client configurations. It includes SQL queries, dependencies, and guidelines for targeting the Bitlocker solution.

This document outlines a monitoring solution for identifying target machines with specific Bitlocker settings, ensuring that only compliant machines are flagged for further action. It includes SQL queries and dependencies for effective implementation.

A thorough examination of Windows 10 computers and their patching status for each client, including details on supported and unsupported systems, patch compliance, and the status of approved, denied, ignored, installed, missing, and failed patches.

Shows the most recently installed Windows Cumulative Update. Useful for verifying patch status and update compliance.

Lists out the machines which has Cumulative Update Installed older than x days.

Provides an overview of the systems cumulative update compliance, including details on the latest installed CU and identification of machines that have reached end‑of‑life (EOL).

Provides an overview of the servers cumulative update compliance, including details on the latest installed CU and identification of machines that have reached end‑of‑life (EOL).

Provides an overview of the workstations cumulative update compliance, including details on the latest installed CU and identification of machines that have reached end‑of‑life (EOL).

This document provides an overview of the Cumulative Update compliance score for Windows computers in an environment managed by Automate. It includes details on dependencies, columns, and the scoring system used to assess compliance based on the age of installed updates.

This document provides an overview of the Cumulative Update compliance score for Windows computers within the Automate environment. It details the data display for managed patch policies, including the age of updates and the scoring system used to assess compliance across production patching groups.

To provide clients with professional-looking patch management reports that they can confidently trust. These reports are based entirely on the cumulative update solution and a custom table.

This Script validate the full version of the OS and compares it with Microsoft database of Windows Cumulative Updates to identify which cumulative update the device has. The data is then formatted and stored in the Custom Field.

This document outlines the implementation of dataviews to present the cumulative update compliance score for Windows computers with managed patch policies. It details the associated content, dependencies, and step-by-step instructions for setting up the solution in ConnectWise Automate, ensuring that your environment maintains compliance with the latest updates.

This document provides a comprehensive overview of the script used to deploy the Rapid Fire compliance management application, including prerequisites, variables, user parameters, and ticketing integration.

This document outlines the process to deploy the Rapid Fire Compliance Management software using client-level EDFs with specific location and computer-level exclusions. It includes associated scripts, monitors, and implementation steps to ensure a successful deployment.

This document outlines a solution that retrieves the computer build number, compares it with Microsoft’s database to identify the installed Cumulative Update, and assesses its compliance status based on the update age.

This document provides a comprehensive guide on implementing and removing the Network Firewall solution, detailing the steps required for installation and removal, as well as the processes involved in monitoring network firewall statuses. It includes important notes and troubleshooting tips for effective management of the firewall solution.

This document provides a detailed overview of a comprehensive patching report dataview, including essential columns such as patching configuration, patch status, and compliance metrics for effective machine management.

This document provides a detailed overview of a patch report, showcasing essential information for effective patch management, including patch configuration, status, and compliance metrics for various machines.

This document provides an overview of the patch and cumulative update compliance score for supported Windows computers in the environment, detailing the compliance metrics, dependencies, and scoring system used to assess the patch management effectiveness.

This document provides a comprehensive overview of the patch and Cumulative Update compliance scores for Windows environments using ConnectWise Automate. It details the metrics for supported Windows computers, including compliance percentages, age of updates, and validation data, grouped by client for better clarity and management.

This document outlines the implementation steps and associated content for the Patching and Cumulative Update Compliance Metrics dataviews in ConnectWise Automate, focusing on Windows computers with managed patch policies and their compliance scores over the past 30 days.

This view aggregates patch data to the Client level. It takes the detailed information from individual computers and summarizes it into high-level statistics. It is used to generate the "Environment Summary" and the overall "CU Compliance" percentage found in the headers of the "All Machines" report.

This view is a specialized version of the general statistics view, filtered strictly for **Servers**. It aggregates patch health data for server operating systems only. It is used to generate the headers and "Environment Summary" for the "CU Compliance - Servers" report, separating server data from workstations to provide a clearer picture of critical infrastructure health.

This view is a specialized version of the general statistics view, filtered strictly for **Workstations** (laptops and desktops). It aggregates patch health data for non-server operating systems only. It is used to generate the headers and "Environment Summary" for the "CU Compliance - Workstations" report, isolating workstation data to provide a clear view of end-user device health.

This view provides a detailed, per-computer analysis of patch health. It lists every machine in the environment along with its operating system details, end-of-life status, and a calculated "Compliance Score" based on how recently the last monthly Cumulative Update (CU) was installed. It serves as the main data source for detailed report sections like "Device Patch Status."

This document outlines the SQL query used for the Patching and CU Compliance Metrics dataview, focusing on supported Windows computers with managed patch policies. It details dependencies, tables, and various metrics related to patch compliance and cumulative updates.

This document outlines the setup and details for a remote monitor designed to ensure that Windows workstations synchronize their time with the NTP server us.pool.ntp.org. It includes configuration details, alert settings, and ticketing information for compliance failures.