mismatch of our types with upstream RSIT

[ghost]

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

• information content security > dropzone: asked on RSIT ML for input -> PR harmonization: remove type dropzone #2006
• information content security > leak: data-leak add (data) leak under information content security enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#61
• intrusions > backdoor: merged into system-compromise in PR harm: remove type backdoor #1995
• intrusions > compromised: replace by system-compromise Add system-compromise enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#59 -> PR harm: rename compromised to system-compromise #1993
• intrusions > defacement: replace by unauthorised-information-modification and a specific identifier Add defacements as example in description of information modification enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#73 -> PR harm: remove type defacement #1994
• intrusions > unauthorized-command not accepted upstream: Add Unauthorized Login and Command enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#49 replacement system-compromise: Add system-compromise enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#59 -> PR harm: rename compromised to system-compromise #1993
• intrusions > unauthorized-login not accepted upstream: Add Unauthorized Login and Command enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#49 replacement system-compromise: Add system-compromise enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#59 -> PR harm: rename compromised to system-compromise #1993
• malicious code > dga domain: Revert "Remove malware-dga-domain as agreed in Vilnius meeting" enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#32 Rejected by RSIT, see Re-classification of 'DGA domain' #1613; replace by other > dga-domain -> PR harm: move dga domain classification to other #1992
• malicious code > malware: replace by infected-system or malware-distribution, PR Introduce Other/malware classification #1917
• malicious code > ransomware: replace by infected-system
• other > proxy: Other can deviate from RSIT
• other > tor: Other can deviate from RSIT
• other > unknown: different name Add other/undetermined enisaeu/Reference-Security-Incident-Taxonomy-Task-Force#46
• vulnerable > vulnerable client: vulnerable-system
• vulnerable > vulnerable service: vulnerable-system
• information content security -> information-content-security (taxonomy expert)

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

cc @aaronkaplan @th-certbund