Skip to content

Define optional/mandatory TARA elements #40

Description

@JuWu89

Please read and review the example of the Headlight TARA described in the attached ISO21434 specification from Annex H. Then represent the described TARA in the newest version of the RDX format. First create a comprehensive version of the described example in the RDX format using all elements described in its JSON schema (e.g. represent the described architecture with your architecture elements, model the attack steps with assumed likelihood and attack feasibility ratings, link all elements together (e.g. assets and attack steps to architecture elements), etc.). As a next step create an additional example using only the bare minimum of the JSON schema to represent the example from the ISO. Once finished, add both your examples to the examples folder. Then create an comparison report which elements are seen as mandatory as they are present in both your example versions and which ones only exist in the full example and are thus optional. Use this information to then adapt the schema to mark elements as mandatory/optional.

ISO_SAE21434.3_Annex-H-Example.pdf

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions