What You Will Achieve
By the end of this tutorial you will have a fully configured TARA project with:
- 8 work item types (
taraRecord, cybersecurityGoal, systemElement, threatScenario, stakeholder, riskControl, sysReq, testCase)
- 5 TARA-specific link roles (
hasThreatScenario, hasStakeholder, hasCybersecurityGoal, derivesRequirement, mitigates)
- 1 Risksheet template (TARATemplate) with 22 columns, 7 views, and 3 formulas
- Dashboard pages: Project Home, Risks Home, TARA Report, Cybersecurity Case
- Shared catalogs for Threat Scenarios and Stakeholders
- Document workflow for risk specification approval
Prerequisites
| Requirement | Details |
|---|
| Polarion ALM | Version 2304 or later |
| Nextedy Risksheet | Licensed and installed on the server |
| User role | Project administrator |
| Solution package | TARA solution archive (.zip) from Nextedy |
Steps
Step 1: Create a New Polarion Project
- Open Polarion Administration and select Create Project.
- Enter a project name (e.g., “TARA Demo”) and set the tracker prefix (e.g.,
TR).
- Assign a project lead and set the project color.
- Save the project.
If you are adding TARA to an existing project, skip to Step 2. The solution adds new work item types and configurations without overwriting existing ones.
Step 2: Import the Solution Package
- Obtain the TARA solution package from Nextedy.
- In Polarion Administration, navigate to Repository and import the solution SVN structure into your project.
- The import installs:
- Work item type definitions in
.polarion/tracker/fields/
- Custom field configurations for
taraRecord, cybersecurityGoal, systemElement, and riskControl
- Enumeration files for all TARA-specific enums (CIAx properties, impact levels, feasibility factors, treatment choices)
- Link role definitions with type constraints
- Form layouts for each work item type
- The TARATemplate risksheet configuration in
modules/RiskTemplates/TARATemplate/
- Dashboard wiki pages in
.polarion/pages/
- Document workflow for
riskSpecification type
Step 3: Verify Work Item Types
Open the project tracker and confirm all 8 types appear in the type selector:
| Type | Purpose |
|---|
systemElement | Components in the vehicle architecture |
taraRecord | Individual risk assessment records |
threatScenario | Named threat scenarios (catalog items) |
stakeholder | Affected entities (catalog items) |
riskControl | Countermeasures that mitigate threats |
cybersecurityGoal | High-level protection objectives with CAL |
sysReq | Cybersecurity and system requirements |
testCase | Verification test cases |
Step 4: Verify the Risksheet Template
- Navigate to Risksheets in the sidebar.
- Confirm that TARATemplate appears in the template list.
- Open the template and verify that 7 views are listed: Overview, 1. Identify Threats, 2. Assess Feasibility, 3. Risk Assessment, 4. Risk Treatment, 5. Req & Verification, Full View.
Step 5: Verify Dashboards
Open each dashboard page and confirm it loads without errors:
| Dashboard | Navigation Path |
|---|
| Project Home | Project sidebar > Home |
| Risks Home | Wiki > Risks > Home |
| TARA Report | Wiki > Risks > TARA Report |
| Cybersecurity Case | Wiki > Risks > Cybersecurity Case |
Dashboards display live statistics. Before any TARA records or system elements exist, all counts will show zero. This is expected.
Step 6: Set Up Initial Catalogs
- Open the Stakeholder Catalog document at
Risks/StakeholderCatalog. Add stakeholder work items representing entities affected by cybersecurity threats (e.g., Vehicle Occupants, Road Users, Vehicle Owner, Service Technician).
- Open the Threat Scenario Catalog at
Risks/ThreatScenarioCatalog. Add threatScenario work items for common threats relevant to your system.
Step 7: Create the System Element Hierarchy
- Open the SYSTEM-ELEMENTS document in the
_default space.
- Add
systemElement work items with the elementType custom field set to system, subsystem, or component.
- Use the
parent link role to establish the hierarchy.
The TARA Demo project ships with a sample hierarchy for a Connected Electric Vehicle with ADAS. Review it as a reference for structuring your own system architecture.
Next Steps