22 docs tagged with "TLS"

This document outlines the process of auditing and establishing hardening rules and policies for ConnectWise Automate servers based on the latest guidelines. It includes a detailed description of the variables involved, the processes executed, and the expected output, aimed at enhancing server security and compliance.

Enables reboot prompts following TLS Hardening. Requires the Reboot Pending Prompt solution to be enabled in the environment.

This stores the TLS Client Enabled state.

Enables TLS hardening for workstations and servers. `Validate` identifies devices that require TLS hardening without making changes. `Enforce` applies hardening to devices flagged by Validate. `Validate` must be enabled for Enforce to work properly.

This stores the TLS Server enabled.

This custom field is populated by the "Validate TLS SSL Hardening" script and flags devices that require TLS/SSL hardening to meet security best practices.

This group shows the agents where the "TLS Enabled List Audit" script is executed to collect the enabled TLS versions audit list.

This PowerShell script enforces TLS/SSL hardening by disabling insecure protocols (SSL 3.0, TLS 1.0, TLS 1.1) and removing specified weak TLS 1.2 cipher suites to strengthen system security and align with modern security standards.

Triggers `Enforce TLS SSL Hardening` script on opted windows servers.

Triggers `Enforce TLS SSL Hardening`script on opted windows workstations.

Triggers `Validate TLS SSL Hardening` script on opted windows Servers.

Triggers `Validate TLS SSL Hardening`script on opted windows servers.

This document outlines the best practices for hardening ConnectWise Automate, including user accounts, group policy edits, internet access considerations, and critical passwords. It also covers firewall settings and TLS configurations to enhance security.

This document outlines the best practices for hardening ConnectWise ScreenConnect, including user accounts, group policy edits, internet access considerations, and critical passwords. It also covers firewall settings and TLS configurations to enhance security.

This custom field stores the installed and enabled TLS Client versions on an endpoint.

This script gathers information about the TLS Client and Server protocol versions installed on an endpoint and stores the data in custom fields.

This PowerShell script shows the list of TLS servers, and client are enabled.

This custom field stores the installed and enabled TLS Server versions on an endpoint.

This solution is built to audit the TLS version audit.

This solution is built to audit the tls version audit.

This solution validates and hardens the system`s SSL/TLS configuration by disabling insecure protocols and weak cipher suites while enabling secure protocols and supporting optional reboot management.

This script validates that insecure protocols (SSL 3.0, TLS 1.0, TLS 1.1) and specified weak cipher suites are disabled at both the server and client levels on the system, while ensuring TLS 1.2 and TLS 1.3 are enabled when supported, providing a clear PASS/FAIL status without making any changes.