Search: “Windows”

5 stories

Searchkeyword smart Sortlatest hot importance relevance

DomainAll Cyber AIWindow24h 3d 7d 30d AllIn the wild Important only Show duplicates

CategoryAll Malware 3965 Vulnerability 3853 Ransomware 2562 Exploit / PoC 1723 Threat actor 837 Data breach 640 Industry 565 Phishing & fraud 428 Policy & legal 410 Research 122 AI safety & security 120 Tools 114 AI tools & infra 106 Advisory 106

SeverityAll critical 5951 high 5070 medium 3246 low 1003 info 456

August updates trigger 0xc0000409 errors on Windows Server 2016

Microsoft says the August 2026 security update causes recurring CompatTelRunner.exe 0xc0000409 crashes on Windows Server 2016 with Compatibility Appraiser enabled; no functional impact.

Microsoft confirmed a known issue in which the August 2026 Windows security update generates recurring Application Error events (Event ID 1000, exception code 0xc0000409) in CompatTelRunner.exe on Windows Server 2016. The issue affects physical and virtual machines, including VMware and Azure environments, and per Microsoft does not affect device functionality. A permanent fix is planned for a future update, and the event log entries can be dismissed temporarily.

BleepingComputerSep 8, 15:22 UTC · 8d agoAdvisory

Windows memory integrity switches on automatically for eligible devices in October 2026

Microsoft's Windows quality updates will automatically enable memory integrity and Virtualization-based Security on eligible devices starting October 2026.

Beginning in October 2026, Windows quality updates will automatically enable memory integrity on eligible devices and turn on Virtualization-based Security where it is not already running. Memory integrity restricts kernel-mode execution to trusted, signed code and drivers, blocking kernel compromise and rootkits. Microsoft said existing administrator decisions remain in effect, and readiness checks weigh hardware capability, compatibility, and performance. Memory integrity also underpins hotpatch updates that install without a reboot, so unprotected devices are excluded from that servicing model.

Help Net SecuritySep 3, 00:00 UTC · 14d agoAdvisory1

Best Practices for Good Endpoint Hardening | Huntress

Huntress outlines endpoint hardening best practices, citing exposed RDP, RMM tool abuse, and ClickFix social engineering as common SMB intrusion paths.

Huntress published defensive guidance on endpoint hardening for small and mid-sized businesses, drawing on observations from its SOC. The post describes common intrusion vectors: internet-exposed RDP brute-forced by automated scanners, phishing emails delivering attacker-controlled remote monitoring and management (RMM) tools, with Huntress reporting a 277% spike in RMM abuse in 2025, and ClickFix attacks using fake CAPTCHA pages that trick users into running malicious commands. Recommended controls include scanning for exposed RDP, SSH, and VPN interfaces, removing unneeded local admin rights, enabling Windows Defender tamper protection, disabling SMBv1, and standardizing on one approved remote access tool, guided by CIS and NIST frameworks.

HuntressSep 10, 15:00 UTC · 6d agoAdvisory

CISA and NIST Release Technical Checklist for Safeguarding Identity Tokens From Theft and Misuse

CISA and NIST published NIST IR 8587, final guidance for protecting identity tokens from forgery, theft, replay, and signing-key compromise.

NIST Interagency Report 8587 (September 15, 2026) expands the IA-13 'Identity Providers and Authorization Servers' control from NIST SP 800-53 R5.1.1, guiding federal agencies and cloud providers on SSO, identity federation, and machine-to-machine authentication. It requires hardware-backed signing-key storage for moderate-impact systems, 90-day key rotation for high-impact systems, token lifetimes under one hour, and sender-constrained mechanisms such as mutual TLS and DPoP. The report cites incidents including forged SAML assertions that exposed over 60,000 emails from a federal agency. It also extends guidance to agentic AI systems using signed tokens and urges post-quantum cryptography migration planning.

Cyber Security NewsSep 15, 17:04 UTC · 1d agoAdvisory1

AWS Certificate Manager sets 2027 end date for email-validated certificate renewals

AWS Certificate Manager will phase out email validation for public certificates during 2027, requiring migration to DNS validation before September 30, 2027.

AWS Certificate Manager will stop offering email validation in new Regions on January 1, 2027, discontinue it for new certificate requests on March 31, 2027, and stop renewing email-validated certificates on September 30, 2027. This precedes the CA/Browser Forum's March 15, 2028 deadline ending email-based domain validation for publicly trusted certificates. AWS is updating the UpdateCertificateOptions API so customers can switch to DNS validation in place while retaining the certificate ARN, with Route 53 support for creating required CNAME records.

Help Net SecurityAug 14, 00:00 UTC · Aug 14, 2026Advisory