-
Notifications
You must be signed in to change notification settings - Fork 297
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
mismatch of our types with upstream RSIT #1409
Labels
Milestone
Comments
ghost
self-assigned this
May 14, 2019
ghost
mentioned this issue
May 14, 2019
21 tasks
ghost
changed the title
Bring our types upstream to RSIT
Bring our types upstream to RSIT or remove them
May 14, 2019
ghost
added this to the 2.1.0 milestone
Oct 10, 2019
ghost
added
architecture
bug
Indicates an unexpected problem or unintended behavior
data-format
labels
Oct 10, 2019
ghost
changed the title
Bring our types upstream to RSIT or remove them
mismath of our types with upstream RSIT
Oct 14, 2019
ghost
changed the title
mismath of our types with upstream RSIT
mismatch of our types with upstream RSIT
Oct 14, 2019
ghost
pushed a commit
that referenced
this issue
Mar 24, 2020
The type is called data-leak in RSIT, rename here with backwards compatibility see #1409
ghost
pushed a commit
that referenced
this issue
Mar 24, 2020
align with RSIT replaced by either 'malware-distribution' or 'infected-system' see #1409
ghost
pushed a commit
that referenced
this issue
Mar 24, 2020
other/unknown is replaced by other/undetermined see #1409
ghost
mentioned this issue
May 14, 2020
ghost
mentioned this issue
Sep 29, 2020
ghost
mentioned this issue
Apr 29, 2021
ghost
added
the
component: core
label
Jun 17, 2021
ghost
pushed a commit
that referenced
this issue
Jun 26, 2021
integrate it into other/other ongoing discussion in RSIT, maybe we can create our type in other or in malicious code in the future fixes #1409
ghost
mentioned this issue
Jun 26, 2021
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
0 participants
There are a couple of types which are not in RSIT. What to do with them?
Revert "Remove malware-dga-domain as agreed in Vilnius meeting" enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#32Rejected by RSIT, see Re-classification of 'DGA domain' #1613; replace by other > dga-domain -> PR harm: move dga domain classification to other #1992information content security
->information-content-security
(taxonomy expert)https://github.com/enisaeu/Reference-Security-Incident-Taxonomy-Task-Force
cc @aaronkaplan @th-certbund
The text was updated successfully, but these errors were encountered: