Threat Catalogs
A threat catalog collects threat classes: kinds of attack, each with the security properties it threatens, the kinds of system elements it acts on and a feasibility rating. TARAs refer to these classes, so a rating maintained in the catalog is reused in every TARA that uses it. What threat classes are and how a TARA uses them is explained in Threat Catalog.

A catalog is a repository
A threat catalog is a repository of the type THREATS_CATALOG in your organization. You find, share and delete it like any other repository, as described in Repositories. A new threat catalog starts with version 1.0.0 and the six STRIDE threat classes.
Your organization creates and maintains its own threat catalogs. Ask your administrator whether a catalog of the ASRG community is available in your installation.
Versions and change requests
A threat catalog is not changed directly. Changes are suggested and collected in a change request. When the change request is merged, the catalog gets a new version, for example 1.1.0. Earlier versions stay available.
How a TARA uses a catalog
When you create a TARA, you can choose a catalog and one of its versions. The TARA keeps working with that version, also when the catalog gets new ones. The Catalog page of the TARA shows which version it uses and whether a newer one is available, and lets you update the TARA to it. Both are described in Create a repository and in the TARA's Catalog page.
Who may do what
What you can do in a threat catalog depends on your role in its repository, Catalog Maintainer, Catalog Contributor or Catalog Viewer, and on your role in the organization. Seeing all change requests and merging or rejecting them is up to those who maintain the catalog. The roles are listed in Roles and permissions.
This chapter shows how to:
- Work with threat classes: browse them, and add, change or delete them as a suggestion
- Select a catalog version
- Create, merge or reject change requests