You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Activity D-TA-1-B.yml
Always make sure to persist the outcome
--> Always persist the outcome
Activity D-TA-2-B.yml
Capture the threat modeling artifacts with tools that are used by your application teams.
--> Capture the threat modeling artifacts with tools used by your application teams.
the developer security culture. Reusable risk patterns,
--> the developer security culture. Reusable risk patterns,
Question D-TA-2-B.yml
Do you use a standard methodology, aligned on your application risk levels?
--> Do you use a standard methodology, aligned with your application risk levels?
You capture the threat modeling artifacts with tools that are used by your application teams
--> You capture the threat modeling artifacts with tools used by your application teams
You regularly (e.g., yearly) review the existing threat models to verify that no new threats are relevant for your applications
--> You review the existing threat models to verify that no new threats are relevant for your applications at least yearly
History from old repo: @SebaDele opened this issue on Dec 20, 2019 @SebaDele self-assigned this on Dec 20, 2019 @SebaDele added SAMM 2.0 2D1ThreatAssessment streamB labels on Dec 21, 2019 @23bartman commented on Dec 23, 2020 @SebaDele Can you review whether version 2.0 is OK on this ? If not, we can consider finetuning the model.
The text was updated successfully, but these errors were encountered:
Activity D-TA-1-B.yml
Always make sure to persist the outcome
--> Always persist the outcome
Activity D-TA-2-B.yml
Capture the threat modeling artifacts with tools that are used by your application teams.
--> Capture the threat modeling artifacts with tools used by your application teams.
the developer security culture. Reusable risk patterns,
--> the developer security culture. Reusable risk patterns,
Question D-TA-2-B.yml
Do you use a standard methodology, aligned on your application risk levels?
--> Do you use a standard methodology, aligned with your application risk levels?
You capture the threat modeling artifacts with tools that are used by your application teams
--> You capture the threat modeling artifacts with tools used by your application teams
You regularly (e.g., yearly) review the existing threat models to verify that no new threats are relevant for your applications
--> You review the existing threat models to verify that no new threats are relevant for your applications at least yearly
History from old repo:
@SebaDele opened this issue on Dec 20, 2019
@SebaDele self-assigned this on Dec 20, 2019
@SebaDele added SAMM 2.0 2D1ThreatAssessment streamB labels on Dec 21, 2019
@23bartman commented on Dec 23, 2020
@SebaDele Can you review whether version 2.0 is OK on this ? If not, we can consider finetuning the model.
The text was updated successfully, but these errors were encountered: