209 various bugs: shoulder surfing #222
Open
+28
−0
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
…rom shoulder surfing while it is being accessed interactively is negligible, due to the limited amount of data exposed at one time via the user interface.
…ategy to make it clear it is a signal to system-modeller, not a security measure.
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.
Branch 209 should stay open because the plan was to use it for a few more bug fixes.
This pull request is because the first fix is worth having in branch dev, without waiting for other fixes. The first fix adds a signalling control strategy addressing shoulder surfing to access confidential data. It provides a way to fully address the threat when it is not a significant concern. Previously, there was no way to do this.
The changes add the control strategy, which uses a control related to access by a specific process to specific data (i.e., a control associated with an inferred DataAccess asset). The threat patterns were then also updated so this inferred asset is included in the matching pattern.