From 7b3df7a88c1290a31321a2015adc689519f24c90 Mon Sep 17 00:00:00 2001 From: Allen Houchins <32207388+allenhouchins@users.noreply.github.com> Date: Fri, 20 Dec 2024 11:14:03 -0600 Subject: [PATCH] Update teams.md --- articles/teams.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/teams.md b/articles/teams.md index ea688bc08b0c..8f08ee88e3dc 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 that have access to company resources. For example, Slack and Gmail. 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.