Skip to main content
Location: /polarion/#/project/{projectId}/wiki/Risks/TARA%20Report ISO/SAE 21434 Alignment: System Element Hierarchy and TARA Coverage

Document Header

FieldValue
TitleTARA Summary Report
SubtitleISO/SAE 21434 — System Element Hierarchy and TARA Coverage
Project IDLive from $projectId
Generated DatePage last-modified timestamp (YYYY-MM-DD)
Total TARA RecordsLive count of all taraRecord items
Subsystem CountLive 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:
VerdictClassificationAction Required
V1—V2AcceptableNo further action needed
V3Investigation RequiredRequires monitoring and documented justification
V4—V5UnacceptableAdditional cybersecurity controls required

Project-Level Summary Cards

Six color-coded KPI cards display the project-wide verdict distribution:
CardColorHex CodeMeaning
V1Green#4CAF50Acceptable — negligible risk
V2Light green#8BC34AAcceptable — low risk
V3Amber#FF9800Investigation required
V4Red#f44336Unacceptable — high risk
V5Dark red#b71c1cUnacceptable — critical risk
UnclassifiedGrey#5e6c84Analysis 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:
ConditionAlert TypeMessage
Any V4 or V5 recordsdanger (red)Unacceptable risks remain — additional controls required
V3 records exist (no V4/V5)warning (amber)Investigation-level risks require monitoring
All records V1 or V2success (green)All TARA records at acceptable risk levels

TARA Structure Tree

A three-level hierarchical table shows per-element verdict statistics:

Column Layout

ColumnWidthContent
Element / TARA30%System element name with link to Risksheet
Records7%Total taraRecord count for this element
V17%Count at verdict 1
V27%Count at verdict 2
V37%Count at verdict 3
V47%Count at verdict 4 (red highlight if > 0)
V57%Count at verdict 5 (red highlight if > 0)
N/A7%Count with no verdict (amber highlight if > 0)

Visual Highlighting

Cell StateBackgroundText Color
V4 or V5 > 0#ffebee (light red)#c62828 (dark red)
N/A > 0#fff3e0 (light amber)#f57c00 (amber)
All othersDefaultDefault

Hierarchy Levels

LevelCSS ClassElement Type
0nx-level-0System
1nx-level-1Subsystem
2nx-level-2Component
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.
ColumnContent
Module TitleLinked to Risksheet view
SubsystemSystem element name (resolved from subsystem document field)
Unacceptable CountNumber of V4 + V5 records (highlighted red)
Action RequiredFixed 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

QueryPurposeLucene
All TARA recordsVerdict statisticsproject.id:{pid} AND type:taraRecord
System elementsTree hierarchyproject.id:{pid} AND type:systemElement
TARA documentsModule lookuptype:riskSpecification AND systemElementId:{eid} AND project.id:{pid}
All TARA modulesAction itemsproject.id:{pid} AND space.id:Risks AND type:riskSpecification
Subsystem lookupSubsystem columnproject.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

MacroPurpose
#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

Source: Risks/TARA Report/page.xml