Are there security implications when enabling the "privateNetworkClientServer" capability for a UWP app

Koen Van Durme 21 Reputation points
2021-05-02T12:22:03.407+00:00

My understanding of the "privateNetworkClientServer" capability is to allow a UWP app to access VPN or local network.

Since the documentation around this is a bit sparse I'm also wondering if there are any other security implications that we need to take into account when enabling this capability.

Universal Windows Platform (UWP)
{count} votes

Accepted answer
  1. Roy Li - MSFT 32,051 Reputation points Microsoft Vendor
    2021-05-03T01:37:56.91+00:00

    Hello,

    Welcome to Microsoft Q&A!

    As the document describes, this capability provides inbound and outbound access to home and work networks through the firewall. This capability is typically used for games that communicate across the local area network (LAN), and for apps that share data across a variety of local devices. If your app specifies musicLibrary, picturesLibrary, or videosLibrary, you don't need to use this capability to access the corresponding library in a Home Group. On Windows, this capability does not provide access to the Internet.

    This is a general-use capability that applies to the most common app scenarios. There should be no security implications if you use the capability normally.

    Thank you.


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Koen Van Durme 21 Reputation points
    2021-06-15T21:39:14.497+00:00

    Sorry for coming back to this @Roy Li - MSFT but do you still have some extra context around the security implications of enabling this capability?

    Since you mentioned

    There should be no security implications if you use the capability normally.

    We are a bit confused about the "normally" part and still wondering what the extra risks are for end users when we would enable this capability?

    This is not yet completely clear from your answer.
    Hoping you can provide some more info.

    Thanks!