Search: “machine identity”

3 stories in the last 24h

Searchkeyword smart Sortlatest hot importance relevance

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

CategoryAll Data breach 4 Advisory 3 Vulnerability 2 Industry 2 Malware 2 Research 2 Threat actor 2 AI industry 1 Phishing & fraud 1 AI safety & security 1 AI research 1 Exploit / PoC 1 Tools 1

SeverityAll critical 1 high 2 medium 12 low 0 info 8

Microsoft shares workaround for Windows domain login issues

Microsoft confirms September 2026 Windows updates trigger domain trust failures via Machine Identity Isolation and shares a workaround for Windows 11 enterprises.

Microsoft confirmed the September 2026 security updates (KB5124008 for Windows 11 24H2/25H2, KB5124012 for 26H1) cause Windows to honor Machine Identity Isolation enforcement settings, breaking domain trust on systems not connected to Windows Server 2025 domain controllers. Admins report valid credentials failing with domain trust and credential errors. The workaround requires disabling Machine Identity Isolation via the same management method that enabled it (Intune, group policy, or registry) and resetting the secure channel with Test-ComputerSecureChannel. Microsoft previously shipped out-of-band fixes for Remote Desktop, Hyper-V, and USB audio issues from the same updates.

BleepingComputer08:24 UTC · 4h agoAdvisory 4 sources

AI agent authorization risks remain a gap in new NIST-CISA token security guidance

NIST and CISA release IR 8587 guidance on securing signed tokens, but AI agent authorization and delegation risks remain out of scope.

NIST, with CISA support, published 'Protecting Tokens and Assertions from Forgery, Theft, and Misuse' (NIST IR 8587), recommending continuous monitoring and tighter token lifecycle controls for SSO and API access. The guidance does not yet fully address AI agent identity, delegation chains, or prompt injection steering agents with valid tokens, and NIST says new or expanded standards are needed. Experts recommend treating AI agents as low-trust non-human identities, maintaining agent inventories, expiring credentials after task completion, and requiring human approval for high-risk actions. The report references shared-signal mechanisms like CAEP and RISC, and follows a May incident where a CISA contractor GitHub repository exposed AWS and GitHub tokens.

CSO OnlineSep 16, 15:42 UTC · 20h agoAdvisory 3 sources

CISA and NIST Issue Guidance to Protect Cloud Identity Tokens

CISA and NIST published Interagency Report 8587 with voluntary guidance to harden cloud identity tokens against theft, forgery, and lateral movement.

CISA and NIST released NIST Interagency Report 8587 on September 15 with final voluntary guidance for federal agencies, cloud providers, and their customers on protecting SSO, federation, and API tokens. Requirements include one-hour maximum token lifetimes, 90-day signing key rotation for high-impact systems, hardware-backed key storage, explicit audience fields, and keeping tokens out of logs. The guidance was motivated by the 2020 ADFS compromise where forged SAML assertions bypassed MFA, and an incident where a leaked consumer signing key enabled token forgery and theft of 60,000+ emails from one agency. Nearly 250 public comments shaped the text, with input from Google, Microsoft, Okta, AWS, Oracle, IBM, HashiCorp, Wiz, and the OpenID Foundation via the Joint Cyber Defense Collaborative.

Infosecurity MagazineSep 16, 14:00 UTC · 22h agoAdvisory