Java: Introduce a class of dataflow nodes for the threat modeling. #14257
+545
−24
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.
In this PR we introduce a class of data flow nodes called
ThreatModelFlowSource.The idea is that these are the exact source nodes we are interested in under a given threat model.
For more background information see EDR.
With this implementation it will also be easy to for a query to "opt-in" to threat models as defined by the
ThreatModelFlowSourceby updating the data flow configuration.With this change, we can convert most of the data flow related queries that are based on
RemoteFlowSourcetoThreatModelFlowSourceas this (should) yield the same results as long as the default threat model is used (the default only contains remote).