What are priority intelligence requirements?
Priority intelligence requirements (PIRs) are the most important questions an organization needs its threat intelligence program to answer. They turn "tell us about threats" into specific, answerable questions tied to business risk, and they decide what the intelligence team collects, analyzes and reports.
Without PIRs, intelligence programs drift toward whatever is loudest in the news. With them, every feed, report and hour of analysis can be checked against a clear purpose.
What makes a good PIR?
- Tied to a decision. Someone will act differently depending on the answer.
- Specific. It names the asset, sector, threat type or time frame.
- Answerable. Available sources can realistically provide an answer.
- Owned. A stakeholder asked for it and will review the answers.
- Time-bound. It is reviewed on a schedule and retired when it no longer matters.
Examples of priority intelligence requirements
Each example below turns a vague question into a PIR someone can act on.
- Instead of "What are the latest threats?" ask "Which ransomware groups are targeting organizations in our sector and region this quarter, and how are they getting initial access?" The SOC, detection engineering and the CISO act on the answer.
- Instead of "Are we on the dark web?" ask "Are credentials, access or data belonging to our organization or key suppliers being offered for sale?" The identity team and the SOC act on the answer.
- Instead of "What vulnerabilities matter?" ask "Which vulnerabilities in software we run are being actively exploited, and by whom?" Vulnerability management acts on the answer.
- Instead of "Who is targeting us?" ask "Which state-sponsored groups have targeted companies like ours in the last year, and what techniques did they use?" The CISO and detection engineering act on the answer.
How do you write PIRs?
- Interview stakeholders. Ask the CISO, SOC lead, risk, fraud and business leaders what decisions they make and what would change them.
- Draft five to ten PIRs. More than that and the program loses focus.
- Break each PIR into specific questions that sources can answer, often called specific intelligence requirements.
- Map sources to questions. Identify which feeds, communities and internal data can answer each one, and where you have gaps.
- Agree on outputs. Decide how answers will be delivered: alerts, detections, bulletins or briefings. See threat bulletins and reporting.
- Review quarterly. Retire PIRs that no longer drive decisions and add new ones.
How do PIRs connect to the SOC and to AI agents?
PIRs give everyone a shared filter. The SOC uses them to decide which intelligence to fuse into detections. CTI uses them to decide what to collect. And AI agents that process intelligence use them to decide which reports matter, as described in agentic CTI. The feedback loop runs the other way too: what the SOC sees should update the PIRs. See unifying CTI and SOC teams.
Frequently asked questions
How many PIRs should we have?
Most programs work best with five to ten. Each one should have an owner and sources that can answer it.
Who owns PIRs?
The CTI lead usually maintains them, but each PIR should have a business or security stakeholder who asked for it and reviews the answers.
How often should PIRs change?
Review them quarterly and after major events, such as a significant incident, a new market or a big change in the threat picture.
Anomali and Priority Intelligence Requirements (PIRs): A Practical Guide
Anomali ThreatStream Next-Gen helps teams align collection and curation to their intelligence priorities, and Anomali's agentic AI can track reporting against those priorities.
Request a demo to see priority-driven intelligence in Anomali.
Read next