Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DE01 Data Flow Sniffing - condition needs improvement #30

Closed
colesmj opened this issue Oct 21, 2018 · 2 comments
Closed

DE01 Data Flow Sniffing - condition needs improvement #30

colesmj opened this issue Oct 21, 2018 · 2 comments
Labels

Comments

@colesmj
Copy link
Collaborator

colesmj commented Oct 21, 2018

"DE01": { "description": "Data Flow Sniffing", "source": (Process, Element, Datastore), "target": Dataflow, "condition": "target.protocol == 'HTTP' and target.isEncrypted is False", },

In this threat, it checks to see if the protocol is HTTP and if the channel is unencrypted. A user by error may set the protocol but not the flag, or vice versa, unless there is code somewhere which makes the connection automatically. Instead, it may be best to make this an OR condition - either http or unencrypted will trigger the threat.

@izar izar added good first issue Good for newcomers Hacktoberfest labels Aug 19, 2020
@nineinchnick
Copy link
Collaborator

Can you check this issue is still valid? The condition now is: not target.isEncrypted or (target.source.inScope and not target.isResponse and (not target.authenticatesDestination or not target.checksDestinationRevocation))

@colesmj
Copy link
Collaborator Author

colesmj commented Jun 25, 2023

Reviewing to clean up issues, and it seems this one has changed. Yes, DE01 seems "better" now, but DE03, which may be a duplicate threat, needs work. Will raise a separate PR for that issue.

@colesmj colesmj closed this as not planned Won't fix, can't repro, duplicate, stale Jun 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants