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

CR01 - Collision in communications? #35

Closed
colesmj opened this issue Oct 21, 2018 · 1 comment
Closed

CR01 - Collision in communications? #35

colesmj opened this issue Oct 21, 2018 · 1 comment

Comments

@colesmj
Copy link
Collaborator

colesmj commented Oct 21, 2018

"CR01": { "description": "Collision Attacks", "source": Process, "target": Process, "condition": "target.implementsCommunicationProtocol is True", },

A collision attack is usually associated with hash algorithms, not communication protocols (unless you mean protocols pre-1980). Implementation of a custom comm protocol does not automatically mean a collision is a security threat, and implementsCommunicationProcotol should not imply a custom one.

@colesmj colesmj changed the title CR01 - Collision in communications? 1980 called and wants its protocol back CR01 - Collision in communications? Oct 21, 2018
@colesmj
Copy link
Collaborator Author

colesmj commented Sep 26, 2020

Looks like this issue is now obsolete - CR01 is no longer Collision Attacks, and no rule in threats.json is based on implementsCommunicationProtocol.

@colesmj colesmj closed this as completed Sep 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants