authorization

Winsage
December 4, 2025
Microsoft is introducing an MCP registry to Windows, enhancing security with protective wrappers and providing local agents with discovery tools. A proxy will enable connectivity for local and remote servers, ensuring robust authentication, auditing, and authorization. Enterprises can control access to the MCP using group policies and default settings, allowing unique identities for connectors. The registration process for an MCP server has been simplified with MSIX packages, making installation more accessible. Developers must have NodeJS installed to use the MCP bundle (mcpb) package, which is built using an NPM package. This approach allows developers to incorporate the MCP server into their application’s installer as an MSIX file for easy distribution and installation.
Winsage
November 18, 2025
Microsoft Windows is evolving to incorporate AI agents that act autonomously, resembling digital coworkers. This shift is facilitated by the Model Context Protocol (MCP), which standardizes agent interactions with tools and data sources, ensuring secure access to system resources. Windows introduces an on-device registry of "agent connectors" for functionalities like file access and system settings, managed through an OS-level proxy that oversees identity, permissions, consent, and audit logging. The initial connectors focus on File Explorer and System Settings, defining clear capabilities and restrictions for agents. A transparent consent model allows users to manage permissions easily, promoting a user-friendly experience. The introduction of an Agent Workspace provides a dedicated environment for agents, ensuring they operate independently and with least-privileged access. Security measures include signed connectors and a standardized proxy for authentication and auditing, enabling visibility into agent actions. Windows is also expanding on-device AI processing with APIs for various functionalities, allowing agents to leverage local models securely. While Windows is not becoming an agent-first operating system, it is establishing a framework for human and agent interactions, positioning itself as a safe environment for AI operations. The foundational elements for this evolution include standard interfaces, clear permissions, isolated environments, and system-level observability.
Winsage
November 18, 2025
Microsoft has introduced a new support document detailing the transformation of Windows 11 into an agentic operating system, emphasizing AI-native capabilities that allow the PC to autonomously manage tasks. A new experimental feature, agent workspace, will soon be available in a private developer preview for Windows Insiders. This feature enables AI to run applications in parallel with the user, designed to be lightweight and secure, with scalable memory and CPU usage. Microsoft has identified three core security pillars for agentic OS experiences: non-repudiation, confidentiality, and authorization. Additionally, essential security principles for AI agents include autonomy, activity logging, user supervision, least privilege, and defined data processing purposes. Microsoft plans to integrate these capabilities into Windows 11, with applications like Copilot Actions being among the first to utilize them, and third-party developers will also be able to create their own AI agents using the provided framework.
Winsage
November 12, 2025
Microsoft has identified a critical vulnerability, CVE-2025-62215, affecting the Windows Kernel, which is currently being exploited. This flaw, rated as Important, involves an elevation of privilege issue due to improper synchronization of shared resources, categorized under race condition (CWE-362) and double free (CWE-415). Exploitation requires high complexity and local authorization, allowing attackers to gain SYSTEM privileges for significant control over the system. The vulnerability affects various versions of Windows, including Windows 10, Windows 11 (multiple versions), and Windows Server (2019, 2022, and 2025), with patches released on November 12, 2025. Organizations are advised to prioritize swift patching and detection efforts, especially for servers and administrative workstations.
AppWizard
November 9, 2025
The indie developer of the cooperative survival horror shooter Misery announced on its Steam community hub that the game was delisted due to a DMCA strike from GSC Game World, which claimed Misery used their content without authorization. The developer, Maewing, shared an email from Valve stating the allegations and emphasized that Misery does not pose a threat to GSC's intellectual property, asserting that all content is original or legally licensed. The post also mentioned that Misery does not include any characters, plotlines, assets, or music from GSC's games. Following the DMCA claim, there was speculation about potential motivations related to the developers' alleged support for the Russian invasion of Ukraine, although this remains unverified. The Misery Discord has since implemented new moderation rules to prevent inflammatory discussions.
Search