Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A CSIRT is the team an organisation makes responsible for handling security incidents. CERT means much the same thing, but the name is trademarked and the remit is usually national or sectoral.

What Are CSIRT and CERT?
A Computer Security Incident Response Team is the group an organisation holds accountable for receiving reports of security incidents, triaging them, coordinating the response, and learning from what happened. CERT — Computer Emergency Response Team — describes the same function, but the name belongs to Carnegie Mellon University, which registered it after establishing CERT/CC in 1988 in the aftermath of the Morris worm. Teams that use the CERT label generally do so under licence, which is why most corporate teams call themselves CSIRTs.
Beyond trademark, usage has settled into a rough convention. National and sectoral teams with a coordinating remit tend to be CERTs or national CSIRTs: they serve a constituency they do not control, issue advisories, and broker information between organisations. Teams inside a single organisation tend to be CSIRTs: they serve one constituency, they have authority over its systems, and they can order a host isolated. A third variant, the Product Security Incident Response Team or PSIRT, handles vulnerability reports about a vendor’s own products rather than attacks on its infrastructure — a distinction that matters enormously to anyone trying to report a flaw and reaching the wrong inbox.
The two are often conflated because they share people and tooling. A security operations centre monitors continuously and detects. A CSIRT responds, and only when something has been confirmed. In small organisations the same five people do both, wearing different hats on different days. In larger ones they are separate functions with a defined handover point, and the quality of that handover is usually what determines how quickly a serious incident is brought under control.
Teams that want to be trusted by peers usually seek recognition. Trusted Introducer, run under the TF-CSIRT umbrella in Europe, offers listed, accredited, and certified status, with certification assessed against the SIM3 maturity model across organisational, human, tools, and process parameters. FIRST, the Forum of Incident Response and Security Teams, has provided a global membership community since 1990 and publishes the CSIRT Services Framework, which is the most practical document available for defining what your team actually offers.
CERT-UK was folded into the NCSC when it opened in October 2016, and the NCSC now acts as the UK national technical authority, running the national incident management function and operating CiSP, its two-way intelligence sharing partnership with industry. Organisations can report incidents to it directly, and for nationally significant compromises it can draw on providers assured under its Cyber Incident Response schemes. None of that removes the organisation’s own obligations — reporting to the NCSC is not reporting to the Information Commissioner’s Office, and the 72-hour breach notification deadline runs regardless.
Start with authority and scope rather than tooling. Write down what counts as an incident, who the team serves, what it is empowered to do without further approval, and how it is reached at 02:00. Add a severity scheme, a small set of playbooks for the scenarios you actually face, and a named deputy for every named lead. Then exercise it. A CSIRT that has never run a scenario is a distribution list.
Our SOC maturation services cover the handover between detection and response, which is where most teams lose their first hour.
Functionally very little. CERT is a trademark held by Carnegie Mellon University, so teams using the name generally do so under licence, and in practice the label is associated with national or sectoral coordinating bodies. CSIRT is the generic term and is what most organisations call their internal response team. Both describe a group responsible for handling security incidents for a defined constituency.
It needs the function, not necessarily a dedicated team. Below a few hundred staff, that usually means a named incident lead, a documented escalation path, a severity scheme, and a retainer with a provider who can supply forensic capability at short notice. What does not work is assuming the IT manager will improvise, since the decisions required in the first hours are legal and commercial as much as technical.
A Product Security Incident Response Team handles vulnerability reports about the products a company sells, rather than attacks on its own infrastructure. It triages researcher submissions, coordinates disclosure, issues advisories, and ships fixes. Any organisation that distributes software or hardware needs one, and it should publish a clearly signposted contact route separate from its corporate incident inbox.
A hybrid model suits most organisations. Keep decision-making, business context, and the relationship with legal and regulators in-house, and buy surge capacity, deep forensic skills, and out-of-hours coverage. The common failure is signing a retainer and never exercising it, so the provider arrives without network diagrams, access, or a named contact who can authorise containment.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.