Comments for proposed Security VP(s)

[parkaneric]

Many thanks for the proposed VPs!
This discussion thread shall foster communication to bring the VPs to a release-able state.

General comment:

• the proposed VPs enables to perform a throughout security analysis. However, I am afraid each organization has to follow its specific process and tools e.g. SAVe for defence projects. Keeping this in mind, VPs in SAF should focus on architectural concerns w.r.t. safety and security: Risk identification and safety/security requirement (traceability) as a result of a chosen mitigation. The gap between is managed usually in a specialized and dedicated tool. However, proposed VPs could be optional in SAF …
• multiple new stereotypes are introduced. Could be existing stereotypes used or extended with tags? See comments for VPs below.
• in general it is hard to understand a comprehensive thread from impact analysis to risk analysis to risk scenarios. Please provide the related VPs per security VP and provide additional documentation.

F7_SECT_Security Context Viewpoint

• Is the security context just another but rather specific Logical Context? Is there really a need for another stereotype?
• Adversary could be another specific Logical Context Element which is defined as abstract?
• Assumptions could be raison d'etre for a new dedicated VP in Common Domain?
• Example chapter: why are external systems aggregated as FFDS_External Systems? Could existing stereotypes (SAF_LogicalExternalSystem) have a standard tag (Security Environment Element)?

F7_ASID_Asset Identification Viewpoint

• the viewpoint seems to expose elements to declare them as assets which need protection. It would be nice to have a filter/search capability, however the only way to define a query to check if an element is exposed on a F7_ASID diagram. Alternatively, a standardized tag value for System Functions etc would enable this? The VP would be presented as a list.
• Furthermore also logical elements as part of a SoI could be a potential asset?

F7_F7_THSC Threat Szenario Viewpoint

• typo: it should read sceanrio