Question

A security manager at a large organization launches a security campaign targeting 340 high-severity SQL injection alerts spread across 60 repositories. She wants to hold each development team accountable by giving them a shared context, a due date, and direct visibility into which alerts they own, so progress can be tracked centrally in Security Overview. Which combination of campaign configuration steps best achieves this goal?

Accepted Answer

Create the campaign with a due date and a description providing remediation guidance, then assign alerts to specific team members or teams so ownership and progress are tracked in Security Overview.

Answer

Bulk-dismiss all 340 alerts with the reason 'won't fix' and open a tracking issue in each of the 60 repositories to coordinate the work manually.

Answer

Create a cross-repository ruleset that blocks all merges to default branches until every SQL injection alert is resolved, without setting a due date.

Answer

Export the alerts to a SARIF file, distribute it to team leads over email, and ask each team to self-report completion percentages weekly.