Parks seasonal hires should receive a looser Carbon Black Cloud policy, and full-time staff should stay on a strict one, including when a seasonal account later becomes full-time. Which grouping method scales?

Parks seasonal hires should receive a looser Carbon Black Cloud policy and full-time staff a strict one, including when a seasonal account later becomes full-time. Use AD/OU or metadata criteria on sensor groups so policy follows the account type automatically—seasonal badges change; group criteria should change with them. Moving each seasonal laptop by hand on day one and again at season end fails by concept because manual moves do not scale and miss role changes. Keeping every parks sensor in Standard and emailing a reminder when someone is hired full-time fails because email is not automated policy assignment. Creating one static list of hostnames and editing it whenever HR changes a role fails because static lists drift and lag HR events. Exam caveat: role-driven CBC policy uses criteria-based sensor groups (AD/OU/metadata)—not manual moves, email reminders, or static hostname lists. Operational check: place a test seasonal account in the seasonal OU and confirm the looser policy, move it to full-time OU and confirm the strict policy on re-evaluation, without console hand moves. Align parks HR offboarding with OU changes so season-end automatically drops privileged prevention assumptions.