> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/capabilities/program-management.md).

# Campaigns and Strategy

## Overview

Detecting and fixing vulnerabilities is only useful if the right work happens in the right order, with the right people, at the right time. Security Program Management is the part of Nullify that runs your security program the way a security engineering lead would: it maintains a prioritized backlog across every capability, monitors emerging threats, understands who owns what and how much they have on their plate, and drives work to completion through campaigns — opening PRs, filing tickets, nudging, and escalating.

## Campaigns

A **campaign** is how Nullify organizes a body of security work toward an objective — "eliminate leaked secrets," "upgrade the dependencies affected by this CVE," "harden our Terraform." Campaigns are the unit you see and steer in the dashboard and API. In the dashboard, campaigns have their own **Campaigns** page, and the quarterly goals they serve are on the **Strategy** page.

### How a campaign runs

1. **Detect** — Nullify proposes campaigns from your current backlog, threat intelligence, and organizational risk, tailored to what it actually found. There's no fixed catalog of templates to pick from.
2. **Decide** — a security leader accepts or dismisses each proposed campaign, or creates one, and sets its scope, dates and story-point limit. What Nullify may do while executing it — open PRs, file tickets, or just notify — comes from the program's [ground rules](#ground-rules).
3. **Execute** — Nullify assigns work to the right owners, opens fix PRs, creates and updates tickets, and escalates when progress stalls.
4. **Report** — progress is tracked in real time: findings in scope, resolved vs. remaining, time to resolution, per-team progress, and SLA compliance.

<figure><picture><source srcset="https://3946391995-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FId2OtLCL6O6V3XSRYxtr%2Fuploads%2Fgit-blob-94e6d3e0f3ff5040ea82a70035036655585e14c0%2Fremediation-campaigns-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://3946391995-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FId2OtLCL6O6V3XSRYxtr%2Fuploads%2Fgit-blob-cf189ff7dcb04461f4fd4d55f7823def6738322c%2Fremediation-campaigns.png?alt=media" alt="Remediation campaigns"></picture><figcaption><p>Scope, progress and PRs per campaign.</p></figcaption></figure>

### Scoping a campaign

Campaigns can target work by finding type, priority, repository, team, file owner, specific CWEs or CVEs, or a combination, or cover a hand-picked list of findings. Campaign targeting currently covers code, dependency, container, secret, supply-chain, and pentest findings.

Common campaign themes Nullify generates include eliminating credential leaks, upgrading vulnerable dependencies, hardening Terraform, closing OWASP Top 10 gaps, and meeting compliance requirements (PCI-DSS, HIPAA, SOC 2) — but every campaign is generated to fit what Nullify finds, not chosen from a fixed list.

### The Campaigns page

**Campaigns** lists every campaign. Once you have campaigns, portfolio totals and the **Latest portfolio update by Nullify** sit above the list. Switch between two views:

* **Grid** — one card per campaign, with its stage (**Scoped**, then **Executing** or **Paused**, then **Closed**), a bar of its findings split into fixed, closed without a fix, in progress and backlog, and counts of its PRs, messages, tickets, story points and escalations. **Open campaign** opens its detail page.
* **Board** — campaigns in lanes by status. The **Active** and **Ended** lanes are always shown. **Scheduled**, **Draft**, **Proposed**, **Paused**, **Cancelled**, **Superseded** and **Inactive** lanes appear only when a campaign has that status.

A proposed campaign shows **Accept** and **Dismiss** where it is listed; you can also decide it on the [Strategy page](#the-strategy-page).

### Creating a campaign

**New campaign** needs the finding-write permission. The dialog has two steps.

1. Describe the campaign:
   * **Name** and **Goal** are required.
   * **Start** is pre-filled with today; the campaign starts at 00:00 UTC on that day. A future start date schedules the campaign.
   * **End** is pre-filled 90 days after today and includes the full selected day in UTC. Turn on **No end date** for an open-ended campaign.
   * **Story point limit** is the campaign's story-point budget: the most fix effort it will take on. It defaults to 1,000.
2. Select **Next: scope** and choose which findings are in scope:
   * **Match a filter** scopes by **Finding type**, **Priority**, **Repository**, **Team**, **File owner**, **CWE** and **CVE**, and shows how many findings currently match. Findings that match later join automatically. The filter starts at urgent code and dependency findings. **Start from a findings view** applies that preset or one of your saved Findings views. A filter that narrows nothing takes on the whole backlog, and the dialog warns you before you save it.
   * **Pick findings** covers exactly the findings you select. The list is fixed, so later matches are not added.

Select **Create campaign** to save it. You can change a campaign's details and scope later with **Edit**.

### Campaign detail

Opening a campaign shows its goal, **Why Nullify picked these findings** for campaigns Nullify generated, and a progress strip: findings **In scope**, **Fixed**, **Closed without a fix**, **In progress** and **Backlog**, plus **PRs opened**, **PRs merged**, **Merge-ready rate**, **Mean time to fix** and **Modelled effort** (estimated at 5 minutes per story point).

With the finding-write permission you can **Edit** the campaign, **Add findings**, or **Delete** it, and, depending on its status, **Pause**, **Resume** or **End now**. Pausing stops Nullify opening PRs and tickets for the campaign and keeps its history. Ending moves its end date to today. Deleting removes the campaign and its progress history, but its findings stay in the backlog.

The detail page has these tabs:

* **Details** — the **Latest update by Nullify**, **Progress over time**, and **Agent run history**: each run Nullify made for the campaign, with its state and time. Open a run to read its narrative or error. Below them, **Reach** shows the priorities, finding types, repositories, teams and people the campaign covers, **Activity** shows what is happening, and **Rollup** shows agent runs, story points consumed and the remaining effort estimate. Last is **Developer engagement**, a per-developer table of DMs sent, direct nudges, replies, items open and closed, reply status and last interaction from the campaign's latest DM chat.
* **Findings** — the findings in scope. Open one to see its full detail without leaving the campaign.
* **Lookback** — shown, and opened first, once a campaign has ended. It is a retrospective: what happened, the PR merge rate, open pull requests, story points consumed, time to fix by remediation stage, a burn-down of campaign findings remaining, SLA by team, and the closed findings. **Start follow-on** (finding-write permission) creates a new campaign, starting today, that works the findings from this one that are still open.

## The Backlog

Nullify maintains a single curated backlog that combines findings from across the platform — code vulnerabilities, vulnerable dependencies and containers, and leaked secrets from [code review](https://docs.nullify.ai/capabilities/code-reviews.md), supply-chain risks from [SCPM](https://docs.nullify.ai/capabilities/scpm.md), and validated findings from [pentests](https://docs.nullify.ai/capabilities/pentests.md). [Bug hunt](https://docs.nullify.ai/capabilities/bug-hunts.md) findings are ticketed and tracked on their own pages rather than planned from this backlog. [Cloud audit](https://docs.nullify.ai/capabilities/cloud-audits.md) findings are too, unless cloud posture fixes are enabled for your workspace, in which case campaigns can plan them.

The backlog is ordered by an overall **priority score** (0–100) that weighs severity, exploitability, reachability, and business impact together — not raw CVSS alone. Resolved findings drop off automatically, and each remaining finding is linked to the PRs and tickets tracking its remediation so status stays current. See [Triage](https://docs.nullify.ai/capabilities/triage.md) for how findings are scored.

## Threat Intelligence

Nullify researches newly disclosed vulnerabilities and supply-chain compromises for all customers and assesses each one against your environment as a **threat investigation**. A confirmed exposure to a critical, known-exploited vulnerability with a fixed release opens a remediation campaign. See [Threat Intelligence](https://docs.nullify.ai/capabilities/threat-intelligence.md).

## Ownership and Capacity

Good routing depends on knowing who owns what and who's overloaded.

* **Ownership** comes from CODEOWNERS, commit history, service metadata, and connected sources like [Compass](https://docs.nullify.ai/connectors/compass.md) and your team structure.
* **Capacity** is a lighter-weight, qualitative read: Nullify considers how many open PRs and assigned tickets a person already has, and their recent history of merging and closing work, so it can route new work to people who can actually take it on and avoid piling onto someone who's swamped.

Nullify respects team boundaries — it won't reassign work across teams without approval. When it can't determine ownership, it raises an [action item](https://docs.nullify.ai/capabilities/working-with-nullify.md) asking you to assign a team.

## Assigning and driving work

When Nullify assigns and sequences work, it weighs the finding's priority (severity, exploitability, reachability, business impact), current ownership, and team capacity. It then drives each item to completion:

* Opens [autofix](https://docs.nullify.ai/capabilities/remediations.md) pull requests and assigns reviewers using the ownership cascade described in Remediations.
* Creates and updates tickets in Jira and other trackers.
* Monitors open security PRs, comments with context, and escalates the ones that stall.
* Tracks each finding's status as its PR or ticket moves.

## Security Program Strategy

Beyond day-to-day work, Nullify maintains a rolling **strategy** — a set of quarterly security goals for your program. The strategy is versioned (so you can see how it's evolved), editable, and Nullify can generate a proposed strategy from your current posture and risk profile. It gives the program a direction that individual campaigns ladder up to.

### The Strategy page

**Strategy** shows the plan quarter by quarter, with the current quarter marked **Current**. A line above the plan gives its status, the date it was settled, its version, and **Drafted by Nullify** when Nullify wrote it. Figures quoted in the plan are as of that date. A goal can cite memories and files from the **Vault** (see [Vault](https://docs.nullify.ai/capabilities/context-engine.md#vault)); each citation appears as a numbered marker that opens the linked source.

<figure><picture><source srcset="https://3946391995-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FId2OtLCL6O6V3XSRYxtr%2Fuploads%2Fgit-blob-f841f36c750ae1a41077f7e6045bf2042f323371%2Fcampaign-strategy-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://3946391995-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FId2OtLCL6O6V3XSRYxtr%2Fuploads%2Fgit-blob-87e936c0c0200806d2e76b7c80b4b59c6be4b17c%2Fcampaign-strategy.png?alt=media" alt="Security program strategy with quarterly objectives"></picture><figcaption><p>Quarterly objectives that guide campaigns.</p></figcaption></figure>

**Edit** opens the plan as one document with a fixed heading per quarter. Write each quarter's outcomes beneath its heading, use @ to link supporting context, and select **Save strategy**. All four quarter headings must stay, and at least one quarter needs a goal. When the saved plan has no goal for the current quarter, **Align to current quarter** opens a draft over the current four quarters that keeps the goals of overlapping quarters; add a current-quarter outcome before you save it. With no strategy yet, **Start strategy** begins one. Changing the strategy needs the configuration-write permission.

**Proposed campaigns** lists the campaigns Nullify has drafted against the strategy, each awaiting a decision. Each proposal shows:

* the quarter goal it serves
* the findings in scope, by severity, and the repositories they are in
* **Why this campaign**: Nullify's reasoning
* the pace it needs in findings per week, compared with your teams' recent pace where Nullify has one, rated **Achievable**, **Stretch** or **Unrealistic**

**Accept** starts the campaign. **Dismiss** cancels it after you confirm, and a dismissed proposal cannot be reopened from this page. Both need the finding-write permission. Findings left out of every proposal are summarized under **Deferred**, with the reasons and a link to them in Findings.

## Ground Rules

You set Manager’s action boundaries with program autonomy policy, tenant and team ground rules, and blocked action types. Controls cover PRs, tickets, messages, and reviewer selection; they do not disable upstream triage. See [Ways of Working](https://docs.nullify.ai/configuration/configuration-manager.md) for the distinct controls and API paths, including settings absent from the current dashboard.

## Metrics & Reporting

Track the program's current state with:

* **Mean Time to Remediate (MTTR)** — average time from discovery to fix, plus related mean-time variants.
* **Finding counts** — current backlog totals.
* **Campaign progress** — resolved vs. remaining, per team.

The dashboard **Overview** also charts findings introduced and fixed by month. Each campaign shows its progress over time, and an ended campaign's **Lookback** tab adds a burn-down of its findings.

## How it connects

Campaigns and Strategy sit at the center of Nullify: it reads triaged findings and the [Context Engine](https://docs.nullify.ai/capabilities/context-engine.md), drives [Remediations](https://docs.nullify.ai/capabilities/remediations.md), routes through your [ticketing](https://docs.nullify.ai/connectors/jira.md) and [messaging](https://docs.nullify.ai/connectors/slack.md) connectors, and raises [action items](https://docs.nullify.ai/capabilities/working-with-nullify.md) when it needs a human decision.

## Automation API

The [Manager API](https://docs.nullify.ai/api-reference/api-reference/manager.md) covers campaigns and run history, strategies and versions, proposals and decisions, action items, plans, state, metrics, chat audit, and escalation configuration. Strategy and campaign proposals arrive as named action items; use their decision workflow to approve or reject them.
