2644 lines
119 KiB
HTML
2644 lines
119 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en" class="Internet-Draft">
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<meta content="Common,Latin" name="scripts">
|
||
<meta content="initial-scale=1.0" name="viewport">
|
||
<title>MISP taxonomy format</title>
|
||
<meta content="Alexandre Dulaunoy" name="author">
|
||
<meta content="Andras Iklody" name="author">
|
||
<meta content="
|
||
This document describes the MISP taxonomy format which describes a simple JSON format to
|
||
represent machine tags (also called triple tags) vocabularies. A public directory of common vocabularies
|
||
called MISP taxonomies is available and relies on the MISP taxonomy format. MISP taxonomies are used to classify
|
||
cyber security events, threats, suspicious events, or indicators.
|
||
" name="description">
|
||
<meta content="xml2rfc 3.12.1" name="generator">
|
||
<meta content="draft-08" name="ietf.draft">
|
||
<!-- Generator version information:
|
||
xml2rfc 3.12.1
|
||
Python 3.8.10
|
||
appdirs 1.4.4
|
||
ConfigArgParse 1.5.3
|
||
google-i18n-address 2.5.0
|
||
html5lib 1.1
|
||
intervaltree 3.1.0
|
||
Jinja2 3.1.2
|
||
kitchen 1.2.6
|
||
lxml 4.9.2
|
||
pycairo 1.16.2
|
||
pycountry 22.3.5
|
||
pyflakes 2.4.0
|
||
PyYAML 6.0
|
||
requests 2.31.0
|
||
setuptools 68.1.2
|
||
six 1.16.0
|
||
-->
|
||
<link href="raw.md.xml" rel="alternate" type="application/rfc+xml">
|
||
<link href="#copyright" rel="license">
|
||
<style type="text/css">/*
|
||
|
||
NOTE: Changes at the bottom of this file overrides some earlier settings.
|
||
|
||
Once the style has stabilized and has been adopted as an official RFC style,
|
||
this can be consolidated so that style settings occur only in one place, but
|
||
for now the contents of this file consists first of the initial CSS work as
|
||
provided to the RFC Formatter (xml2rfc) work, followed by itemized and
|
||
commented changes found necssary during the development of the v3
|
||
formatters.
|
||
|
||
*/
|
||
|
||
/* fonts */
|
||
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
|
||
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
|
||
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
|
||
|
||
@viewport {
|
||
zoom: 1.0;
|
||
width: extend-to-zoom;
|
||
}
|
||
@-ms-viewport {
|
||
width: extend-to-zoom;
|
||
zoom: 1.0;
|
||
}
|
||
/* general and mobile first */
|
||
html {
|
||
}
|
||
body {
|
||
max-width: 90%;
|
||
margin: 1.5em auto;
|
||
color: #222;
|
||
background-color: #fff;
|
||
font-size: 14px;
|
||
font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
|
||
line-height: 1.6;
|
||
scroll-behavior: smooth;
|
||
}
|
||
.ears {
|
||
display: none;
|
||
}
|
||
|
||
/* headings */
|
||
#title, h1, h2, h3, h4, h5, h6 {
|
||
margin: 1em 0 0.5em;
|
||
font-weight: bold;
|
||
line-height: 1.3;
|
||
}
|
||
#title {
|
||
clear: both;
|
||
border-bottom: 1px solid #ddd;
|
||
margin: 0 0 0.5em 0;
|
||
padding: 1em 0 0.5em;
|
||
}
|
||
.author {
|
||
padding-bottom: 4px;
|
||
}
|
||
h1 {
|
||
font-size: 26px;
|
||
margin: 1em 0;
|
||
}
|
||
h2 {
|
||
font-size: 22px;
|
||
margin-top: -20px; /* provide offset for in-page anchors */
|
||
padding-top: 33px;
|
||
}
|
||
h3 {
|
||
font-size: 18px;
|
||
margin-top: -36px; /* provide offset for in-page anchors */
|
||
padding-top: 42px;
|
||
}
|
||
h4 {
|
||
font-size: 16px;
|
||
margin-top: -36px; /* provide offset for in-page anchors */
|
||
padding-top: 42px;
|
||
}
|
||
h5, h6 {
|
||
font-size: 14px;
|
||
}
|
||
#n-copyright-notice {
|
||
border-bottom: 1px solid #ddd;
|
||
padding-bottom: 1em;
|
||
margin-bottom: 1em;
|
||
}
|
||
/* general structure */
|
||
p {
|
||
padding: 0;
|
||
margin: 0 0 1em 0;
|
||
text-align: left;
|
||
}
|
||
div, span {
|
||
position: relative;
|
||
}
|
||
div {
|
||
margin: 0;
|
||
}
|
||
.alignRight.art-text {
|
||
background-color: #f9f9f9;
|
||
border: 1px solid #eee;
|
||
border-radius: 3px;
|
||
padding: 1em 1em 0;
|
||
margin-bottom: 1.5em;
|
||
}
|
||
.alignRight.art-text pre {
|
||
padding: 0;
|
||
}
|
||
.alignRight {
|
||
margin: 1em 0;
|
||
}
|
||
.alignRight > *:first-child {
|
||
border: none;
|
||
margin: 0;
|
||
float: right;
|
||
clear: both;
|
||
}
|
||
.alignRight > *:nth-child(2) {
|
||
clear: both;
|
||
display: block;
|
||
border: none;
|
||
}
|
||
svg {
|
||
display: block;
|
||
}
|
||
.alignCenter.art-text {
|
||
background-color: #f9f9f9;
|
||
border: 1px solid #eee;
|
||
border-radius: 3px;
|
||
padding: 1em 1em 0;
|
||
margin-bottom: 1.5em;
|
||
}
|
||
.alignCenter.art-text pre {
|
||
padding: 0;
|
||
}
|
||
.alignCenter {
|
||
margin: 1em 0;
|
||
}
|
||
.alignCenter > *:first-child {
|
||
border: none;
|
||
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't
|
||
support flexbox yet.
|
||
*/
|
||
display: table;
|
||
margin: 0 auto;
|
||
}
|
||
|
||
/* lists */
|
||
ol, ul {
|
||
padding: 0;
|
||
margin: 0 0 1em 2em;
|
||
}
|
||
ol ol, ul ul, ol ul, ul ol {
|
||
margin-left: 1em;
|
||
}
|
||
li {
|
||
margin: 0 0 0.25em 0;
|
||
}
|
||
.ulCompact li {
|
||
margin: 0;
|
||
}
|
||
ul.empty, .ulEmpty {
|
||
list-style-type: none;
|
||
}
|
||
ul.empty li, .ulEmpty li {
|
||
margin-top: 0.5em;
|
||
}
|
||
ul.ulBare, li.ulBare {
|
||
margin-left: 0em !important;
|
||
}
|
||
ul.compact, .ulCompact,
|
||
ol.compact, .olCompact {
|
||
line-height: 100%;
|
||
margin: 0 0 0 2em;
|
||
}
|
||
|
||
/* definition lists */
|
||
dl {
|
||
}
|
||
dl > dt {
|
||
float: left;
|
||
margin-right: 1em;
|
||
}
|
||
/*
|
||
dl.nohang > dt {
|
||
float: none;
|
||
}
|
||
*/
|
||
dl > dd {
|
||
margin-bottom: .8em;
|
||
min-height: 1.3em;
|
||
}
|
||
dl.compact > dd, .dlCompact > dd {
|
||
margin-bottom: 0em;
|
||
}
|
||
dl > dd > dl {
|
||
margin-top: 0.5em;
|
||
margin-bottom: 0em;
|
||
}
|
||
|
||
/* links */
|
||
a {
|
||
text-decoration: none;
|
||
}
|
||
a[href] {
|
||
color: #22e; /* Arlen: WCAG 2019 */
|
||
}
|
||
a[href]:hover {
|
||
background-color: #f2f2f2;
|
||
}
|
||
figcaption a[href],
|
||
a[href].selfRef {
|
||
color: #222;
|
||
}
|
||
/* XXX probably not this:
|
||
a.selfRef:hover {
|
||
background-color: transparent;
|
||
cursor: default;
|
||
} */
|
||
|
||
/* Figures */
|
||
tt, code, pre, code {
|
||
background-color: #f9f9f9;
|
||
font-family: 'Roboto Mono', monospace;
|
||
}
|
||
pre {
|
||
border: 1px solid #eee;
|
||
margin: 0;
|
||
padding: 1em;
|
||
}
|
||
img {
|
||
max-width: 100%;
|
||
}
|
||
figure {
|
||
margin: 0;
|
||
}
|
||
figure blockquote {
|
||
margin: 0.8em 0.4em 0.4em;
|
||
}
|
||
figcaption {
|
||
font-style: italic;
|
||
margin: 0 0 1em 0;
|
||
}
|
||
@media screen {
|
||
pre {
|
||
overflow-x: auto;
|
||
max-width: 100%;
|
||
max-width: calc(100% - 22px);
|
||
}
|
||
}
|
||
|
||
/* aside, blockquote */
|
||
aside, blockquote {
|
||
margin-left: 0;
|
||
padding: 1.2em 2em;
|
||
}
|
||
blockquote {
|
||
background-color: #f9f9f9;
|
||
color: #111; /* Arlen: WCAG 2019 */
|
||
border: 1px solid #ddd;
|
||
border-radius: 3px;
|
||
margin: 1em 0;
|
||
}
|
||
cite {
|
||
display: block;
|
||
text-align: right;
|
||
font-style: italic;
|
||
}
|
||
|
||
/* tables */
|
||
table {
|
||
width: 100%;
|
||
margin: 0 0 1em;
|
||
border-collapse: collapse;
|
||
border: 1px solid #eee;
|
||
}
|
||
th, td {
|
||
text-align: left;
|
||
vertical-align: top;
|
||
padding: 0.5em 0.75em;
|
||
}
|
||
th {
|
||
text-align: left;
|
||
background-color: #e9e9e9;
|
||
}
|
||
tr:nth-child(2n+1) > td {
|
||
background-color: #f5f5f5;
|
||
}
|
||
table caption {
|
||
font-style: italic;
|
||
margin: 0;
|
||
padding: 0;
|
||
text-align: left;
|
||
}
|
||
table p {
|
||
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should
|
||
be allowed within tables more generally, it would be far better to select on a class. */
|
||
margin: 0;
|
||
}
|
||
|
||
/* pilcrow */
|
||
a.pilcrow {
|
||
color: #666; /* Arlen: AHDJ 2019 */
|
||
text-decoration: none;
|
||
visibility: hidden;
|
||
user-select: none;
|
||
-ms-user-select: none;
|
||
-o-user-select:none;
|
||
-moz-user-select: none;
|
||
-khtml-user-select: none;
|
||
-webkit-user-select: none;
|
||
-webkit-touch-callout: none;
|
||
}
|
||
@media screen {
|
||
aside:hover > a.pilcrow,
|
||
p:hover > a.pilcrow,
|
||
blockquote:hover > a.pilcrow,
|
||
div:hover > a.pilcrow,
|
||
li:hover > a.pilcrow,
|
||
pre:hover > a.pilcrow {
|
||
visibility: visible;
|
||
}
|
||
a.pilcrow:hover {
|
||
background-color: transparent;
|
||
}
|
||
}
|
||
|
||
/* misc */
|
||
hr {
|
||
border: 0;
|
||
border-top: 1px solid #eee;
|
||
}
|
||
.bcp14 {
|
||
font-variant: small-caps;
|
||
}
|
||
|
||
.role {
|
||
font-variant: all-small-caps;
|
||
}
|
||
|
||
/* info block */
|
||
#identifiers {
|
||
margin: 0;
|
||
font-size: 0.9em;
|
||
}
|
||
#identifiers dt {
|
||
width: 3em;
|
||
clear: left;
|
||
}
|
||
#identifiers dd {
|
||
float: left;
|
||
margin-bottom: 0;
|
||
}
|
||
/* Fix PDF info block run off issue */
|
||
@media print {
|
||
#identifiers dd {
|
||
float: none;
|
||
}
|
||
}
|
||
#identifiers .authors .author {
|
||
display: inline-block;
|
||
margin-right: 1.5em;
|
||
}
|
||
#identifiers .authors .org {
|
||
font-style: italic;
|
||
}
|
||
|
||
/* The prepared/rendered info at the very bottom of the page */
|
||
.docInfo {
|
||
color: #666; /* Arlen: WCAG 2019 */
|
||
font-size: 0.9em;
|
||
font-style: italic;
|
||
margin-top: 2em;
|
||
}
|
||
.docInfo .prepared {
|
||
float: left;
|
||
}
|
||
.docInfo .prepared {
|
||
float: right;
|
||
}
|
||
|
||
/* table of contents */
|
||
#toc {
|
||
padding: 0.75em 0 2em 0;
|
||
margin-bottom: 1em;
|
||
}
|
||
nav.toc ul {
|
||
margin: 0 0.5em 0 0;
|
||
padding: 0;
|
||
list-style: none;
|
||
}
|
||
nav.toc li {
|
||
line-height: 1.3em;
|
||
margin: 0.75em 0;
|
||
padding-left: 1.2em;
|
||
text-indent: -1.2em;
|
||
}
|
||
/* references */
|
||
.references dt {
|
||
text-align: right;
|
||
font-weight: bold;
|
||
min-width: 7em;
|
||
}
|
||
.references dd {
|
||
margin-left: 8em;
|
||
overflow: auto;
|
||
}
|
||
|
||
.refInstance {
|
||
margin-bottom: 1.25em;
|
||
}
|
||
|
||
.references .ascii {
|
||
margin-bottom: 0.25em;
|
||
}
|
||
|
||
/* index */
|
||
.index ul {
|
||
margin: 0 0 0 1em;
|
||
padding: 0;
|
||
list-style: none;
|
||
}
|
||
.index ul ul {
|
||
margin: 0;
|
||
}
|
||
.index li {
|
||
margin: 0;
|
||
text-indent: -2em;
|
||
padding-left: 2em;
|
||
padding-bottom: 5px;
|
||
}
|
||
.indexIndex {
|
||
margin: 0.5em 0 1em;
|
||
}
|
||
.index a {
|
||
font-weight: 700;
|
||
}
|
||
/* make the index two-column on all but the smallest screens */
|
||
@media (min-width: 600px) {
|
||
.index ul {
|
||
-moz-column-count: 2;
|
||
-moz-column-gap: 20px;
|
||
}
|
||
.index ul ul {
|
||
-moz-column-count: 1;
|
||
-moz-column-gap: 0;
|
||
}
|
||
}
|
||
|
||
/* authors */
|
||
address.vcard {
|
||
font-style: normal;
|
||
margin: 1em 0;
|
||
}
|
||
|
||
address.vcard .nameRole {
|
||
font-weight: 700;
|
||
margin-left: 0;
|
||
}
|
||
address.vcard .label {
|
||
font-family: "Noto Sans",Arial,Helvetica,sans-serif;
|
||
margin: 0.5em 0;
|
||
}
|
||
address.vcard .type {
|
||
display: none;
|
||
}
|
||
.alternative-contact {
|
||
margin: 1.5em 0 1em;
|
||
}
|
||
hr.addr {
|
||
border-top: 1px dashed;
|
||
margin: 0;
|
||
color: #ddd;
|
||
max-width: calc(100% - 16px);
|
||
}
|
||
|
||
/* temporary notes */
|
||
.rfcEditorRemove::before {
|
||
position: absolute;
|
||
top: 0.2em;
|
||
right: 0.2em;
|
||
padding: 0.2em;
|
||
content: "The RFC Editor will remove this note";
|
||
color: #9e2a00; /* Arlen: WCAG 2019 */
|
||
background-color: #ffd; /* Arlen: WCAG 2019 */
|
||
}
|
||
.rfcEditorRemove {
|
||
position: relative;
|
||
padding-top: 1.8em;
|
||
background-color: #ffd; /* Arlen: WCAG 2019 */
|
||
border-radius: 3px;
|
||
}
|
||
.cref {
|
||
background-color: #ffd; /* Arlen: WCAG 2019 */
|
||
padding: 2px 4px;
|
||
}
|
||
.crefSource {
|
||
font-style: italic;
|
||
}
|
||
/* alternative layout for smaller screens */
|
||
@media screen and (max-width: 1023px) {
|
||
body {
|
||
padding-top: 2em;
|
||
}
|
||
#title {
|
||
padding: 1em 0;
|
||
}
|
||
h1 {
|
||
font-size: 24px;
|
||
}
|
||
h2 {
|
||
font-size: 20px;
|
||
margin-top: -18px; /* provide offset for in-page anchors */
|
||
padding-top: 38px;
|
||
}
|
||
#identifiers dd {
|
||
max-width: 60%;
|
||
}
|
||
#toc {
|
||
position: fixed;
|
||
z-index: 2;
|
||
top: 0;
|
||
right: 0;
|
||
padding: 0;
|
||
margin: 0;
|
||
background-color: inherit;
|
||
border-bottom: 1px solid #ccc;
|
||
}
|
||
#toc h2 {
|
||
margin: -1px 0 0 0;
|
||
padding: 4px 0 4px 6px;
|
||
padding-right: 1em;
|
||
min-width: 190px;
|
||
font-size: 1.1em;
|
||
text-align: right;
|
||
background-color: #444;
|
||
color: white;
|
||
cursor: pointer;
|
||
}
|
||
#toc h2::before { /* css hamburger */
|
||
float: right;
|
||
position: relative;
|
||
width: 1em;
|
||
height: 1px;
|
||
left: -164px;
|
||
margin: 6px 0 0 0;
|
||
background: white none repeat scroll 0 0;
|
||
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
|
||
content: "";
|
||
}
|
||
#toc nav {
|
||
display: none;
|
||
padding: 0.5em 1em 1em;
|
||
overflow: auto;
|
||
height: calc(100vh - 48px);
|
||
border-left: 1px solid #ddd;
|
||
}
|
||
}
|
||
|
||
/* alternative layout for wide screens */
|
||
@media screen and (min-width: 1024px) {
|
||
body {
|
||
max-width: 724px;
|
||
margin: 42px auto;
|
||
padding-left: 1.5em;
|
||
padding-right: 29em;
|
||
}
|
||
#toc {
|
||
position: fixed;
|
||
top: 42px;
|
||
right: 42px;
|
||
width: 25%;
|
||
margin: 0;
|
||
padding: 0 1em;
|
||
z-index: 1;
|
||
}
|
||
#toc h2 {
|
||
border-top: none;
|
||
border-bottom: 1px solid #ddd;
|
||
font-size: 1em;
|
||
font-weight: normal;
|
||
margin: 0;
|
||
padding: 0.25em 1em 1em 0;
|
||
}
|
||
#toc nav {
|
||
display: block;
|
||
height: calc(90vh - 84px);
|
||
bottom: 0;
|
||
padding: 0.5em 0 0;
|
||
overflow: auto;
|
||
}
|
||
img { /* future proofing */
|
||
max-width: 100%;
|
||
height: auto;
|
||
}
|
||
}
|
||
|
||
/* pagination */
|
||
@media print {
|
||
body {
|
||
|
||
width: 100%;
|
||
}
|
||
p {
|
||
orphans: 3;
|
||
widows: 3;
|
||
}
|
||
#n-copyright-notice {
|
||
border-bottom: none;
|
||
}
|
||
#toc, #n-introduction {
|
||
page-break-before: always;
|
||
}
|
||
#toc {
|
||
border-top: none;
|
||
padding-top: 0;
|
||
}
|
||
figure, pre {
|
||
page-break-inside: avoid;
|
||
}
|
||
figure {
|
||
overflow: scroll;
|
||
}
|
||
h1, h2, h3, h4, h5, h6 {
|
||
page-break-after: avoid;
|
||
}
|
||
h2+*, h3+*, h4+*, h5+*, h6+* {
|
||
page-break-before: avoid;
|
||
}
|
||
pre {
|
||
white-space: pre-wrap;
|
||
word-wrap: break-word;
|
||
font-size: 10pt;
|
||
}
|
||
table {
|
||
border: 1px solid #ddd;
|
||
}
|
||
td {
|
||
border-top: 1px solid #ddd;
|
||
}
|
||
}
|
||
|
||
/* This is commented out here, as the string-set: doesn't
|
||
pass W3C validation currently */
|
||
/*
|
||
.ears thead .left {
|
||
string-set: ears-top-left content();
|
||
}
|
||
|
||
.ears thead .center {
|
||
string-set: ears-top-center content();
|
||
}
|
||
|
||
.ears thead .right {
|
||
string-set: ears-top-right content();
|
||
}
|
||
|
||
.ears tfoot .left {
|
||
string-set: ears-bottom-left content();
|
||
}
|
||
|
||
.ears tfoot .center {
|
||
string-set: ears-bottom-center content();
|
||
}
|
||
|
||
.ears tfoot .right {
|
||
string-set: ears-bottom-right content();
|
||
}
|
||
*/
|
||
|
||
@page :first {
|
||
padding-top: 0;
|
||
@top-left {
|
||
content: normal;
|
||
border: none;
|
||
}
|
||
@top-center {
|
||
content: normal;
|
||
border: none;
|
||
}
|
||
@top-right {
|
||
content: normal;
|
||
border: none;
|
||
}
|
||
}
|
||
|
||
@page {
|
||
size: A4;
|
||
margin-bottom: 45mm;
|
||
padding-top: 20px;
|
||
/* The follwing is commented out here, but set appropriately by in code, as
|
||
the content depends on the document */
|
||
/*
|
||
@top-left {
|
||
content: 'Internet-Draft';
|
||
vertical-align: bottom;
|
||
border-bottom: solid 1px #ccc;
|
||
}
|
||
@top-left {
|
||
content: string(ears-top-left);
|
||
vertical-align: bottom;
|
||
border-bottom: solid 1px #ccc;
|
||
}
|
||
@top-center {
|
||
content: string(ears-top-center);
|
||
vertical-align: bottom;
|
||
border-bottom: solid 1px #ccc;
|
||
}
|
||
@top-right {
|
||
content: string(ears-top-right);
|
||
vertical-align: bottom;
|
||
border-bottom: solid 1px #ccc;
|
||
}
|
||
@bottom-left {
|
||
content: string(ears-bottom-left);
|
||
vertical-align: top;
|
||
border-top: solid 1px #ccc;
|
||
}
|
||
@bottom-center {
|
||
content: string(ears-bottom-center);
|
||
vertical-align: top;
|
||
border-top: solid 1px #ccc;
|
||
}
|
||
@bottom-right {
|
||
content: '[Page ' counter(page) ']';
|
||
vertical-align: top;
|
||
border-top: solid 1px #ccc;
|
||
}
|
||
*/
|
||
|
||
}
|
||
|
||
/* Changes introduced to fix issues found during implementation */
|
||
/* Make sure links are clickable even if overlapped by following H* */
|
||
a {
|
||
z-index: 2;
|
||
}
|
||
/* Separate body from document info even without intervening H1 */
|
||
section {
|
||
clear: both;
|
||
}
|
||
|
||
|
||
/* Top align author divs, to avoid names without organization dropping level with org names */
|
||
.author {
|
||
vertical-align: top;
|
||
}
|
||
|
||
/* Leave room in document info to show Internet-Draft on one line */
|
||
#identifiers dt {
|
||
width: 8em;
|
||
}
|
||
|
||
/* Don't waste quite as much whitespace between label and value in doc info */
|
||
#identifiers dd {
|
||
margin-left: 1em;
|
||
}
|
||
|
||
/* Give floating toc a background color (needed when it's a div inside section */
|
||
#toc {
|
||
background-color: white;
|
||
}
|
||
|
||
/* Make the collapsed ToC header render white on gray also when it's a link */
|
||
@media screen and (max-width: 1023px) {
|
||
#toc h2 a,
|
||
#toc h2 a:link,
|
||
#toc h2 a:focus,
|
||
#toc h2 a:hover,
|
||
#toc a.toplink,
|
||
#toc a.toplink:hover {
|
||
color: white;
|
||
background-color: #444;
|
||
text-decoration: none;
|
||
}
|
||
}
|
||
|
||
/* Give the bottom of the ToC some whitespace */
|
||
@media screen and (min-width: 1024px) {
|
||
#toc {
|
||
padding: 0 0 1em 1em;
|
||
}
|
||
}
|
||
|
||
/* Style section numbers with more space between number and title */
|
||
.section-number {
|
||
padding-right: 0.5em;
|
||
}
|
||
|
||
/* prevent monospace from becoming overly large */
|
||
tt, code, pre, code {
|
||
font-size: 95%;
|
||
}
|
||
|
||
/* Fix the height/width aspect for ascii art*/
|
||
pre.sourcecode,
|
||
.art-text pre {
|
||
line-height: 1.12;
|
||
}
|
||
|
||
|
||
/* Add styling for a link in the ToC that points to the top of the document */
|
||
a.toplink {
|
||
float: right;
|
||
margin-right: 0.5em;
|
||
}
|
||
|
||
/* Fix the dl styling to match the RFC 7992 attributes */
|
||
dl > dt,
|
||
dl.dlParallel > dt {
|
||
float: left;
|
||
margin-right: 1em;
|
||
}
|
||
dl.dlNewline > dt {
|
||
float: none;
|
||
}
|
||
|
||
/* Provide styling for table cell text alignment */
|
||
table td.text-left,
|
||
table th.text-left {
|
||
text-align: left;
|
||
}
|
||
table td.text-center,
|
||
table th.text-center {
|
||
text-align: center;
|
||
}
|
||
table td.text-right,
|
||
table th.text-right {
|
||
text-align: right;
|
||
}
|
||
|
||
/* Make the alternative author contact informatio look less like just another
|
||
author, and group it closer with the primary author contact information */
|
||
.alternative-contact {
|
||
margin: 0.5em 0 0.25em 0;
|
||
}
|
||
address .non-ascii {
|
||
margin: 0 0 0 2em;
|
||
}
|
||
|
||
/* With it being possible to set tables with alignment
|
||
left, center, and right, { width: 100%; } does not make sense */
|
||
table {
|
||
width: auto;
|
||
}
|
||
|
||
/* Avoid reference text that sits in a block with very wide left margin,
|
||
because of a long floating dt label.*/
|
||
.references dd {
|
||
overflow: visible;
|
||
}
|
||
|
||
/* Control caption placement */
|
||
caption {
|
||
caption-side: bottom;
|
||
}
|
||
|
||
/* Limit the width of the author address vcard, so names in right-to-left
|
||
script don't end up on the other side of the page. */
|
||
|
||
address.vcard {
|
||
max-width: 30em;
|
||
margin-right: auto;
|
||
}
|
||
|
||
/* For address alignment dependent on LTR or RTL scripts */
|
||
address div.left {
|
||
text-align: left;
|
||
}
|
||
address div.right {
|
||
text-align: right;
|
||
}
|
||
|
||
/* Provide table alignment support. We can't use the alignX classes above
|
||
since they do unwanted things with caption and other styling. */
|
||
table.right {
|
||
margin-left: auto;
|
||
margin-right: 0;
|
||
}
|
||
table.center {
|
||
margin-left: auto;
|
||
margin-right: auto;
|
||
}
|
||
table.left {
|
||
margin-left: 0;
|
||
margin-right: auto;
|
||
}
|
||
|
||
/* Give the table caption label the same styling as the figcaption */
|
||
caption a[href] {
|
||
color: #222;
|
||
}
|
||
|
||
@media print {
|
||
.toplink {
|
||
display: none;
|
||
}
|
||
|
||
/* avoid overwriting the top border line with the ToC header */
|
||
#toc {
|
||
padding-top: 1px;
|
||
}
|
||
|
||
/* Avoid page breaks inside dl and author address entries */
|
||
.vcard {
|
||
page-break-inside: avoid;
|
||
}
|
||
|
||
}
|
||
/* Tweak the bcp14 keyword presentation */
|
||
.bcp14 {
|
||
font-variant: small-caps;
|
||
font-weight: bold;
|
||
font-size: 0.9em;
|
||
}
|
||
/* Tweak the invisible space above H* in order not to overlay links in text above */
|
||
h2 {
|
||
margin-top: -18px; /* provide offset for in-page anchors */
|
||
padding-top: 31px;
|
||
}
|
||
h3 {
|
||
margin-top: -18px; /* provide offset for in-page anchors */
|
||
padding-top: 24px;
|
||
}
|
||
h4 {
|
||
margin-top: -18px; /* provide offset for in-page anchors */
|
||
padding-top: 24px;
|
||
}
|
||
/* Float artwork pilcrow to the right */
|
||
@media screen {
|
||
.artwork a.pilcrow {
|
||
display: block;
|
||
line-height: 0.7;
|
||
margin-top: 0.15em;
|
||
}
|
||
}
|
||
/* Make pilcrows on dd visible */
|
||
@media screen {
|
||
dd:hover > a.pilcrow {
|
||
visibility: visible;
|
||
}
|
||
}
|
||
/* Make the placement of figcaption match that of a table's caption
|
||
by removing the figure's added bottom margin */
|
||
.alignLeft.art-text,
|
||
.alignCenter.art-text,
|
||
.alignRight.art-text {
|
||
margin-bottom: 0;
|
||
}
|
||
.alignLeft,
|
||
.alignCenter,
|
||
.alignRight {
|
||
margin: 1em 0 0 0;
|
||
}
|
||
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
|
||
possibly even requiring a new line */
|
||
@media print {
|
||
a.pilcrow {
|
||
display: none;
|
||
}
|
||
}
|
||
/* Styling for the external metadata */
|
||
div#external-metadata {
|
||
background-color: #eee;
|
||
padding: 0.5em;
|
||
margin-bottom: 0.5em;
|
||
display: none;
|
||
}
|
||
div#internal-metadata {
|
||
padding: 0.5em; /* to match the external-metadata padding */
|
||
}
|
||
/* Styling for title RFC Number */
|
||
h1#rfcnum {
|
||
clear: both;
|
||
margin: 0 0 -1em;
|
||
padding: 1em 0 0 0;
|
||
}
|
||
/* Make .olPercent look the same as <ol><li> */
|
||
dl.olPercent > dd {
|
||
margin-bottom: 0.25em;
|
||
min-height: initial;
|
||
}
|
||
/* Give aside some styling to set it apart */
|
||
aside {
|
||
border-left: 1px solid #ddd;
|
||
margin: 1em 0 1em 2em;
|
||
padding: 0.2em 2em;
|
||
}
|
||
aside > dl,
|
||
aside > ol,
|
||
aside > ul,
|
||
aside > table,
|
||
aside > p {
|
||
margin-bottom: 0.5em;
|
||
}
|
||
/* Additional page break settings */
|
||
@media print {
|
||
figcaption, table caption {
|
||
page-break-before: avoid;
|
||
}
|
||
}
|
||
/* Font size adjustments for print */
|
||
@media print {
|
||
body { font-size: 10pt; line-height: normal; max-width: 96%; }
|
||
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
|
||
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
|
||
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
|
||
h4 { font-size: 1em; padding-top: 1.5em; }
|
||
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
|
||
}
|
||
/* Sourcecode margin in print, when there's no pilcrow */
|
||
@media print {
|
||
.artwork,
|
||
.sourcecode {
|
||
margin-bottom: 1em;
|
||
}
|
||
}
|
||
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
|
||
table {
|
||
min-width: 20em;
|
||
}
|
||
/* ol type a */
|
||
ol.type-a { list-style-type: lower-alpha; }
|
||
ol.type-A { list-style-type: upper-alpha; }
|
||
ol.type-i { list-style-type: lower-roman; }
|
||
ol.type-I { list-style-type: lower-roman; }
|
||
/* Apply the print table and row borders in general, on request from the RPC,
|
||
and increase the contrast between border and odd row background sligthtly */
|
||
table {
|
||
border: 1px solid #ddd;
|
||
}
|
||
td {
|
||
border-top: 1px solid #ddd;
|
||
}
|
||
tr:nth-child(2n+1) > td {
|
||
background-color: #f8f8f8;
|
||
}
|
||
/* Use style rules to govern display of the TOC. */
|
||
@media screen and (max-width: 1023px) {
|
||
#toc nav { display: none; }
|
||
#toc.active nav { display: block; }
|
||
}
|
||
/* Add support for keepWithNext */
|
||
.keepWithNext {
|
||
break-after: avoid-page;
|
||
break-after: avoid-page;
|
||
}
|
||
/* Add support for keepWithPrevious */
|
||
.keepWithPrevious {
|
||
break-before: avoid-page;
|
||
}
|
||
/* Change the approach to avoiding breaks inside artwork etc. */
|
||
figure, pre, table, .artwork, .sourcecode {
|
||
break-before: auto;
|
||
break-after: auto;
|
||
}
|
||
/* Avoid breaks between <dt> and <dd> */
|
||
dl {
|
||
break-before: auto;
|
||
break-inside: auto;
|
||
}
|
||
dt {
|
||
break-before: auto;
|
||
break-after: avoid-page;
|
||
}
|
||
dd {
|
||
break-before: avoid-page;
|
||
break-after: auto;
|
||
orphans: 3;
|
||
widows: 3
|
||
}
|
||
span.break, dd.break {
|
||
margin-bottom: 0;
|
||
min-height: 0;
|
||
break-before: auto;
|
||
break-inside: auto;
|
||
break-after: auto;
|
||
}
|
||
/* Undo break-before ToC */
|
||
@media print {
|
||
#toc {
|
||
break-before: auto;
|
||
}
|
||
}
|
||
/* Text in compact lists should not get extra bottim margin space,
|
||
since that would makes the list not compact */
|
||
ul.compact p, .ulCompact p,
|
||
ol.compact p, .olCompact p {
|
||
margin: 0;
|
||
}
|
||
/* But the list as a whole needs the extra space at the end */
|
||
section ul.compact,
|
||
section .ulCompact,
|
||
section ol.compact,
|
||
section .olCompact {
|
||
margin-bottom: 1em; /* same as p not within ul.compact etc. */
|
||
}
|
||
/* The tt and code background above interferes with for instance table cell
|
||
backgrounds. Changed to something a bit more selective. */
|
||
tt, code {
|
||
background-color: transparent;
|
||
}
|
||
p tt, p code, li tt, li code {
|
||
background-color: #f8f8f8;
|
||
}
|
||
/* Tweak the pre margin -- 0px doesn't come out well */
|
||
pre {
|
||
margin-top: 0.5px;
|
||
}
|
||
/* Tweak the comact list text */
|
||
ul.compact, .ulCompact,
|
||
ol.compact, .olCompact,
|
||
dl.compact, .dlCompact {
|
||
line-height: normal;
|
||
}
|
||
/* Don't add top margin for nested lists */
|
||
li > ul, li > ol, li > dl,
|
||
dd > ul, dd > ol, dd > dl,
|
||
dl > dd > dl {
|
||
margin-top: initial;
|
||
}
|
||
/* Elements that should not be rendered on the same line as a <dt> */
|
||
/* This should match the element list in writer.text.TextWriter.render_dl() */
|
||
dd > div.artwork:first-child,
|
||
dd > aside:first-child,
|
||
dd > figure:first-child,
|
||
dd > ol:first-child,
|
||
dd > div:first-child > pre.sourcecode,
|
||
dd > table:first-child,
|
||
dd > ul:first-child {
|
||
clear: left;
|
||
}
|
||
/* fix for weird browser behaviour when <dd/> is empty */
|
||
dt+dd:empty::before{
|
||
content: "\00a0";
|
||
}
|
||
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
|
||
li > p {
|
||
margin-bottom: 0.5em
|
||
}
|
||
/* Don't let p margin spill out from inside list items */
|
||
li > p:last-of-type {
|
||
margin-bottom: 0;
|
||
}
|
||
</style>
|
||
<link href="rfc-local.css" rel="stylesheet" type="text/css">
|
||
<script type="application/javascript">async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(let t=0;t<e.length;t++)if(/#identifiers/.exec(e[t].selectorText)){const a=e[t].cssText.replace("#identifiers","#external-updates");document.styleSheets[0].insertRule(a,document.styleSheets[0].cssRules.length)}}catch(e){console.log(e)}const e=document.getElementById("external-metadata");if(e)try{var t,a="",o=function(e){const t=document.getElementsByTagName("meta");for(let a=0;a<t.length;a++)if(t[a].getAttribute("name")===e)return t[a].getAttribute("content");return""}("rfc.number");if(o){t="https://www.rfc-editor.org/rfc/rfc"+o+".json";try{const e=await fetch(t);a=await e.json()}catch(e){t=document.URL.indexOf("html")>=0?document.URL.replace(/html$/,"json"):document.URL+".json";const o=await fetch(t);a=await o.json()}}if(!a)return;e.style.display="block";const s="",d="https://datatracker.ietf.org/doc",n="https://datatracker.ietf.org/ipr/search",c="https://www.rfc-editor.org/info",l=a.doc_id.toLowerCase(),i=a.doc_id.slice(0,3).toLowerCase(),f=a.doc_id.slice(3).replace(/^0+/,""),u={status:"Status",obsoletes:"Obsoletes",obsoleted_by:"Obsoleted By",updates:"Updates",updated_by:"Updated By",see_also:"See Also",errata_url:"Errata"};let h="<dl style='overflow:hidden' id='external-updates'>";["status","obsoletes","obsoleted_by","updates","updated_by","see_also","errata_url"].forEach(e=>{if("status"==e){a[e]=a[e].toLowerCase();var t=a[e].split(" "),o=t.length,w="",p=1;for(let e=0;e<o;e++)p<o?w=w+r(t[e])+" ":w+=r(t[e]),p++;a[e]=w}else if("obsoletes"==e||"obsoleted_by"==e||"updates"==e||"updated_by"==e){var g,m="",b=1;g=a[e].length;for(let t=0;t<g;t++)a[e][t]&&(a[e][t]=String(a[e][t]).toLowerCase(),m=b<g?m+"<a href='"+s+"/rfc/".concat(a[e][t])+"'>"+a[e][t].slice(3)+"</a>, ":m+"<a href='"+s+"/rfc/".concat(a[e][t])+"'>"+a[e][t].slice(3)+"</a>",b++);a[e]=m}else if("see_also"==e){var y,L="",C=1;y=a[e].length;for(let t=0;t<y;t++)if(a[e][t]){a[e][t]=String(a[e][t]);var _=a[e][t].slice(0,3),v=a[e][t].slice(3).replace(/^0+/,"");L=C<y?"RFC"!=_?L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+_+" "+v+"</a>, ":L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+v+"</a>, ":"RFC"!=_?L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+_+" "+v+"</a>":L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+v+"</a>",C++}a[e]=L}else if("errata_url"==e){var R="";R=a[e]?R+"<a href='"+a[e]+"'>Errata exist</a> | <a href='"+d+"/"+l+"'>Datatracker</a>| <a href='"+n+"/?"+i+"="+f+"&submit="+i+"'>IPR</a> | <a href='"+c+"/"+l+"'>Info page</a>":"<a href='"+d+"/"+l+"'>Datatracker</a> | <a href='"+n+"/?"+i+"="+f+"&submit="+i+"'>IPR</a> | <a href='"+c+"/"+l+"'>Info page</a>",a[e]=R}""!=a[e]?"Errata"==u[e]?h+=`<dt>More info:</dt><dd>${a[e]}</dd>`:h+=`<dt>${u[e]}:</dt><dd>${a[e]}</dd>`:"Errata"==u[e]&&(h+=`<dt>More info:</dt><dd>${a[e]}</dd>`)}),h+="</dl>",e.innerHTML=h}catch(e){console.log(e)}else console.log("Could not locate metadata <div> element");function r(e){return e.charAt(0).toUpperCase()+e.slice(1)}}window.removeEventListener("load",addMetadata),window.addEventListener("load",addMetadata);</script>
|
||
</head>
|
||
<body>
|
||
<script src="metadata.min.js"></script>
|
||
<table class="ears">
|
||
<thead><tr>
|
||
<td class="left">Internet-Draft</td>
|
||
<td class="center">MISP taxonomy format</td>
|
||
<td class="right">December 2023</td>
|
||
</tr></thead>
|
||
<tfoot><tr>
|
||
<td class="left">Dulaunoy & Iklody</td>
|
||
<td class="center">Expires 26 June 2024</td>
|
||
<td class="right">[Page]</td>
|
||
</tr></tfoot>
|
||
</table>
|
||
<div id="external-metadata" class="document-information"></div>
|
||
<div id="internal-metadata" class="document-information">
|
||
<dl id="identifiers">
|
||
<dt class="label-workgroup">Workgroup:</dt>
|
||
<dd class="workgroup">Network Working Group</dd>
|
||
<dt class="label-internet-draft">Internet-Draft:</dt>
|
||
<dd class="internet-draft">draft-08</dd>
|
||
<dt class="label-published">Published:</dt>
|
||
<dd class="published">
|
||
<time datetime="2023-12-24" class="published">24 December 2023</time>
|
||
</dd>
|
||
<dt class="label-intended-status">Intended Status:</dt>
|
||
<dd class="intended-status">Informational</dd>
|
||
<dt class="label-expires">Expires:</dt>
|
||
<dd class="expires"><time datetime="2024-06-26">26 June 2024</time></dd>
|
||
<dt class="label-authors">Authors:</dt>
|
||
<dd class="authors">
|
||
<div class="author">
|
||
<div class="author-name">A. Dulaunoy</div>
|
||
<div class="org">CIRCL</div>
|
||
</div>
|
||
<div class="author">
|
||
<div class="author-name">A. Iklody</div>
|
||
<div class="org">CIRCL</div>
|
||
</div>
|
||
</dd>
|
||
</dl>
|
||
</div>
|
||
<h1 id="title">MISP taxonomy format</h1>
|
||
<section id="section-abstract">
|
||
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
|
||
<p id="section-abstract-1">This document describes the MISP taxonomy format which describes a simple JSON format to
|
||
represent machine tags (also called triple tags) vocabularies. A public directory of common vocabularies
|
||
called MISP taxonomies is available and relies on the MISP taxonomy format. MISP taxonomies are used to classify
|
||
cyber security events, threats, suspicious events, or indicators.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
|
||
</section>
|
||
<div id="status-of-memo">
|
||
<section id="section-boilerplate.1">
|
||
<h2 id="name-status-of-this-memo">
|
||
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
|
||
</h2>
|
||
<p id="section-boilerplate.1-1">
|
||
This Internet-Draft is submitted in full conformance with the
|
||
provisions of BCP 78 and BCP 79.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
|
||
<p id="section-boilerplate.1-2">
|
||
Internet-Drafts are working documents of the Internet Engineering Task
|
||
Force (IETF). Note that other groups may also distribute working
|
||
documents as Internet-Drafts. The list of current Internet-Drafts is
|
||
at <span><a href="https://datatracker.ietf.org/drafts/current/">https://datatracker.ietf.org/drafts/current/</a></span>.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
|
||
<p id="section-boilerplate.1-3">
|
||
Internet-Drafts are draft documents valid for a maximum of six months
|
||
and may be updated, replaced, or obsoleted by other documents at any
|
||
time. It is inappropriate to use Internet-Drafts as reference
|
||
material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
|
||
<p id="section-boilerplate.1-4">
|
||
This Internet-Draft will expire on 26 June 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
|
||
</section>
|
||
</div>
|
||
<div id="copyright">
|
||
<section id="section-boilerplate.2">
|
||
<h2 id="name-copyright-notice">
|
||
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
|
||
</h2>
|
||
<p id="section-boilerplate.2-1">
|
||
Copyright (c) 2023 IETF Trust and the persons identified as the
|
||
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
|
||
<p id="section-boilerplate.2-2">
|
||
This document is subject to BCP 78 and the IETF Trust's Legal
|
||
Provisions Relating to IETF Documents
|
||
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
|
||
publication of this document. Please review these documents
|
||
carefully, as they describe your rights and restrictions with
|
||
respect to this document.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
|
||
</section>
|
||
</div>
|
||
<div id="toc">
|
||
<section id="section-toc.1">
|
||
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
|
||
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
|
||
</h2>
|
||
<nav class="toc"><ul class="compact toc ulBare ulEmpty">
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
|
||
<p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>. <a href="#name-introduction" class="xref">Introduction</a></p>
|
||
<ul class="compact toc ulBare ulEmpty">
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.1">
|
||
<p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>. <a href="#name-conventions-and-terminology" class="xref">Conventions and Terminology</a></p>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
|
||
<p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>. <a href="#name-format" class="xref">Format</a></p>
|
||
<ul class="compact toc ulBare ulEmpty">
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.1">
|
||
<p id="section-toc.1-1.2.2.1.1" class="keepWithNext"><a href="#section-2.1" class="xref">2.1</a>. <a href="#name-overview" class="xref">Overview</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.2">
|
||
<p id="section-toc.1-1.2.2.2.1"><a href="#section-2.2" class="xref">2.2</a>. <a href="#name-predicates" class="xref">predicates</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.3">
|
||
<p id="section-toc.1-1.2.2.3.1"><a href="#section-2.3" class="xref">2.3</a>. <a href="#name-values" class="xref">values</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.4">
|
||
<p id="section-toc.1-1.2.2.4.1"><a href="#section-2.4" class="xref">2.4</a>. <a href="#name-optional-fields" class="xref">optional fields</a></p>
|
||
<ul class="compact toc ulBare ulEmpty">
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.4.2.1">
|
||
<p id="section-toc.1-1.2.2.4.2.1.1"><a href="#section-2.4.1" class="xref">2.4.1</a>. <a href="#name-colour" class="xref">colour</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.4.2.2">
|
||
<p id="section-toc.1-1.2.2.4.2.2.1"><a href="#section-2.4.2" class="xref">2.4.2</a>. <a href="#name-description" class="xref">description</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.4.2.3">
|
||
<p id="section-toc.1-1.2.2.4.2.3.1"><a href="#section-2.4.3" class="xref">2.4.3</a>. <a href="#name-numerical_value" class="xref">numerical_value</a></p>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
|
||
<p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-directory" class="xref">Directory</a></p>
|
||
<ul class="compact toc ulBare ulEmpty">
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1">
|
||
<p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>. <a href="#name-sample-manifest" class="xref">Sample Manifest</a></p>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
|
||
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-sample-taxonomy-in-misp-tax" class="xref">Sample Taxonomy in MISP taxonomy format</a></p>
|
||
<ul class="compact toc ulBare ulEmpty">
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1">
|
||
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-admiralty-scale-taxonomy" class="xref">Admiralty Scale Taxonomy</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2">
|
||
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-open-source-intelligence-cl" class="xref">Open Source Intelligence - Classification</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3">
|
||
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-available-taxonomies-in-the" class="xref">Available taxonomies in the public directory</a></p>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
|
||
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-json-schema" class="xref">JSON Schema</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
|
||
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
|
||
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-normative-references" class="xref">Normative References</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
|
||
<p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>. <a href="#name-informative-references" class="xref">Informative References</a></p>
|
||
</li>
|
||
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
|
||
<p id="section-toc.1-1.9.1"><a href="#appendix-A" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
|
||
</li>
|
||
</ul>
|
||
</nav>
|
||
</section>
|
||
</div>
|
||
<div id="introduction">
|
||
<section id="section-1">
|
||
<h2 id="name-introduction">
|
||
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
|
||
</h2>
|
||
<p id="section-1-1">Sharing threat information became a fundamental requirements on the Internet, security and intelligence community at large. Threat
|
||
information can include indicators of compromise, malicious file indicators, financial fraud indicators
|
||
or even detailed information about a threat actor. While sharing such indicators or information, classification plays an important role
|
||
to ensure adequate distribution, understanding, validation or action of the shared information. MISP taxonomies is a public repository
|
||
of known vocabularies that can be used in threat information sharing.<a href="#section-1-1" class="pilcrow">¶</a></p>
|
||
<p id="section-1-2">Machine tags were introduced in 2007 <span>[<a href="#machine-tags" class="xref">machine-tags</a>]</span> to allow users to be more precise when tagging their pictures with geolocation.
|
||
So a machine tag is a tag which uses a special syntax to provide more information to users and machines. Machine tags are also known
|
||
as triple tags due to their format.<a href="#section-1-2" class="pilcrow">¶</a></p>
|
||
<p id="section-1-3">In the MISP taxonomy context, machine tags help analysts to classify their cybersecurity events, indicators or threats. MISP taxonomies can be used for classification, filtering, triggering actions or visualisation depending on their use in threat intelligence platforms such as MISP <span>[<a href="#MISP-P" class="xref">MISP-P</a>]</span>.<a href="#section-1-3" class="pilcrow">¶</a></p>
|
||
<div id="conventions-and-terminology">
|
||
<section id="section-1.1">
|
||
<h3 id="name-conventions-and-terminology">
|
||
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-conventions-and-terminology" class="section-name selfRef">Conventions and Terminology</a>
|
||
</h3>
|
||
<p id="section-1.1-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>",
|
||
"<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this
|
||
document are to be interpreted as described in RFC 2119 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span>.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
|
||
</section>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
<div id="format">
|
||
<section id="section-2">
|
||
<h2 id="name-format">
|
||
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-format" class="section-name selfRef">Format</a>
|
||
</h2>
|
||
<p id="section-2-1">A machine tag is composed of a namespace (<span class="bcp14">MUST</span>), a predicate (<span class="bcp14">MUST</span>) and an optional value (<span class="bcp14">OPTIONAL</span>).<a href="#section-2-1" class="pilcrow">¶</a></p>
|
||
<p id="section-2-2">Machine tags are represented as a string. Below listed are a set of sample machine tags for different namespaces such as tlp, admiralty-scale and osint.<a href="#section-2-2" class="pilcrow">¶</a></p>
|
||
<div class="alignLeft art-text artwork" id="section-2-3">
|
||
<pre>tlp:amber
|
||
admiralty-scale:information-credibility="1"
|
||
osint:source-type="blog-post"
|
||
</pre><a href="#section-2-3" class="pilcrow">¶</a>
|
||
</div>
|
||
<p id="section-2-4">The MISP taxonomy format describes how to define a machine tag namespace in a parseable format. The objective is to provide a simple format
|
||
to describe machine tag (aka triple tag) vocabularies.<a href="#section-2-4" class="pilcrow">¶</a></p>
|
||
<div id="overview">
|
||
<section id="section-2.1">
|
||
<h3 id="name-overview">
|
||
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-overview" class="section-name selfRef">Overview</a>
|
||
</h3>
|
||
<p id="section-2.1-1">The MISP taxonomy format uses the JSON <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span> format. Each namespace is represented as a JSON object with meta information including the following fields: namespace, description, version, type.<a href="#section-2.1-1" class="pilcrow">¶</a></p>
|
||
<p id="section-2.1-2">namespace defines the overall namespace of the machine tag. The namespace is represented as a string and <span class="bcp14">MUST</span> be present. The description is represented as a string and <span class="bcp14">MUST</span> be present. A version is represented as a unsigned integer <span class="bcp14">MUST</span> be present. A type defines where a specific taxonomy is applicable and a type can be applicable at event, user or org level. The type is represented as an array containing one or more type and <span class="bcp14">SHOULD</span> be present. If a type is not mentioned, by default, the taxonomy is applicable at event level only. An exclusive boolean property <span class="bcp14">MAY</span> be present and defines at namespace level if the predicates are mutually exclusive.<a href="#section-2.1-2" class="pilcrow">¶</a></p>
|
||
<p id="section-2.1-3">predicates defines all the predicates available in the namespace defined. predicates is represented as an array of JSON objects. predicates <span class="bcp14">MUST</span> be present and <span class="bcp14">MUST</span> at least content one element.<a href="#section-2.1-3" class="pilcrow">¶</a></p>
|
||
<p id="section-2.1-4">values defines all the values for each predicate in the namespace defined. values <span class="bcp14">SHOULD</span> be present.<a href="#section-2.1-4" class="pilcrow">¶</a></p>
|
||
</section>
|
||
</div>
|
||
<div id="predicates">
|
||
<section id="section-2.2">
|
||
<h3 id="name-predicates">
|
||
<a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-predicates" class="section-name selfRef">predicates</a>
|
||
</h3>
|
||
<p id="section-2.2-1">The predicates array contains one or more JSON objects which lists all the possible predicates. The JSON object contains two fields: value and expanded. value <span class="bcp14">MUST</span> be present. expanded <span class="bcp14">SHOULD</span> be present. value is represented as a string and describes the predicate value. The predicate value <span class="bcp14">MUST</span> not contain spaces or colons. expanded is represented as a string and describes the human-readable version of the predicate value. An exclusive property <span class="bcp14">MAY</span> be present and defines at namespace level if the values are mutually exclusive.<a href="#section-2.2-1" class="pilcrow">¶</a></p>
|
||
</section>
|
||
</div>
|
||
<div id="values">
|
||
<section id="section-2.3">
|
||
<h3 id="name-values">
|
||
<a href="#section-2.3" class="section-number selfRef">2.3. </a><a href="#name-values" class="section-name selfRef">values</a>
|
||
</h3>
|
||
<p id="section-2.3-1">The values array contain one or more JSON objects which lists all the possible values of a predicate. The JSON object contains two fields: predicate and entry. predicate is represented as a string and describes the predicate value. entry is an array with one or more JSON objects. The JSON object contains two fields: value and expanded. value <span class="bcp14">MUST</span> be present. expanded <span class="bcp14">SHOULD</span> be present. value is represented as a string and describes the machine parsable value. expanded is represented as a string and describes the human-readable version of the value.<a href="#section-2.3-1" class="pilcrow">¶</a></p>
|
||
</section>
|
||
</div>
|
||
<div id="optional-fields">
|
||
<section id="section-2.4">
|
||
<h3 id="name-optional-fields">
|
||
<a href="#section-2.4" class="section-number selfRef">2.4. </a><a href="#name-optional-fields" class="section-name selfRef">optional fields</a>
|
||
</h3>
|
||
<div id="colour">
|
||
<section id="section-2.4.1">
|
||
<h4 id="name-colour">
|
||
<a href="#section-2.4.1" class="section-number selfRef">2.4.1. </a><a href="#name-colour" class="section-name selfRef">colour</a>
|
||
</h4>
|
||
<p id="section-2.4.1-1">colour fields <span class="bcp14">MAY</span> be used at predicates or values level to set a specify colour that <span class="bcp14">MAY</span> be used by the implementation. The colour field is described as an RGB colour fill in hexadecimal representation.<a href="#section-2.4.1-1" class="pilcrow">¶</a></p>
|
||
<p id="section-2.4.1-2">Example use of the colour field in the Traffic Light Protocol (TLP):<a href="#section-2.4.1-2" class="pilcrow">¶</a></p>
|
||
<div class="alignLeft art-text artwork" id="section-2.4.1-3">
|
||
<pre>"predicates": [
|
||
{
|
||
"colour": "#CC0033",
|
||
"expanded": "(TLP:RED) Information exclusively and directly
|
||
given to (a group of) individual recipients.
|
||
Sharing outside is not legitimate.",
|
||
"value": "red"
|
||
},
|
||
{
|
||
"colour": "#FFC000",
|
||
"expanded": "(TLP:AMBER) Information exclusively given
|
||
to an organization; sharing limited within
|
||
the organization to be effectively acted upon.",
|
||
"value": "amber"
|
||
}...]
|
||
</pre><a href="#section-2.4.1-3" class="pilcrow">¶</a>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
<div id="description">
|
||
<section id="section-2.4.2">
|
||
<h4 id="name-description">
|
||
<a href="#section-2.4.2" class="section-number selfRef">2.4.2. </a><a href="#name-description" class="section-name selfRef">description</a>
|
||
</h4>
|
||
<p id="section-2.4.2-1">description fields <span class="bcp14">MAY</span> be used at predicates or values level to add a descriptive and human-readable information about the specific predicate or value. The field is represented as a string. Implementations <span class="bcp14">MAY</span> use the description field to improve more contextual information. The description at the namespace level is a <span class="bcp14">MUST</span> as described above.<a href="#section-2.4.2-1" class="pilcrow">¶</a></p>
|
||
</section>
|
||
</div>
|
||
<div id="numerical-value">
|
||
<section id="section-2.4.3">
|
||
<h4 id="name-numerical_value">
|
||
<a href="#section-2.4.3" class="section-number selfRef">2.4.3. </a><a href="#name-numerical_value" class="section-name selfRef">numerical_value</a>
|
||
</h4>
|
||
<p id="section-2.4.3-1">numerical_value fields <span class="bcp14">MAY</span> be used at a predicate or value level to add a machine-readable numeric value to a specific predicate or value.
|
||
The field is represented as a JSON number. Implementations <span class="bcp14">SHOULD</span> use the decimal value provided to support scoring or filtering.<a href="#section-2.4.3-1" class="pilcrow">¶</a></p>
|
||
<p id="section-2.4.3-2">The decimal range for numerical_value <span class="bcp14">SHOULD</span> use a range from 0 up to 100. The range is recommended to support common mathematical properties
|
||
among taxonomies.<a href="#section-2.4.3-2" class="pilcrow">¶</a></p>
|
||
<p id="section-2.4.3-3">Example use of the numerical_value in the MISP confidence level:<a href="#section-2.4.3-3" class="pilcrow">¶</a></p>
|
||
<div class="alignLeft art-text artwork" id="section-2.4.3-4">
|
||
<pre> {
|
||
"predicate": "confidence-level",
|
||
"entry": [
|
||
{
|
||
"expanded": "Completely confident",
|
||
"value": "completely-confident",
|
||
"numerical_value": 100
|
||
},
|
||
{
|
||
"expanded": "Usually confident",
|
||
"value": "usually-confident",
|
||
"numerical_value": 75
|
||
},
|
||
{
|
||
"expanded": "Fairly confident",
|
||
"value": "fairly-confident",
|
||
"numerical_value": 50
|
||
},
|
||
{
|
||
"expanded": "Rarely confident",
|
||
"value": "rarely-confident",
|
||
"numerical_value": 25
|
||
},
|
||
{
|
||
"expanded": "Unconfident",
|
||
"value": "unconfident",
|
||
"numerical_value": 0
|
||
},
|
||
{
|
||
"expanded": "Confidence cannot be evaluated",
|
||
"value": "confidence-cannot-be-evalued"
|
||
}
|
||
]
|
||
}
|
||
</pre><a href="#section-2.4.3-4" class="pilcrow">¶</a>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
<div id="directory">
|
||
<section id="section-3">
|
||
<h2 id="name-directory">
|
||
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-directory" class="section-name selfRef">Directory</a>
|
||
</h2>
|
||
<p id="section-3-1">The MISP taxonomies directory is publicly available <span>[<a href="#MISP-T" class="xref">MISP-T</a>]</span> in a git repository. The repository
|
||
contains a directory per namespace then a file machinetag.json which contains the taxonomy as
|
||
described in the format above. In the root of the repository, a MANIFEST.json exists containing
|
||
a list of all the taxonomies.<a href="#section-3-1" class="pilcrow">¶</a></p>
|
||
<p id="section-3-2">The MANIFEST.json file is composed of an JSON object with metadata like version, license, description, url and path.
|
||
A taxonomies array describes the taxonomy available with the description, name and version field.<a href="#section-3-2" class="pilcrow">¶</a></p>
|
||
<div id="sample-manifest">
|
||
<section id="section-3.1">
|
||
<h3 id="name-sample-manifest">
|
||
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-sample-manifest" class="section-name selfRef">Sample Manifest</a>
|
||
</h3>
|
||
<div class="alignLeft art-text artwork" id="section-3.1-1">
|
||
<pre>{
|
||
"version": "20161009",
|
||
"license": "CC-0",
|
||
"description": "Manifest file of MISP taxonomies available.",
|
||
"url":
|
||
"https://raw.githubusercontent.com/MISP/misp-taxonomies/master/",
|
||
"path": "machinetag.json",
|
||
"taxonomies": [
|
||
{
|
||
"description": "The Admiralty Scale (also called the NATO System)
|
||
is used to rank the reliability of a source and
|
||
the credibility of an information.",
|
||
"name": "admiralty-scale",
|
||
"version": 1
|
||
},
|
||
{
|
||
"description": "Open Source Intelligence - Classification.",
|
||
"name": "osint",
|
||
"version": 2
|
||
}]
|
||
}
|
||
</pre><a href="#section-3.1-1" class="pilcrow">¶</a>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
<div id="sample-taxonomy-in-misp-taxonomy-format">
|
||
<section id="section-4">
|
||
<h2 id="name-sample-taxonomy-in-misp-tax">
|
||
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-sample-taxonomy-in-misp-tax" class="section-name selfRef">Sample Taxonomy in MISP taxonomy format</a>
|
||
</h2>
|
||
<div id="admiralty-scale-taxonomy">
|
||
<section id="section-4.1">
|
||
<h3 id="name-admiralty-scale-taxonomy">
|
||
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-admiralty-scale-taxonomy" class="section-name selfRef">Admiralty Scale Taxonomy</a>
|
||
</h3>
|
||
<div class="alignLeft art-text artwork" id="section-4.1-1">
|
||
<pre> "namespace": "admiralty-scale",
|
||
"description": "The Admiralty Scale (also called the NATO System)
|
||
is used to rank the reliability of a source and
|
||
the credibility of an information.",
|
||
"version": 1,
|
||
"predicates": [
|
||
{
|
||
"value": "source-reliability",
|
||
"expanded": "Source Reliability"
|
||
},
|
||
{
|
||
"value": "information-credibility",
|
||
"expanded": "Information Credibility"
|
||
}
|
||
],
|
||
"values": [
|
||
{
|
||
"predicate": "source-reliability",
|
||
"entry": [
|
||
{
|
||
"value": "a",
|
||
"expanded": "Completely reliable"
|
||
},
|
||
{
|
||
"value": "b",
|
||
"expanded": "Usually reliable"
|
||
},
|
||
{
|
||
"value": "c",
|
||
"expanded": "Fairly reliable"
|
||
},
|
||
{
|
||
"value": "d",
|
||
"expanded": "Not usually reliable"
|
||
},
|
||
{
|
||
"value": "e",
|
||
"expanded": "Unreliable"
|
||
},
|
||
{
|
||
"value": "f",
|
||
"expanded": "Reliability cannot be judged"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"predicate": "information-credibility",
|
||
"entry": [
|
||
{
|
||
"value": "1",
|
||
"expanded": "Confirmed by other sources"
|
||
},
|
||
{
|
||
"value": "2",
|
||
"expanded": "Probably true"
|
||
},
|
||
{
|
||
"value": "3",
|
||
"expanded": "Possibly true"
|
||
},
|
||
{
|
||
"value": "4",
|
||
"expanded": "Doubtful"
|
||
},
|
||
{
|
||
"value": "5",
|
||
"expanded": "Improbable"
|
||
},
|
||
{
|
||
"value": "6",
|
||
"expanded": "Truth cannot be judged"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
}
|
||
</pre><a href="#section-4.1-1" class="pilcrow">¶</a>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
<div id="open-source-intelligence-classification">
|
||
<section id="section-4.2">
|
||
<h3 id="name-open-source-intelligence-cl">
|
||
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-open-source-intelligence-cl" class="section-name selfRef">Open Source Intelligence - Classification</a>
|
||
</h3>
|
||
<div class="alignLeft art-text artwork" id="section-4.2-1">
|
||
<pre>{
|
||
"values": [
|
||
{
|
||
"entry": [
|
||
{
|
||
"expanded": "Blog post",
|
||
"value": "blog-post"
|
||
},
|
||
{
|
||
"expanded": "Technical or analysis report",
|
||
"value": "technical-report"
|
||
},
|
||
{
|
||
"expanded": "News report",
|
||
"value": "news-report"
|
||
},
|
||
{
|
||
"expanded": "Pastie-like website",
|
||
"value": "pastie-website"
|
||
},
|
||
{
|
||
"expanded": "Electronic forum",
|
||
"value": "electronic-forum"
|
||
},
|
||
{
|
||
"expanded": "Mailing-list",
|
||
"value": "mailing-list"
|
||
},
|
||
{
|
||
"expanded": "Block or Filter List",
|
||
"value": "block-or-filter-list"
|
||
},
|
||
{
|
||
"expanded": "Expansion",
|
||
"value": "expansion"
|
||
}
|
||
],
|
||
"predicate": "source-type"
|
||
},
|
||
{
|
||
"predicate": "lifetime",
|
||
"entry": [
|
||
{
|
||
"value": "perpetual",
|
||
"expanded": "Perpetual",
|
||
"description": "Information available publicly on long-term"
|
||
},
|
||
{
|
||
"value": "ephemeral",
|
||
"expanded": "Ephemeral",
|
||
"description": "Information available publicly on short-term"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"predicate": "certainty",
|
||
"entry": [
|
||
{
|
||
"numerical_value": 100,
|
||
"value": "100",
|
||
"expanded": "100% Certainty",
|
||
"description": "100% Certainty"
|
||
},
|
||
{
|
||
"numerical_value": 93,
|
||
"value": "93",
|
||
"expanded": "93% Almost certain",
|
||
"description": "93% Almost certain"
|
||
},
|
||
{
|
||
"numerical_value": 75,
|
||
"value": "75",
|
||
"expanded": "75% Probable",
|
||
"description": "75% Probable"
|
||
},
|
||
{
|
||
"numerical_value": 50,
|
||
"value": "50",
|
||
"expanded": "50% Chances about even",
|
||
"description": "50% Chances about even"
|
||
},
|
||
{
|
||
"numerical_value": 30,
|
||
"value": "30",
|
||
"expanded": "30% Probably not",
|
||
"description": "30% Probably not"
|
||
},
|
||
{
|
||
"numerical_value": 7,
|
||
"value": "7",
|
||
"expanded": "7% Almost certainly not",
|
||
"description": "7% Almost certainly not"
|
||
},
|
||
{
|
||
"numerical_value": 0,
|
||
"value": "0",
|
||
"expanded": "0% Impossibility",
|
||
"description": "0% Impossibility"
|
||
}
|
||
]
|
||
}
|
||
],
|
||
"namespace": "osint",
|
||
"description": "Open Source Intelligence - Classification",
|
||
"version": 3,
|
||
"predicates": [
|
||
{
|
||
"value": "source-type",
|
||
"expanded": "Source Type"
|
||
},
|
||
{
|
||
"value": "lifetime",
|
||
"expanded": "Lifetime of the information
|
||
as Open Source Intelligence"
|
||
},
|
||
{
|
||
"value": "certainty",
|
||
"expanded": "Certainty of the elements mentioned
|
||
in this Open Source Intelligence"
|
||
}
|
||
]
|
||
}
|
||
|
||
</pre><a href="#section-4.2-1" class="pilcrow">¶</a>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
<div id="available-taxonomies-in-the-public-directory">
|
||
<section id="section-4.3">
|
||
<h3 id="name-available-taxonomies-in-the">
|
||
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-available-taxonomies-in-the" class="section-name selfRef">Available taxonomies in the public directory</a>
|
||
</h3>
|
||
<p id="section-4.3-1">The public directory of MISP taxonomies <span>[<a href="#MISP-T" class="xref">MISP-T</a>]</span> contains a variety of taxonomy in various fields such as:<a href="#section-4.3-1" class="pilcrow">¶</a></p>
|
||
<span class="break"></span><dl class="dlCompact dlParallel" id="section-4.3-2">
|
||
<dt id="section-4.3-2.1">CERT-XLM:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.2">CERT-XLM Security Incident Classification.<a href="#section-4.3-2.2" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.3">DFRLab-dichotomies-of-disinformation:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.4">DFRLab Dichotomies of Disinformation.<a href="#section-4.3-2.4" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.5">DML:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.6">The Detection Maturity Level (DML) model is a capability maturity model for referencing ones maturity in detecting cyber attacks. It's designed for organizations who perform intel-driven detection and response and who put an emphasis on having a mature detection program.<a href="#section-4.3-2.6" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.7">GrayZone:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.8">Gray Zone of Active defense includes all elements which lay between reactive defense elements and offensive operations. It does fill the gray spot between them. Taxo may be used for active defense planning or modeling.<a href="#section-4.3-2.8" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.9">PAP:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.10">The Permissible Actions Protocol - or short: PAP - was designed to indicate how the received information can be used.<a href="#section-4.3-2.10" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.11">access-method:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.12">The access method used to remotely access a system.<a href="#section-4.3-2.12" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.13">accessnow:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.14">Access Now classification to classify an issue (such as security, human rights, youth rights).<a href="#section-4.3-2.14" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.15">action-taken:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.16">Action taken in the case of a security incident (CSIRT perspective).<a href="#section-4.3-2.16" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.17">admiralty-scale:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.18">The Admiralty Scale or Ranking (also called the NATO System) is used to rank the reliability of a source and the credibility of an information. Reference based on FM 2-22.3 (FM 34-52) HUMAN INTELLIGENCE COLLECTOR OPERATIONS and NATO documents.<a href="#section-4.3-2.18" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.19">adversary:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.20">An overview and description of the adversary infrastructure<a href="#section-4.3-2.20" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.21">ais-marking:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.22">The AIS Marking Schema implementation is maintained by the National Cybersecurity and Communication Integration Center (NCCIC) of the U.S. Department of Homeland Security (DHS)<a href="#section-4.3-2.22" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.23">analyst-assessment:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.24">A series of assessment predicates describing the analyst capabilities to perform analysis. These assessment can be assigned by the analyst him/herself or by another party evaluating the analyst.<a href="#section-4.3-2.24" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.25">approved-category-of-action:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.26">A pre-approved category of action for indicators being shared with partners (MIMIC).<a href="#section-4.3-2.26" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.27">artificial-satellites:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.28">This taxonomy was designed to describe artificial satellites<a href="#section-4.3-2.28" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.29">aviation:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.30">A taxonomy describing security threats or incidents against the aviation sector.<a href="#section-4.3-2.30" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.31">binary-class:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.32">Custom taxonomy for types of binary file.<a href="#section-4.3-2.32" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.33">cccs:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.34">Internal taxonomy for CCCS.<a href="#section-4.3-2.34" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.35">circl:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.36">CIRCL Taxonomy - Schemes of Classification in Incident Response and Detection.<a href="#section-4.3-2.36" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.37">cnsd:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.38">La presente taxonomia es la primera versi&#243;n disponible para el Centro Nacional de Seguridad Digital del Per&#250;.<a href="#section-4.3-2.38" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.39">coa:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.40">Course of action taken within organization to discover, detect, deny, disrupt, degrade, deceive and/or destroy an attack.<a href="#section-4.3-2.40" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.41">collaborative-intelligence:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.42">Collaborative intelligence support language is a common language to support analysts to perform their analysis to get crowdsourced support when using threat intelligence sharing platform like MISP. The objective of this language is to advance collaborative analysis and to share earlier than later.<a href="#section-4.3-2.42" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.43">common-taxonomy:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.44">Common Taxonomy for Law enforcement and CSIRTs<a href="#section-4.3-2.44" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.45">copine-scale:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.46">The COPINE Scale is a rating system created in Ireland and used in the United Kingdom to categorise the severity of images of child sex abuse. The scale was developed by staff at the COPINE (Combating Paedophile Information Networks in Europe) project. The COPINE Project was founded in 1997, and is based in the Department of Applied Psychology, University College Cork, Ireland.<a href="#section-4.3-2.46" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.47">course-of-action:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.48">A Course Of Action analysis considers six potential courses of action for the development of a cyber security capability.<a href="#section-4.3-2.48" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.49">crowdsec:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.50">Crowdsec IP address classifications and behaviors taxonomy.<a href="#section-4.3-2.50" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.51">cryptocurrency-threat:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.52">Threats targetting cryptocurrency, based on CipherTrace report.<a href="#section-4.3-2.52" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.53">csirt-americas:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.54">Taxonom&#237;a CSIRT Am&#233;ricas.<a href="#section-4.3-2.54" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.55">csirt_case_classification:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.56">It is critical that the CSIRT provide consistent and timely response to the customer, and that sensitive information is handled appropriately. This document provides the guidelines needed for CSIRT Incident Managers (IM) to classify the case category, criticality level, and sensitivity level for each CSIRT case. This information will be entered into the Incident Tracking System (ITS) when a case is created. Consistent case classification is required for the CSIRT to provide accurate reporting to management on a regular basis. In addition, the classifications will provide CSIRT IM's with proper case handling procedures and will form the basis of SLA's between the CSIRT and other Company departments.<a href="#section-4.3-2.56" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.57">cssa:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.58">The CSSA agreed sharing taxonomy.<a href="#section-4.3-2.58" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.59">cti:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.60">Cyber Threat Intelligence cycle to control workflow state of your process.<a href="#section-4.3-2.60" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.61">current-event:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.62">Current events - Schemes of Classification in Incident Response and Detection<a href="#section-4.3-2.62" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.63">cyber-threat-framework:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.64">Cyber Threat Framework was developed by the US Government to enable consistent characterization and categorization of cyber threat events, and to identify trends or changes in the activities of cyber adversaries. <a href="https://www.dni.gov/index.php/cyber-threat-framework">https://www.dni.gov/index.php/cyber-threat-framework</a><a href="#section-4.3-2.64" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.65">cycat:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.66">Taxonomy used by CyCAT, the Universal Cybersecurity Resource Catalogue, to categorize the namespaces it supports and uses.<a href="#section-4.3-2.66" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.67">cytomic-orion:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.68">Taxonomy to describe desired actions for Cytomic Orion<a href="#section-4.3-2.68" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.69">dark-web:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.70">Criminal motivation and content detection the dark web: A categorisation model for law enforcement. ref: Janis Dalins, Campbell Wilson, Mark Carman. Taxonomy updated by MISP Project and extended by the JRC (Joint Research Centre) of the European Commission.<a href="#section-4.3-2.70" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.71">data-classification:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.72">Data classification for data potentially at risk of exfiltration based on table 2.1 of Solving Cyber Risk book.<a href="#section-4.3-2.72" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.73">dcso-sharing:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.74">Taxonomy defined in the DCSO MISP Event Guide. It provides guidance for the creation and consumption of MISP events in a way that minimises the extra effort for the sending party, while enhancing the usefulness for receiving parties.<a href="#section-4.3-2.74" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.75">ddos:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.76">Distributed Denial of Service - or short: DDoS - taxonomy supports the description of Denial of Service attacks and especially the types they belong too.<a href="#section-4.3-2.76" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.77">de-vs:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.78">German (DE) Government classification markings (VS).<a href="#section-4.3-2.78" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.79">death-possibilities:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.80">Taxonomy of Death Possibilities<a href="#section-4.3-2.80" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.81">deception:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.82">Deception is an important component of information operations, valuable for both offense and defense.<a href="#section-4.3-2.82" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.83">dga:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.84">A taxonomy to describe domain-generation algorithms often called DGA. Ref: A Comprehensive Measurement Study of Domain Generating Malware Daniel Plohmann and others.<a href="#section-4.3-2.84" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.85">dhs-ciip-sectors:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.86">DHS critical sectors as in <a href="https://www.dhs.gov/critical-infrastructure-sectors">https://www.dhs.gov/critical-infrastructure-sectors</a><a href="#section-4.3-2.86" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.87">diamond-model:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.88">The Diamond Model for Intrusion Analysis establishes the basic atomic element of any intrusion activity, the event, composed of four core features: adversary, infrastructure, capability, and victim.<a href="#section-4.3-2.88" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.89">diamond-model-for-influence-operations:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.90">The diamond model for influence operations analysis is a framework that leads analysts and researchers toward a comprehensive understanding of a malign influence campaign by addressing the socio-political, technical, and psychological aspects of the campaign. The diamond model for influence operations analysis consists of 5 components: 4 corners and a core element. The 4 corners are divided into 2 axes: influencer and audience on the socio-political axis, capabilities and infrastructure on the technical axis. Narrative makes up the core of the diamond.<a href="#section-4.3-2.90" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.91">dni-ism:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.92">A subset of Information Security Marking Metadata ISM as required by Executive Order (EO) 13526. As described by DNI.gov as Data Encoding Specifications for Information Security Marking Metadata in Controlled Vocabulary Enumeration Values for ISM<a href="#section-4.3-2.92" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.93">domain-abuse:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.94">Domain Name Abuse - taxonomy to tag domain names used for cybercrime.<a href="#section-4.3-2.94" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.95">doping-substances:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.96">This taxonomy aims to list doping substances<a href="#section-4.3-2.96" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.97">drugs:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.98">A taxonomy based on the superclass and class of drugs. Based on <a href="https://www.drugbank.ca/releases/latest">https://www.drugbank.ca/releases/latest</a><a href="#section-4.3-2.98" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.99">economical-impact:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.100">Economical impact is a taxonomy to describe the financial impact as positive or negative gain to the tagged information (e.g. data exfiltration loss, a positive gain for an adversary).<a href="#section-4.3-2.100" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.101">ecsirt:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.102">Incident Classification by the ecsirt.net version mkVI of 31 March 2015 enriched with IntelMQ taxonomy-type mapping.<a href="#section-4.3-2.102" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.103">enisa:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.104">The present threat taxonomy is an initial version that has been developed on the basis of available ENISA material. This material has been used as an ENISA-internal structuring aid for information collection and threat consolidation purposes. It emerged in the time period 2012-2015.<a href="#section-4.3-2.104" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.105">estimative-language:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.106">Estimative language to describe quality and credibility of underlying sources, data, and methodologies based Intelligence Community Directive 203 (ICD 203) and JP 2-0, Joint Intelligence<a href="#section-4.3-2.106" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.107">eu-marketop-and-publicadmin:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.108">Market operators and public administrations that must comply to some notifications requirements under EU NIS directive<a href="#section-4.3-2.108" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.109">eu-nis-sector-and-subsectors:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.110">Sectors, subsectors, and digital services as identified by the NIS Directive<a href="#section-4.3-2.110" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.111">euci:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.112">EU classified information (EUCI) means any information or material designated by a EU security classification, the unauthorised disclosure of which could cause varying degrees of prejudice to the interests of the European Union or of one or more of the Member States.<a href="#section-4.3-2.112" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.113">europol-event:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.114">This taxonomy was designed to describe the type of events<a href="#section-4.3-2.114" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.115">europol-incident:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.116">This taxonomy was designed to describe the type of incidents by class.<a href="#section-4.3-2.116" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.117">event-assessment:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.118">A series of assessment predicates describing the event assessment performed to make judgement(s) under a certain level of uncertainty.<a href="#section-4.3-2.118" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.119">event-classification:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.120">Classification of events as seen in tools such as RT/IR, MISP and other<a href="#section-4.3-2.120" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.121">exercise:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.122">Exercise is a taxonomy to describe if the information is part of one or more cyber or crisis exercise.<a href="#section-4.3-2.122" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.123">extended-event:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.124">Reasons why an event has been extended. This taxonomy must be used on the extended event. The competitive analysis aspect is from Psychology of Intelligence Analysis by Richard J. Heuer, Jr. ref:<a href="http://www.foo.be/docs/intelligence/PsychofIntelNew.pdf">http://www.foo.be/docs/intelligence/PsychofIntelNew.pdf</a><a href="#section-4.3-2.124" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.125">failure-mode-in-machine-learning:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.126">The purpose of this taxonomy is to jointly tabulate both the of these failure modes in a single place. Intentional failures wherein the failure is caused by an active adversary attempting to subvert the system to attain her goals - either to misclassify the result, infer private training data, or to steal the underlying algorithm. Unintentional failures wherein the failure is because an ML system produces a formally correct but completely unsafe outcome.<a href="#section-4.3-2.126" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.127">false-positive:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.128">This taxonomy aims to ballpark the expected amount of false positives.<a href="#section-4.3-2.128" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.129">file-type:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.130">List of known file types.<a href="#section-4.3-2.130" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.131">financial:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.132">Financial taxonomy to describe financial services, infrastructure and financial scope.<a href="#section-4.3-2.132" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.133">flesch-reading-ease:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.134">Flesch Reading Ease is a revised system for determining the comprehension difficulty of written material. The scoring of the flesh score can have a maximum of 121.22 and there is no limit on how low a score can be (negative score are valid).<a href="#section-4.3-2.134" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.135">fpf:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.136">The Future of Privacy Forum (FPF) <a href="https://fpf.org/2016/04/25/a-visual-guide-to-practical-data-de-identification/">visual guide to practical de-identification</a> taxonomy is used to evaluate the degree of identifiability of personal data and the types of pseudonymous data, de-identified data and anonymous data. The work of FPF is licensed under a creative commons attribution 4.0 international license.<a href="#section-4.3-2.136" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.137">fr-classif:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.138">French gov information classification system<a href="#section-4.3-2.138" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.139">gdpr:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.140">Taxonomy related to the REGULATION (EU) 2016/679 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)<a href="#section-4.3-2.140" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.141">gea-nz-activities:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.142">Information needed to track or monitor moments, periods or events that occur over time. This type of information is focused on occurrences that must be tracked for business reasons or represent a specific point in the evolution of 'The Business'.<a href="#section-4.3-2.142" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.143">gea-nz-entities:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.144">Information relating to instances of entities or things.<a href="#section-4.3-2.144" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.145">gea-nz-motivators:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.146">Information relating to authority or governance.<a href="#section-4.3-2.146" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.147">gsma-attack-category:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.148">Taxonomy used by GSMA for their information sharing program with telco describing the attack categories<a href="#section-4.3-2.148" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.149">gsma-fraud:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.150">Taxonomy used by GSMA for their information sharing program with telco describing the various aspects of fraud<a href="#section-4.3-2.150" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.151">gsma-network-technology:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.152">Taxonomy used by GSMA for their information sharing program with telco describing the types of infrastructure. WiP<a href="#section-4.3-2.152" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.153">honeypot-basic:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.154">Updated (CIRCL, Seamus Dowling and EURECOM) from Christian Seifert, Ian Welch, Peter Komisarczuk, 'Taxonomy of Honeypots', Technical Report CS-TR-06/12, VICTORIA UNIVERSITY OF WELLINGTON, School of Mathematical and Computing Sciences, June 2006, <a href="http://www.mcs.vuw.ac.nz/comp/Publications/archive/CS-TR-06/CS-TR-06-12.pdf">http://www.mcs.vuw.ac.nz/comp/Publications/archive/CS-TR-06/CS-TR-06-12.pdf</a><a href="#section-4.3-2.154" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.155">ics:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.156">FIRST.ORG CTI SIG - MISP Proposal for ICS/OT Threat Attribution (IOC) Project<a href="#section-4.3-2.156" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.157">iep:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.158">Forum of Incident Response and Security Teams (FIRST) Information Exchange Policy (IEP) framework<a href="#section-4.3-2.158" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.159">iep2-policy:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.160">Forum of Incident Response and Security Teams (FIRST) Information Exchange Policy (IEP) v2.0 Policy<a href="#section-4.3-2.160" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.161">iep2-reference:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.162">Forum of Incident Response and Security Teams (FIRST) Information Exchange Policy (IEP) v2.0 Reference<a href="#section-4.3-2.162" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.163">ifx-vetting:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.164">The IFX taxonomy is used to categorise information (MISP events and attributes) to aid in the intelligence vetting process<a href="#section-4.3-2.164" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.165">incident-disposition:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.166">How an incident is classified in its process to be resolved. The taxonomy is inspired from NASA Incident Response and Management Handbook. <a href="https://www.nasa.gov/pdf/589502main_ITS-HBK-2810.09-02%20%5bNASA%20Information%20Security%20Incident%20Management%5d.pdf#page=9">https://www.nasa.gov/pdf/589502main_ITS-HBK-2810.09-02%20%5bNASA%20Information%20Security%20Incident%20Management%5d.pdf#page=9</a><a href="#section-4.3-2.166" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.167">infoleak:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.168">A taxonomy describing information leaks and especially information classified as being potentially leaked. The taxonomy is based on the work by CIRCL on the AIL framework. The taxonomy aim is to be used at large to improve classification of leaked information.<a href="#section-4.3-2.168" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.169">information-origin:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.170">Taxonomy for tagging information by its origin: human-generated or AI-generated.<a href="#section-4.3-2.170" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.171">information-security-data-source:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.172">Taxonomy to classify the information security data sources.<a href="#section-4.3-2.172" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.173">information-security-indicators:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.174">A full set of operational indicators for organizations to use to benchmark their security posture.<a href="#section-4.3-2.174" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.175">interactive-cyber-training-audience:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.176">Describes the target of cyber training and education.<a href="#section-4.3-2.176" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.177">interactive-cyber-training-technical-setup:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.178">The technical setup consists of environment structure, deployment, and orchestration.<a href="#section-4.3-2.178" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.179">interactive-cyber-training-training-environment:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.180">The training environment details the environment around the training, consisting of training type and scenario.<a href="#section-4.3-2.180" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.181">interactive-cyber-training-training-setup:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.182">The training setup further describes the training itself with the scoring, roles, the training mode as well as the customization level.<a href="#section-4.3-2.182" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.183">interception-method:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.184">The interception method used to intercept traffic.<a href="#section-4.3-2.184" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.185">ioc:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.186">An IOC classification to facilitate automation of malicious and non malicious artifacts<a href="#section-4.3-2.186" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.187">iot:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.188">Internet of Things taxonomy, based on IOT UK report <a href="https://iotuk.org.uk/wp-content/uploads/2017/01/IOT-Taxonomy-Report.pdf">https://iotuk.org.uk/wp-content/uploads/2017/01/IOT-Taxonomy-Report.pdf</a><a href="#section-4.3-2.188" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.189">kill-chain:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.190">The Cyber Kill Chain, a phase-based model developed by Lockheed Martin, aims to help categorise and identify the stage of an attack.<a href="#section-4.3-2.190" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.191">maec-delivery-vectors:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.192">Vectors used to deliver malware based on MAEC 5.0<a href="#section-4.3-2.192" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.193">maec-malware-behavior:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.194">Malware behaviours based on MAEC 5.0<a href="#section-4.3-2.194" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.195">maec-malware-capabilities:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.196">Malware Capabilities based on MAEC 5.0<a href="#section-4.3-2.196" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.197">maec-malware-obfuscation-methods:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.198">Obfuscation methods used by malware based on MAEC 5.0<a href="#section-4.3-2.198" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.199">malware_classification:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.200">Classification based on different categories. Based on <a href="https://www.sans.org/reading-room/whitepapers/incident/malware-101-viruses-32848">https://www.sans.org/reading-room/whitepapers/incident/malware-101-viruses-32848</a><a href="#section-4.3-2.200" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.201">misinformation-website-label:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.202">classification for the identification of type of misinformation among websites. Source:False, Misleading, Clickbait-y, and/or Satirical News Sources by Melissa Zimdars 2019<a href="#section-4.3-2.202" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.203">misp:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.204">MISP taxonomy to infer with MISP behavior or operation.<a href="#section-4.3-2.204" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.205">misp-workflow:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.206">MISP workflow taxonomy to support result of workflow execution.<a href="#section-4.3-2.206" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.207">monarc-threat:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.208">MONARC Threats Taxonomy<a href="#section-4.3-2.208" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.209">ms-caro-malware:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.210">Malware Type and Platform classification based on Microsoft's implementation of the Computer Antivirus Research Organization (CARO) Naming Scheme and Malware Terminology. Based on <a href="https://www.microsoft.com/en-us/security/portal/mmpc/shared/malwarenaming.aspx">https://www.microsoft.com/en-us/security/portal/mmpc/shared/malwarenaming.aspx</a>, <a href="https://www.microsoft.com/security/portal/mmpc/shared/glossary.aspx">https://www.microsoft.com/security/portal/mmpc/shared/glossary.aspx</a>, <a href="https://www.microsoft.com/security/portal/mmpc/shared/objectivecriteria.aspx">https://www.microsoft.com/security/portal/mmpc/shared/objectivecriteria.aspx</a>, and <a href="http://www.caro.org/definitions/index.html">http://www.caro.org/definitions/index.html</a>. Malware families are extracted from Microsoft SIRs since 2008 based on <a href="https://www.microsoft.com/security/sir/archive/default.aspx">https://www.microsoft.com/security/sir/archive/default.aspx</a> and <a href="https://www.microsoft.com/en-us/security/portal/threat/threats.aspx">https://www.microsoft.com/en-us/security/portal/threat/threats.aspx</a>. Note that SIRs do NOT include all Microsoft malware families.<a href="#section-4.3-2.210" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.211">ms-caro-malware-full:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.212">Malware Type and Platform classification based on Microsoft's implementation of the Computer Antivirus Research Organization (CARO) Naming Scheme and Malware Terminology. Based on <a href="https://www.microsoft.com/en-us/security/portal/mmpc/shared/malwarenaming.aspx">https://www.microsoft.com/en-us/security/portal/mmpc/shared/malwarenaming.aspx</a>, <a href="https://www.microsoft.com/security/portal/mmpc/shared/glossary.aspx">https://www.microsoft.com/security/portal/mmpc/shared/glossary.aspx</a>, <a href="https://www.microsoft.com/security/portal/mmpc/shared/objectivecriteria.aspx">https://www.microsoft.com/security/portal/mmpc/shared/objectivecriteria.aspx</a>, and <a href="http://www.caro.org/definitions/index.html">http://www.caro.org/definitions/index.html</a>. Malware families are extracted from Microsoft SIRs since 2008 based on <a href="https://www.microsoft.com/security/sir/archive/default.aspx">https://www.microsoft.com/security/sir/archive/default.aspx</a> and <a href="https://www.microsoft.com/en-us/security/portal/threat/threats.aspx">https://www.microsoft.com/en-us/security/portal/threat/threats.aspx</a>. Note that SIRs do NOT include all Microsoft malware families.<a href="#section-4.3-2.212" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.213">mwdb:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.214">Malware Database (mwdb) Taxonomy - Tags used across the platform<a href="#section-4.3-2.214" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.215">nato:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.216">NATO classification markings.<a href="#section-4.3-2.216" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.217">nis:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.218">The taxonomy is meant for large scale cybersecurity incidents, as mentioned in the Commission Recommendation of 13 September 2017, also known as the blueprint. It has two core parts: The nature of the incident, i.e. the underlying cause, that triggered the incident, and the impact of the incident, i.e. the impact on services, in which sector(s) of economy and society.<a href="#section-4.3-2.218" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.219">nis2:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.220">The taxonomy is meant for large scale cybersecurity incidents, as mentioned in the Commission Recommendation of 13 May 2022, also known as the provisional agreement. It has two core parts: The nature of the incident, i.e. the underlying cause, that triggered the incident, and the impact of the incident, i.e. the impact on services, in which sector(s) of economy and society.<a href="#section-4.3-2.220" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.221">open_threat:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.222">Open Threat Taxonomy v1.1 base on James Tarala of SANS <a href="http://www.auditscripts.com/resources/open_threat_taxonomy_v1.1a.pdf">http://www.auditscripts.com/resources/open_threat_taxonomy_v1.1a.pdf</a>, <a href="https://files.sans.org/summit/Threat_Hunting_Incident_Response_Summit_2016/PDFs/Using-Open-Tools-to-Convert-Threat-Intelligence-into-Practical-Defenses-James-Tarala-SANS-Institute.pdf">https://files.sans.org/summit/Threat_Hunting_Incident_Response_Summit_2016/PDFs/Using-Open-Tools-to-Convert-Threat-Intelligence-into-Practical-Defenses-James-Tarala-SANS-Institute.pdf</a>, <a href="https://www.youtube.com/watch?v=5rdGOOFC_yE">https://www.youtube.com/watch?v=5rdGOOFC_yE</a>, and <a href="https://www.rsaconference.com/writable/presentations/file_upload/str-r04_using-an-open-source-threat-model-for-prioritized-defense-final.pdf">https://www.rsaconference.com/writable/presentations/file_upload/str-r04_using-an-open-source-threat-model-for-prioritized-defense-final.pdf</a><a href="#section-4.3-2.222" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.223">osint:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.224">Open Source Intelligence - Classification (MISP taxonomies)<a href="#section-4.3-2.224" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.225">pandemic:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.226">Pandemic<a href="#section-4.3-2.226" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.227">passivetotal:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.228">Tags from RiskIQ's PassiveTotal service<a href="#section-4.3-2.228" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.229">pentest:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.230">Penetration test (pentest) classification.<a href="#section-4.3-2.230" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.231">phishing:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.232">Taxonomy to classify phishing attacks including techniques, collection mechanisms and analysis status.<a href="#section-4.3-2.232" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.233">poison-taxonomy:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.234">Non-exhaustive taxonomy of natural poison<a href="#section-4.3-2.234" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.235">political-spectrum:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.236">A political spectrum is a system to characterize and classify different political positions in relation to one another.<a href="#section-4.3-2.236" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.237">priority-level:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.238">After an incident is scored, it is assigned a priority level. The six levels listed below are aligned with NCCIC, DHS, and the CISS to help provide a common lexicon when discussing incidents. This priority assignment drives NCCIC urgency, pre-approved incident response offerings, reporting requirements, and recommendations for leadership escalation. Generally, incident priority distribution should follow a similar pattern to the graph below. Based on <a href="https://www.us-cert.gov/NCCIC-Cyber-Incident-Scoring-System">https://www.us-cert.gov/NCCIC-Cyber-Incident-Scoring-System</a>.<a href="#section-4.3-2.238" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.239">pyoti:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.240">PyOTI automated enrichment schemes for point in time classification of indicators.<a href="#section-4.3-2.240" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.241">ransomware:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.242">Ransomware is used to define ransomware types and the elements that compose them.<a href="#section-4.3-2.242" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.243">ransomware-roles:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.244">The seven roles seen in most ransomware incidents.<a href="#section-4.3-2.244" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.245">retention:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.246">Add a retenion time to events to automatically remove the IDS-flag on ip-dst or ip-src attributes. We calculate the time elapsed based on the date of the event. Supported time units are: d(ays), w(eeks), m(onths), y(ears). The numerical_value is just for sorting in the web-interface and is not used for calculations.<a href="#section-4.3-2.246" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.247">rsit:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.248">Reference Security Incident Classification Taxonomy<a href="#section-4.3-2.248" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.249">rt_event_status:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.250">Status of events used in Request Tracker.<a href="#section-4.3-2.250" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.251">runtime-packer:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.252">Runtime or software packer used to combine compressed or encrypted data with the decompression or decryption code. This code can add additional obfuscations mechanisms including polymorphic-packer or other obfuscation techniques. This taxonomy lists all the known or official packer used for legitimate use or for packing malicious binaries.<a href="#section-4.3-2.252" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.253">scrippsco2-fgc:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.254">Flags describing the sample<a href="#section-4.3-2.254" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.255">scrippsco2-fgi:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.256">Flags describing the sample for isotopic data (C14, O18)<a href="#section-4.3-2.256" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.257">scrippsco2-sampling-stations:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.258">Sampling stations of the Scripps CO2 Program<a href="#section-4.3-2.258" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.259">sentinel-threattype:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.260">Sentinel indicator threat types.<a href="#section-4.3-2.260" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.261">smart-airports-threats:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.262">Threat taxonomy in the scope of securing smart airports by ENISA. <a href="https://www.enisa.europa.eu/publications/securing-smart-airports">https://www.enisa.europa.eu/publications/securing-smart-airports</a><a href="#section-4.3-2.262" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.263">social-engineering-attack-vectors:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.264">Attack vectors used in social engineering as described in 'A Taxonomy of Social Engineering Defense Mechanisms' by Dalal Alharthi and others.<a href="#section-4.3-2.264" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.265">srbcert:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.266">SRB-CERT Taxonomy - Schemes of Classification in Incident Response and Detection<a href="#section-4.3-2.266" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.267">state-responsibility:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.268">A spectrum of state responsibility to more directly tie the goals of attribution to the needs of policymakers.<a href="#section-4.3-2.268" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.269">stealth_malware:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.270">Classification based on malware stealth techniques. Described in <a href="https://vxheaven.org/lib/pdf/Introducing%20Stealth%20Malware%20Taxonomy.pdf">https://vxheaven.org/lib/pdf/Introducing%20Stealth%20Malware%20Taxonomy.pdf</a><a href="#section-4.3-2.270" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.271">stix-ttp:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.272">TTPs are representations of the behavior or modus operandi of cyber adversaries.<a href="#section-4.3-2.272" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.273">targeted-threat-index:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.274">The Targeted Threat Index is a metric for assigning an overall threat ranking score to email messages that deliver malware to a victim's computer. The TTI metric was first introduced at SecTor 2013 by Seth Hardy as part of the talk "RATastrophe: Monitoring a Malware Menagerie" along with Katie Kleemola and Greg Wiseman.<a href="#section-4.3-2.274" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.275">thales_group:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.276">Thales Group Taxonomy - was designed with the aim of enabling desired sharing and preventing unwanted sharing between Thales Group security communities.<a href="#section-4.3-2.276" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.277">threatmatch:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.278">The ThreatMatch Sectors, Incident types, Malware types and Alert types are applicable for any ThreatMatch instances and should be used for all CIISI and TIBER Projects.<a href="#section-4.3-2.278" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.279">threats-to-dns:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.280">An overview of some of the known attacks related to DNS as described by Torabi, S., Boukhtouta, A., Assi, C., & Debbabi, M. (2018) in Detecting Internet Abuse by Analyzing Passive DNS Traffic: A Survey of Implemented Systems. IEEE Communications Surveys & Tutorials, 1-1. doi:10.1109/comst.2018.2849614<a href="#section-4.3-2.280" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.281">tlp:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.282">The Traffic Light Protocol (TLP) (v2.0) was created to facilitate greater sharing of potentially sensitive information and more effective collaboration. Information sharing happens from an information source, towards one or more recipients. TLP is a set of four standard labels (a fifth label is included in amber to limit the diffusion) used to indicate the sharing boundaries to be applied by the recipients. Only labels listed in this standard are considered valid by FIRST. This taxonomy includes additional labels for backward compatibility which are no more validated by FIRST SIG.<a href="#section-4.3-2.282" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.283">tor:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.284">Taxonomy to describe Tor network infrastructure<a href="#section-4.3-2.284" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.285">trust:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.286">The Indicator of Trust provides insight about data on what can be trusted and known as a good actor. Similar to a whitelist but on steroids, reusing features one would use with Indicators of Compromise, but to filter out what is known to be good.<a href="#section-4.3-2.286" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.287">type:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.288">Taxonomy to describe different types of intelligence gathering discipline which can be described the origin of intelligence.<a href="#section-4.3-2.288" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.289">unified-kill-chain:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.290">The Unified Kill Chain is a refinement to the Kill Chain.<a href="#section-4.3-2.290" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.291">use-case-applicability:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.292">The Use Case Applicability categories reflect standard resolution categories, to clearly display alerting rule configuration problems.<a href="#section-4.3-2.292" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.293">veris:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.294">Vocabulary for Event Recording and Incident Sharing (VERIS)<a href="#section-4.3-2.294" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.295">vmray:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.296">VMRay taxonomies to map VMRay Thread Identifier scores and artifacts.<a href="#section-4.3-2.296" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.297">vocabulaire-des-probabilites-estimatives:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.298">Ce vocabulaire attribue des valeurs en pourcentage &#224; certains &#233;nonc&#233;s de probabilit&#233;<a href="#section-4.3-2.298" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
<dt id="section-4.3-2.299">workflow:</dt>
|
||
<dd style="margin-left: 1.5em" id="section-4.3-2.300">Workflow support language is a common language to support intelligence analysts to perform their analysis on data and information.<a href="#section-4.3-2.300" class="pilcrow">¶</a>
|
||
</dd>
|
||
<dd class="break"></dd>
|
||
</dl>
|
||
</section>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
<div id="json-schema">
|
||
<section id="section-5">
|
||
<h2 id="name-json-schema">
|
||
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-json-schema" class="section-name selfRef">JSON Schema</a>
|
||
</h2>
|
||
<p id="section-5-1">The JSON Schema <span>[<a href="#JSON-SCHEMA" class="xref">JSON-SCHEMA</a>]</span> below defines the structure of the MISP taxonomy document
|
||
as literally described before. The JSON Schema is used validating a MISP taxonomy. The validation
|
||
is a <em>MUST</em> if the taxonomy is included in the MISP taxonomies directory.<a href="#section-5-1" class="pilcrow">¶</a></p>
|
||
<div class="alignLeft art-text artwork" id="section-5-2">
|
||
<pre>{
|
||
"$schema": "http://json-schema.org/schema#",
|
||
"title": "Validator for misp-taxonomies",
|
||
"id": "https://www.github.com/MISP/misp-taxonomies/schema.json",
|
||
"defs": {
|
||
"entry": {
|
||
"type": "array",
|
||
"uniqueItems": true,
|
||
"items": {
|
||
"type": "object",
|
||
"additionalProperties": false,
|
||
"properties": {
|
||
"numerical_value": {
|
||
"type": "number"
|
||
},
|
||
"expanded": {
|
||
"type": "string"
|
||
},
|
||
"description": {
|
||
"type": "string"
|
||
},
|
||
"colour": {
|
||
"type": "string"
|
||
},
|
||
"value": {
|
||
"type": "string"
|
||
},
|
||
"required": [
|
||
"value"
|
||
]
|
||
}
|
||
}
|
||
},
|
||
"values": {
|
||
"type": "array",
|
||
"uniqueItems": true,
|
||
"items": {
|
||
"type": "object",
|
||
"additionalProperties": false,
|
||
"properties": {
|
||
"entry": {
|
||
"$ref": "#/defs/entry"
|
||
},
|
||
"predicate": {
|
||
"type": "string"
|
||
}
|
||
},
|
||
"required": [
|
||
"predicate"
|
||
]
|
||
}
|
||
},
|
||
"predicates": {
|
||
"type": "array",
|
||
"uniqueItems": true,
|
||
"items": {
|
||
"type": "object",
|
||
"additionalProperties": false,
|
||
"properties": {
|
||
"numerical_value": {
|
||
"type": "number"
|
||
},
|
||
"colour": {
|
||
"type": "string"
|
||
},
|
||
"description": {
|
||
"type": "string"
|
||
},
|
||
"expanded": {
|
||
"type": "string"
|
||
},
|
||
"value": {
|
||
"type": "string"
|
||
},
|
||
"exclusive": {
|
||
"type": "boolean"
|
||
},
|
||
"required": [
|
||
"value"
|
||
]
|
||
}
|
||
}
|
||
}
|
||
},
|
||
"type": "object",
|
||
"additionalProperties": false,
|
||
"properties": {
|
||
"version": {
|
||
"type": "integer"
|
||
},
|
||
"description": {
|
||
"type": "string"
|
||
},
|
||
"expanded": {
|
||
"type": "string"
|
||
},
|
||
"namespace": {
|
||
"type": "string"
|
||
},
|
||
"exclusive": {
|
||
"type": "boolean"
|
||
},
|
||
"type": {
|
||
"type": "array",
|
||
"uniqueItems": true,
|
||
"items": {
|
||
"type": "string",
|
||
"enum": [
|
||
"org",
|
||
"user",
|
||
"attribute",
|
||
"event"
|
||
]
|
||
}
|
||
},
|
||
"refs": {
|
||
"type": "array",
|
||
"uniqueItems": true,
|
||
"items": {
|
||
"type": "string"
|
||
}
|
||
},
|
||
"predicates": {
|
||
"$ref": "#/defs/predicates"
|
||
},
|
||
"values": {
|
||
"$ref": "#/defs/values"
|
||
}
|
||
},
|
||
"required": [
|
||
"namespace",
|
||
"description",
|
||
"version",
|
||
"predicates"
|
||
]
|
||
}
|
||
</pre><a href="#section-5-2" class="pilcrow">¶</a>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
<div id="acknowledgements">
|
||
<section id="section-6">
|
||
<h2 id="name-acknowledgements">
|
||
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
|
||
</h2>
|
||
<p id="section-6-1">The authors wish to thank all the MISP community who are supporting the creation
|
||
of open standards in threat intelligence sharing.<a href="#section-6-1" class="pilcrow">¶</a></p>
|
||
</section>
|
||
</div>
|
||
<section id="section-7">
|
||
<h2 id="name-normative-references">
|
||
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
|
||
</h2>
|
||
<dl class="references">
|
||
<dt id="RFC2119">[RFC2119]</dt>
|
||
<dd>
|
||
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>></span>. </dd>
|
||
<dd class="break"></dd>
|
||
<dt id="RFC8259">[RFC8259]</dt>
|
||
<dd>
|
||
<span class="refAuthor">Bray, T., Ed.</span>, <span class="refTitle">"The JavaScript Object Notation (JSON) Data Interchange Format"</span>, <span class="seriesInfo">STD 90</span>, <span class="seriesInfo">RFC 8259</span>, <span class="seriesInfo">DOI 10.17487/RFC8259</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8259">https://www.rfc-editor.org/info/rfc8259</a>></span>. </dd>
|
||
<dd class="break"></dd>
|
||
</dl>
|
||
</section>
|
||
<section id="section-8">
|
||
<h2 id="name-informative-references">
|
||
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
|
||
</h2>
|
||
<dl class="references">
|
||
<dt id="JSON-SCHEMA">[JSON-SCHEMA]</dt>
|
||
<dd>
|
||
<span class="refAuthor">Wright, A.</span>, <span class="refTitle">"JSON Schema: A Media Type for Describing JSON Documents"</span>, <time datetime="2016" class="refDate">2016</time>, <span><<a href="https://tools.ietf.org/html/draft-wright-json-schema">https://tools.ietf.org/html/draft-wright-json-schema</a>></span>. </dd>
|
||
<dd class="break"></dd>
|
||
<dt id="MISP-P">[MISP-P]</dt>
|
||
<dd>
|
||
<span class="refAuthor">Community, M.</span>, <span class="refTitle">"MISP Project - Malware Information Sharing Platform and Threat Sharing"</span>, <span><<a href="https://github.com/MISP">https://github.com/MISP</a>></span>. </dd>
|
||
<dd class="break"></dd>
|
||
<dt id="MISP-T">[MISP-T]</dt>
|
||
<dd>
|
||
<span class="refAuthor">Community, M.</span>, <span class="refTitle">"MISP Taxonomies - shared and common vocabularies of tags"</span>, <span><<a href="https://github.com/MISP/misp-taxonomies">https://github.com/MISP/misp-taxonomies</a>></span>. </dd>
|
||
<dd class="break"></dd>
|
||
<dt id="machine-tags">[machine-tags]</dt>
|
||
<dd>
|
||
<span class="refAuthor">Cope, A. S.</span>, <span class="refTitle">"Machine tags"</span>, <time datetime="2007" class="refDate">2007</time>, <span><<a href="https://www.flickr.com/groups/51035612836@N01/discuss/72157594497877875/">https://www.flickr.com/groups/51035612836@N01/discuss/72157594497877875/</a>></span>. </dd>
|
||
<dd class="break"></dd>
|
||
</dl>
|
||
</section>
|
||
<div id="authors-addresses">
|
||
<section id="appendix-A">
|
||
<h2 id="name-authors-addresses">
|
||
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
|
||
</h2>
|
||
<address class="vcard">
|
||
<div dir="auto" class="left"><span class="fn nameRole">Alexandre Dulaunoy</span></div>
|
||
<div dir="auto" class="left"><span class="org">Computer Incident Response Center Luxembourg</span></div>
|
||
<div dir="auto" class="left"><span class="street-address">122, rue Adolphe Fischer</span></div>
|
||
<div dir="auto" class="left">L-<span class="postal-code">L-1521</span> <span class="locality">Luxembourg</span>
|
||
</div>
|
||
<div dir="auto" class="left"><span class="country-name">Luxembourg</span></div>
|
||
<div class="tel">
|
||
<span>Phone:</span>
|
||
<a href="tel:+352%20247%2088444" class="tel">+352 247 88444</a>
|
||
</div>
|
||
<div class="email">
|
||
<span>Email:</span>
|
||
<a href="mailto:alexandre.dulaunoy@circl.lu" class="email">alexandre.dulaunoy@circl.lu</a>
|
||
</div>
|
||
</address>
|
||
<address class="vcard">
|
||
<div dir="auto" class="left"><span class="fn nameRole">Andras Iklody</span></div>
|
||
<div dir="auto" class="left"><span class="org">Computer Incident Response Center Luxembourg</span></div>
|
||
<div dir="auto" class="left"><span class="street-address">122, rue Adolphe Fischer</span></div>
|
||
<div dir="auto" class="left">L-<span class="postal-code">L-1521</span> <span class="locality">Luxembourg</span>
|
||
</div>
|
||
<div dir="auto" class="left"><span class="country-name">Luxembourg</span></div>
|
||
<div class="tel">
|
||
<span>Phone:</span>
|
||
<a href="tel:+352%20247%2088444" class="tel">+352 247 88444</a>
|
||
</div>
|
||
<div class="email">
|
||
<span>Email:</span>
|
||
<a href="mailto:andras.iklody@circl.lu" class="email">andras.iklody@circl.lu</a>
|
||
</div>
|
||
</address>
|
||
</section>
|
||
</div>
|
||
<script>const toc = document.getElementById("toc");
|
||
toc.querySelector("h2").addEventListener("click", e => {
|
||
toc.classList.toggle("active");
|
||
});
|
||
toc.querySelector("nav").addEventListener("click", e => {
|
||
toc.classList.remove("active");
|
||
});
|
||
</script>
|
||
</body>
|
||
</html>
|