A transit authority stages Velociraptor-class collectors only on labeled IR jump hosts first. What rollout pattern is that?

Staging Velociraptor-class collectors only on labeled IR jump hosts first is a phased defensive agent rollout. New or powerful collection tooling is validated on a small, explicitly labeled set of municipal IR jump hosts before broader deploy across transit endpoints. Staging surfaces compatibility, performance, credential handling, and alert noise issues where blast radius is limited—avoiding the confusion with phasing collector server rollout onto labeled municipal IR jump hosts before broader deploy, which stages the server infrastructure rather than the defensive agent.

Phasing collector server rollout onto labeled municipal IR jump hosts before broader deploy fails the described rollout pattern: it stages the collector server infrastructure rather than phasing a defensive agent rollout onto labeled IR jump hosts before broader deploy. Phasing defensive agent rollout onto labeled municipal file servers before broader deploy fails the described rollout pattern: it targets file servers rather than phasing the rollout onto labeled IR jump hosts first. Phasing offline collector rollout onto labeled municipal IR jump hosts before broader deploy fails the described rollout pattern: it stages an offline collector rather than phasing a defensive agent rollout onto labeled IR jump hosts before broader deploy.

Exam caveat: Phased rollout should include success criteria (CPU/memory impact, successful collections, access control verified) before ring expansion. Labeling jump hosts in CMDB/tags prevents accidental targeting of production fare devices. Powerful IR tooling needs strict RBAC—staging is necessary but not sufficient without access control.

Operational check: Tag IR jump hosts; deploy collectors only to that tag initially; run tabletop collection tests; review logs for credential exposure; expand rings with change tickets; and ban phasing defensive agent rollout onto labeled municipal file servers before broader deploy, which targets the wrong host type and is not the phased rollout pattern.