From d9d96e28226e9d75e95f50aa3fa217a7d7f4f349 Mon Sep 17 00:00:00 2001 From: Allen Houchins <32207388+allenhouchins@users.noreply.github.com> Date: Wed, 8 Jan 2025 16:17:36 -0600 Subject: [PATCH] Update teams.md (#24957) Minor changes to support fleetdm/confidential#9168 and https://github.com/fleetdm/fleet/pull/24952 --- articles/teams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/teams.md b/articles/teams.md index ea688bc08b..934be78511 100644 --- a/articles/teams.md +++ b/articles/teams.md @@ -20,7 +20,7 @@ Fleet's best practice teams: - `Compliance exclusions`: All contributors' test work computers or virtual machines (VMs). Used for validating workflows for Fleet customers or reproducing bugs in the Fleet product. - `📱🏢 Company-owned iPhones`: iPhones purchased by the organization that enroll to Fleet automatically via Apple Business Manager. For example, iPhones used by iOS Engineers. - `🔳🏢 Company-owned iPads`: iPads purchased by the organization that enroll to Fleet automatically via Apple Business Manager. For example, conference-room iPads. - +- `📱🔐 Personally-owned iPhones`: End users' personal iPhones, like those enrolled through a BYOD program, that have access to company resources. If some of your hosts don't fall under the above teams, what are these hosts for? The answer determines the the hosts' risk/compliance needs, and thus their security basline, and thus their "team" in Fleet. If the hosts' have a different compliance needs, and thus different security baseline, then it's time to create a new team in Fleet.