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

mismatch of our types with upstream RSIT #1409

Closed
16 tasks done
ghost opened this issue May 14, 2019 · 0 comments
Closed
16 tasks done

mismatch of our types with upstream RSIT #1409

ghost opened this issue May 14, 2019 · 0 comments
Labels
architecture bug Indicates an unexpected problem or unintended behavior component: core data-format
Milestone

Comments

@ghost
Copy link

ghost commented May 14, 2019

There are a couple of types which are not in RSIT. What to do with them?

https://github.com/enisaeu/Reference-Security-Incident-Taxonomy-Task-Force

cc @aaronkaplan @th-certbund

@ghost ghost self-assigned this May 14, 2019
@ghost ghost changed the title Bring our types upstream to RSIT Bring our types upstream to RSIT or remove them May 14, 2019
@ghost ghost added this to the 2.1.0 milestone Oct 10, 2019
@ghost ghost added architecture bug Indicates an unexpected problem or unintended behavior data-format labels Oct 10, 2019
@ghost ghost changed the title Bring our types upstream to RSIT or remove them mismath of our types with upstream RSIT Oct 14, 2019
@ghost ghost changed the title mismath of our types with upstream RSIT mismatch of our types with upstream RSIT Oct 14, 2019
@ghost ghost modified the milestones: 2.1.0, 2.2.0 Oct 25, 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 ghost modified the milestones: 2.2.0, 3.0.0 Mar 24, 2020
ghost pushed a commit that referenced this issue May 4, 2021
the classification
malicious code / malware
is replaced by
malcious code / infected system
malcious code / malware-distribution
other / malware for all other cases, i.e. malware itself

fixes #1752
related to #1409
ghost pushed a commit that referenced this issue May 4, 2021
the classification
malicious code / malware
is replaced by
malcious code / infected system
malcious code / malware-distribution
other / malware for all other cases, i.e. malware itself

fixes #1752
related to #1409
@ghost 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 ghost closed this as completed in 8cefe11 Jun 28, 2021
waldbauer-certat pushed a commit that referenced this issue May 31, 2022
the classification
malicious code / malware
is replaced by
malcious code / infected system
malcious code / malware-distribution
other / malware for all other cases, i.e. malware itself

fixes #1752
related to #1409
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture bug Indicates an unexpected problem or unintended behavior component: core data-format
Projects
None yet
Development

No branches or pull requests

0 participants