Stryker Products SAFE to Use!
Severe operating disruptions are still underway at one of the world’s leading medical companies. While Stryker Corporation’s internal Microsoft environment is under investigation, the company released an update last night and has cleared its connected products for use.
The customer update states they have found no malware or ransomware in their environment, and their connected products are safe to use. Customer Updates: Stryker Network Disruption | Stryker
VEEAM Backup & Replication
Two high and four critical vulnerabilities have been resolved in Veeam Backup & Replication 13.0.1.2067, released on March 12, 2026.
Several of the weaknesses addressed include remote code execution, which allows less privileged domain users to execute code on vulnerable servers. Additionally, CVE-2026-21708 allows an authenticated domain user to perform remote code execution (RCE) on the Backup Server as the postgres user.
The vulnerabilities affect versions 13.0.1.1071 and earlier builds of version 13. Check versions and upgrade to 13.0.1.2067 if devices are on an older instance. KB4831: Vulnerabilities Resolved in Veeam Backup & Replication 13.0.1.2067
Windows Deprecating RC4 Authentication on Domain Controllers
RC4 is considered cryptographically weak and is vulnerable to attacks such as Kerberoasting, which can lead to credential theft and compromise of the network. Continuing to rely on RC4 poses a significant security risk; therefore, Microsoft will disable RC4 encryption by default on Windows domain controllers, beginning with the April 2026 patches.
To prepare for the encryption shift, expect to adjust computer accounts using Group Policy Objects (GPOs) or through an operating system upgrade. General user accounts may need to have their passwords changed. Service Accounts may also require the msDS-SupportedEncryptionTypes attribute to be set. Security Transplant Alert as Microsoft Pulls the Plug on RC4 – Fortified Health Security
Fortified recommends applying patches and updates where possible and only after adequate testing in a development environment to ensure stability and compliance with organizational change management policies.