From 7f90a3f32fff0a304e242eab70fa94075f9b5e77 Mon Sep 17 00:00:00 2001 From: juliaroesschen <132892973+juliaroesschen@users.noreply.github.com> Date: Fri, 14 Jun 2024 16:17:17 +0200 Subject: [PATCH] Add Access Control Video to docs (#198) --- src/pages/how-to/manage-network-access.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/pages/how-to/manage-network-access.mdx b/src/pages/how-to/manage-network-access.mdx index 7cebeaba..aaf8c2bc 100644 --- a/src/pages/how-to/manage-network-access.mdx +++ b/src/pages/how-to/manage-network-access.mdx @@ -2,11 +2,16 @@ # Manage network access NetBird enables administrators to oversee and manage access between resources (peers) through access policies. These policies specify which peers and peer groups are permitted to connect to each other, detail the protocols and ports for these connections, and offer the option to include posture checks to apply zero trust principles, helping to adapt access control to specific contexts. +Watch our Access Control video on YouTube: + +
+ +
+ ## Introduction Initially, a NetBird account is configured with a `Default` policy which allows peers to connect via any protocol, resulting in the formation of a full mesh network. This setup often suits small networks or those requiring minimal security. In scenarios where higher security is needed or access to specific resources must be restricted for certain users or services, policies can be set up to determine access permissions. - Access control policies make use of groups to control connections between peers. These groups, which are sets of peers (meaning different machines with the NetBird client installed), can be added as Source or Destination of a policy. They are evaluated when the Management service distributes the list of peers across your network. ## Concepts