Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal
The purpose of this PR is to perform automated threat modeling of the OWASP Juice Shop application using Threagile and analyze the security risks in both baseline and secure deployment variants.
This lab demonstrates how infrastructure and communication security controls, such as HTTPS and storage encryption, affect the overall threat landscape and reduce security risks.
Changes
threagile-model.yamlreport.pdfrisks.jsonstats.jsonlabs/submission2.mdthreagile-model.secure.yamllabs/submission2.mdTesting
The threat model was tested by running Threagile in Docker to generate threat analysis outputs.
Baseline model generation:
docker run --rm -v "$(pwd)":/app/work threagile/threagile \ -model /app/work/labs/lab2/threagile-model.yaml \ -output /app/work/labs/lab2/baselineSecure model generation:
docker run --rm -v "$(pwd)":/app/work threagile/threagile \ -model /app/work/labs/lab2/threagile-model.secure.yaml \ -output /app/work/labs/lab2/secureRisk comparison performed using jq analysis script.
All required artifacts were successfully generated and verified.
Risk comparison was performed using jq analysis script to compare baseline and secure threat models.
The results showed that enabling HTTPS and storage encryption reduced the number of security risks related to unencrypted communication and unencrypted assets.
All required threat model artifacts were successfully generated and verified.
Artifacts & Screenshots
Generated artifacts:
Baseline model:
Secure model:
Documentation:
Checklist