mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 00:49:03 +00:00
Update teams.md (#27995)
Updated best practice team names to align to the recent changes we are making to support Android. See the following for more info: fleetdm/confidential#9192
This commit is contained in:
parent
1e8267b0e0
commit
a85f9c5233
1 changed files with 2 additions and 3 deletions
|
|
@ -21,9 +21,8 @@ Fleet's best practice teams:
|
|||
- `☁️ Servers`: Security team's production servers.
|
||||
- `☁️🐣 Servers (canary)`: Security team's test servers.
|
||||
- `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.
|
||||
- `📱🏢 Company-owned Mobile Devices`: iPhones and iPads purchased by the organization that enroll to Fleet automatically via Apple Business Manager. For example, iPhones used by iOS Engineers or conference room iPads.
|
||||
- `📱🔐 Personal Mobile Devices`: End users' personal Android devices or iPhones, like those enrolled through a BYOD program, that have access to company resources.
|
||||
|
||||
If some of your hosts don't fit into the teams listed above, consider their purpose. This will help determine their risk and compliance requirements, which in turn define their security baseline and appropriate team in Fleet. If these hosts have distinct compliance needs and security baselines, it's advisable to create a new team in Fleet.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue