# Incident response roles and responsibilities

Guide, read 16 November 2026

**The short answer.** An incident response team needs an executive sponsor, an incident lead, a technical lead, a communications lead, a legal and privacy lead, and support from human resources, physical security and system owners. NIST SP 800-61 Rev. 3 describes these role families. This page, read on 16 November 2026, gives each role's decisions.

## Who is on an incident response team?

The team is a set of roles, not a department. NIST SP 800-61 Rev. 3, section 2.2, gives examples: leadership, incident handlers, technology professionals, legal, public affairs and media relations, human resources, physical security and facilities management, and asset owners. Incident handlers may be on staff, on contract, or available when needed.

Small organizations often combine roles and use an outside provider for handlers; the plan should still name each role and a deputy.

| Role | Decides | NIST role family |
| --- | --- | --- |
| Executive sponsor | Funding; shutting down or rebuilding critical services | Leadership |
| Incident lead | Declaring and closing; priorities | Incident handlers |
| Technical lead | Containment and recovery actions | Technology professionals |
| Communications lead | Every message; spokesperson | Public affairs and media relations |
| Legal and privacy lead | Notice duties and clocks; law enforcement contact | Legal |
| Human resources | Cases involving employees | Human resources |
| Facilities | Physical access to sites and devices | Physical security |
| System and data owners | Recovery priority for their assets | Asset owners |

Who is on an incident response team?

## What should be said about outside providers?

NIST describes a shared responsibility model: the contract should define the provider's responsibilities, information flows, coordination and authority to act, including restrictions such as sharing sanitized incident information with other customers or deactivating services to contain an incident.

Service providers can hold privileged access, so NIST advises considering the risk of malicious insiders or provider compromise, and using confidentiality agreements and contract clauses.

## How do you assign roles in a small team?

Name one person per role even when the same person holds several, and name a deputy for each. Check that no single absence leaves a role empty. Print the table and put it in the plan, section 2 of the [template](/).

For a business with no security staff, the [small business template](/templates/incident-response-plan-template-for-small-business/) reduces the roles to an incident lead, outside help and a decision-maker for money.

## Related pages

- [Incident response plan: what it contains and how to build one](/plans/)
- [Free incident response plan template](/)
- [Incident response plan vs business continuity plan](/plans/incident-response-plan-vs-business-continuity-plan/)
- [Incident response policy: what it is and who approves it](/plans/incident-response-policy/)
- [Incident response severity levels](/plans/incident-response-severity-levels/)
- [What is an incident response plan?](/plans/what-is-an-incident-response-plan/)
- [Incident response steps: the order and who does what](/steps/)
- [Incident response playbook: what it is and how to build a library](/playbooks/)

## Sources

- NIST SP 800-61 Rev. 3, full text (April 2025): https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/plans/incident-response-roles-and-responsibilities/
