Skip to content

Quest Security and Service Advisories

As an ongoing service to Quest's valued clients, our team of experts monitors security and service advisories we are seeing in the market from multiple vendors and these important notices are sent to our clients. You can view an overview of our recent advisories below. If you need more information on any of these advisories, or would like to set up a meeting to discuss them further, please reach out to our team.

November 2026

Security Advisory: Multi-Agency Warning on Attacks Against IoT and OT Devices (11/9)

Quest has been notified of a joint fact sheet from CISA, the FBI, HHS, USDA, and the Department of Transportation warning of active malicious cyber activity targeting internet-connected devices that monitor and control physical equipment. While the advisory was prompted by attacks on refrigeration and temperature-monitoring controllers, the techniques involved apply to Internet of Things (IoT) and operational technology (OT) devices broadly, including building management and HVAC controllers, environmental and temperature sensors, IP cameras, access control panels, smart power and UPS management cards, and other network-connected equipment that is often deployed and forgotten.

Vendor: Multiple (vendor-agnostic; no specific manufacturers named)
CVE(s): The advisory addresses a class of attack against unpatched and misconfigured devices.
CVSS: N/A – Quest rates this as High priority
In the Wild: Yes. The authoring agencies report they are aware of malicious cyber activity targeting IoT and OT systems globally, across multiple sectors. This follows a similar June 2026 joint warning about attacks on internet-exposed automatic tank gauge systems, reflecting a broader trend of attackers targeting connected devices.
Unauthenticated: Yes. Authentication bypass is one of the cited attack vectors.
Description: Attackers are targeting internet-accessible and unpatched IoT/OT devices through three primary vectors: authentication bypass, arbitrary code injection, and weak configurations (such as default passwords and exposed management interfaces). Once access is gained, attackers can alter device settings and operating parameters remotely.
Impact: A successful compromise could allow an attacker to manipulate the physical equipment a device controls, potentially causing equipment damage or shortened service life, fire or safety hazards, spoiled inventory, or product loss, and indirect harm to consumers. Attackers may also cause a loss of visibility into current device status and readings (a “denial-of-view” condition), preventing staff from noticing a problem until damage has occurred.
Workarounds: No single patch addresses this threat. Risk is reduced by removing internet exposure and applying the hardening steps below.

Link to Source(s):

1. CISA: Hardening Industrial Refrigeration and Cold Chain Monitoring Systems
2. CISA: Primary Mitigations to Reduce Cyber Threats to Operational Technology
3. CISA: Defend the Edge: The Critical Importance of Edge Device Security
4. CISA: Internet Exposure Reduction Guidance

Recommendation:

1. Inventory connected devices: Identify all IoT, OT, and smart building devices on your network, including equipment installed and managed by third-party vendors, and determine which are reachable from the internet.
2. Eliminate public internet exposure: Do not expose device management interfaces or controller panels directly to the internet. Where remote access is required, route it through a VPN or firewall that is kept fully patched.
3. Segment IoT devices: Place IoT/OT devices on dedicated VLANs separated from business networks and user workstations.
4. Enforce credential security: Change all default passwords, use strong unique credentials, and enable phishing-resistant MFA wherever the device or management platform supports it.
5. Apply patches: Keep device firmware current and establish a lifecycle process to retire and replace end-of-life devices that no longer receive vendor updates.
6. Restrict access: Allowlist only the specific devices and IP addresses authorized to manage or change device settings, and review vendor remote access.
7. Back up configurations: Maintain current offsite and offline backups of device configurations and test restoring them.
8. Monitor and report: Enable device logging and review it for unexpected changes. Where devices do not produce usable logs, monitor network traffic to and from them.
9. Set safe operating limits: Define safe operating limits for devices that control physical equipment and configure alerts for any changes outside those ranges.

If you need assistance identifying internet-exposed IoT devices, segmenting them from your business network, reviewing your connected-device security posture, or discussing this advisory in more detail, please let us know, and we will set up a call.

Security Advisory: Increased Attacks on Firewalls and Edge Devices (11/2)

Quest Technology Management is seeing a rise in attacks targeting internet-facing firewalls, VPN appliances, routers, and other edge devices. Recent guidance from CISA, the FBI, and the U.S. Department of Health and Human Services (HHS) reflects the same trend. Attackers are exploiting unsupported and vulnerable edge devices because they provide a direct path into corporate networks.

What Organizations Should Know
After compromising a firewall or VPN appliance, attackers may:

1. Establish persistent access and steal administrative credentials
2. Bypass or disable security controls
3. Move laterally and access internal systems, Microsoft 365, and VPNs
4. Exfiltrate data or deploy ransomware

In many cases, security updates were available before the attack occurred. Federal guidance urges organizations to prioritize actively exploited vulnerabilities, especially those affecting internet-facing systems.

Recommended Actions for Organizations to Take Immediately

1. Confirm all edge devices run supported firmware and apply critical security updates
2. Replace any end-of-support devices
3. Restrict administrative interfaces to trusted networks and require MFA
4. Remove unnecessary VPN and administrator access
5. Review firewall, VPN, and administrator logs for suspicious activity
6. Confirm EDR is deployed, healthy, and actively monitored
7. Protect and regularly test backups against ransomware
8. Maintain an inventory of internet-facing devices and their owners

If a device may have been compromised, a firmware update alone is not enough. You may also need to reset credentials, review configurations, analyze logs, and determine whether attackers reached the broader network.

How Quest Can Help

1. Firewall, VPN, and edge-device firmware, configuration, and log reviews
2. External vulnerability and attack-surface assessments
3. Microsoft 365 and identity security assessments
4. EDR validation and incident response
5. Ransomware preparedness and replacement planning for unsupported devices

For healthcare organizations: HHS guidance specifically calls for prioritizing actively exploited vulnerabilities in firewalls, VPN gateways, and other internet-facing systems.

To schedule a review of your firewall, VPN, or edge-device environment, contact your Quest account representative, or reach out to our Security Operations Center.

If you would like to have a broader conversation about cybersecurity, infrastructure, Microsoft 365, identity, endpoint, monitoring, or incident response, Quest can help.

 

October 2026

Security Advisory: Critical Vulnerabilities in PHP Require Immediate Patching (10/21)

Quest has been notified of two critical vulnerabilities in PHP, collectively known as PHP2Shell, that could allow an unauthenticated attacker to execute malicious code on affected web servers and on any device using PHP. PHP released security updates on October 21, 2026, and strongly recommends immediate scanning, verification, and remediation. The affected PHP runtime is a fundamental part of many websites, business applications, and web-based device management systems, including firewalls.

Vendor: PHP
CVEs: CVE-2026-109618 and CVE-2026-109619
CVSS: 9.2 (Critical)
In the Wild: No (although working exploits have been verified)
Unauthenticated: Yes
Description: Both CVEs allow an unauthenticated remote attacker to execute arbitrary system commands on an affected web server through a single HTTP request, independent of the application, CMS, or framework running on top of PHP.
Impact: A successful exploit allows command execution as the affected user, which can be used to deploy web shells, harvest database and API credentials from configuration files, and pivot into internal networks.
Workarounds: Yes. See PHP’s Blog for temporary workarounds. Customers who restrict sensitive web portals to trusted internal networks are at greatly reduced risk.
Link to Source(s): PHP Advisory
IOC Available: No
Recommendation: Review vendor advisories to confirm applicability, implement workarounds as described in the vendor advisory, and apply updates as soon as possible.

If you need assistance with scanning your internal or external surface to confirm applicability, patching or updating PHP, or discussing this vulnerability in more detail, please let us know and we will set up a call.

 

Security Advisory: Upcoming Microsoft MFA Deadlines (10/14)

Microsoft is changing how Multi-factor authentication (MFA) works in Microsoft Entra ID. These changes are designed to move users away from SMS and voice authentication and toward passkeys and other phishing-resistant methods.

Although your organization may use third-party authenticators like Duo, Microsoft’s changes can still affect Entra ID policies, MFA enrollment, password resets, fallback methods, and user sign-in.

Key dates:

  • September 1, 2026: Some users who use SMS or voice may be prompted to register a passkey.
  • February 1, 2027: Microsoft-provided SMS and voice authentication will be retired for most users.
  • July 1, 2027: Global Administrators and external users will be affected.

Users who rely solely on SMS or voice may receive a blocking prompt requiring them to register another authentication method.

Recommended Action:

Quest recommends auditing each client’s MFA configuration to:

  • Identify users relying on SMS or voice
  • Review Entra ID, Conditional Access, SSPR, and legacy MFA settings
  • Confirm how Duo interacts with Microsoft authentication policies
  • Test administrators, guests, remote users, and emergency accounts
  • Select and enroll users in passkeys, Windows Hello, FIDO2 keys, or another approved method
  • Prepare user communications and help desk procedures

Microsoft recommends passkeys as the primary replacement. SMS or voice should generally be retained only where there is a documented business, regulatory, or operational need. (learn.microsoft.com)

Organizations should begin this review now to reduce user disruption and prevent sign-in or password-reset issues.

If you need assistance with auditing your MFA configuration and reviewing your Entra ID settings, or would like to discuss these changes in more detail, please let us know, and we will set up a call.

September 2026

Security Advisory: Upcoming Changes to SSL/TLS Certificate Validity Periods (9/25)

Quest’s security team is reaching out to highlight significant upcoming changes in the SSL/TLS certificate industry that will impact all organizations using publicly trusted certificates. These changes are designed to enhance security and encourage adoption of new cryptographic standards

Here are the key dates and changes to be aware of:
• March 15, 2026: Certificates will have a maximum validity period of 200 days.
• March 15, 2027: Validity periods will be reduced to 100 days.
• March 15, 2029: Certificates will have a maximum validity period of 47 days.

Why This Is Happening:
• Reduce exposure if a certificate or private key is compromised.
• Facilitate faster adoption of new cryptographic standards and algorithms.
• Improve your security posture through more frequent key rotation.
• Prepare for future cryptographic and post-quantum changes.
• Encourage automated certificate management instead of manual renewals.

What Happens If You Do Nothing:
• Expired certificates can lead to operational disruptions, revenue loss, compliance violations, and reputational damage.
• Manual rotation often results in teams losing track of expiration dates.

How Quest Can Help:
• Assist with the discovery and inventory of certificates.
• Provide centralized, automated rotation strategies and workflows.
• Centralize certificate management, automate workflows, and enable automatic certificate rotation.

Common Areas Where Certificates Are Used:
• Web servers
• Load balancers (on-premises/cloud)
• VPN appliances
• Firewalls
• Wireless controllers
• VMware vCenter
• Cisco ISE
• Reverse proxies
• Storage management interfaces
• SaaS applications using custom certificates
• Applications

We encourage you to start planning for these changes to ensure a smooth transition and maintain the security of your systems. Please feel free to reach out to us if you have any questions or need assistance with your certificate management strategy.

Thank you for your attention to this important matter.

Security Advisory: Critical Cisco ISE and Secure Firewall Flaws Under Active Exploitation (9/17)

Quest has been notified of multiple security advisories addressing critical vulnerabilities in Cisco Identity Services Engine (ISE) and Cisco Secure Firewall (ASA/FTD/FMC) products. Cisco has patched critical security vulnerabilities that could allow authenticated and unauthenticated adversaries to perform authentication bypass, remote code execution (RCE), and path traversal on impacted products listed in its security advisories.

Vendor: Cisco
CVE(s): See Cisco Advisory for complete list of CVE’s
CVSS: 10.0 (Critical)
In the Wild: Yes. Cisco PSIRT is aware of active exploitation of these vulnerabilities. Cisco strongly recommends that customers upgrade to a fixed software release to remediate this as soon as possible.

Unauthenticated: Yes

Description: Multiple vulnerabilities in Cisco Identity Services Engine (ISE) and Cisco Secure Firewall (ASA/FTD/FMC) products allow a remote unauthenticated attacker to achieve remote code execution on affected devices.

Impact: A successful exploit could allow an attacker to obtain root-level access to the underlying operating system.

Workarounds: None

Link to Source(s): Cisco Security Advisories

IOC Available: Yes (see advisories)

Recommendation:

  1. Treat this advisory as a high-priority patching event.
  2. Review vendor advisories to confirm applicability and apply updates as necessary. Identify any deployed Cisco ISE and Cisco Secure Firewall (ASA/FTD/FMC) systems.
  3. Review Cisco advisories and apply available fixed releases immediately.
  4. Prioritize patching of CVE-2026-76460 and other CVSS 10.0 ISE vulnerabilities.
  5. Review logs for unexpected authentication activity, administrative access, and configuration changes.
  6. Accelerate remediation if systems are internet-accessible or provide network access control functions.

If you need assistance reviewing and patching impacted Cisco Identity Services Engine (ISE) or Cisco Secure Firewall (ASA/FTD/FMC) systems, or if you would like to discuss these vulnerabilities in more detail, please let us know and we will set up a call.

Security Advisory: CrowdStrike Falcon Privilege Escalation Vulnerability (9/4)

Quest has been notified of a security advisory regarding an alleged CrowdStrike Falcon privilege escalation vulnerability known as FalconFlank. FalconFlank is a privilege escalation vulnerability that abuses the Microsoft Office malicious macros remediation feature in the CrowdStrike Falcon agent. CrowdStrike is actively investigating the claims and has published mitigation guidance for partners and customers.

For customers whose CrowdStrike Falcon environment is actively managed by Quest, the recommended mitigation has already been implemented on your behalf by the Quest security team.

For self-managed CrowdStrike Falcon environments, Quest recommends that you review the Tech Alert FalconFlank advisory in your support portal for mitigation measures and the latest updates from CrowdStrike.

If you need assistance reviewing CrowdStrike’s guidance and confirming that the recommended mitigation has been applied within your environment, or if you would like to discuss these vulnerabilities in more detail, please let us know, and we will set up a call.

Quest will provide updates as more information becomes available.

Security Advisory: Critical Vulnerabilities in Microsoft Exchange Server (9/2)

Quest has been notified of a security advisory addressing critical vulnerabilities in Microsoft Exchange products (2016, 2019, and SE). Microsoft has patched critical security vulnerabilities in Microsoft Exchange Server that allow attackers to access all user Exchange mailboxes.

Vendor: Microsoft Exchange
CVE(s): CVE-2026-62911, CVE-2026-42897

CVSS: Critical
In the Wild: Yes / Active (Exploit Code has been published)
Unauthenticated: No

Description: A critical vulnerability in Microsoft Exchange Server (2016, 2019, and SE) allows an authenticated attacker to bypass authentication through a capture-replay technique and elevate privileges over a network.

Impact: A successful exploit could allow an attacker to take over the mailboxes of all Exchange users. Attackers could send emails, read emails, and download attachments.

Workarounds: None

Link to source(s): Microsoft Advisories: CVE-2026-62911 , CVE-2026-42897

IOC Available: No

Recommendation: Review vendor advisories, confirm applicability, and apply updates as necessary.

***Important*** If the Exchange Server is exposed to the internet (OWA, etc.), it is highly recommended to take immediate action to remove it from internet access until updates are applied.

If you need assistance reviewing and patching impacted Microsoft Exchange products or systems, or if you would like to discuss these vulnerabilities in more detail, please let us know, and we will set up a call.

August 2026

Security Advisory: Hidden Gaps in Active Environments (8/24)

Quest continues to observe a recurring pattern across client environments: security tools are active and generating alerts, yet gaps often exist right alongside them. Common findings include devices or log sources left out of monitoring, configurations and policies that have not been reviewed since deployment, and remediation responsibilities that are not clearly assigned. These gaps usually stay hidden until a security event brings them to light.

Recommended Review

We recommend that organizations periodically verify three items:

  1. Coverage: Are the right devices, systems, and security logs included in monitoring? Confirm that recently added, decommissioned, patched, or reconfigured assets are reflected in your current monitoring scope.
  2. Configuration: Do your device security configurations and policies match the current environment? A security product can work exactly as designed while an outdated or incomplete configuration still leaves you exposed. Review configurations as your technology, users, and threats change.
  3. Ownership: When an alert, vulnerability, or other security concern surfaces, is it clear who investigates and who remediates? Ownership should be documented and understood before an event, not decided during one.

Scope Note

Responsibility for these activities varies from one organization to the next. It may sit with your internal team, a single third-party provider, or several providers at once. Where scope is uncertain or ambiguous, treat the item as unassigned until it is confirmed.

Assistance

If you are unsure about your current coverage, configuration, logging, or response responsibilities, please let us know. Our team can review your environment and help clarify where each responsibility sits.

Security Advisory: Cisco VPN Denial of Service vulnerability in ASA and FTD (8/12)

Quest has been notified of a security advisory addressing high-risk vulnerabilities in the Remote Access SSL VPN service for Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software that could allow an unauthenticated, remote attacker to cause the device to reload unexpectedly, resulting in a denial-of-service (DoS) condition.

Vendor: Cisco
CVE(s): CVE-2026-20349
CVSS: 8.6 High
In the Wild: Yes
Unauthenticated: Yes

Description: Insufficient error checking when processing HTTP requests in the Remote Access SSL VPN service for Cisco Secure Firewall Adaptive Security Appliance (ASA) Software and Cisco Secure Firewall Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause the device to reload unexpectedly.

Impact: A successful exploit could allow the attacker to cause the affected device to reload, resulting in a DoS condition.

Workarounds: None

Link to Source(s): CVE-2026-20349

IOC Available: No

Recommendation: Review vendor advisories to confirm applicability and apply updates as necessary.

If you need assistance reviewing and patching impacted Cisco devices, or would like to discuss these vulnerabilities in more detail, let us know, and we will set up a call.

July 2026

Security Advisory: Critical Vulnerabilities in Broadcom VMware Products (7/29)

Quest has been notified of a security advisory addressing critical vulnerabilities in Broadcom VMware products. Broadcom has urgently patched a critical security vulnerability that could allow unauthenticated users to perform privilege escalation exploits on impacted products listed in their security advisory.

Vendor: Broadcom/VMware
CVE(s): CVE-2026-59309, CVE-2026-59310, CVE-2026-47876, CVE-2026-41703, CVE-2026-41709
CVSS: 9.8 Critical
In the Wild: No
Unauthenticated: Yes

Description: Multiple vulnerabilities in VMware ESX, vCenter, Workstation, and Fusion were privately reported to Broadcom. Updates are available to remediate these vulnerabilities in affected Broadcom products.

Impact: A successful exploit could allow an attacker to execute arbitrary code on affected Broadcom products, elevate privileges, and gain full control of the underlying Broadcom VMware system.

Workarounds: None

Link to source(s): Broadcom Advisory

IOC Available: No

Recommendation: Review vendor advisories, confirm applicability, and apply updates as necessary.

If you need assistance reviewing and patching impacted Broadcom VMware products/systems, or if you would like to discuss these vulnerabilities in more detail, please let us know, and we will set up a call.

Security Advisory: Azure Copilot Agents enabled by default starting August 1 (7/27):

Microsoft has announced that, beginning August 1, 2026, Azure Copilot will transition away from the current “Agent Mode” experience and instead provide direct access to individual “Azure Copilot agents.” Organizations using Azure Copilot should review agent access, governance controls, and change-management procedures before the transition date.

What Is Changing?

Currently, Azure Copilot offers an Agent Mode experience that can invoke specialized AI agents to assist with cloud operations. Beginning August 1, 2026, Microsoft will replace this experience with direct access to supported agents, allowing users to interact with specific capabilities such as migration, observability, resiliency, optimization, and troubleshooting.

Important: For Microsoft tenants that already have Azure Copilot enabled, all Azure Copilot agents, including agents in Public Preview, will be enabled by default. If Azure Copilot is currently disabled for your tenant, Azure Copilot agents will remain disabled after this change.

Security Considerations

Certain Azure Copilot agents may remain in Public Preview status and may not meet internal production-use requirements.

  • Access and Permission Review: AI agents may have visibility into cloud resources, operational data, and configuration information.
  • Change Management: Organizations should ensure human oversight remains in place for infrastructure, networking, and security changes.
  • Compliance and Audit Requirements: Organizations subject to PCI-DSS, HIPAA, CJIS, FFIEC, NIST, CMMC, or similar frameworks should evaluate whether agent capabilities introduce new compliance considerations.
  • Data Exposure Review: Organizations should understand what operational information may be accessible through Azure Copilot agent interactions.

Recommendation

Quest recommends that organizations treat the introduction of individually accessible AI agents as a governance event and review security, compliance, access management, and change-control requirements before broad deployment.

  • Review Azure Copilot agent availability (enabled/disabled) within the tenant.
  • Identify which agents are GA versus Public Preview.
  • Update AI governance and acceptable-use policies.
  • Review Azure RBAC permissions and privileged access assignments.
  • Perform security and compliance assessments for any newly available agents.

If you need assistance determining your Microsoft tenant’s Azure Copilot enablement status or reviewing any of these recommendations, please let us know, and we will set up a call.

Security Advisory: Unpatched Firewalls Are Being Exploited (7/14):

Quest Technology Management’s Security Operations Center (SOC) has recently responded to multiple cybersecurity incidents involving the exploitation of unpatched internet-facing firewalls. These attacks are part of a broader trend in which cybercriminals target edge devices to gain initial access to corporate networks.

What We’re Seeing

Our incident response team has observed attackers successfully exploiting known vulnerabilities in:

  • SonicWall firewalls
  • Fortinet FortiGate firewalls

After gaining access, attackers commonly:

  • Establish persistent access to the environment
  • Escalate privileges and obtain administrative credentials
  • Move laterally across the network
  • Disable or evade security controls
  • Exfiltrate sensitive data
  • Deploy ransomware or other destructive payloads

In nearly every case, patches or firmware updates for the exploited vulnerabilities were available before the attack occurred.

Recommended Actions

We recommend that organizations take the following steps immediately:

  • Verify that all internet-facing firewalls and VPN appliances are running the latest supported firmware.
  • Apply all critical and high-severity security updates without delay.
  • Restrict firewall management interfaces to trusted networks only.
  • Require Multi-Factor Authentication (MFA) for all administrative and remote access accounts.
  • Review VPN users and remove inactive or unnecessary accounts.
  • Confirm that Endpoint Detection and Response (EDR) is deployed, healthy, and actively monitored.
  • Review administrative account activity for signs of unauthorized access.
  • Verify that backups are protected from ransomware and regularly tested for recovery.

How Quest Can Help

Quest Technology Management can assist with:

  • Firewall firmware and security configuration reviews
  • External vulnerability assessments
  • Attack surface and exposure reviews
  • Microsoft 365 and identity security assessments
  • Endpoint Detection and Response (EDR) validation
  • Security monitoring and incident response services
  • Ransomware preparedness and tabletop exercises

Cybercriminals continue to prioritize organizations with vulnerable internet-facing infrastructure. Keeping perimeter devices fully patched, limiting administrative access, and continuously monitoring for suspicious activity are among the most effective ways to reduce your organization’s risk.

If you would like Quest to review your firewall environment or perform a security health assessment, contact your Quest account representative or reach out to our Security Operations Center.

Security Advisory: Microsoft RC4 Final Enforcement Begins July 2026:

Quest Advisory Reminder: This is a follow-up to our earlier advisory regarding Microsoft’s deprecation of RC4 encryption in Windows Kerberos. The July 2026 Windows updates introduce Phase 2 (Final Enforcement), which removes the manual rollback capability and enforces AES encryption by default. If you have not yet completed your migration from RC4 to AES, you must do so now to avoid authentication failures.

Why This Matters Now
Microsoft has announced a phased deprecation and default disablement of RC4 (Rivest Cipher 4) encryption within Windows Kerberos authentication due to vulnerabilities disclosed under CVE-2026-20833. RC4 is considered cryptographically weak and susceptible to modern credential theft attacks, such as Kerberoasting.

As part of this change, Microsoft will update Windows domain controller behavior so that AES-based encryption is used by default, and authentication requests relying on RC4 will eventually fail unless explicitly remediated. To avoid authentication issues, organizations must plan and complete a safe migration from RC4 to AES before enforcement.

Critical change in July 2026: With Phase 2 (Final Enforcement), the manual rollback option will no longer be available. Once these updates apply, you will not be able to temporarily revert to RC4 to work around authentication problems. Any unremediated service accounts, devices, or applications may stop authenticating with no fallback option.

View the announcement here: Managing Kerberos RC4 Usage for Service Accounts (CVE-2026-20833)

Microsoft’s Enforcement Timeline

  1. January 2026 – Audit Phase Starts
  2. April 2026 – Phase 1 Enforcement (Enforced with Microsoft April ’26 Patch Tuesday OS patches. Applications and accounts may start to fail if not remediated; manual rollback option available.)
  3.  July 2026 – Phase 2 Final Enforcement (Manual rollback option removed to force AES encryption.)

We are now entering the final phase. After the July 2026 updates, there is no manual rollback safety net. Remediation must be complete before these updates apply.

Potential Impact

  1. Legacy service accounts using RC4-only encryption
  2. Older NAS devices or appliances integrated with Active Directory
  3. Any third-party applications that do not support AES Kerberos encryption
  4. Non-Windows systems (including Linux-based systems) authenticating to Active Directory

Recommendation
Quest recommends the following actions to avoid business disruption:

  1. Ensure all domain controllers are fully patched on or after January 13, 2026 (to enable additional audit and control features).
  2. Identify RC4 usage:
    • If a SIEM platform is available, review Domain Controller logs for Kerberos-related events that may indicate RC4 usage.
    • Use Microsoft-provided temporary registry keys and scripts to detect RC4 dependencies in Domain Controller logs.
  3. Remediate impacted accounts and applications:
    • Reset passwords for service accounts to generate AES keys.
    • Upgrade or replace non-compliant devices or applications (engage application vendors as needed, as remediation may require application-level changes outside of infrastructure management).
    4. Continue to test/review logs to ensure RC4 event findings are no longer being generated.
    5. Ensure all domain controller backups are successful (prior to the implementation of Microsoft’s April 14 Patch Tuesday).
    6. Patch domain controllers during a low-impact maintenance window and allow adequate time for remediation.
    7. Test all business processes. If impacted, follow up with Quest or Microsoft to assist with the assessment and configuration of a temporary workaround.

Important: Any temporary workarounds that depend on the manual rollback option will stop working after the July 2026 Phase 2 enforcement. Confirm full remediation before that deadline, as no rollback path will remain.

Useful Microsoft Links

  1. Detect and remediate RC4 usage in Kerberos
  2. Beyond RC4 for Windows authentication

If you need assistance identifying RC4 usage, validating application compatibility, or planning a phased remediation in more detail, please let us know.

Contact Quest Today  ˄
close slider