Type ID: taraRecord
Label: TARA Record
Icon: type_risk.gif
Risksheet role: Primary row type (riskType)
Custom Fields
Threat Identification Fields
| Field ID | Name | Type | Risksheet Column | Hierarchy Level |
|---|
ciaxProperty | CIAx Property | enum:taraRecord-ciaxProperty | ciaxProperty | 2 |
damageScenario | Damage Scenario | text/plain | damageScenario | 3 |
threatPath | Threat Path | text/plain | threatPath | 5 |
ciaxProperty field captures which security dimension is threatened. See CIAx Security Properties for allowed values.
The damageScenario field is free-text describing the harm that results if the threat is realized. It pairs with taraImpact as the qualitative rationale for the severity rating.
The threatPath field describes the specific attack vector — the sequence of steps an attacker must complete. This is the lowest level of the Risksheet’s 5-level hierarchy.
Attack Feasibility Factor Fields
Five fields implement the EVITA Attack Potential methodology referenced in ISO/SAE 21434 Annex G:
| Field ID | Name | Type | Risksheet Header | Score Range |
|---|
attackTime | Elapsed Time | enum:taraRecord-attackTime | TIME | 0—19 |
attackExpertise | Specialist Expertise | enum:taraRecord-attackExpertise | EXP | 0—8 |
attackKnowledge | Knowledge of Item | enum:taraRecord-attackKnowledge | KNOW | 0—11 |
attackWoo | Window of Opportunity | enum:taraRecord-attackWoo | WOO | 0—10 |
attackEquipment | Equipment | enum:taraRecord-attackEquipment | EQP | 0—9 |
feasibilityFormula in Risksheet sums all five scores to compute the aggregate taraFeasibility. See Attack Feasibility Factor Enums for all values and scores.
Risk Assessment Fields
| Field ID | Name | Type | Computed | Risksheet Column |
|---|
taraImpact | Impact | enum:taraRecord-taraImpact | No | taraImpact |
taraFeasibility | Attack Feasibility | enum:taraRecord-taraFeasibility | Yes (formula) | taraFeasibility |
taraVerdict | Risk Verdict | integer | Yes (formula) | taraVerdict |
taraImpact field is manually set by the analyst. Values: negligible, moderate, major, severe. See TARA Impact Levels.
The taraFeasibility field is computed by the feasibilityFormula:
| Aggregate Score | Feasibility Level |
|---|
| 0—13 | high (High) |
| 14—19 | medium (Medium) |
| 20—24 | low (Low) |
| 25+ | veryLow (Very Low) |
taraVerdict field is computed by the verdictFormula (Impact x Feasibility matrix):
| Impact \ Feasibility | Very Low | Low | Medium | High |
|---|
| Severe | 3 | 4 | 5 | 5 |
| Major | 2 | 3 | 4 | 5 |
| Moderate | 1 | 2 | 3 | 4 |
| Negligible | 1 | 1 | 1 | 1 |
Risk Treatment Fields
| Field ID | Name | Type | Risksheet Column |
|---|
treatmentChoice | Treatment Choice | enum:taraRecord-treatmentChoice | treatmentChoice |
treatmentStatus | Treatment Status | enum:taraRecord-treatmentStatus | treatmentStatus |
taraClaims | Claims | text/plain | taraClaims |
taraControls | Controls | text/plain | (not in Risksheet views) |
treatmentChoice field records the risk treatment strategy:
| Value | When to Use | Required Follow-up |
|---|
reducing | Apply controls to reduce risk | Link a cybersecurityGoal + riskControl |
avoiding | Eliminate the threat source | Link a cybersecurityGoal |
sharing | Transfer risk to another party | Document rationale in taraClaims |
retaining | Accept risk after analysis | Document rationale in taraClaims |
The Risksheet goalHighlight decorator shows an orange outline when treatmentChoice is Reducing or Avoiding but no cybersecurityGoal is linked. The claimHighlight decorator shows an orange outline when treatmentChoice is Retaining or Sharing but taraClaims is empty.
Cell Decorators
| Decorator | Field | Behavior |
|---|
impactDecorator | taraImpact | Color by severity: negligible (green), moderate (amber), major (orange), severe (red) |
feasibilityDecorator | taraFeasibility | veryLow/low (green), medium (amber), high (red) |
verdictDecorator | taraVerdict | 5-color gradient: V1 (#4CAF50) through V5 (#b71c1c) |
rowHeaderVerdict | Row header | Entire row header colored by verdict level |
goalHighlight | cybersecurityGoal | Orange outline when goal is required but missing |
claimHighlight | taraClaims | Orange outline when claim is required but missing |
Link Roles
| Role | Direction | Target Type |
|---|
hasStakeholder | outgoing | stakeholder |
hasThreatScenario | outgoing | threatScenario |
hasCybersecurityGoal | outgoing | cybersecurityGoal |
mitigates | incoming (from riskControl) | — |
taraRecord-form-layout.xml), the following fields are read-only:
- Input fields:
attackTime, attackExpertise, attackKnowledge, attackWoo, attackEquipment, taraImpact, damageScenario, threatPath
- Computed fields:
taraFeasibility, taraVerdict, description
All editing is performed exclusively through the Risksheet interface.
Risksheet Hierarchy Position
The taraRecord participates in a 5-level hierarchy within the Risksheet:
| Level | Column | Grouped By |
|---|
| 1 | stakeholder | Who is affected |
| 2 | ciaxProperty | What security property |
| 3 | damageScenario | What harm results |
| 4 | threatScenario | How the threat manifests |
| 5 | threatPath | Specific attack vector |
