Location: /polarion/#/project/{projectId}/wiki/Risks/TARA%20Report
ISO/SAE 21434 Alignment: System Element Hierarchy and TARA Coverage
| Field | Value |
|---|
| Title | TARA Summary Report |
| Subtitle | ISO/SAE 21434 — System Element Hierarchy and TARA Coverage |
| Project ID | Live from $projectId |
| Generated Date | Page last-modified timestamp (YYYY-MM-DD) |
| Total TARA Records | Live count of all taraRecord items |
| Subsystem Count | Live count of subsystem-level system elements |
Verdict Classification Guide
An informational alert box at the top of the report explains the three verdict classification bands:
| Verdict | Classification | Action Required |
|---|
| V1—V2 | Acceptable | No further action needed |
| V3 | Investigation Required | Requires monitoring and documented justification |
| V4—V5 | Unacceptable | Additional cybersecurity controls required |
Project-Level Summary Cards
Six color-coded KPI cards display the project-wide verdict distribution:
| Card | Color | Hex Code | Meaning |
|---|
| V1 | Green | #4CAF50 | Acceptable — negligible risk |
| V2 | Light green | #8BC34A | Acceptable — low risk |
| V3 | Amber | #FF9800 | Investigation required |
| V4 | Red | #f44336 | Unacceptable — high risk |
| V5 | Dark red | #b71c1c | Unacceptable — critical risk |
| Unclassified | Grey | #5e6c84 | Analysis incomplete (no verdict set) |
Records without a taraVerdict value are counted as Unclassified, indicating the analysis is not yet complete.
Conditional Risk Status Alert
A contextual banner appears below the summary cards based on project-wide verdict state:
| Condition | Alert Type | Message |
|---|
| Any V4 or V5 records | danger (red) | Unacceptable risks remain — additional controls required |
| V3 records exist (no V4/V5) | warning (amber) | Investigation-level risks require monitoring |
| All records V1 or V2 | success (green) | All TARA records at acceptable risk levels |
TARA Structure Tree
A three-level hierarchical table shows per-element verdict statistics:
Column Layout
| Column | Width | Content |
|---|
| Element / TARA | 30% | System element name with link to Risksheet |
| Records | 7% | Total taraRecord count for this element |
| V1 | 7% | Count at verdict 1 |
| V2 | 7% | Count at verdict 2 |
| V3 | 7% | Count at verdict 3 |
| V4 | 7% | Count at verdict 4 (red highlight if > 0) |
| V5 | 7% | Count at verdict 5 (red highlight if > 0) |
| N/A | 7% | Count with no verdict (amber highlight if > 0) |
Visual Highlighting
| Cell State | Background | Text Color |
|---|
| V4 or V5 > 0 | #ffebee (light red) | #c62828 (dark red) |
| N/A > 0 | #fff3e0 (light amber) | #f57c00 (amber) |
| All others | Default | Default |
Hierarchy Levels
| Level | CSS Class | Element Type |
|---|
| 0 | nx-level-0 | System |
| 1 | nx-level-1 | Subsystem |
| 2 | nx-level-2 | Component |
Each element row links to its TARA module in Risksheet view. Elements without a TARA show an orange “Missing TARA” warning label.
TARA Coverage Summary Alert
After the structure tree, an info alert displays coverage statistics:
{totalElements} system elements | {existingCount} TARAs exist | {missingCount} TARAs missing
- existingCount: System elements with a matching
riskSpecification document (via systemElementId)
- missingCount: System elements with no matching TARA document
Unacceptable Risk Action Items
This section renders only when V4 or V5 records exist in the project. It provides an actionable list of TARA modules requiring immediate attention.
| Column | Content |
|---|
| Module Title | Linked to Risksheet view |
| Subsystem | System element name (resolved from subsystem document field) |
| Unacceptable Count | Number of V4 + V5 records (highlighted red) |
| Action Required | Fixed text: review and add controls |
If no V4/V5 records exist, this entire section is hidden. The summary cards showing V4=0 and V5=0 are the only indicator that no action items are pending.
Data Queries
| Query | Purpose | Lucene |
|---|
| All TARA records | Verdict statistics | project.id:{pid} AND type:taraRecord |
| System elements | Tree hierarchy | project.id:{pid} AND type:systemElement |
| TARA documents | Module lookup | type:riskSpecification AND systemElementId:{eid} AND project.id:{pid} |
| All TARA modules | Action items | project.id:{pid} AND space.id:Risks AND type:riskSpecification |
| Subsystem lookup | Subsystem column | project.id:{pid} AND type:systemElement AND elementType.KEY:subsystem |
All taraRecord items are loaded into memory once and iterated in nested loops for each system element. On large projects with many TARA records, this pattern may have performance implications.
Velocity Macros Used
| Macro | Purpose |
|---|
#nxDocHeader() / #nxDocHeaderEnd() | Report header with title and metadata |
#nxDocInfoItem() | Metadata key-value pairs in header |
#nxSummaryCards() / #nxSummaryCard() | Verdict KPI tiles |
#nxAlert() | Conditional banners (danger/warning/success/info) |
#nxNavTableStyles() | Hierarchical table CSS (nx-nav-tree) |
#nxSection() / #nxSubsection() | Content sections |
#nxSpaceFooter() | Standard Nextedy footer |
Related Pages
Source: Risks/TARA Report/page.xml