A parks department prefers read-only SOAR integrations first, then write actions after metrics prove value. What privilege approach is that?

A parks department that prefers read-only SOAR integrations first, then write actions after metrics prove value, is using progressive privilege. Read-only enrichment validates data quality, alert volume, and operational usefulness without granting delete, isolate, or mailbox-modify rights on day one. After metrics show reliable enrichment and operator readiness, write scopes can be added deliberately for proven playbooks—reducing the chance that early automation bricks POS gear, irrigation controllers, or staff mail during tuning.

Why the other options fail by concept: Scoped just-in-time elevation that starts read-only and grants write access after municipal metrics prove value uses temporary case-by-case elevation rather than progressively expanding baseline privilege to include write actions. Progressive privilege that starts read-only and adds vendor playbooks after municipal metrics prove value adds content rather than privilege, adding vendor playbooks instead of adding write actions. Progressive privilege that starts read-only and removes write actions after municipal metrics prove value reverses direction, removing write after municipal metrics prove value instead of adding write actions.

Exam caveat: Progressive privilege is a rollout strategy, not a permanent ban on containment; high-value write actions should still carry approval gates and versioned releases. Operational check: start connectors read-only, measure enrichment accuracy and case time saved, then expand specific write actions under change control with rollback and owner assignment.