| 1 |
<!DOCTYPE html> |
| 2 |
<html lang="en" class="RFC"> |
| 3 |
<head> |
| 4 |
<meta charset="utf-8"> |
| 5 |
<meta content="Common,Latin" name="scripts"> |
| 6 |
<meta content="initial-scale=1.0" name="viewport"> |
| 7 |
<title>RFC 9116: A File Format to Aid in Security Vulnerability Disclosure</title> |
| 8 |
<meta content="Edwin Foudil" name="author"> |
| 9 |
<meta content="Yakov Shafranovich" name="author"> |
| 10 |
<meta content=' |
| 11 |
When security vulnerabilities are discovered by |
| 12 |
researchers, proper reporting channels are often lacking. As a result, |
| 13 |
vulnerabilities may be left unreported. This document defines a machine-parsable format |
| 14 |
("security.txt") to help organizations describe their vulnerability disclosure practices |
| 15 |
to make it easier for researchers to report vulnerabilities. |
| 16 |
' name="description"> |
| 17 |
<meta content="xml2rfc 3.12.2" name="generator"> |
| 18 |
<meta content="9116" name="rfc.number"> |
| 19 |
<!-- Generator version information: |
| 20 |
xml2rfc 3.12.2 |
| 21 |
Python 3.6.15 |
| 22 |
appdirs 1.4.4 |
| 23 |
ConfigArgParse 1.4.1 |
| 24 |
google-i18n-address 2.4.0 |
| 25 |
html5lib 1.0.1 |
| 26 |
intervaltree 3.0.2 |
| 27 |
Jinja2 2.11.3 |
| 28 |
kitchen 1.2.6 |
| 29 |
lxml 4.4.2 |
| 30 |
pycairo 1.15.1 |
| 31 |
pycountry 19.8.18 |
| 32 |
pyflakes 2.1.1 |
| 33 |
PyYAML 5.4.1 |
| 34 |
requests 2.24.0 |
| 35 |
setuptools 40.5.0 |
| 36 |
six 1.14.0 |
| 37 |
WeasyPrint 52.5 |
| 38 |
--> |
| 39 |
<link href="rfc9116.xml" rel="alternate" type="application/rfc+xml"> |
| 40 |
<link href="#copyright" rel="license"> |
| 41 |
<style type="text/css">/* |
| 42 |
|
| 43 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 44 |
|
| 45 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 46 |
this can be consolidated so that style settings occur only in one place, but |
| 47 |
for now the contents of this file consists first of the initial CSS work as |
| 48 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 49 |
commented changes found necssary during the development of the v3 |
| 50 |
formatters. |
| 51 |
|
| 52 |
*/ |
| 53 |
|
| 54 |
/* fonts */ |
| 55 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 56 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 57 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 58 |
|
| 59 |
@viewport { |
| 60 |
zoom: 1.0; |
| 61 |
width: extend-to-zoom; |
| 62 |
} |
| 63 |
@-ms-viewport { |
| 64 |
width: extend-to-zoom; |
| 65 |
zoom: 1.0; |
| 66 |
} |
| 67 |
/* general and mobile first */ |
| 68 |
html { |
| 69 |
} |
| 70 |
body { |
| 71 |
max-width: 90%; |
| 72 |
margin: 1.5em auto; |
| 73 |
color: #222; |
| 74 |
background-color: #fff; |
| 75 |
font-size: 14px; |
| 76 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 77 |
line-height: 1.6; |
| 78 |
scroll-behavior: smooth; |
| 79 |
} |
| 80 |
.ears { |
| 81 |
display: none; |
| 82 |
} |
| 83 |
|
| 84 |
/* headings */ |
| 85 |
#title, h1, h2, h3, h4, h5, h6 { |
| 86 |
margin: 1em 0 0.5em; |
| 87 |
font-weight: bold; |
| 88 |
line-height: 1.3; |
| 89 |
} |
| 90 |
#title { |
| 91 |
clear: both; |
| 92 |
border-bottom: 1px solid #ddd; |
| 93 |
margin: 0 0 0.5em 0; |
| 94 |
padding: 1em 0 0.5em; |
| 95 |
} |
| 96 |
.author { |
| 97 |
padding-bottom: 4px; |
| 98 |
} |
| 99 |
h1 { |
| 100 |
font-size: 26px; |
| 101 |
margin: 1em 0; |
| 102 |
} |
| 103 |
h2 { |
| 104 |
font-size: 22px; |
| 105 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 106 |
padding-top: 33px; |
| 107 |
} |
| 108 |
h3 { |
| 109 |
font-size: 18px; |
| 110 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 111 |
padding-top: 42px; |
| 112 |
} |
| 113 |
h4 { |
| 114 |
font-size: 16px; |
| 115 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 116 |
padding-top: 42px; |
| 117 |
} |
| 118 |
h5, h6 { |
| 119 |
font-size: 14px; |
| 120 |
} |
| 121 |
#n-copyright-notice { |
| 122 |
border-bottom: 1px solid #ddd; |
| 123 |
padding-bottom: 1em; |
| 124 |
margin-bottom: 1em; |
| 125 |
} |
| 126 |
/* general structure */ |
| 127 |
p { |
| 128 |
padding: 0; |
| 129 |
margin: 0 0 1em 0; |
| 130 |
text-align: left; |
| 131 |
} |
| 132 |
div, span { |
| 133 |
position: relative; |
| 134 |
} |
| 135 |
div { |
| 136 |
margin: 0; |
| 137 |
} |
| 138 |
.alignRight.art-text { |
| 139 |
background-color: #f9f9f9; |
| 140 |
border: 1px solid #eee; |
| 141 |
border-radius: 3px; |
| 142 |
padding: 1em 1em 0; |
| 143 |
margin-bottom: 1.5em; |
| 144 |
} |
| 145 |
.alignRight.art-text pre { |
| 146 |
padding: 0; |
| 147 |
} |
| 148 |
.alignRight { |
| 149 |
margin: 1em 0; |
| 150 |
} |
| 151 |
.alignRight > *:first-child { |
| 152 |
border: none; |
| 153 |
margin: 0; |
| 154 |
float: right; |
| 155 |
clear: both; |
| 156 |
} |
| 157 |
.alignRight > *:nth-child(2) { |
| 158 |
clear: both; |
| 159 |
display: block; |
| 160 |
border: none; |
| 161 |
} |
| 162 |
svg { |
| 163 |
display: block; |
| 164 |
} |
| 165 |
.alignCenter.art-text { |
| 166 |
background-color: #f9f9f9; |
| 167 |
border: 1px solid #eee; |
| 168 |
border-radius: 3px; |
| 169 |
padding: 1em 1em 0; |
| 170 |
margin-bottom: 1.5em; |
| 171 |
} |
| 172 |
.alignCenter.art-text pre { |
| 173 |
padding: 0; |
| 174 |
} |
| 175 |
.alignCenter { |
| 176 |
margin: 1em 0; |
| 177 |
} |
| 178 |
.alignCenter > *:first-child { |
| 179 |
border: none; |
| 180 |
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't |
| 181 |
support flexbox yet. |
| 182 |
*/ |
| 183 |
display: table; |
| 184 |
margin: 0 auto; |
| 185 |
} |
| 186 |
|
| 187 |
/* lists */ |
| 188 |
ol, ul { |
| 189 |
padding: 0; |
| 190 |
margin: 0 0 1em 2em; |
| 191 |
} |
| 192 |
ol ol, ul ul, ol ul, ul ol { |
| 193 |
margin-left: 1em; |
| 194 |
} |
| 195 |
li { |
| 196 |
margin: 0 0 0.25em 0; |
| 197 |
} |
| 198 |
.ulCompact li { |
| 199 |
margin: 0; |
| 200 |
} |
| 201 |
ul.empty, .ulEmpty { |
| 202 |
list-style-type: none; |
| 203 |
} |
| 204 |
ul.empty li, .ulEmpty li { |
| 205 |
margin-top: 0.5em; |
| 206 |
} |
| 207 |
ul.ulBare, li.ulBare { |
| 208 |
margin-left: 0em !important; |
| 209 |
} |
| 210 |
ul.compact, .ulCompact, |
| 211 |
ol.compact, .olCompact { |
| 212 |
line-height: 100%; |
| 213 |
margin: 0 0 0 2em; |
| 214 |
} |
| 215 |
|
| 216 |
/* definition lists */ |
| 217 |
dl { |
| 218 |
} |
| 219 |
dl > dt { |
| 220 |
float: left; |
| 221 |
margin-right: 1em; |
| 222 |
} |
| 223 |
/* |
| 224 |
dl.nohang > dt { |
| 225 |
float: none; |
| 226 |
} |
| 227 |
*/ |
| 228 |
dl > dd { |
| 229 |
margin-bottom: .8em; |
| 230 |
min-height: 1.3em; |
| 231 |
} |
| 232 |
dl.compact > dd, .dlCompact > dd { |
| 233 |
margin-bottom: 0em; |
| 234 |
} |
| 235 |
dl > dd > dl { |
| 236 |
margin-top: 0.5em; |
| 237 |
margin-bottom: 0em; |
| 238 |
} |
| 239 |
|
| 240 |
/* links */ |
| 241 |
a { |
| 242 |
text-decoration: none; |
| 243 |
} |
| 244 |
a[href] { |
| 245 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 246 |
} |
| 247 |
a[href]:hover { |
| 248 |
background-color: #f2f2f2; |
| 249 |
} |
| 250 |
figcaption a[href], |
| 251 |
a[href].selfRef { |
| 252 |
color: #222; |
| 253 |
} |
| 254 |
/* XXX probably not this: |
| 255 |
a.selfRef:hover { |
| 256 |
background-color: transparent; |
| 257 |
cursor: default; |
| 258 |
} */ |
| 259 |
|
| 260 |
/* Figures */ |
| 261 |
tt, code, pre, code { |
| 262 |
background-color: #f9f9f9; |
| 263 |
font-family: 'Roboto Mono', monospace; |
| 264 |
} |
| 265 |
pre { |
| 266 |
border: 1px solid #eee; |
| 267 |
margin: 0; |
| 268 |
padding: 1em; |
| 269 |
} |
| 270 |
img { |
| 271 |
max-width: 100%; |
| 272 |
} |
| 273 |
figure { |
| 274 |
margin: 0; |
| 275 |
} |
| 276 |
figure blockquote { |
| 277 |
margin: 0.8em 0.4em 0.4em; |
| 278 |
} |
| 279 |
figcaption { |
| 280 |
font-style: italic; |
| 281 |
margin: 0 0 1em 0; |
| 282 |
} |
| 283 |
@media screen { |
| 284 |
pre { |
| 285 |
overflow-x: auto; |
| 286 |
max-width: 100%; |
| 287 |
max-width: calc(100% - 22px); |
| 288 |
} |
| 289 |
} |
| 290 |
|
| 291 |
/* aside, blockquote */ |
| 292 |
aside, blockquote { |
| 293 |
margin-left: 0; |
| 294 |
padding: 1.2em 2em; |
| 295 |
} |
| 296 |
blockquote { |
| 297 |
background-color: #f9f9f9; |
| 298 |
color: #111; /* Arlen: WCAG 2019 */ |
| 299 |
border: 1px solid #ddd; |
| 300 |
border-radius: 3px; |
| 301 |
margin: 1em 0; |
| 302 |
} |
| 303 |
cite { |
| 304 |
display: block; |
| 305 |
text-align: right; |
| 306 |
font-style: italic; |
| 307 |
} |
| 308 |
|
| 309 |
/* tables */ |
| 310 |
table { |
| 311 |
width: 100%; |
| 312 |
margin: 0 0 1em; |
| 313 |
border-collapse: collapse; |
| 314 |
border: 1px solid #eee; |
| 315 |
} |
| 316 |
th, td { |
| 317 |
text-align: left; |
| 318 |
vertical-align: top; |
| 319 |
padding: 0.5em 0.75em; |
| 320 |
} |
| 321 |
th { |
| 322 |
text-align: left; |
| 323 |
background-color: #e9e9e9; |
| 324 |
} |
| 325 |
tr:nth-child(2n+1) > td { |
| 326 |
background-color: #f5f5f5; |
| 327 |
} |
| 328 |
table caption { |
| 329 |
font-style: italic; |
| 330 |
margin: 0; |
| 331 |
padding: 0; |
| 332 |
text-align: left; |
| 333 |
} |
| 334 |
table p { |
| 335 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 336 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 337 |
margin: 0; |
| 338 |
} |
| 339 |
|
| 340 |
/* pilcrow */ |
| 341 |
a.pilcrow { |
| 342 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 343 |
text-decoration: none; |
| 344 |
visibility: hidden; |
| 345 |
user-select: none; |
| 346 |
-ms-user-select: none; |
| 347 |
-o-user-select:none; |
| 348 |
-moz-user-select: none; |
| 349 |
-khtml-user-select: none; |
| 350 |
-webkit-user-select: none; |
| 351 |
-webkit-touch-callout: none; |
| 352 |
} |
| 353 |
@media screen { |
| 354 |
aside:hover > a.pilcrow, |
| 355 |
p:hover > a.pilcrow, |
| 356 |
blockquote:hover > a.pilcrow, |
| 357 |
div:hover > a.pilcrow, |
| 358 |
li:hover > a.pilcrow, |
| 359 |
pre:hover > a.pilcrow { |
| 360 |
visibility: visible; |
| 361 |
} |
| 362 |
a.pilcrow:hover { |
| 363 |
background-color: transparent; |
| 364 |
} |
| 365 |
} |
| 366 |
|
| 367 |
/* misc */ |
| 368 |
hr { |
| 369 |
border: 0; |
| 370 |
border-top: 1px solid #eee; |
| 371 |
} |
| 372 |
.bcp14 { |
| 373 |
font-variant: small-caps; |
| 374 |
} |
| 375 |
|
| 376 |
.role { |
| 377 |
font-variant: all-small-caps; |
| 378 |
} |
| 379 |
|
| 380 |
/* info block */ |
| 381 |
#identifiers { |
| 382 |
margin: 0; |
| 383 |
font-size: 0.9em; |
| 384 |
} |
| 385 |
#identifiers dt { |
| 386 |
width: 3em; |
| 387 |
clear: left; |
| 388 |
} |
| 389 |
#identifiers dd { |
| 390 |
float: left; |
| 391 |
margin-bottom: 0; |
| 392 |
} |
| 393 |
/* Fix PDF info block run off issue */ |
| 394 |
@media print { |
| 395 |
#identifiers dd { |
| 396 |
float: none; |
| 397 |
} |
| 398 |
} |
| 399 |
#identifiers .authors .author { |
| 400 |
display: inline-block; |
| 401 |
margin-right: 1.5em; |
| 402 |
} |
| 403 |
#identifiers .authors .org { |
| 404 |
font-style: italic; |
| 405 |
} |
| 406 |
|
| 407 |
/* The prepared/rendered info at the very bottom of the page */ |
| 408 |
.docInfo { |
| 409 |
color: #666; /* Arlen: WCAG 2019 */ |
| 410 |
font-size: 0.9em; |
| 411 |
font-style: italic; |
| 412 |
margin-top: 2em; |
| 413 |
} |
| 414 |
.docInfo .prepared { |
| 415 |
float: left; |
| 416 |
} |
| 417 |
.docInfo .prepared { |
| 418 |
float: right; |
| 419 |
} |
| 420 |
|
| 421 |
/* table of contents */ |
| 422 |
#toc { |
| 423 |
padding: 0.75em 0 2em 0; |
| 424 |
margin-bottom: 1em; |
| 425 |
} |
| 426 |
nav.toc ul { |
| 427 |
margin: 0 0.5em 0 0; |
| 428 |
padding: 0; |
| 429 |
list-style: none; |
| 430 |
} |
| 431 |
nav.toc li { |
| 432 |
line-height: 1.3em; |
| 433 |
margin: 0.75em 0; |
| 434 |
padding-left: 1.2em; |
| 435 |
text-indent: -1.2em; |
| 436 |
} |
| 437 |
/* references */ |
| 438 |
.references dt { |
| 439 |
text-align: right; |
| 440 |
font-weight: bold; |
| 441 |
min-width: 7em; |
| 442 |
} |
| 443 |
.references dd { |
| 444 |
margin-left: 8em; |
| 445 |
overflow: auto; |
| 446 |
} |
| 447 |
|
| 448 |
.refInstance { |
| 449 |
margin-bottom: 1.25em; |
| 450 |
} |
| 451 |
|
| 452 |
.references .ascii { |
| 453 |
margin-bottom: 0.25em; |
| 454 |
} |
| 455 |
|
| 456 |
/* index */ |
| 457 |
.index ul { |
| 458 |
margin: 0 0 0 1em; |
| 459 |
padding: 0; |
| 460 |
list-style: none; |
| 461 |
} |
| 462 |
.index ul ul { |
| 463 |
margin: 0; |
| 464 |
} |
| 465 |
.index li { |
| 466 |
margin: 0; |
| 467 |
text-indent: -2em; |
| 468 |
padding-left: 2em; |
| 469 |
padding-bottom: 5px; |
| 470 |
} |
| 471 |
.indexIndex { |
| 472 |
margin: 0.5em 0 1em; |
| 473 |
} |
| 474 |
.index a { |
| 475 |
font-weight: 700; |
| 476 |
} |
| 477 |
/* make the index two-column on all but the smallest screens */ |
| 478 |
@media (min-width: 600px) { |
| 479 |
.index ul { |
| 480 |
-moz-column-count: 2; |
| 481 |
-moz-column-gap: 20px; |
| 482 |
} |
| 483 |
.index ul ul { |
| 484 |
-moz-column-count: 1; |
| 485 |
-moz-column-gap: 0; |
| 486 |
} |
| 487 |
} |
| 488 |
|
| 489 |
/* authors */ |
| 490 |
address.vcard { |
| 491 |
font-style: normal; |
| 492 |
margin: 1em 0; |
| 493 |
} |
| 494 |
|
| 495 |
address.vcard .nameRole { |
| 496 |
font-weight: 700; |
| 497 |
margin-left: 0; |
| 498 |
} |
| 499 |
address.vcard .label { |
| 500 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 501 |
margin: 0.5em 0; |
| 502 |
} |
| 503 |
address.vcard .type { |
| 504 |
display: none; |
| 505 |
} |
| 506 |
.alternative-contact { |
| 507 |
margin: 1.5em 0 1em; |
| 508 |
} |
| 509 |
hr.addr { |
| 510 |
border-top: 1px dashed; |
| 511 |
margin: 0; |
| 512 |
color: #ddd; |
| 513 |
max-width: calc(100% - 16px); |
| 514 |
} |
| 515 |
|
| 516 |
/* temporary notes */ |
| 517 |
.rfcEditorRemove::before { |
| 518 |
position: absolute; |
| 519 |
top: 0.2em; |
| 520 |
right: 0.2em; |
| 521 |
padding: 0.2em; |
| 522 |
content: "The RFC Editor will remove this note"; |
| 523 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 524 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 525 |
} |
| 526 |
.rfcEditorRemove { |
| 527 |
position: relative; |
| 528 |
padding-top: 1.8em; |
| 529 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 530 |
border-radius: 3px; |
| 531 |
} |
| 532 |
.cref { |
| 533 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 534 |
padding: 2px 4px; |
| 535 |
} |
| 536 |
.crefSource { |
| 537 |
font-style: italic; |
| 538 |
} |
| 539 |
/* alternative layout for smaller screens */ |
| 540 |
@media screen and (max-width: 1023px) { |
| 541 |
body { |
| 542 |
padding-top: 2em; |
| 543 |
} |
| 544 |
#title { |
| 545 |
padding: 1em 0; |
| 546 |
} |
| 547 |
h1 { |
| 548 |
font-size: 24px; |
| 549 |
} |
| 550 |
h2 { |
| 551 |
font-size: 20px; |
| 552 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 553 |
padding-top: 38px; |
| 554 |
} |
| 555 |
#identifiers dd { |
| 556 |
max-width: 60%; |
| 557 |
} |
| 558 |
#toc { |
| 559 |
position: fixed; |
| 560 |
z-index: 2; |
| 561 |
top: 0; |
| 562 |
right: 0; |
| 563 |
padding: 0; |
| 564 |
margin: 0; |
| 565 |
background-color: inherit; |
| 566 |
border-bottom: 1px solid #ccc; |
| 567 |
} |
| 568 |
#toc h2 { |
| 569 |
margin: -1px 0 0 0; |
| 570 |
padding: 4px 0 4px 6px; |
| 571 |
padding-right: 1em; |
| 572 |
min-width: 190px; |
| 573 |
font-size: 1.1em; |
| 574 |
text-align: right; |
| 575 |
background-color: #444; |
| 576 |
color: white; |
| 577 |
cursor: pointer; |
| 578 |
} |
| 579 |
#toc h2::before { /* css hamburger */ |
| 580 |
float: right; |
| 581 |
position: relative; |
| 582 |
width: 1em; |
| 583 |
height: 1px; |
| 584 |
left: -164px; |
| 585 |
margin: 6px 0 0 0; |
| 586 |
background: white none repeat scroll 0 0; |
| 587 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 588 |
content: ""; |
| 589 |
} |
| 590 |
#toc nav { |
| 591 |
display: none; |
| 592 |
padding: 0.5em 1em 1em; |
| 593 |
overflow: auto; |
| 594 |
height: calc(100vh - 48px); |
| 595 |
border-left: 1px solid #ddd; |
| 596 |
} |
| 597 |
} |
| 598 |
|
| 599 |
/* alternative layout for wide screens */ |
| 600 |
@media screen and (min-width: 1024px) { |
| 601 |
body { |
| 602 |
max-width: 724px; |
| 603 |
margin: 42px auto; |
| 604 |
padding-left: 1.5em; |
| 605 |
padding-right: 29em; |
| 606 |
} |
| 607 |
#toc { |
| 608 |
position: fixed; |
| 609 |
top: 42px; |
| 610 |
right: 42px; |
| 611 |
width: 25%; |
| 612 |
margin: 0; |
| 613 |
padding: 0 1em; |
| 614 |
z-index: 1; |
| 615 |
} |
| 616 |
#toc h2 { |
| 617 |
border-top: none; |
| 618 |
border-bottom: 1px solid #ddd; |
| 619 |
font-size: 1em; |
| 620 |
font-weight: normal; |
| 621 |
margin: 0; |
| 622 |
padding: 0.25em 1em 1em 0; |
| 623 |
} |
| 624 |
#toc nav { |
| 625 |
display: block; |
| 626 |
height: calc(90vh - 84px); |
| 627 |
bottom: 0; |
| 628 |
padding: 0.5em 0 0; |
| 629 |
overflow: auto; |
| 630 |
} |
| 631 |
img { /* future proofing */ |
| 632 |
max-width: 100%; |
| 633 |
height: auto; |
| 634 |
} |
| 635 |
} |
| 636 |
|
| 637 |
/* pagination */ |
| 638 |
@media print { |
| 639 |
body { |
| 640 |
|
| 641 |
width: 100%; |
| 642 |
} |
| 643 |
p { |
| 644 |
orphans: 3; |
| 645 |
widows: 3; |
| 646 |
} |
| 647 |
#n-copyright-notice { |
| 648 |
border-bottom: none; |
| 649 |
} |
| 650 |
#toc, #n-introduction { |
| 651 |
page-break-before: always; |
| 652 |
} |
| 653 |
#toc { |
| 654 |
border-top: none; |
| 655 |
padding-top: 0; |
| 656 |
} |
| 657 |
figure, pre { |
| 658 |
page-break-inside: avoid; |
| 659 |
} |
| 660 |
figure { |
| 661 |
overflow: scroll; |
| 662 |
} |
| 663 |
h1, h2, h3, h4, h5, h6 { |
| 664 |
page-break-after: avoid; |
| 665 |
} |
| 666 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 667 |
page-break-before: avoid; |
| 668 |
} |
| 669 |
pre { |
| 670 |
white-space: pre-wrap; |
| 671 |
word-wrap: break-word; |
| 672 |
font-size: 10pt; |
| 673 |
} |
| 674 |
table { |
| 675 |
border: 1px solid #ddd; |
| 676 |
} |
| 677 |
td { |
| 678 |
border-top: 1px solid #ddd; |
| 679 |
} |
| 680 |
} |
| 681 |
|
| 682 |
/* This is commented out here, as the string-set: doesn't |
| 683 |
pass W3C validation currently */ |
| 684 |
/* |
| 685 |
.ears thead .left { |
| 686 |
string-set: ears-top-left content(); |
| 687 |
} |
| 688 |
|
| 689 |
.ears thead .center { |
| 690 |
string-set: ears-top-center content(); |
| 691 |
} |
| 692 |
|
| 693 |
.ears thead .right { |
| 694 |
string-set: ears-top-right content(); |
| 695 |
} |
| 696 |
|
| 697 |
.ears tfoot .left { |
| 698 |
string-set: ears-bottom-left content(); |
| 699 |
} |
| 700 |
|
| 701 |
.ears tfoot .center { |
| 702 |
string-set: ears-bottom-center content(); |
| 703 |
} |
| 704 |
|
| 705 |
.ears tfoot .right { |
| 706 |
string-set: ears-bottom-right content(); |
| 707 |
} |
| 708 |
*/ |
| 709 |
|
| 710 |
@page :first { |
| 711 |
padding-top: 0; |
| 712 |
@top-left { |
| 713 |
content: normal; |
| 714 |
border: none; |
| 715 |
} |
| 716 |
@top-center { |
| 717 |
content: normal; |
| 718 |
border: none; |
| 719 |
} |
| 720 |
@top-right { |
| 721 |
content: normal; |
| 722 |
border: none; |
| 723 |
} |
| 724 |
} |
| 725 |
|
| 726 |
@page { |
| 727 |
size: A4; |
| 728 |
margin-bottom: 45mm; |
| 729 |
padding-top: 20px; |
| 730 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 731 |
the content depends on the document */ |
| 732 |
/* |
| 733 |
@top-left { |
| 734 |
content: 'Internet-Draft'; |
| 735 |
vertical-align: bottom; |
| 736 |
border-bottom: solid 1px #ccc; |
| 737 |
} |
| 738 |
@top-left { |
| 739 |
content: string(ears-top-left); |
| 740 |
vertical-align: bottom; |
| 741 |
border-bottom: solid 1px #ccc; |
| 742 |
} |
| 743 |
@top-center { |
| 744 |
content: string(ears-top-center); |
| 745 |
vertical-align: bottom; |
| 746 |
border-bottom: solid 1px #ccc; |
| 747 |
} |
| 748 |
@top-right { |
| 749 |
content: string(ears-top-right); |
| 750 |
vertical-align: bottom; |
| 751 |
border-bottom: solid 1px #ccc; |
| 752 |
} |
| 753 |
@bottom-left { |
| 754 |
content: string(ears-bottom-left); |
| 755 |
vertical-align: top; |
| 756 |
border-top: solid 1px #ccc; |
| 757 |
} |
| 758 |
@bottom-center { |
| 759 |
content: string(ears-bottom-center); |
| 760 |
vertical-align: top; |
| 761 |
border-top: solid 1px #ccc; |
| 762 |
} |
| 763 |
@bottom-right { |
| 764 |
content: '[Page ' counter(page) ']'; |
| 765 |
vertical-align: top; |
| 766 |
border-top: solid 1px #ccc; |
| 767 |
} |
| 768 |
*/ |
| 769 |
|
| 770 |
} |
| 771 |
|
| 772 |
/* Changes introduced to fix issues found during implementation */ |
| 773 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 774 |
a { |
| 775 |
z-index: 2; |
| 776 |
} |
| 777 |
/* Separate body from document info even without intervening H1 */ |
| 778 |
section { |
| 779 |
clear: both; |
| 780 |
} |
| 781 |
|
| 782 |
|
| 783 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 784 |
.author { |
| 785 |
vertical-align: top; |
| 786 |
} |
| 787 |
|
| 788 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 789 |
#identifiers dt { |
| 790 |
width: 8em; |
| 791 |
} |
| 792 |
|
| 793 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 794 |
#identifiers dd { |
| 795 |
margin-left: 1em; |
| 796 |
} |
| 797 |
|
| 798 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 799 |
#toc { |
| 800 |
background-color: white; |
| 801 |
} |
| 802 |
|
| 803 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 804 |
@media screen and (max-width: 1023px) { |
| 805 |
#toc h2 a, |
| 806 |
#toc h2 a:link, |
| 807 |
#toc h2 a:focus, |
| 808 |
#toc h2 a:hover, |
| 809 |
#toc a.toplink, |
| 810 |
#toc a.toplink:hover { |
| 811 |
color: white; |
| 812 |
background-color: #444; |
| 813 |
text-decoration: none; |
| 814 |
} |
| 815 |
} |
| 816 |
|
| 817 |
/* Give the bottom of the ToC some whitespace */ |
| 818 |
@media screen and (min-width: 1024px) { |
| 819 |
#toc { |
| 820 |
padding: 0 0 1em 1em; |
| 821 |
} |
| 822 |
} |
| 823 |
|
| 824 |
/* Style section numbers with more space between number and title */ |
| 825 |
.section-number { |
| 826 |
padding-right: 0.5em; |
| 827 |
} |
| 828 |
|
| 829 |
/* prevent monospace from becoming overly large */ |
| 830 |
tt, code, pre, code { |
| 831 |
font-size: 95%; |
| 832 |
} |
| 833 |
|
| 834 |
/* Fix the height/width aspect for ascii art*/ |
| 835 |
pre.sourcecode, |
| 836 |
.art-text pre { |
| 837 |
line-height: 1.12; |
| 838 |
} |
| 839 |
|
| 840 |
|
| 841 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 842 |
a.toplink { |
| 843 |
float: right; |
| 844 |
margin-right: 0.5em; |
| 845 |
} |
| 846 |
|
| 847 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 848 |
dl > dt, |
| 849 |
dl.dlParallel > dt { |
| 850 |
float: left; |
| 851 |
margin-right: 1em; |
| 852 |
} |
| 853 |
dl.dlNewline > dt { |
| 854 |
float: none; |
| 855 |
} |
| 856 |
|
| 857 |
/* Provide styling for table cell text alignment */ |
| 858 |
table td.text-left, |
| 859 |
table th.text-left { |
| 860 |
text-align: left; |
| 861 |
} |
| 862 |
table td.text-center, |
| 863 |
table th.text-center { |
| 864 |
text-align: center; |
| 865 |
} |
| 866 |
table td.text-right, |
| 867 |
table th.text-right { |
| 868 |
text-align: right; |
| 869 |
} |
| 870 |
|
| 871 |
/* Make the alternative author contact informatio look less like just another |
| 872 |
author, and group it closer with the primary author contact information */ |
| 873 |
.alternative-contact { |
| 874 |
margin: 0.5em 0 0.25em 0; |
| 875 |
} |
| 876 |
address .non-ascii { |
| 877 |
margin: 0 0 0 2em; |
| 878 |
} |
| 879 |
|
| 880 |
/* With it being possible to set tables with alignment |
| 881 |
left, center, and right, { width: 100%; } does not make sense */ |
| 882 |
table { |
| 883 |
width: auto; |
| 884 |
} |
| 885 |
|
| 886 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 887 |
because of a long floating dt label.*/ |
| 888 |
.references dd { |
| 889 |
overflow: visible; |
| 890 |
} |
| 891 |
|
| 892 |
/* Control caption placement */ |
| 893 |
caption { |
| 894 |
caption-side: bottom; |
| 895 |
} |
| 896 |
|
| 897 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 898 |
script don't end up on the other side of the page. */ |
| 899 |
|
| 900 |
address.vcard { |
| 901 |
max-width: 30em; |
| 902 |
margin-right: auto; |
| 903 |
} |
| 904 |
|
| 905 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 906 |
address div.left { |
| 907 |
text-align: left; |
| 908 |
} |
| 909 |
address div.right { |
| 910 |
text-align: right; |
| 911 |
} |
| 912 |
|
| 913 |
/* Provide table alignment support. We can't use the alignX classes above |
| 914 |
since they do unwanted things with caption and other styling. */ |
| 915 |
table.right { |
| 916 |
margin-left: auto; |
| 917 |
margin-right: 0; |
| 918 |
} |
| 919 |
table.center { |
| 920 |
margin-left: auto; |
| 921 |
margin-right: auto; |
| 922 |
} |
| 923 |
table.left { |
| 924 |
margin-left: 0; |
| 925 |
margin-right: auto; |
| 926 |
} |
| 927 |
|
| 928 |
/* Give the table caption label the same styling as the figcaption */ |
| 929 |
caption a[href] { |
| 930 |
color: #222; |
| 931 |
} |
| 932 |
|
| 933 |
@media print { |
| 934 |
.toplink { |
| 935 |
display: none; |
| 936 |
} |
| 937 |
|
| 938 |
/* avoid overwriting the top border line with the ToC header */ |
| 939 |
#toc { |
| 940 |
padding-top: 1px; |
| 941 |
} |
| 942 |
|
| 943 |
/* Avoid page breaks inside dl and author address entries */ |
| 944 |
.vcard { |
| 945 |
page-break-inside: avoid; |
| 946 |
} |
| 947 |
|
| 948 |
} |
| 949 |
/* Tweak the bcp14 keyword presentation */ |
| 950 |
.bcp14 { |
| 951 |
font-variant: small-caps; |
| 952 |
font-weight: bold; |
| 953 |
font-size: 0.9em; |
| 954 |
} |
| 955 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 956 |
h2 { |
| 957 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 958 |
padding-top: 31px; |
| 959 |
} |
| 960 |
h3 { |
| 961 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 962 |
padding-top: 24px; |
| 963 |
} |
| 964 |
h4 { |
| 965 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 966 |
padding-top: 24px; |
| 967 |
} |
| 968 |
/* Float artwork pilcrow to the right */ |
| 969 |
@media screen { |
| 970 |
.artwork a.pilcrow { |
| 971 |
display: block; |
| 972 |
line-height: 0.7; |
| 973 |
margin-top: 0.15em; |
| 974 |
} |
| 975 |
} |
| 976 |
/* Make pilcrows on dd visible */ |
| 977 |
@media screen { |
| 978 |
dd:hover > a.pilcrow { |
| 979 |
visibility: visible; |
| 980 |
} |
| 981 |
} |
| 982 |
/* Make the placement of figcaption match that of a table's caption |
| 983 |
by removing the figure's added bottom margin */ |
| 984 |
.alignLeft.art-text, |
| 985 |
.alignCenter.art-text, |
| 986 |
.alignRight.art-text { |
| 987 |
margin-bottom: 0; |
| 988 |
} |
| 989 |
.alignLeft, |
| 990 |
.alignCenter, |
| 991 |
.alignRight { |
| 992 |
margin: 1em 0 0 0; |
| 993 |
} |
| 994 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 995 |
possibly even requiring a new line */ |
| 996 |
@media print { |
| 997 |
a.pilcrow { |
| 998 |
display: none; |
| 999 |
} |
| 1000 |
} |
| 1001 |
/* Styling for the external metadata */ |
| 1002 |
div#external-metadata { |
| 1003 |
background-color: #eee; |
| 1004 |
padding: 0.5em; |
| 1005 |
margin-bottom: 0.5em; |
| 1006 |
display: none; |
| 1007 |
} |
| 1008 |
div#internal-metadata { |
| 1009 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 1010 |
} |
| 1011 |
/* Styling for title RFC Number */ |
| 1012 |
h1#rfcnum { |
| 1013 |
clear: both; |
| 1014 |
margin: 0 0 -1em; |
| 1015 |
padding: 1em 0 0 0; |
| 1016 |
} |
| 1017 |
/* Make .olPercent look the same as <ol><li> */ |
| 1018 |
dl.olPercent > dd { |
| 1019 |
margin-bottom: 0.25em; |
| 1020 |
min-height: initial; |
| 1021 |
} |
| 1022 |
/* Give aside some styling to set it apart */ |
| 1023 |
aside { |
| 1024 |
border-left: 1px solid #ddd; |
| 1025 |
margin: 1em 0 1em 2em; |
| 1026 |
padding: 0.2em 2em; |
| 1027 |
} |
| 1028 |
aside > dl, |
| 1029 |
aside > ol, |
| 1030 |
aside > ul, |
| 1031 |
aside > table, |
| 1032 |
aside > p { |
| 1033 |
margin-bottom: 0.5em; |
| 1034 |
} |
| 1035 |
/* Additional page break settings */ |
| 1036 |
@media print { |
| 1037 |
figcaption, table caption { |
| 1038 |
page-break-before: avoid; |
| 1039 |
} |
| 1040 |
} |
| 1041 |
/* Font size adjustments for print */ |
| 1042 |
@media print { |
| 1043 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1044 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1045 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1046 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1047 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1048 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1049 |
} |
| 1050 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1051 |
@media print { |
| 1052 |
.artwork, |
| 1053 |
.sourcecode { |
| 1054 |
margin-bottom: 1em; |
| 1055 |
} |
| 1056 |
} |
| 1057 |
/* Avoid narrow tables forcing too narrow table captions, which may render badly */ |
| 1058 |
table { |
| 1059 |
min-width: 20em; |
| 1060 |
} |
| 1061 |
/* ol type a */ |
| 1062 |
ol.type-a { list-style-type: lower-alpha; } |
| 1063 |
ol.type-A { list-style-type: upper-alpha; } |
| 1064 |
ol.type-i { list-style-type: lower-roman; } |
| 1065 |
ol.type-I { list-style-type: lower-roman; } |
| 1066 |
/* Apply the print table and row borders in general, on request from the RPC, |
| 1067 |
and increase the contrast between border and odd row background sligthtly */ |
| 1068 |
table { |
| 1069 |
border: 1px solid #ddd; |
| 1070 |
} |
| 1071 |
td { |
| 1072 |
border-top: 1px solid #ddd; |
| 1073 |
} |
| 1074 |
tr:nth-child(2n+1) > td { |
| 1075 |
background-color: #f8f8f8; |
| 1076 |
} |
| 1077 |
/* Use style rules to govern display of the TOC. */ |
| 1078 |
@media screen and (max-width: 1023px) { |
| 1079 |
#toc nav { display: none; } |
| 1080 |
#toc.active nav { display: block; } |
| 1081 |
} |
| 1082 |
/* Add support for keepWithNext */ |
| 1083 |
.keepWithNext { |
| 1084 |
break-after: avoid-page; |
| 1085 |
break-after: avoid-page; |
| 1086 |
} |
| 1087 |
/* Add support for keepWithPrevious */ |
| 1088 |
.keepWithPrevious { |
| 1089 |
break-before: avoid-page; |
| 1090 |
} |
| 1091 |
/* Change the approach to avoiding breaks inside artwork etc. */ |
| 1092 |
figure, pre, table, .artwork, .sourcecode { |
| 1093 |
break-before: auto; |
| 1094 |
break-after: auto; |
| 1095 |
} |
| 1096 |
/* Avoid breaks between <dt> and <dd> */ |
| 1097 |
dl { |
| 1098 |
break-before: auto; |
| 1099 |
break-inside: auto; |
| 1100 |
} |
| 1101 |
dt { |
| 1102 |
break-before: auto; |
| 1103 |
break-after: avoid-page; |
| 1104 |
} |
| 1105 |
dd { |
| 1106 |
break-before: avoid-page; |
| 1107 |
break-after: auto; |
| 1108 |
orphans: 3; |
| 1109 |
widows: 3 |
| 1110 |
} |
| 1111 |
span.break, dd.break { |
| 1112 |
margin-bottom: 0; |
| 1113 |
min-height: 0; |
| 1114 |
break-before: auto; |
| 1115 |
break-inside: auto; |
| 1116 |
break-after: auto; |
| 1117 |
} |
| 1118 |
/* Undo break-before ToC */ |
| 1119 |
@media print { |
| 1120 |
#toc { |
| 1121 |
break-before: auto; |
| 1122 |
} |
| 1123 |
} |
| 1124 |
/* Text in compact lists should not get extra bottim margin space, |
| 1125 |
since that would makes the list not compact */ |
| 1126 |
ul.compact p, .ulCompact p, |
| 1127 |
ol.compact p, .olCompact p { |
| 1128 |
margin: 0; |
| 1129 |
} |
| 1130 |
/* But the list as a whole needs the extra space at the end */ |
| 1131 |
section ul.compact, |
| 1132 |
section .ulCompact, |
| 1133 |
section ol.compact, |
| 1134 |
section .olCompact { |
| 1135 |
margin-bottom: 1em; /* same as p not within ul.compact etc. */ |
| 1136 |
} |
| 1137 |
/* The tt and code background above interferes with for instance table cell |
| 1138 |
backgrounds. Changed to something a bit more selective. */ |
| 1139 |
tt, code { |
| 1140 |
background-color: transparent; |
| 1141 |
} |
| 1142 |
p tt, p code, li tt, li code { |
| 1143 |
background-color: #f8f8f8; |
| 1144 |
} |
| 1145 |
/* Tweak the pre margin -- 0px doesn't come out well */ |
| 1146 |
pre { |
| 1147 |
margin-top: 0.5px; |
| 1148 |
} |
| 1149 |
/* Tweak the comact list text */ |
| 1150 |
ul.compact, .ulCompact, |
| 1151 |
ol.compact, .olCompact, |
| 1152 |
dl.compact, .dlCompact { |
| 1153 |
line-height: normal; |
| 1154 |
} |
| 1155 |
/* Don't add top margin for nested lists */ |
| 1156 |
li > ul, li > ol, li > dl, |
| 1157 |
dd > ul, dd > ol, dd > dl, |
| 1158 |
dl > dd > dl { |
| 1159 |
margin-top: initial; |
| 1160 |
} |
| 1161 |
/* Elements that should not be rendered on the same line as a <dt> */ |
| 1162 |
/* This should match the element list in writer.text.TextWriter.render_dl() */ |
| 1163 |
dd > div.artwork:first-child, |
| 1164 |
dd > aside:first-child, |
| 1165 |
dd > figure:first-child, |
| 1166 |
dd > ol:first-child, |
| 1167 |
dd > div:first-child > pre.sourcecode, |
| 1168 |
dd > table:first-child, |
| 1169 |
dd > ul:first-child { |
| 1170 |
clear: left; |
| 1171 |
} |
| 1172 |
/* fix for weird browser behaviour when <dd/> is empty */ |
| 1173 |
dt+dd:empty::before{ |
| 1174 |
content: "\00a0"; |
| 1175 |
} |
| 1176 |
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */ |
| 1177 |
li > p { |
| 1178 |
margin-bottom: 0.5em |
| 1179 |
} |
| 1180 |
/* Don't let p margin spill out from inside list items */ |
| 1181 |
li > p:last-of-type { |
| 1182 |
margin-bottom: 0; |
| 1183 |
} |
| 1184 |
</style> |
| 1185 |
<link href="rfc-local.css" rel="stylesheet" type="text/css"> |
| 1186 |
<link href="https://dx.doi.org/10.17487/rfc9116" rel="alternate"> |
| 1187 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1188 |
<link href="https://datatracker.ietf.org/doc/draft-foudil-securitytxt-12" rel="prev"> |
| 1189 |
</head> |
| 1190 |
<body> |
| 1191 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1192 |
<table class="ears"> |
| 1193 |
<thead><tr> |
| 1194 |
<td class="left">RFC 9116</td> |
| 1195 |
<td class="center">security.txt</td> |
| 1196 |
<td class="right">April 2022</td> |
| 1197 |
</tr></thead> |
| 1198 |
<tfoot><tr> |
| 1199 |
<td class="left">Foudil & Shafranovich</td> |
| 1200 |
<td class="center">Informational</td> |
| 1201 |
<td class="right">[Page]</td> |
| 1202 |
</tr></tfoot> |
| 1203 |
</table> |
| 1204 |
<div id="external-metadata" class="document-information"></div> |
| 1205 |
<div id="internal-metadata" class="document-information"> |
| 1206 |
<dl id="identifiers"> |
| 1207 |
<dt class="label-stream">Stream:</dt> |
| 1208 |
<dd class="stream">Internet Engineering Task Force (IETF)</dd> |
| 1209 |
<dt class="label-rfc">RFC:</dt> |
| 1210 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9116" class="eref">9116</a></dd> |
| 1211 |
<dt class="label-category">Category:</dt> |
| 1212 |
<dd class="category">Informational</dd> |
| 1213 |
<dt class="label-published">Published:</dt> |
| 1214 |
<dd class="published"> |
| 1215 |
<time datetime="2022-04" class="published">April 2022</time> |
| 1216 |
</dd> |
| 1217 |
<dt class="label-issn">ISSN:</dt> |
| 1218 |
<dd class="issn">2070-1721</dd> |
| 1219 |
<dt class="label-authors">Authors:</dt> |
| 1220 |
<dd class="authors"> |
| 1221 |
<div class="author"> |
| 1222 |
<div class="author-name">E. Foudil</div> |
| 1223 |
</div> |
| 1224 |
<div class="author"> |
| 1225 |
<div class="author-name">Y. Shafranovich</div> |
| 1226 |
<div class="org">Nightwatch Cybersecurity</div> |
| 1227 |
</div> |
| 1228 |
</dd> |
| 1229 |
</dl> |
| 1230 |
</div> |
| 1231 |
<h1 id="rfcnum">RFC 9116</h1> |
| 1232 |
<h1 id="title">A File Format to Aid in Security Vulnerability Disclosure</h1> |
| 1233 |
<section id="section-abstract"> |
| 1234 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1235 |
<p id="section-abstract-1">When security vulnerabilities are discovered by |
| 1236 |
researchers, proper reporting channels are often lacking. As a result, |
| 1237 |
vulnerabilities may be left unreported. This document defines a machine-parsable format |
| 1238 |
("security.txt") to help organizations describe their vulnerability disclosure practices |
| 1239 |
to make it easier for researchers to report vulnerabilities.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1240 |
</section> |
| 1241 |
<div id="status-of-memo"> |
| 1242 |
<section id="section-boilerplate.1"> |
| 1243 |
<h2 id="name-status-of-this-memo"> |
| 1244 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1245 |
</h2> |
| 1246 |
<p id="section-boilerplate.1-1"> |
| 1247 |
This document is not an Internet Standards Track specification; it is |
| 1248 |
published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1249 |
<p id="section-boilerplate.1-2"> |
| 1250 |
This document is a product of the Internet Engineering Task Force |
| 1251 |
(IETF). It represents the consensus of the IETF community. It has |
| 1252 |
received public review and has been approved for publication by the |
| 1253 |
Internet Engineering Steering Group (IESG). Not all documents |
| 1254 |
approved by the IESG are candidates for any level of Internet |
| 1255 |
Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1256 |
<p id="section-boilerplate.1-3"> |
| 1257 |
Information about the current status of this document, any |
| 1258 |
errata, and how to provide feedback on it may be obtained at |
| 1259 |
<span><a href="https://www.rfc-editor.org/info/rfc9116">https://www.rfc-editor.org/info/rfc9116</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1260 |
</section> |
| 1261 |
</div> |
| 1262 |
<div id="copyright"> |
| 1263 |
<section id="section-boilerplate.2"> |
| 1264 |
<h2 id="name-copyright-notice"> |
| 1265 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1266 |
</h2> |
| 1267 |
<p id="section-boilerplate.2-1"> |
| 1268 |
Copyright (c) 2022 IETF Trust and the persons identified as the |
| 1269 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1270 |
<p id="section-boilerplate.2-2"> |
| 1271 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1272 |
Provisions Relating to IETF Documents |
| 1273 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1274 |
publication of this document. Please review these documents |
| 1275 |
carefully, as they describe your rights and restrictions with |
| 1276 |
respect to this document. Code Components extracted from this |
| 1277 |
document must include Revised BSD License text as described in |
| 1278 |
Section 4.e of the Trust Legal Provisions and are provided without |
| 1279 |
warranty as described in the Revised BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p> |
| 1280 |
</section> |
| 1281 |
</div> |
| 1282 |
<div id="toc"> |
| 1283 |
<section id="section-toc.1"> |
| 1284 |
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> |
| 1285 |
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> |
| 1286 |
</h2> |
| 1287 |
<nav class="toc"><ul class="compact toc ulBare ulEmpty"> |
| 1288 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1"> |
| 1289 |
<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> |
| 1290 |
<ul class="compact toc ulBare ulEmpty"> |
| 1291 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.1"> |
| 1292 |
<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-motivation-prior-work-and-s" class="xref">Motivation, Prior Work, and Scope</a></p> |
| 1293 |
</li> |
| 1294 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.2"> |
| 1295 |
<p id="section-toc.1-1.1.2.2.1" class="keepWithNext"><a href="#section-1.2" class="xref">1.2</a>. <a href="#name-terminology" class="xref">Terminology</a></p> |
| 1296 |
</li> |
| 1297 |
</ul> |
| 1298 |
</li> |
| 1299 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2"> |
| 1300 |
<p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>. <a href="#name-the-specification" class="xref">The Specification</a></p> |
| 1301 |
<ul class="compact toc ulBare ulEmpty"> |
| 1302 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.1"> |
| 1303 |
<p id="section-toc.1-1.2.2.1.1"><a href="#section-2.1" class="xref">2.1</a>. <a href="#name-comments" class="xref">Comments</a></p> |
| 1304 |
</li> |
| 1305 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.2"> |
| 1306 |
<p id="section-toc.1-1.2.2.2.1"><a href="#section-2.2" class="xref">2.2</a>. <a href="#name-line-separator" class="xref">Line Separator</a></p> |
| 1307 |
</li> |
| 1308 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.3"> |
| 1309 |
<p id="section-toc.1-1.2.2.3.1"><a href="#section-2.3" class="xref">2.3</a>. <a href="#name-digital-signature" class="xref">Digital Signature</a></p> |
| 1310 |
</li> |
| 1311 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.4"> |
| 1312 |
<p id="section-toc.1-1.2.2.4.1"><a href="#section-2.4" class="xref">2.4</a>. <a href="#name-extensibility" class="xref">Extensibility</a></p> |
| 1313 |
</li> |
| 1314 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5"> |
| 1315 |
<p id="section-toc.1-1.2.2.5.1"><a href="#section-2.5" class="xref">2.5</a>. <a href="#name-field-definitions" class="xref">Field Definitions</a></p> |
| 1316 |
<ul class="compact toc ulBare ulEmpty"> |
| 1317 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5.2.1"> |
| 1318 |
<p id="section-toc.1-1.2.2.5.2.1.1"><a href="#section-2.5.1" class="xref">2.5.1</a>. <a href="#name-acknowledgments" class="xref">Acknowledgments</a></p> |
| 1319 |
</li> |
| 1320 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5.2.2"> |
| 1321 |
<p id="section-toc.1-1.2.2.5.2.2.1"><a href="#section-2.5.2" class="xref">2.5.2</a>. <a href="#name-canonical" class="xref">Canonical</a></p> |
| 1322 |
</li> |
| 1323 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5.2.3"> |
| 1324 |
<p id="section-toc.1-1.2.2.5.2.3.1"><a href="#section-2.5.3" class="xref">2.5.3</a>. <a href="#name-contact" class="xref">Contact</a></p> |
| 1325 |
</li> |
| 1326 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5.2.4"> |
| 1327 |
<p id="section-toc.1-1.2.2.5.2.4.1"><a href="#section-2.5.4" class="xref">2.5.4</a>. <a href="#name-encryption" class="xref">Encryption</a></p> |
| 1328 |
</li> |
| 1329 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5.2.5"> |
| 1330 |
<p id="section-toc.1-1.2.2.5.2.5.1"><a href="#section-2.5.5" class="xref">2.5.5</a>. <a href="#name-expires" class="xref">Expires</a></p> |
| 1331 |
</li> |
| 1332 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5.2.6"> |
| 1333 |
<p id="section-toc.1-1.2.2.5.2.6.1"><a href="#section-2.5.6" class="xref">2.5.6</a>. <a href="#name-hiring" class="xref">Hiring</a></p> |
| 1334 |
</li> |
| 1335 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5.2.7"> |
| 1336 |
<p id="section-toc.1-1.2.2.5.2.7.1"><a href="#section-2.5.7" class="xref">2.5.7</a>. <a href="#name-policy" class="xref">Policy</a></p> |
| 1337 |
</li> |
| 1338 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.5.2.8"> |
| 1339 |
<p id="section-toc.1-1.2.2.5.2.8.1"><a href="#section-2.5.8" class="xref">2.5.8</a>. <a href="#name-preferred-languages" class="xref">Preferred-Languages</a></p> |
| 1340 |
</li> |
| 1341 |
</ul> |
| 1342 |
</li> |
| 1343 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.6"> |
| 1344 |
<p id="section-toc.1-1.2.2.6.1"><a href="#section-2.6" class="xref">2.6</a>. <a href="#name-example-of-an-unsigned-secu" class="xref">Example of an Unsigned "security.txt" File</a></p> |
| 1345 |
</li> |
| 1346 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2.2.7"> |
| 1347 |
<p id="section-toc.1-1.2.2.7.1"><a href="#section-2.7" class="xref">2.7</a>. <a href="#name-example-of-a-signed-securit" class="xref">Example of a Signed "security.txt" File</a></p> |
| 1348 |
</li> |
| 1349 |
</ul> |
| 1350 |
</li> |
| 1351 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3"> |
| 1352 |
<p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-location-of-the-securitytxt" class="xref">Location of the security.txt File</a></p> |
| 1353 |
<ul class="compact toc ulBare ulEmpty"> |
| 1354 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1"> |
| 1355 |
<p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>. <a href="#name-scope-of-the-file" class="xref">Scope of the File</a></p> |
| 1356 |
</li> |
| 1357 |
</ul> |
| 1358 |
</li> |
| 1359 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4"> |
| 1360 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-file-format-description-and" class="xref">File Format Description and ABNF Grammar</a></p> |
| 1361 |
</li> |
| 1362 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5"> |
| 1363 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a></p> |
| 1364 |
<ul class="compact toc ulBare ulEmpty"> |
| 1365 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1"> |
| 1366 |
<p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>. <a href="#name-compromised-files-and-incid" class="xref">Compromised Files and Incident Response</a></p> |
| 1367 |
</li> |
| 1368 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.2"> |
| 1369 |
<p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>. <a href="#name-redirects" class="xref">Redirects</a></p> |
| 1370 |
</li> |
| 1371 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.3"> |
| 1372 |
<p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>. <a href="#name-incorrect-or-stale-informat" class="xref">Incorrect or Stale Information</a></p> |
| 1373 |
</li> |
| 1374 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.4"> |
| 1375 |
<p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>. <a href="#name-intentionally-malformed-fil" class="xref">Intentionally Malformed Files, Resources, and Reports</a></p> |
| 1376 |
</li> |
| 1377 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.5"> |
| 1378 |
<p id="section-toc.1-1.5.2.5.1"><a href="#section-5.5" class="xref">5.5</a>. <a href="#name-no-implied-permission-for-t" class="xref">No Implied Permission for Testing</a></p> |
| 1379 |
</li> |
| 1380 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.6"> |
| 1381 |
<p id="section-toc.1-1.5.2.6.1"><a href="#section-5.6" class="xref">5.6</a>. <a href="#name-multi-user-environments" class="xref">Multi-User Environments</a></p> |
| 1382 |
</li> |
| 1383 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.7"> |
| 1384 |
<p id="section-toc.1-1.5.2.7.1"><a href="#section-5.7" class="xref">5.7</a>. <a href="#name-protecting-data-in-transit" class="xref">Protecting Data in Transit</a></p> |
| 1385 |
</li> |
| 1386 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.8"> |
| 1387 |
<p id="section-toc.1-1.5.2.8.1"><a href="#section-5.8" class="xref">5.8</a>. <a href="#name-spam-and-spurious-reports" class="xref">Spam and Spurious Reports</a></p> |
| 1388 |
</li> |
| 1389 |
</ul> |
| 1390 |
</li> |
| 1391 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6"> |
| 1392 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p> |
| 1393 |
<ul class="compact toc ulBare ulEmpty"> |
| 1394 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1"> |
| 1395 |
<p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>. <a href="#name-well-known-uris-registry" class="xref">Well-Known URIs Registry</a></p> |
| 1396 |
</li> |
| 1397 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2"> |
| 1398 |
<p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>. <a href="#name-registry-for-securitytxt-fi" class="xref">Registry for security.txt Fields</a></p> |
| 1399 |
</li> |
| 1400 |
</ul> |
| 1401 |
</li> |
| 1402 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7"> |
| 1403 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-references" class="xref">References</a></p> |
| 1404 |
<ul class="compact toc ulBare ulEmpty"> |
| 1405 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1"> |
| 1406 |
<p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>. <a href="#name-normative-references" class="xref">Normative References</a></p> |
| 1407 |
</li> |
| 1408 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2"> |
| 1409 |
<p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>. <a href="#name-informative-references" class="xref">Informative References</a></p> |
| 1410 |
</li> |
| 1411 |
</ul> |
| 1412 |
</li> |
| 1413 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8"> |
| 1414 |
<p id="section-toc.1-1.8.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgments-2" class="xref">Acknowledgments</a></p> |
| 1415 |
</li> |
| 1416 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9"> |
| 1417 |
<p id="section-toc.1-1.9.1"><a href="#appendix-B" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p> |
| 1418 |
</li> |
| 1419 |
</ul> |
| 1420 |
</nav> |
| 1421 |
</section> |
| 1422 |
</div> |
| 1423 |
<div id="introduction"> |
| 1424 |
<section id="section-1"> |
| 1425 |
<h2 id="name-introduction"> |
| 1426 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1427 |
</h2> |
| 1428 |
<div id="motivation"> |
| 1429 |
<section id="section-1.1"> |
| 1430 |
<h3 id="name-motivation-prior-work-and-s"> |
| 1431 |
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-motivation-prior-work-and-s" class="section-name selfRef">Motivation, Prior Work, and Scope</a> |
| 1432 |
</h3> |
| 1433 |
<p id="section-1.1-1">Many security researchers encounter situations where they are unable |
| 1434 |
to report security vulnerabilities to organizations because there are |
| 1435 |
no reporting channels to contact the owner of a particular |
| 1436 |
resource, and no information is available about the vulnerability disclosure practices |
| 1437 |
of such owner.<a href="#section-1.1-1" class="pilcrow">¶</a></p> |
| 1438 |
<p id="section-1.1-2">As per <span><a href="https://www.rfc-editor.org/rfc/rfc2142#section-4" class="relref">Section 4</a> of [<a href="#RFC2142" class="xref">RFC2142</a>]</span>, there is an existing convention |
| 1439 |
of using the <SECURITY@domain> email address for communications regarding |
| 1440 |
security issues. That convention provides only a single, email-based |
| 1441 |
channel of communication per domain and does not provide |
| 1442 |
a way for domain owners to publish information about their security disclosure |
| 1443 |
practices.<a href="#section-1.1-2" class="pilcrow">¶</a></p> |
| 1444 |
<p id="section-1.1-3">There are also contact conventions prescribed for Internet Service Providers (ISPs) |
| 1445 |
in <span><a href="https://www.rfc-editor.org/rfc/rfc3013#section-2" class="relref">Section 2</a> of [<a href="#RFC3013" class="xref">RFC3013</a>]</span>, for Computer Security Incident Response Teams (CSIRTs) |
| 1446 |
in <span><a href="https://www.rfc-editor.org/rfc/rfc2350#section-3.2" class="relref">Section 3.2</a> of [<a href="#RFC2350" class="xref">RFC2350</a>]</span>, and for site operators in <span><a href="https://www.rfc-editor.org/rfc/rfc2196#section-5.2" class="relref">Section 5.2</a> of [<a href="#RFC2196" class="xref">RFC2196</a>]</span>. As per <span>[<a href="#RFC7485" class="xref">RFC7485</a>]</span>, there is also contact information provided by |
| 1447 |
Regional Internet Registries (RIRs) and domain registries for owners of IP |
| 1448 |
addresses, Autonomous System Numbers (ASNs), and domain names. However, none of |
| 1449 |
these tackle the issue of how security researchers can locate contact information |
| 1450 |
and vulnerability disclosure practices for organizations in order to report |
| 1451 |
vulnerabilities.<a href="#section-1.1-3" class="pilcrow">¶</a></p> |
| 1452 |
<p id="section-1.1-4">In this document, we define a richer, machine-parsable, and more extensible way |
| 1453 |
for organizations to communicate information about their security disclosure |
| 1454 |
practices and ways to contact them. Other details of vulnerability disclosure |
| 1455 |
are outside the scope of this document. Readers are encouraged to consult other |
| 1456 |
documents such as <span>[<a href="#ISO.29147.2018" class="xref">ISO.29147.2018</a>]</span> or <span>[<a href="#CERT.CVD" class="xref">CERT.CVD</a>]</span>.<a href="#section-1.1-4" class="pilcrow">¶</a></p> |
| 1457 |
<p id="section-1.1-5">As per <span>[<a href="#CERT.CVD" class="xref">CERT.CVD</a>]</span>, "vulnerability response" refers to reports of product vulnerabilities, |
| 1458 |
which is related to but distinct from reports of network intrusions and compromised |
| 1459 |
websites ("incident response"). The mechanism defined in this document is intended |
| 1460 |
to be used for the former ("vulnerability response"). If implementors want |
| 1461 |
to utilize this mechanism for incident response, they should be aware of additional |
| 1462 |
security considerations discussed in <a href="#compromise" class="xref">Section 5.1</a>.<a href="#section-1.1-5" class="pilcrow">¶</a></p> |
| 1463 |
<p id="section-1.1-6">The "security.txt" file is intended to be complementary and not a substitute |
| 1464 |
or replacement for other public resources maintained by organizations regarding |
| 1465 |
their security disclosure practices.<a href="#section-1.1-6" class="pilcrow">¶</a></p> |
| 1466 |
</section> |
| 1467 |
</div> |
| 1468 |
<div id="terminology"> |
| 1469 |
<section id="section-1.2"> |
| 1470 |
<h3 id="name-terminology"> |
| 1471 |
<a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a> |
| 1472 |
</h3> |
| 1473 |
<p id="section-1.2-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>", |
| 1474 |
"<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and |
| 1475 |
"<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as described in |
| 1476 |
BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they appear in all capitals, as shown here.<a href="#section-1.2-1" class="pilcrow">¶</a></p> |
| 1477 |
<p id="section-1.2-2">The term "researcher" corresponds |
| 1478 |
to the terms "finder" and "reporter" in <span>[<a href="#ISO.29147.2018" class="xref">ISO.29147.2018</a>]</span> and <span>[<a href="#CERT.CVD" class="xref">CERT.CVD</a>]</span>. |
| 1479 |
The term "organization" corresponds to the term "vendor" |
| 1480 |
in <span>[<a href="#ISO.29147.2018" class="xref">ISO.29147.2018</a>]</span> and <span>[<a href="#CERT.CVD" class="xref">CERT.CVD</a>]</span>.<a href="#section-1.2-2" class="pilcrow">¶</a></p> |
| 1481 |
<p id="section-1.2-3">The term "implementors" includes all parties involved in |
| 1482 |
the vulnerability disclosure process.<a href="#section-1.2-3" class="pilcrow">¶</a></p> |
| 1483 |
</section> |
| 1484 |
</div> |
| 1485 |
</section> |
| 1486 |
</div> |
| 1487 |
<div id="the-specification"> |
| 1488 |
<section id="section-2"> |
| 1489 |
<h2 id="name-the-specification"> |
| 1490 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-the-specification" class="section-name selfRef">The Specification</a> |
| 1491 |
</h2> |
| 1492 |
<p id="section-2-1">This document defines a text file to be placed in a known location |
| 1493 |
that provides information about vulnerability disclosure practices of a particular organization. |
| 1494 |
The format of this file is machine parsable and <span class="bcp14">MUST</span> follow the ABNF grammar defined in |
| 1495 |
<a href="#abnf" class="xref">Section 4</a>. This file is intended to help security researchers when |
| 1496 |
disclosing security vulnerabilities.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1497 |
<p id="section-2-2">By convention, the file is named "security.txt". The location and scope are described |
| 1498 |
in <a href="#location" class="xref">Section 3</a>.<a href="#section-2-2" class="pilcrow">¶</a></p> |
| 1499 |
<p id="section-2-3">This text file contains multiple fields with different values. A field contains a "name", which is the first part of a field all the way up |
| 1500 |
to the colon (for example: "Contact:") and follows the syntax defined for "field-name" in <span><a href="https://www.rfc-editor.org/rfc/rfc5322#section-3.6.8" class="relref">Section 3.6.8</a> of [<a href="#RFC5322" class="xref">RFC5322</a>]</span>. Field names are case insensitive (as per <span><a href="https://www.rfc-editor.org/rfc/rfc5234#section-2.3" class="relref">Section 2.3</a> of [<a href="#RFC5234" class="xref">RFC5234</a>]</span>). |
| 1501 |
The "value" comes after the field name (for example: "mailto:[email protected]") and follows the syntax |
| 1502 |
defined for "unstructured" in <span><a href="https://www.rfc-editor.org/rfc/rfc5322#section-3.2.5" class="relref">Section 3.2.5</a> of [<a href="#RFC5322" class="xref">RFC5322</a>]</span>. The file <span class="bcp14">MAY</span> also contain blank lines.<a href="#section-2-3" class="pilcrow">¶</a></p> |
| 1503 |
<p id="section-2-4">A field <span class="bcp14">MUST</span> always consist of a name and a value |
| 1504 |
(for example: "Contact: mailto:[email protected]"). A "security.txt" file |
| 1505 |
can have an unlimited number of fields. Each field <span class="bcp14">MUST</span> appear on |
| 1506 |
its own line. Unless otherwise specified by the field definition, |
| 1507 |
multiple values <span class="bcp14">MUST NOT</span> be chained together for a single field. |
| 1508 |
Unless otherwise indicated in a definition of a particular field, a field <span class="bcp14">MAY</span> appear |
| 1509 |
multiple times.<a href="#section-2-4" class="pilcrow">¶</a></p> |
| 1510 |
<p id="section-2-5">Implementors should be aware that some of the fields may |
| 1511 |
contain URIs using percent-encoding (as per <span><a href="https://www.rfc-editor.org/rfc/rfc3986#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC3986" class="xref">RFC3986</a>]</span>).<a href="#section-2-5" class="pilcrow">¶</a></p> |
| 1512 |
<div id="comments"> |
| 1513 |
<section id="section-2.1"> |
| 1514 |
<h3 id="name-comments"> |
| 1515 |
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-comments" class="section-name selfRef">Comments</a> |
| 1516 |
</h3> |
| 1517 |
<p id="section-2.1-1">Any line beginning with the "#" (%x23) symbol <span class="bcp14">MUST</span> be interpreted as a comment. The content of the comment may contain any ASCII or Unicode characters in the |
| 1518 |
%x21-7E and %x80-FFFFF ranges plus the tab (%x09) and space (%x20) characters.<a href="#section-2.1-1" class="pilcrow">¶</a></p> |
| 1519 |
<p id="section-2.1-2">Example:<a href="#section-2.1-2" class="pilcrow">¶</a></p> |
| 1520 |
<div class="alignLeft art-text artwork" id="section-2.1-3"> |
| 1521 |
<pre> |
| 1522 |
# This is a comment. |
| 1523 |
</pre><a href="#section-2.1-3" class="pilcrow">¶</a> |
| 1524 |
</div> |
| 1525 |
</section> |
| 1526 |
</div> |
| 1527 |
<div id="line-separator"> |
| 1528 |
<section id="section-2.2"> |
| 1529 |
<h3 id="name-line-separator"> |
| 1530 |
<a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-line-separator" class="section-name selfRef">Line Separator</a> |
| 1531 |
</h3> |
| 1532 |
<p id="section-2.2-1">Every line <span class="bcp14">MUST</span> end with either a carriage return and line feed |
| 1533 |
characters (CRLF / %x0D %x0A) or just a line feed character (LF / %x0A).<a href="#section-2.2-1" class="pilcrow">¶</a></p> |
| 1534 |
</section> |
| 1535 |
</div> |
| 1536 |
<div id="signature"> |
| 1537 |
<section id="section-2.3"> |
| 1538 |
<h3 id="name-digital-signature"> |
| 1539 |
<a href="#section-2.3" class="section-number selfRef">2.3. </a><a href="#name-digital-signature" class="section-name selfRef">Digital Signature</a> |
| 1540 |
</h3> |
| 1541 |
<p id="section-2.3-1">It is <span class="bcp14">RECOMMENDED</span> that a "security.txt" file be digitally signed |
| 1542 |
using an OpenPGP cleartext signature as described in <span><a href="https://www.rfc-editor.org/rfc/rfc4880#section-7" class="relref">Section 7</a> of [<a href="#RFC4880" class="xref">RFC4880</a>]</span>. When digital signatures are used, it is also |
| 1543 |
<span class="bcp14">RECOMMENDED</span> that organizations use the "Canonical" field (as per <a href="#canonical" class="xref">Section 2.5.2</a>), |
| 1544 |
thus allowing the digital signature to authenticate the location of the file.<a href="#section-2.3-1" class="pilcrow">¶</a></p> |
| 1545 |
<p id="section-2.3-2">When it comes to verifying the key used to generate the signature, it is always |
| 1546 |
the security researcher's responsibility to make sure the key being |
| 1547 |
used is indeed one they trust.<a href="#section-2.3-2" class="pilcrow">¶</a></p> |
| 1548 |
</section> |
| 1549 |
</div> |
| 1550 |
<div id="extensibility"> |
| 1551 |
<section id="section-2.4"> |
| 1552 |
<h3 id="name-extensibility"> |
| 1553 |
<a href="#section-2.4" class="section-number selfRef">2.4. </a><a href="#name-extensibility" class="section-name selfRef">Extensibility</a> |
| 1554 |
</h3> |
| 1555 |
<p id="section-2.4-1">Like many other formats and protocols, this format may need to be changed |
| 1556 |
over time to fit the ever-changing landscape of the Internet. Therefore, |
| 1557 |
extensibility is provided via an IANA registry for fields as defined |
| 1558 |
in <a href="#registry" class="xref">Section 6.2</a>. Any fields registered via that process <span class="bcp14">MUST</span> be |
| 1559 |
considered optional. To encourage extensibility and interoperability, |
| 1560 |
researchers <span class="bcp14">MUST</span> ignore any fields they do not explicitly support.<a href="#section-2.4-1" class="pilcrow">¶</a></p> |
| 1561 |
<p id="section-2.4-2">In general, implementors should "be conservative in what you do, |
| 1562 |
be liberal in what you accept from others" (as per <span>[<a href="#RFC0793" class="xref">RFC0793</a>]</span>).<a href="#section-2.4-2" class="pilcrow">¶</a></p> |
| 1563 |
</section> |
| 1564 |
</div> |
| 1565 |
<div id="field-definitions"> |
| 1566 |
<section id="section-2.5"> |
| 1567 |
<h3 id="name-field-definitions"> |
| 1568 |
<a href="#section-2.5" class="section-number selfRef">2.5. </a><a href="#name-field-definitions" class="section-name selfRef">Field Definitions</a> |
| 1569 |
</h3> |
| 1570 |
<p id="section-2.5-1">Unless otherwise stated, all fields <span class="bcp14">MUST</span> be considered optional.<a href="#section-2.5-1" class="pilcrow">¶</a></p> |
| 1571 |
<div id="acknowledgments"> |
| 1572 |
<section id="section-2.5.1"> |
| 1573 |
<h4 id="name-acknowledgments"> |
| 1574 |
<a href="#section-2.5.1" class="section-number selfRef">2.5.1. </a><a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a> |
| 1575 |
</h4> |
| 1576 |
<p id="section-2.5.1-1">The "Acknowledgments" field indicates a link to a page where security |
| 1577 |
researchers are recognized for their reports. The page being referenced |
| 1578 |
should list security researchers that reported security vulnerabilities |
| 1579 |
and collaborated to remediate them. Organizations should be careful |
| 1580 |
to limit the vulnerability information being published in order |
| 1581 |
to prevent future attacks.<a href="#section-2.5.1-1" class="pilcrow">¶</a></p> |
| 1582 |
<p id="section-2.5.1-2">If this field indicates a web URI, then it <span class="bcp14">MUST</span> begin with "https://" |
| 1583 |
(as per <span><a href="https://www.rfc-editor.org/rfc/rfc7230#section-2.7.2" class="relref">Section 2.7.2</a> of [<a href="#RFC7230" class="xref">RFC7230</a>]</span>).<a href="#section-2.5.1-2" class="pilcrow">¶</a></p> |
| 1584 |
<p id="section-2.5.1-3">Example:<a href="#section-2.5.1-3" class="pilcrow">¶</a></p> |
| 1585 |
<div class="alignLeft art-text artwork" id="section-2.5.1-4"> |
| 1586 |
<pre> |
| 1587 |
Acknowledgments: https://example.com/hall-of-fame.html |
| 1588 |
</pre><a href="#section-2.5.1-4" class="pilcrow">¶</a> |
| 1589 |
</div> |
| 1590 |
<p id="section-2.5.1-5">Example security acknowledgments page:<a href="#section-2.5.1-5" class="pilcrow">¶</a></p> |
| 1591 |
<div class="alignLeft art-text artwork" id="section-2.5.1-6"> |
| 1592 |
<pre> |
| 1593 |
We would like to thank the following researchers: |
| 1594 |
|
| 1595 |
(2017-04-15) Frank Denis - Reflected cross-site scripting |
| 1596 |
(2017-01-02) Alice Quinn - SQL injection |
| 1597 |
(2016-12-24) John Buchner - Stored cross-site scripting |
| 1598 |
(2016-06-10) Anna Richmond - A server configuration issue |
| 1599 |
</pre><a href="#section-2.5.1-6" class="pilcrow">¶</a> |
| 1600 |
</div> |
| 1601 |
</section> |
| 1602 |
</div> |
| 1603 |
<div id="canonical"> |
| 1604 |
<section id="section-2.5.2"> |
| 1605 |
<h4 id="name-canonical"> |
| 1606 |
<a href="#section-2.5.2" class="section-number selfRef">2.5.2. </a><a href="#name-canonical" class="section-name selfRef">Canonical</a> |
| 1607 |
</h4> |
| 1608 |
<p id="section-2.5.2-1">The "Canonical" field indicates the canonical URIs where the "security.txt" file is located, |
| 1609 |
which is usually something like "https://example.com/.well-known/security.txt". |
| 1610 |
If this field indicates a web URI, then it <span class="bcp14">MUST</span> begin with "https://" |
| 1611 |
(as per <span><a href="https://www.rfc-editor.org/rfc/rfc7230#section-2.7.2" class="relref">Section 2.7.2</a> of [<a href="#RFC7230" class="xref">RFC7230</a>]</span>).<a href="#section-2.5.2-1" class="pilcrow">¶</a></p> |
| 1612 |
<p id="section-2.5.2-2">While this field indicates that a "security.txt" retrieved from a given URI |
| 1613 |
is intended to apply to that URI, it <span class="bcp14">MUST NOT</span> be interpreted to apply to |
| 1614 |
all canonical URIs listed within the file. Researchers <span class="bcp14">SHOULD</span> use an additional |
| 1615 |
trust mechanism such as a digital signature (as per <a href="#signature" class="xref">Section 2.3</a>) to make the |
| 1616 |
determination that a particular canonical URI is applicable.<a href="#section-2.5.2-2" class="pilcrow">¶</a></p> |
| 1617 |
<p id="section-2.5.2-3">If this field appears within a "security.txt" file and the URI used to |
| 1618 |
retrieve that file is not listed within any canonical fields, |
| 1619 |
then the contents of the file <span class="bcp14">SHOULD NOT</span> be trusted.<a href="#section-2.5.2-3" class="pilcrow">¶</a></p> |
| 1620 |
<div class="alignLeft art-text artwork" id="section-2.5.2-4"> |
| 1621 |
<pre> |
| 1622 |
Canonical: https://www.example.com/.well-known/security.txt |
| 1623 |
Canonical: https://someserver.example.com/.well-known/security.txt |
| 1624 |
</pre><a href="#section-2.5.2-4" class="pilcrow">¶</a> |
| 1625 |
</div> |
| 1626 |
</section> |
| 1627 |
</div> |
| 1628 |
<div id="contact"> |
| 1629 |
<section id="section-2.5.3"> |
| 1630 |
<h4 id="name-contact"> |
| 1631 |
<a href="#section-2.5.3" class="section-number selfRef">2.5.3. </a><a href="#name-contact" class="section-name selfRef">Contact</a> |
| 1632 |
</h4> |
| 1633 |
<p id="section-2.5.3-1">The "Contact" field indicates a method that researchers |
| 1634 |
should use for reporting security |
| 1635 |
vulnerabilities such as an email address, a phone number, and/or a |
| 1636 |
web page with contact information. This field <span class="bcp14">MUST</span> |
| 1637 |
always be present in a "security.txt" file. If this field indicates a web URI, |
| 1638 |
then it <span class="bcp14">MUST</span> begin with "https://" (as per <span><a href="https://www.rfc-editor.org/rfc/rfc7230#section-2.7.2" class="relref">Section 2.7.2</a> of [<a href="#RFC7230" class="xref">RFC7230</a>]</span>). |
| 1639 |
Security email addresses should use the conventions defined in <span><a href="https://www.rfc-editor.org/rfc/rfc2142#section-4" class="relref">Section 4</a> of [<a href="#RFC2142" class="xref">RFC2142</a>]</span>.<a href="#section-2.5.3-1" class="pilcrow">¶</a></p> |
| 1640 |
<p id="section-2.5.3-2">The value <span class="bcp14">MUST</span> follow the URI syntax described in <span><a href="https://www.rfc-editor.org/rfc/rfc3986#section-3" class="relref">Section 3</a> of [<a href="#RFC3986" class="xref">RFC3986</a>]</span>. |
| 1641 |
This means that "mailto" and "tel" URI schemes must be used |
| 1642 |
when specifying email addresses and telephone numbers, as defined in <span>[<a href="#RFC6068" class="xref">RFC6068</a>]</span> |
| 1643 |
and <span>[<a href="#RFC3966" class="xref">RFC3966</a>]</span>. When the value of this field is an email address, |
| 1644 |
it is <span class="bcp14">RECOMMENDED</span> that encryption be used (as per <a href="#encryption" class="xref">Section 2.5.4</a>).<a href="#section-2.5.3-2" class="pilcrow">¶</a></p> |
| 1645 |
<p id="section-2.5.3-3">These <span class="bcp14">SHOULD</span> be listed in order of preference, with the first occurrence being the preferred |
| 1646 |
method of contact, the second occurrence being the second most preferred method of contact, etc. In the example below, the first email address |
| 1647 |
("[email protected]") is the preferred method of contact.<a href="#section-2.5.3-3" class="pilcrow">¶</a></p> |
| 1648 |
<div class="alignLeft art-text artwork" id="section-2.5.3-4"> |
| 1649 |
<pre> |
| 1650 |
Contact: mailto:[email protected] |
| 1651 |
Contact: mailto:security%2Buri%[email protected] |
| 1652 |
Contact: tel:+1-201-555-0123 |
| 1653 |
Contact: https://example.com/security-contact.html |
| 1654 |
</pre><a href="#section-2.5.3-4" class="pilcrow">¶</a> |
| 1655 |
</div> |
| 1656 |
</section> |
| 1657 |
</div> |
| 1658 |
<div id="encryption"> |
| 1659 |
<section id="section-2.5.4"> |
| 1660 |
<h4 id="name-encryption"> |
| 1661 |
<a href="#section-2.5.4" class="section-number selfRef">2.5.4. </a><a href="#name-encryption" class="section-name selfRef">Encryption</a> |
| 1662 |
</h4> |
| 1663 |
<p id="section-2.5.4-1">The "Encryption" field indicates an encryption key that |
| 1664 |
security researchers should use for encrypted communication. Keys <span class="bcp14">MUST NOT</span> |
| 1665 |
appear in this field. Instead, the value of this field |
| 1666 |
<span class="bcp14">MUST</span> be a URI pointing to a location where the key can be retrieved. |
| 1667 |
If this field indicates a web URI, then it <span class="bcp14">MUST</span> begin with "https://" |
| 1668 |
(as per <span><a href="https://www.rfc-editor.org/rfc/rfc7230#section-2.7.2" class="relref">Section 2.7.2</a> of [<a href="#RFC7230" class="xref">RFC7230</a>]</span>).<a href="#section-2.5.4-1" class="pilcrow">¶</a></p> |
| 1669 |
<p id="section-2.5.4-2">When it comes to verifying the authenticity of the key, it is always the security |
| 1670 |
researcher's responsibility to make sure the key being specified is indeed one |
| 1671 |
they trust. Researchers must not assume that this key is |
| 1672 |
used to generate the digital signature referenced in <a href="#signature" class="xref">Section 2.3</a>.<a href="#section-2.5.4-2" class="pilcrow">¶</a></p> |
| 1673 |
<p id="section-2.5.4-3">Example of an OpenPGP key available from a web server:<a href="#section-2.5.4-3" class="pilcrow">¶</a></p> |
| 1674 |
<div class="alignLeft art-text artwork" id="section-2.5.4-4"> |
| 1675 |
<pre> |
| 1676 |
Encryption: https://example.com/pgp-key.txt |
| 1677 |
</pre><a href="#section-2.5.4-4" class="pilcrow">¶</a> |
| 1678 |
</div> |
| 1679 |
<p id="section-2.5.4-5">Example of an OpenPGP key available from an OPENPGPKEY DNS record:<a href="#section-2.5.4-5" class="pilcrow">¶</a></p> |
| 1680 |
<div class="alignLeft art-text artwork" id="section-2.5.4-6"> |
| 1681 |
<pre> |
| 1682 |
Encryption: dns:5d2d37ab76d47d36._openpgpkey.example.com?type=OPENPGPKEY |
| 1683 |
</pre><a href="#section-2.5.4-6" class="pilcrow">¶</a> |
| 1684 |
</div> |
| 1685 |
<p id="section-2.5.4-7">Example of an OpenPGP key being referenced by its fingerprint:<a href="#section-2.5.4-7" class="pilcrow">¶</a></p> |
| 1686 |
<div class="alignLeft art-text artwork" id="section-2.5.4-8"> |
| 1687 |
<pre> |
| 1688 |
Encryption: openpgp4fpr:5f2de5521c63a801ab59ccb603d49de44b29100f |
| 1689 |
</pre><a href="#section-2.5.4-8" class="pilcrow">¶</a> |
| 1690 |
</div> |
| 1691 |
</section> |
| 1692 |
</div> |
| 1693 |
<div id="expires"> |
| 1694 |
<section id="section-2.5.5"> |
| 1695 |
<h4 id="name-expires"> |
| 1696 |
<a href="#section-2.5.5" class="section-number selfRef">2.5.5. </a><a href="#name-expires" class="section-name selfRef">Expires</a> |
| 1697 |
</h4> |
| 1698 |
<p id="section-2.5.5-1">The "Expires" field indicates the date and time after which the data contained in the "security.txt" |
| 1699 |
file is considered stale and should not be used (as per <a href="#stale" class="xref">Section 5.3</a>). The value of this field is formatted |
| 1700 |
according to the Internet profiles of <span>[<a href="#ISO.8601-1" class="xref">ISO.8601-1</a>]</span> and <span>[<a href="#ISO.8601-2" class="xref">ISO.8601-2</a>]</span> as defined in <span>[<a href="#RFC3339" class="xref">RFC3339</a>]</span>. It is <span class="bcp14">RECOMMENDED</span> that the value |
| 1701 |
of this field be less than a year into the future to avoid staleness.<a href="#section-2.5.5-1" class="pilcrow">¶</a></p> |
| 1702 |
<p id="section-2.5.5-2">This field <span class="bcp14">MUST</span> always be present and <span class="bcp14">MUST NOT</span> appear more than once.<a href="#section-2.5.5-2" class="pilcrow">¶</a></p> |
| 1703 |
<div class="alignLeft art-text artwork" id="section-2.5.5-3"> |
| 1704 |
<pre> |
| 1705 |
Expires: 2021-12-31T18:37:07z |
| 1706 |
</pre><a href="#section-2.5.5-3" class="pilcrow">¶</a> |
| 1707 |
</div> |
| 1708 |
</section> |
| 1709 |
</div> |
| 1710 |
<div id="hiring"> |
| 1711 |
<section id="section-2.5.6"> |
| 1712 |
<h4 id="name-hiring"> |
| 1713 |
<a href="#section-2.5.6" class="section-number selfRef">2.5.6. </a><a href="#name-hiring" class="section-name selfRef">Hiring</a> |
| 1714 |
</h4> |
| 1715 |
<p id="section-2.5.6-1">The "Hiring" field is used for linking to the vendor's security-related job positions. |
| 1716 |
If this field indicates a web URI, then it <span class="bcp14">MUST</span> begin with "https://" |
| 1717 |
(as per <span><a href="https://www.rfc-editor.org/rfc/rfc7230#section-2.7.2" class="relref">Section 2.7.2</a> of [<a href="#RFC7230" class="xref">RFC7230</a>]</span>).<a href="#section-2.5.6-1" class="pilcrow">¶</a></p> |
| 1718 |
<div class="alignLeft art-text artwork" id="section-2.5.6-2"> |
| 1719 |
<pre> |
| 1720 |
Hiring: https://example.com/jobs.html |
| 1721 |
</pre><a href="#section-2.5.6-2" class="pilcrow">¶</a> |
| 1722 |
</div> |
| 1723 |
</section> |
| 1724 |
</div> |
| 1725 |
<div id="policy"> |
| 1726 |
<section id="section-2.5.7"> |
| 1727 |
<h4 id="name-policy"> |
| 1728 |
<a href="#section-2.5.7" class="section-number selfRef">2.5.7. </a><a href="#name-policy" class="section-name selfRef">Policy</a> |
| 1729 |
</h4> |
| 1730 |
<p id="section-2.5.7-1">The "Policy" field indicates a link to where the vulnerability disclosure policy is located. |
| 1731 |
This can help security researchers understand |
| 1732 |
the organization's vulnerability reporting practices. |
| 1733 |
If this field indicates a web URI, then it <span class="bcp14">MUST</span> begin with "https://" |
| 1734 |
(as per <span><a href="https://www.rfc-editor.org/rfc/rfc7230#section-2.7.2" class="relref">Section 2.7.2</a> of [<a href="#RFC7230" class="xref">RFC7230</a>]</span>).<a href="#section-2.5.7-1" class="pilcrow">¶</a></p> |
| 1735 |
<p id="section-2.5.7-2">Example:<a href="#section-2.5.7-2" class="pilcrow">¶</a></p> |
| 1736 |
<div class="alignLeft art-text artwork" id="section-2.5.7-3"> |
| 1737 |
<pre> |
| 1738 |
Policy: https://example.com/disclosure-policy.html |
| 1739 |
</pre><a href="#section-2.5.7-3" class="pilcrow">¶</a> |
| 1740 |
</div> |
| 1741 |
</section> |
| 1742 |
</div> |
| 1743 |
<div id="preflang"> |
| 1744 |
<section id="section-2.5.8"> |
| 1745 |
<h4 id="name-preferred-languages"> |
| 1746 |
<a href="#section-2.5.8" class="section-number selfRef">2.5.8. </a><a href="#name-preferred-languages" class="section-name selfRef">Preferred-Languages</a> |
| 1747 |
</h4> |
| 1748 |
<p id="section-2.5.8-1">The "Preferred-Languages" field can be used to indicate a set of natural languages that |
| 1749 |
are preferred when submitting security reports. This set <span class="bcp14">MAY</span> list multiple |
| 1750 |
values, separated by commas. If this field is included, then at least |
| 1751 |
one value <span class="bcp14">MUST</span> be listed. The values within this set are language tags |
| 1752 |
(as defined in <span>[<a href="#RFC5646" class="xref">RFC5646</a>]</span>). If this field is absent, security researchers |
| 1753 |
may assume that English is the language to be used (as per <span><a href="https://www.rfc-editor.org/rfc/rfc2277#section-4.5" class="relref">Section 4.5</a> of [<a href="#RFC2277" class="xref">RFC2277</a>]</span>).<a href="#section-2.5.8-1" class="pilcrow">¶</a></p> |
| 1754 |
<p id="section-2.5.8-2">The order in which they appear is not an indication of priority; |
| 1755 |
the listed languages are intended to have equal priority.<a href="#section-2.5.8-2" class="pilcrow">¶</a></p> |
| 1756 |
<p id="section-2.5.8-3">This field <span class="bcp14">MUST NOT</span> appear more than once.<a href="#section-2.5.8-3" class="pilcrow">¶</a></p> |
| 1757 |
<p id="section-2.5.8-4">Example (English, Spanish and French):<a href="#section-2.5.8-4" class="pilcrow">¶</a></p> |
| 1758 |
<div class="alignLeft art-text artwork" id="section-2.5.8-5"> |
| 1759 |
<pre> |
| 1760 |
Preferred-Languages: en, es, fr |
| 1761 |
</pre><a href="#section-2.5.8-5" class="pilcrow">¶</a> |
| 1762 |
</div> |
| 1763 |
</section> |
| 1764 |
</div> |
| 1765 |
</section> |
| 1766 |
</div> |
| 1767 |
<div id="example-of-an-unsigned-securitytxt-file"> |
| 1768 |
<section id="section-2.6"> |
| 1769 |
<h3 id="name-example-of-an-unsigned-secu"> |
| 1770 |
<a href="#section-2.6" class="section-number selfRef">2.6. </a><a href="#name-example-of-an-unsigned-secu" class="section-name selfRef">Example of an Unsigned "security.txt" File</a> |
| 1771 |
</h3> |
| 1772 |
<div class="alignLeft art-text artwork" id="section-2.6-1"> |
| 1773 |
<pre> |
| 1774 |
# Our security address |
| 1775 |
Contact: mailto:[email protected] |
| 1776 |
|
| 1777 |
# Our OpenPGP key |
| 1778 |
Encryption: https://example.com/pgp-key.txt |
| 1779 |
|
| 1780 |
# Our security policy |
| 1781 |
Policy: https://example.com/security-policy.html |
| 1782 |
|
| 1783 |
# Our security acknowledgments page |
| 1784 |
Acknowledgments: https://example.com/hall-of-fame.html |
| 1785 |
|
| 1786 |
Expires: 2021-12-31T18:37:07z |
| 1787 |
</pre><a href="#section-2.6-1" class="pilcrow">¶</a> |
| 1788 |
</div> |
| 1789 |
</section> |
| 1790 |
</div> |
| 1791 |
<div id="example-of-a-signed-securitytxt-file"> |
| 1792 |
<section id="section-2.7"> |
| 1793 |
<h3 id="name-example-of-a-signed-securit"> |
| 1794 |
<a href="#section-2.7" class="section-number selfRef">2.7. </a><a href="#name-example-of-a-signed-securit" class="section-name selfRef">Example of a Signed "security.txt" File</a> |
| 1795 |
</h3> |
| 1796 |
<div class="alignLeft art-text artwork" id="section-2.7-1"> |
| 1797 |
<pre> |
| 1798 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 1799 |
Hash: SHA256 |
| 1800 |
|
| 1801 |
# Canonical URI |
| 1802 |
Canonical: https://example.com/.well-known/security.txt |
| 1803 |
|
| 1804 |
# Our security address |
| 1805 |
Contact: mailto:[email protected] |
| 1806 |
|
| 1807 |
# Our OpenPGP key |
| 1808 |
Encryption: https://example.com/pgp-key.txt |
| 1809 |
|
| 1810 |
# Our security policy |
| 1811 |
Policy: https://example.com/security-policy.html |
| 1812 |
|
| 1813 |
# Our security acknowledgments page |
| 1814 |
Acknowledgments: https://example.com/hall-of-fame.html |
| 1815 |
|
| 1816 |
Expires: 2021-12-31T18:37:07z |
| 1817 |
-----BEGIN PGP SIGNATURE----- |
| 1818 |
Version: GnuPG v2.2 |
| 1819 |
|
| 1820 |
[signature] |
| 1821 |
-----END PGP SIGNATURE----- |
| 1822 |
</pre><a href="#section-2.7-1" class="pilcrow">¶</a> |
| 1823 |
</div> |
| 1824 |
</section> |
| 1825 |
</div> |
| 1826 |
</section> |
| 1827 |
</div> |
| 1828 |
<div id="location"> |
| 1829 |
<section id="section-3"> |
| 1830 |
<h2 id="name-location-of-the-securitytxt"> |
| 1831 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-location-of-the-securitytxt" class="section-name selfRef">Location of the security.txt File</a> |
| 1832 |
</h2> |
| 1833 |
<p id="section-3-1">For web-based services, organizations <span class="bcp14">MUST</span> place the "security.txt" file under the "/.well-known/" path, e.g., https://example.com/.well-known/security.txt |
| 1834 |
as per <span>[<a href="#RFC8615" class="xref">RFC8615</a>]</span> of a domain name or IP address. For legacy compatibility, a "security.txt" file might be placed at the top-level path |
| 1835 |
or redirect (as per <span><a href="https://www.rfc-editor.org/rfc/rfc7231#section-6.4" class="relref">Section 6.4</a> of [<a href="#RFC7231" class="xref">RFC7231</a>]</span>) to the "security.txt" file under the "/.well-known/" path. If a "security.txt" file |
| 1836 |
is present in both locations, the one in the "/.well-known/" path <span class="bcp14">MUST</span> be used.<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1837 |
<p id="section-3-2">The file <span class="bcp14">MUST</span> be accessed via HTTP 1.0 or a higher version, |
| 1838 |
and the file access <span class="bcp14">MUST</span> use the "https" scheme (as per <span><a href="https://www.rfc-editor.org/rfc/rfc7230#section-2.7.2" class="relref">Section 2.7.2</a> of [<a href="#RFC7230" class="xref">RFC7230</a>]</span>). |
| 1839 |
It <span class="bcp14">MUST</span> have a Content-Type of "text/plain" |
| 1840 |
with the default charset parameter set to "utf-8" (as per <span><a href="https://www.rfc-editor.org/rfc/rfc2046#section-4.1.3" class="relref">Section 4.1.3</a> of [<a href="#RFC2046" class="xref">RFC2046</a>]</span>).<a href="#section-3-2" class="pilcrow">¶</a></p> |
| 1841 |
<p id="section-3-3">Retrieval of "security.txt" files and resources indicated within such files may result in a redirect (as per <span><a href="https://www.rfc-editor.org/rfc/rfc7231#section-6.4" class="relref">Section 6.4</a> of [<a href="#RFC7231" class="xref">RFC7231</a>]</span>). Researchers should perform additional analysis (as per <a href="#redirects" class="xref">Section 5.2</a>) to make sure these redirects |
| 1842 |
are not malicious or pointing to resources controlled by an attacker.<a href="#section-3-3" class="pilcrow">¶</a></p> |
| 1843 |
<div id="scope-of-the-file"> |
| 1844 |
<section id="section-3.1"> |
| 1845 |
<h3 id="name-scope-of-the-file"> |
| 1846 |
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-scope-of-the-file" class="section-name selfRef">Scope of the File</a> |
| 1847 |
</h3> |
| 1848 |
<p id="section-3.1-1">A "security.txt" file <span class="bcp14">MUST</span> only apply to the domain |
| 1849 |
or IP address in the URI used to retrieve it, not to any of its subdomains or parent domains. |
| 1850 |
A "security.txt" file <span class="bcp14">MAY</span> also apply to products and services provided by the organization publishing the file.<a href="#section-3.1-1" class="pilcrow">¶</a></p> |
| 1851 |
<p id="section-3.1-2">As per <a href="#motivation" class="xref">Section 1.1</a>, this specification is intended for a vulnerability response. |
| 1852 |
If implementors want to use this for an incident response, they should be aware of additional security considerations discussed in <a href="#compromise" class="xref">Section 5.1</a>.<a href="#section-3.1-2" class="pilcrow">¶</a></p> |
| 1853 |
<p id="section-3.1-3">Organizations <span class="bcp14">SHOULD</span> use the policy directive (as per <a href="#policy" class="xref">Section 2.5.7</a>) |
| 1854 |
to provide additional details regarding the scope and details of their vulnerability disclosure process.<a href="#section-3.1-3" class="pilcrow">¶</a></p> |
| 1855 |
<p id="section-3.1-4">Some examples appear below:<a href="#section-3.1-4" class="pilcrow">¶</a></p> |
| 1856 |
<div class="alignLeft art-text artwork" id="section-3.1-5"> |
| 1857 |
<pre> |
| 1858 |
# The following only applies to example.com. |
| 1859 |
https://example.com/.well-known/security.txt |
| 1860 |
|
| 1861 |
# This only applies to subdomain.example.com. |
| 1862 |
https://subdomain.example.com/.well-known/security.txt |
| 1863 |
|
| 1864 |
# This security.txt file applies to IPv4 address of 192.0.2.0. |
| 1865 |
https://192.0.2.0/.well-known/security.txt |
| 1866 |
|
| 1867 |
# This security.txt file applies to IPv6 address of 2001:db8:8:4::2. |
| 1868 |
https://[2001:db8:8:4::2]/.well-known/security.txt |
| 1869 |
</pre><a href="#section-3.1-5" class="pilcrow">¶</a> |
| 1870 |
</div> |
| 1871 |
</section> |
| 1872 |
</div> |
| 1873 |
</section> |
| 1874 |
</div> |
| 1875 |
<div id="abnf"> |
| 1876 |
<section id="section-4"> |
| 1877 |
<h2 id="name-file-format-description-and"> |
| 1878 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-file-format-description-and" class="section-name selfRef">File Format Description and ABNF Grammar</a> |
| 1879 |
</h2> |
| 1880 |
<p id="section-4-1" class="keepWithNext">The file format of the "security.txt" file <span class="bcp14">MUST</span> be plain text (MIME type "text/plain") as defined |
| 1881 |
in <span><a href="https://www.rfc-editor.org/rfc/rfc2046#section-4.1.3" class="relref">Section 4.1.3</a> of [<a href="#RFC2046" class="xref">RFC2046</a>]</span> and <span class="bcp14">MUST</span> be encoded using UTF-8 <span>[<a href="#RFC3629" class="xref">RFC3629</a>]</span> in Net-Unicode form <span>[<a href="#RFC5198" class="xref">RFC5198</a>]</span>.<a href="#section-4-1" class="pilcrow">¶</a></p> |
| 1882 |
<p id="section-4-2">The format of this file <span class="bcp14">MUST</span> follow the ABNF definition below (which incorporates the core ABNF rules from |
| 1883 |
<span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span> and uses the case-sensitive string support from <span>[<a href="#RFC7405" class="xref">RFC7405</a>]</span>).<a href="#section-4-2" class="pilcrow">¶</a></p> |
| 1884 |
<div id="section-4-3"> |
| 1885 |
<pre class="lang-abnf sourcecode"> |
| 1886 |
body = signed / unsigned |
| 1887 |
|
| 1888 |
unsigned = *line (contact-field eol) ; one or more required |
| 1889 |
*line (expires-field eol) ; exactly one required |
| 1890 |
*line [lang-field eol] *line ; exactly one optional |
| 1891 |
; order of fields within the file is not important |
| 1892 |
; except that if contact-field appears more |
| 1893 |
; than once, the order of those indicates |
| 1894 |
; priority (see Section 3.5.3) |
| 1895 |
|
| 1896 |
; signed is the production that should match the OpenPGP clearsigned |
| 1897 |
; document |
| 1898 |
signed = cleartext-header |
| 1899 |
1*(hash-header) |
| 1900 |
CRLF |
| 1901 |
cleartext |
| 1902 |
signature |
| 1903 |
|
| 1904 |
cleartext-header = %s"-----BEGIN PGP SIGNED MESSAGE-----" CRLF |
| 1905 |
|
| 1906 |
hash-header = %s"Hash: " hash-alg *("," hash-alg) CRLF |
| 1907 |
|
| 1908 |
hash-alg = token |
| 1909 |
; imported from RFC 2045; see RFC 4880 Section |
| 1910 |
; 10.3.3 for a pointer to the registry of |
| 1911 |
; valid values |
| 1912 |
|
| 1913 |
;cleartext = 1*( UTF8-octets [CR] LF) |
| 1914 |
; dash-escaped per RFC 4880 Section 7.1 |
| 1915 |
|
| 1916 |
cleartext = *((line-dash / line-from / line-nodash) [CR] LF) |
| 1917 |
|
| 1918 |
line-dash = ("- ") "-" *UTF8-char-not-cr |
| 1919 |
; MUST include initial "- " |
| 1920 |
|
| 1921 |
line-from = ["- "] "From " *UTF8-char-not-cr |
| 1922 |
; SHOULD include initial "- " |
| 1923 |
|
| 1924 |
line-nodash = ["- "] *UTF8-char-not-cr |
| 1925 |
; MAY include initial "- " |
| 1926 |
|
| 1927 |
UTF8-char-not-dash = UTF8-1-not-dash / UTF8-2 / UTF8-3 / UTF8-4 |
| 1928 |
UTF8-1-not-dash = %x00-2C / %x2E-7F |
| 1929 |
UTF8-char-not-cr = UTF8-1-not-cr / UTF8-2 / UTF8-3 / UTF8-4 |
| 1930 |
UTF8-1-not-cr = %x00-0C / %x0E-7F |
| 1931 |
|
| 1932 |
; UTF8 rules from RFC 3629 |
| 1933 |
UTF8-octets = *( UTF8-char ) |
| 1934 |
UTF8-char = UTF8-1 / UTF8-2 / UTF8-3 / UTF8-4 |
| 1935 |
UTF8-1 = %x00-7F |
| 1936 |
UTF8-2 = %xC2-DF UTF8-tail |
| 1937 |
UTF8-3 = %xE0 %xA0-BF UTF8-tail / %xE1-EC 2( UTF8-tail ) / |
| 1938 |
%xED %x80-9F UTF8-tail / %xEE-EF 2( UTF8-tail ) |
| 1939 |
UTF8-4 = %xF0 %x90-BF 2( UTF8-tail ) / |
| 1940 |
%xF1-F3 3( UTF8-tail ) / |
| 1941 |
%xF4 %x80-8F 2( UTF8-tail ) |
| 1942 |
UTF8-tail = %x80-BF |
| 1943 |
|
| 1944 |
signature = armor-header |
| 1945 |
armor-keys |
| 1946 |
CRLF |
| 1947 |
signature-data |
| 1948 |
armor-tail |
| 1949 |
|
| 1950 |
armor-header = %s"-----BEGIN PGP SIGNATURE-----" CRLF |
| 1951 |
|
| 1952 |
armor-keys = *(token ": " *( VCHAR / WSP ) CRLF) |
| 1953 |
; Armor Header Keys from RFC 4880 |
| 1954 |
|
| 1955 |
armor-tail = %s"-----END PGP SIGNATURE-----" CRLF |
| 1956 |
|
| 1957 |
signature-data = 1*(1*(ALPHA / DIGIT / "=" / "+" / "/") CRLF) |
| 1958 |
; base64; see RFC 4648 |
| 1959 |
; includes RFC 4880 checksum |
| 1960 |
|
| 1961 |
line = [ (field / comment) ] eol |
| 1962 |
|
| 1963 |
eol = *WSP [CR] LF |
| 1964 |
|
| 1965 |
field = ; optional fields |
| 1966 |
ack-field / |
| 1967 |
can-field / |
| 1968 |
contact-field / ; optional repeated instances |
| 1969 |
encryption-field / |
| 1970 |
hiring-field / |
| 1971 |
policy-field / |
| 1972 |
ext-field |
| 1973 |
|
| 1974 |
fs = ":" |
| 1975 |
|
| 1976 |
comment = "#" *(WSP / VCHAR / %x80-FFFFF) |
| 1977 |
|
| 1978 |
ack-field = "Acknowledgments" fs SP uri |
| 1979 |
|
| 1980 |
can-field = "Canonical" fs SP uri |
| 1981 |
|
| 1982 |
contact-field = "Contact" fs SP uri |
| 1983 |
|
| 1984 |
expires-field = "Expires" fs SP date-time |
| 1985 |
|
| 1986 |
encryption-field = "Encryption" fs SP uri |
| 1987 |
|
| 1988 |
hiring-field = "Hiring" fs SP uri |
| 1989 |
|
| 1990 |
lang-field = "Preferred-Languages" fs SP lang-values |
| 1991 |
|
| 1992 |
policy-field = "Policy" fs SP uri |
| 1993 |
|
| 1994 |
date-time = < imported from Section 5.6 of [RFC3339] > |
| 1995 |
|
| 1996 |
lang-tag = < Language-Tag from Section 2.1 of [RFC5646] > |
| 1997 |
|
| 1998 |
lang-values = lang-tag *(*WSP "," *WSP lang-tag) |
| 1999 |
|
| 2000 |
uri = < URI as per Section 3 of [RFC3986] > |
| 2001 |
|
| 2002 |
ext-field = field-name fs SP unstructured |
| 2003 |
|
| 2004 |
field-name = < imported from Section 3.6.8 of [RFC5322] > |
| 2005 |
|
| 2006 |
unstructured = < imported from Section 3.2.5 of [RFC5322] > |
| 2007 |
|
| 2008 |
token = < imported from Section 5.1 of [RFC2045] > |
| 2009 |
|
| 2010 |
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z |
| 2011 |
|
| 2012 |
BIT = "0" / "1" |
| 2013 |
|
| 2014 |
CHAR = %x01-7F |
| 2015 |
; any 7-bit US-ASCII character, |
| 2016 |
; excluding NUL |
| 2017 |
|
| 2018 |
CR = %x0D |
| 2019 |
; carriage return |
| 2020 |
|
| 2021 |
CRLF = CR LF |
| 2022 |
; Internet standard newline |
| 2023 |
|
| 2024 |
CTL = %x00-1F / %x7F |
| 2025 |
; controls |
| 2026 |
|
| 2027 |
DIGIT = %x30-39 |
| 2028 |
; 0-9 |
| 2029 |
|
| 2030 |
DQUOTE = %x22 |
| 2031 |
; " (Double Quote) |
| 2032 |
|
| 2033 |
HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F" |
| 2034 |
|
| 2035 |
HTAB = %x09 |
| 2036 |
; horizontal tab |
| 2037 |
|
| 2038 |
LF = %x0A |
| 2039 |
; linefeed |
| 2040 |
|
| 2041 |
LWSP = *(WSP / CRLF WSP) |
| 2042 |
; Use of this linear-white-space rule |
| 2043 |
; permits lines containing only white |
| 2044 |
; space that are no longer legal in |
| 2045 |
; mail headers and have caused |
| 2046 |
; interoperability problems in other |
| 2047 |
; contexts. |
| 2048 |
; Do not use when defining mail |
| 2049 |
; headers and use with caution in |
| 2050 |
; other contexts. |
| 2051 |
|
| 2052 |
OCTET = %x00-FF |
| 2053 |
; 8 bits of data |
| 2054 |
|
| 2055 |
SP = %x20 |
| 2056 |
|
| 2057 |
VCHAR = %x21-7E |
| 2058 |
; visible (printing) characters |
| 2059 |
|
| 2060 |
WSP = SP / HTAB |
| 2061 |
; white space |
| 2062 |
</pre><a href="#section-4-3" class="pilcrow">¶</a> |
| 2063 |
</div> |
| 2064 |
<p id="section-4-4">"ext-field" refers to extension fields, which are discussed in <a href="#extensibility" class="xref">Section 2.4</a>.<a href="#section-4-4" class="pilcrow">¶</a></p> |
| 2065 |
</section> |
| 2066 |
</div> |
| 2067 |
<div id="security-considerations"> |
| 2068 |
<section id="section-5"> |
| 2069 |
<h2 id="name-security-considerations"> |
| 2070 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 2071 |
</h2> |
| 2072 |
<p id="section-5-1">Because of the use of URIs and well-known resources, security considerations of |
| 2073 |
<span>[<a href="#RFC3986" class="xref">RFC3986</a>]</span> and <span>[<a href="#RFC8615" class="xref">RFC8615</a>]</span> apply here, in addition to the |
| 2074 |
considerations outlined below.<a href="#section-5-1" class="pilcrow">¶</a></p> |
| 2075 |
<div id="compromise"> |
| 2076 |
<section id="section-5.1"> |
| 2077 |
<h3 id="name-compromised-files-and-incid"> |
| 2078 |
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-compromised-files-and-incid" class="section-name selfRef">Compromised Files and Incident Response</a> |
| 2079 |
</h3> |
| 2080 |
<p id="section-5.1-1">An attacker that has compromised a website is able to compromise |
| 2081 |
the "security.txt" file as well or set up a redirect to their own site. |
| 2082 |
This can result in security reports not being received by the organization |
| 2083 |
or being sent to the attacker.<a href="#section-5.1-1" class="pilcrow">¶</a></p> |
| 2084 |
<p id="section-5.1-2">To protect against this, organizations should use the "Canonical" field to indicate the locations |
| 2085 |
of the file (as per <a href="#canonical" class="xref">Section 2.5.2</a>), digitally sign their "security.txt" |
| 2086 |
files (as per <a href="#signature" class="xref">Section 2.3</a>), and regularly monitor the file and |
| 2087 |
the referenced resources to detect tampering.<a href="#section-5.1-2" class="pilcrow">¶</a></p> |
| 2088 |
<p id="section-5.1-3">Security researchers should validate the "security.txt" file, including verifying |
| 2089 |
the digital signature and checking any available historical records before using the information |
| 2090 |
contained in the file. If the "security.txt" file looks suspicious or compromised, |
| 2091 |
it should not be used.<a href="#section-5.1-3" class="pilcrow">¶</a></p> |
| 2092 |
<p id="section-5.1-4">While it is not recommended, implementors may choose to use the information published |
| 2093 |
within a "security.txt" file for an incident response. In such cases, extreme caution |
| 2094 |
should be taken before trusting such information, since |
| 2095 |
it may have been compromised by an attacker. Researchers should use additional methods |
| 2096 |
to verify such data including out-of-band verification of the Pretty Good Privacy (PGP) signature, DNSSEC-based approaches, etc.<a href="#section-5.1-4" class="pilcrow">¶</a></p> |
| 2097 |
</section> |
| 2098 |
</div> |
| 2099 |
<div id="redirects"> |
| 2100 |
<section id="section-5.2"> |
| 2101 |
<h3 id="name-redirects"> |
| 2102 |
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-redirects" class="section-name selfRef">Redirects</a> |
| 2103 |
</h3> |
| 2104 |
<p id="section-5.2-1">When retrieving the file and any resources referenced in the file, researchers should record |
| 2105 |
any redirects since they can lead to a different domain or IP address controlled by an attacker. Further |
| 2106 |
inspection of such redirects is recommended before using the information contained within the file.<a href="#section-5.2-1" class="pilcrow">¶</a></p> |
| 2107 |
</section> |
| 2108 |
</div> |
| 2109 |
<div id="stale"> |
| 2110 |
<section id="section-5.3"> |
| 2111 |
<h3 id="name-incorrect-or-stale-informat"> |
| 2112 |
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-incorrect-or-stale-informat" class="section-name selfRef">Incorrect or Stale Information</a> |
| 2113 |
</h3> |
| 2114 |
<p id="section-5.3-1">If information and resources referenced in a "security.txt" file are incorrect |
| 2115 |
or not kept up to date, this can result in security reports not being received |
| 2116 |
by the organization or sent to incorrect contacts, thus exposing possible |
| 2117 |
security issues to third parties. Not having a "security.txt" file may be preferable |
| 2118 |
to having stale information in this file. Organizations must use |
| 2119 |
the "Expires" field (see <a href="#expires" class="xref">Section 2.5.5</a>) to indicate to researchers when |
| 2120 |
the data in the file is no longer valid.<a href="#section-5.3-1" class="pilcrow">¶</a></p> |
| 2121 |
<p id="section-5.3-2">Organizations should ensure that information in this file and any referenced |
| 2122 |
resources such as web pages, email addresses, and telephone numbers |
| 2123 |
are kept current, are accessible, are controlled by the organization, |
| 2124 |
and are kept secure.<a href="#section-5.3-2" class="pilcrow">¶</a></p> |
| 2125 |
</section> |
| 2126 |
</div> |
| 2127 |
<div id="intentionally-malformed-files-resources-and-reports"> |
| 2128 |
<section id="section-5.4"> |
| 2129 |
<h3 id="name-intentionally-malformed-fil"> |
| 2130 |
<a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-intentionally-malformed-fil" class="section-name selfRef">Intentionally Malformed Files, Resources, and Reports</a> |
| 2131 |
</h3> |
| 2132 |
<p id="section-5.4-1">It is possible for compromised or malicious sites to create files that are extraordinarily |
| 2133 |
large or otherwise malformed in an attempt to discover or exploit weaknesses |
| 2134 |
in the parsing code. |
| 2135 |
|
| 2136 |
Researchers should make sure that any such code |
| 2137 |
is robust against large or malformed files and fields, and they may choose to have the code not parse files larger than 32 KBs, those with fields longer than 2,048 characters, or those containing more than 1,000 lines. The ABNF grammar (as defined in |
| 2138 |
<a href="#abnf" class="xref">Section 4</a>) can also be used as a way to verify these files.<a href="#section-5.4-1" class="pilcrow">¶</a></p> |
| 2139 |
<p id="section-5.4-2">The same concerns apply to any other resources referenced within "security.txt" |
| 2140 |
files, as well as any security reports received as a result of publishing |
| 2141 |
this file. Such resources and reports may be hostile, malformed, or malicious.<a href="#section-5.4-2" class="pilcrow">¶</a></p> |
| 2142 |
</section> |
| 2143 |
</div> |
| 2144 |
<div id="no-implied-permission-for-testing"> |
| 2145 |
<section id="section-5.5"> |
| 2146 |
<h3 id="name-no-implied-permission-for-t"> |
| 2147 |
<a href="#section-5.5" class="section-number selfRef">5.5. </a><a href="#name-no-implied-permission-for-t" class="section-name selfRef">No Implied Permission for Testing</a> |
| 2148 |
</h3> |
| 2149 |
<p id="section-5.5-1">The presence of a "security.txt" file might be interpreted by researchers |
| 2150 |
as providing permission to do security testing against the domain or IP address |
| 2151 |
where it is published or against products and services provided by the organization publishing |
| 2152 |
the file. |
| 2153 |
This might result in increased testing against an organization by researchers. On the other hand, a decision not |
| 2154 |
to publish a "security.txt" file might be interpreted by the |
| 2155 |
organization operating that website to be a way to signal to researchers |
| 2156 |
that permission to test that particular site or project is denied. This might result in pushback against |
| 2157 |
researchers reporting security issues to that organization.<a href="#section-5.5-1" class="pilcrow">¶</a></p> |
| 2158 |
<p id="section-5.5-2">Therefore, researchers shouldn't assume that the presence or absence of |
| 2159 |
a "security.txt" file grants or denies permission for security testing. |
| 2160 |
Any such permission may be indicated in the company's vulnerability disclosure policy |
| 2161 |
(as per <a href="#policy" class="xref">Section 2.5.7</a>) or a new field (as per <a href="#extensibility" class="xref">Section 2.4</a>).<a href="#section-5.5-2" class="pilcrow">¶</a></p> |
| 2162 |
</section> |
| 2163 |
</div> |
| 2164 |
<div id="multi-user-environments"> |
| 2165 |
<section id="section-5.6"> |
| 2166 |
<h3 id="name-multi-user-environments"> |
| 2167 |
<a href="#section-5.6" class="section-number selfRef">5.6. </a><a href="#name-multi-user-environments" class="section-name selfRef">Multi-User Environments</a> |
| 2168 |
</h3> |
| 2169 |
<p id="section-5.6-1">In multi-user / multi-tenant environments, it may be possible for a user to take |
| 2170 |
over the location of the "security.txt" file. Organizations should reserve |
| 2171 |
the "security.txt" namespace at the root to ensure no third party can create a page with |
| 2172 |
the "security.txt" AND "/.well-known/security.txt" names.<a href="#section-5.6-1" class="pilcrow">¶</a></p> |
| 2173 |
</section> |
| 2174 |
</div> |
| 2175 |
<div id="protecting-data-in-transit"> |
| 2176 |
<section id="section-5.7"> |
| 2177 |
<h3 id="name-protecting-data-in-transit"> |
| 2178 |
<a href="#section-5.7" class="section-number selfRef">5.7. </a><a href="#name-protecting-data-in-transit" class="section-name selfRef">Protecting Data in Transit</a> |
| 2179 |
</h3> |
| 2180 |
<p id="section-5.7-1">To protect a "security.txt" file from being tampered with in transit, implementors <span class="bcp14">MUST</span> use |
| 2181 |
HTTPS (as per <span><a href="https://www.rfc-editor.org/rfc/rfc7230#section-2.7.2" class="relref">Section 2.7.2</a> of [<a href="#RFC7230" class="xref">RFC7230</a>]</span>) when serving the file itself and for retrieval of any web URIs |
| 2182 |
referenced in it (except when otherwise noted in this specification). As part of the TLS |
| 2183 |
handshake, researchers should validate the provided X.509 certificate |
| 2184 |
in accordance with <span>[<a href="#RFC6125" class="xref">RFC6125</a>]</span> and the following considerations:<a href="#section-5.7-1" class="pilcrow">¶</a></p> |
| 2185 |
<ul class="normal"> |
| 2186 |
<li class="normal" id="section-5.7-2.1">Matching is performed only against the DNS-ID identifiers.<a href="#section-5.7-2.1" class="pilcrow">¶</a> |
| 2187 |
</li> |
| 2188 |
<li class="normal" id="section-5.7-2.2">DNS domain names in server certificates <span class="bcp14">MAY</span> contain the wildcard |
| 2189 |
character '*' as the complete leftmost label within the identifier.<a href="#section-5.7-2.2" class="pilcrow">¶</a> |
| 2190 |
</li> |
| 2191 |
</ul> |
| 2192 |
<p id="section-5.7-3">The certificate may also be checked for revocation via the Online Certificate Status |
| 2193 |
Protocol (OCSP) <span>[<a href="#RFC6960" class="xref">RFC6960</a>]</span>, certificate revocation lists (CRLs), or similar mechanisms.<a href="#section-5.7-3" class="pilcrow">¶</a></p> |
| 2194 |
<p id="section-5.7-4">In cases where the "security.txt" file cannot be served via HTTPS (such as localhost) or is |
| 2195 |
being served with an invalid certificate, additional human validation is recommended since |
| 2196 |
the contents may have been modified while in transit.<a href="#section-5.7-4" class="pilcrow">¶</a></p> |
| 2197 |
<p id="section-5.7-5">As an additional layer of protection, it is also recommended that |
| 2198 |
organizations digitally sign their "security.txt" file with OpenPGP (as per <a href="#signature" class="xref">Section 2.3</a>). |
| 2199 |
Also, to protect security reports from being tampered with or observed while in transit, |
| 2200 |
organizations should specify encryption keys (as per <a href="#encryption" class="xref">Section 2.5.4</a>) unless |
| 2201 |
HTTPS is being used for report submission.<a href="#section-5.7-5" class="pilcrow">¶</a></p> |
| 2202 |
<p id="section-5.7-6">However, the determination of validity of such keys is out of scope |
| 2203 |
for this specification. Security researchers need to establish other secure means to |
| 2204 |
verify them.<a href="#section-5.7-6" class="pilcrow">¶</a></p> |
| 2205 |
</section> |
| 2206 |
</div> |
| 2207 |
<div id="spam-and-spurious-reports"> |
| 2208 |
<section id="section-5.8"> |
| 2209 |
<h3 id="name-spam-and-spurious-reports"> |
| 2210 |
<a href="#section-5.8" class="section-number selfRef">5.8. </a><a href="#name-spam-and-spurious-reports" class="section-name selfRef">Spam and Spurious Reports</a> |
| 2211 |
</h3> |
| 2212 |
<p id="section-5.8-1">Similar to concerns in <span>[<a href="#RFC2142" class="xref">RFC2142</a>]</span>, denial-of-service attacks via spam reports |
| 2213 |
would become easier once a "security.txt" file is published by |
| 2214 |
an organization. In addition, there is an increased likelihood of reports |
| 2215 |
being sent in an automated fashion and/or as a result of automated scans without |
| 2216 |
human analysis. Attackers can also use this file as a way to spam unrelated |
| 2217 |
third parties by listing their resources and/or contact information.<a href="#section-5.8-1" class="pilcrow">¶</a></p> |
| 2218 |
<p id="section-5.8-2">Organizations need to weigh the advantages of publishing this file versus |
| 2219 |
the possible disadvantages and increased resources required to analyze |
| 2220 |
security reports.<a href="#section-5.8-2" class="pilcrow">¶</a></p> |
| 2221 |
<p id="section-5.8-3">Security researchers should review all information within the "security.txt" |
| 2222 |
file before submitting reports in an automated fashion or reports resulting from automated scans.<a href="#section-5.8-3" class="pilcrow">¶</a></p> |
| 2223 |
</section> |
| 2224 |
</div> |
| 2225 |
</section> |
| 2226 |
</div> |
| 2227 |
<div id="iana-considerations"> |
| 2228 |
<section id="section-6"> |
| 2229 |
<h2 id="name-iana-considerations"> |
| 2230 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 2231 |
</h2> |
| 2232 |
<p id="section-6-1">Implementors should be aware that any resources referenced within |
| 2233 |
a "security.txt" file <span class="bcp14">MUST NOT</span> point to the Well-Known URIs namespace unless |
| 2234 |
they are registered with IANA (as per <span>[<a href="#RFC8615" class="xref">RFC8615</a>]</span>).<a href="#section-6-1" class="pilcrow">¶</a></p> |
| 2235 |
<div id="well-known-uris-registry"> |
| 2236 |
<section id="section-6.1"> |
| 2237 |
<h3 id="name-well-known-uris-registry"> |
| 2238 |
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-well-known-uris-registry" class="section-name selfRef">Well-Known URIs Registry</a> |
| 2239 |
</h3> |
| 2240 |
<p id="section-6.1-1">IANA has updated the "Well-Known URIs" registry with the following additional |
| 2241 |
values (using the template from <span>[<a href="#RFC8615" class="xref">RFC8615</a>]</span>):<a href="#section-6.1-1" class="pilcrow">¶</a></p> |
| 2242 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.1-2"> |
| 2243 |
<dt id="section-6.1-2.1">URI suffix:</dt> |
| 2244 |
<dd style="margin-left: 1.5em" id="section-6.1-2.2">security.txt<a href="#section-6.1-2.2" class="pilcrow">¶</a> |
| 2245 |
</dd> |
| 2246 |
<dd class="break"></dd> |
| 2247 |
<dt id="section-6.1-2.3">Change controller:</dt> |
| 2248 |
<dd style="margin-left: 1.5em" id="section-6.1-2.4">IETF<a href="#section-6.1-2.4" class="pilcrow">¶</a> |
| 2249 |
</dd> |
| 2250 |
<dd class="break"></dd> |
| 2251 |
<dt id="section-6.1-2.5">Specification document(s):</dt> |
| 2252 |
<dd style="margin-left: 1.5em" id="section-6.1-2.6">RFC 9116<a href="#section-6.1-2.6" class="pilcrow">¶</a> |
| 2253 |
</dd> |
| 2254 |
<dd class="break"></dd> |
| 2255 |
<dt id="section-6.1-2.7">Status:</dt> |
| 2256 |
<dd style="margin-left: 1.5em" id="section-6.1-2.8">permanent<a href="#section-6.1-2.8" class="pilcrow">¶</a> |
| 2257 |
</dd> |
| 2258 |
<dd class="break"></dd> |
| 2259 |
</dl> |
| 2260 |
</section> |
| 2261 |
</div> |
| 2262 |
<div id="registry"> |
| 2263 |
<section id="section-6.2"> |
| 2264 |
<h3 id="name-registry-for-securitytxt-fi"> |
| 2265 |
<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-registry-for-securitytxt-fi" class="section-name selfRef">Registry for security.txt Fields</a> |
| 2266 |
</h3> |
| 2267 |
<p id="section-6.2-1">IANA has created the "security.txt Fields" registry in |
| 2268 |
accordance with <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>. This registry contains fields for |
| 2269 |
use in "security.txt" files, defined by this specification.<a href="#section-6.2-1" class="pilcrow">¶</a></p> |
| 2270 |
<p id="section-6.2-2">New registrations or updates <span class="bcp14">MUST</span> be published in accordance with the |
| 2271 |
"Expert Review" guidelines as described in Sections |
| 2272 |
<a href="https://www.rfc-editor.org/rfc/rfc8126#section-4.5" class="relref">4.5</a> and <a href="https://www.rfc-editor.org/rfc/rfc8126#section-5" class="relref">5</a> of <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>. Any new field thus registered is considered optional |
| 2273 |
by this specification unless a new version of this specification is published.<a href="#section-6.2-2" class="pilcrow">¶</a></p> |
| 2274 |
<p id="section-6.2-3">Designated experts should determine whether a proposed registration or update |
| 2275 |
provides value to organizations and researchers using this format and makes sense in the context of industry-accepted vulnerability disclosure processes |
| 2276 |
such as <span>[<a href="#ISO.29147.2018" class="xref">ISO.29147.2018</a>]</span> and <span>[<a href="#CERT.CVD" class="xref">CERT.CVD</a>]</span>.<a href="#section-6.2-3" class="pilcrow">¶</a></p> |
| 2277 |
<p id="section-6.2-4">New registrations and updates <span class="bcp14">MUST</span> contain the following information:<a href="#section-6.2-4" class="pilcrow">¶</a></p> |
| 2278 |
<ol start="1" type="1" class="normal type-1" id="section-6.2-5"> |
| 2279 |
<li id="section-6.2-5.1">Name of the field being registered or updated<a href="#section-6.2-5.1" class="pilcrow">¶</a> |
| 2280 |
</li> |
| 2281 |
<li id="section-6.2-5.2">Short description of the field<a href="#section-6.2-5.2" class="pilcrow">¶</a> |
| 2282 |
</li> |
| 2283 |
<li id="section-6.2-5.3">Whether the field can appear more than once<a href="#section-6.2-5.3" class="pilcrow">¶</a> |
| 2284 |
</li> |
| 2285 |
<li id="section-6.2-5.4"> |
| 2286 |
<p id="section-6.2-5.4.1"> New or updated status, which <span class="bcp14">MUST</span> be one of the following:<a href="#section-6.2-5.4.1" class="pilcrow">¶</a></p> |
| 2287 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.2-5.4.2"> |
| 2288 |
<dt id="section-6.2-5.4.2.1">current:</dt> |
| 2289 |
<dd style="margin-left: 1.5em" id="section-6.2-5.4.2.2">The field is in current use.<a href="#section-6.2-5.4.2.2" class="pilcrow">¶</a> |
| 2290 |
</dd> |
| 2291 |
<dd class="break"></dd> |
| 2292 |
<dt id="section-6.2-5.4.2.3">deprecated:</dt> |
| 2293 |
<dd style="margin-left: 1.5em" id="section-6.2-5.4.2.4">The field has been in use, but new usage is discouraged.<a href="#section-6.2-5.4.2.4" class="pilcrow">¶</a> |
| 2294 |
</dd> |
| 2295 |
<dd class="break"></dd> |
| 2296 |
<dt id="section-6.2-5.4.2.5">historic:</dt> |
| 2297 |
<dd style="margin-left: 1.5em" id="section-6.2-5.4.2.6">The field is no longer in current use.<a href="#section-6.2-5.4.2.6" class="pilcrow">¶</a> |
| 2298 |
</dd> |
| 2299 |
<dd class="break"></dd> |
| 2300 |
</dl> |
| 2301 |
</li> |
| 2302 |
<li id="section-6.2-5.5">Change controller<a href="#section-6.2-5.5" class="pilcrow">¶</a> |
| 2303 |
</li> |
| 2304 |
<li id="section-6.2-5.6">The document in which the specification of the field is published (if available)<a href="#section-6.2-5.6" class="pilcrow">¶</a> |
| 2305 |
</li> |
| 2306 |
</ol> |
| 2307 |
<p id="section-6.2-6">Existing registrations may be marked historic or deprecated, as appropriate, by a future update to this document.<a href="#section-6.2-6" class="pilcrow">¶</a></p> |
| 2308 |
<p id="section-6.2-7">The initial registry contains these values:<a href="#section-6.2-7" class="pilcrow">¶</a></p> |
| 2309 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.2-8"> |
| 2310 |
<dt id="section-6.2-8.1">Field Name:</dt> |
| 2311 |
<dd style="margin-left: 1.5em" id="section-6.2-8.2">Acknowledgments<a href="#section-6.2-8.2" class="pilcrow">¶</a> |
| 2312 |
</dd> |
| 2313 |
<dd class="break"></dd> |
| 2314 |
<dt id="section-6.2-8.3">Description:</dt> |
| 2315 |
<dd style="margin-left: 1.5em" id="section-6.2-8.4">link to page where security researchers are recognized<a href="#section-6.2-8.4" class="pilcrow">¶</a> |
| 2316 |
</dd> |
| 2317 |
<dd class="break"></dd> |
| 2318 |
<dt id="section-6.2-8.5">Multiple Appearances:</dt> |
| 2319 |
<dd style="margin-left: 1.5em" id="section-6.2-8.6">yes<a href="#section-6.2-8.6" class="pilcrow">¶</a> |
| 2320 |
</dd> |
| 2321 |
<dd class="break"></dd> |
| 2322 |
<dt id="section-6.2-8.7">Status:</dt> |
| 2323 |
<dd style="margin-left: 1.5em" id="section-6.2-8.8">current<a href="#section-6.2-8.8" class="pilcrow">¶</a> |
| 2324 |
</dd> |
| 2325 |
<dd class="break"></dd> |
| 2326 |
<dt id="section-6.2-8.9">Change controller:</dt> |
| 2327 |
<dd style="margin-left: 1.5em" id="section-6.2-8.10">IETF<a href="#section-6.2-8.10" class="pilcrow">¶</a> |
| 2328 |
</dd> |
| 2329 |
<dd class="break"></dd> |
| 2330 |
<dt id="section-6.2-8.11">Reference:</dt> |
| 2331 |
<dd style="margin-left: 1.5em" id="section-6.2-8.12">RFC 9116<a href="#section-6.2-8.12" class="pilcrow">¶</a> |
| 2332 |
</dd> |
| 2333 |
<dd class="break"></dd> |
| 2334 |
</dl> |
| 2335 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.2-9"> |
| 2336 |
<dt id="section-6.2-9.1">Field Name:</dt> |
| 2337 |
<dd style="margin-left: 1.5em" id="section-6.2-9.2">Canonical<a href="#section-6.2-9.2" class="pilcrow">¶</a> |
| 2338 |
</dd> |
| 2339 |
<dd class="break"></dd> |
| 2340 |
<dt id="section-6.2-9.3">Description:</dt> |
| 2341 |
<dd style="margin-left: 1.5em" id="section-6.2-9.4">canonical URI for this file<a href="#section-6.2-9.4" class="pilcrow">¶</a> |
| 2342 |
</dd> |
| 2343 |
<dd class="break"></dd> |
| 2344 |
<dt id="section-6.2-9.5">Multiple Appearances:</dt> |
| 2345 |
<dd style="margin-left: 1.5em" id="section-6.2-9.6">yes<a href="#section-6.2-9.6" class="pilcrow">¶</a> |
| 2346 |
</dd> |
| 2347 |
<dd class="break"></dd> |
| 2348 |
<dt id="section-6.2-9.7">Status:</dt> |
| 2349 |
<dd style="margin-left: 1.5em" id="section-6.2-9.8">current<a href="#section-6.2-9.8" class="pilcrow">¶</a> |
| 2350 |
</dd> |
| 2351 |
<dd class="break"></dd> |
| 2352 |
<dt id="section-6.2-9.9">Change controller:</dt> |
| 2353 |
<dd style="margin-left: 1.5em" id="section-6.2-9.10">IETF<a href="#section-6.2-9.10" class="pilcrow">¶</a> |
| 2354 |
</dd> |
| 2355 |
<dd class="break"></dd> |
| 2356 |
<dt id="section-6.2-9.11">Reference:</dt> |
| 2357 |
<dd style="margin-left: 1.5em" id="section-6.2-9.12">RFC 9116<a href="#section-6.2-9.12" class="pilcrow">¶</a> |
| 2358 |
</dd> |
| 2359 |
<dd class="break"></dd> |
| 2360 |
</dl> |
| 2361 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.2-10"> |
| 2362 |
<dt id="section-6.2-10.1">Field Name:</dt> |
| 2363 |
<dd style="margin-left: 1.5em" id="section-6.2-10.2">Contact<a href="#section-6.2-10.2" class="pilcrow">¶</a> |
| 2364 |
</dd> |
| 2365 |
<dd class="break"></dd> |
| 2366 |
<dt id="section-6.2-10.3">Description:</dt> |
| 2367 |
<dd style="margin-left: 1.5em" id="section-6.2-10.4">contact information to use for reporting vulnerabilities<a href="#section-6.2-10.4" class="pilcrow">¶</a> |
| 2368 |
</dd> |
| 2369 |
<dd class="break"></dd> |
| 2370 |
<dt id="section-6.2-10.5">Multiple Appearances:</dt> |
| 2371 |
<dd style="margin-left: 1.5em" id="section-6.2-10.6">yes<a href="#section-6.2-10.6" class="pilcrow">¶</a> |
| 2372 |
</dd> |
| 2373 |
<dd class="break"></dd> |
| 2374 |
<dt id="section-6.2-10.7">Status:</dt> |
| 2375 |
<dd style="margin-left: 1.5em" id="section-6.2-10.8">current<a href="#section-6.2-10.8" class="pilcrow">¶</a> |
| 2376 |
</dd> |
| 2377 |
<dd class="break"></dd> |
| 2378 |
<dt id="section-6.2-10.9">Change controller:</dt> |
| 2379 |
<dd style="margin-left: 1.5em" id="section-6.2-10.10">IETF<a href="#section-6.2-10.10" class="pilcrow">¶</a> |
| 2380 |
</dd> |
| 2381 |
<dd class="break"></dd> |
| 2382 |
<dt id="section-6.2-10.11">Reference:</dt> |
| 2383 |
<dd style="margin-left: 1.5em" id="section-6.2-10.12">RFC 9116<a href="#section-6.2-10.12" class="pilcrow">¶</a> |
| 2384 |
</dd> |
| 2385 |
<dd class="break"></dd> |
| 2386 |
</dl> |
| 2387 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.2-11"> |
| 2388 |
<dt id="section-6.2-11.1">Field Name:</dt> |
| 2389 |
<dd style="margin-left: 1.5em" id="section-6.2-11.2">Expires<a href="#section-6.2-11.2" class="pilcrow">¶</a> |
| 2390 |
</dd> |
| 2391 |
<dd class="break"></dd> |
| 2392 |
<dt id="section-6.2-11.3">Description:</dt> |
| 2393 |
<dd style="margin-left: 1.5em" id="section-6.2-11.4">date and time after which this file is considered stale<a href="#section-6.2-11.4" class="pilcrow">¶</a> |
| 2394 |
</dd> |
| 2395 |
<dd class="break"></dd> |
| 2396 |
<dt id="section-6.2-11.5">Multiple Appearances:</dt> |
| 2397 |
<dd style="margin-left: 1.5em" id="section-6.2-11.6">no<a href="#section-6.2-11.6" class="pilcrow">¶</a> |
| 2398 |
</dd> |
| 2399 |
<dd class="break"></dd> |
| 2400 |
<dt id="section-6.2-11.7">Status:</dt> |
| 2401 |
<dd style="margin-left: 1.5em" id="section-6.2-11.8">current<a href="#section-6.2-11.8" class="pilcrow">¶</a> |
| 2402 |
</dd> |
| 2403 |
<dd class="break"></dd> |
| 2404 |
<dt id="section-6.2-11.9">Change controller:</dt> |
| 2405 |
<dd style="margin-left: 1.5em" id="section-6.2-11.10">IETF<a href="#section-6.2-11.10" class="pilcrow">¶</a> |
| 2406 |
</dd> |
| 2407 |
<dd class="break"></dd> |
| 2408 |
<dt id="section-6.2-11.11">Reference:</dt> |
| 2409 |
<dd style="margin-left: 1.5em" id="section-6.2-11.12">RFC 9116<a href="#section-6.2-11.12" class="pilcrow">¶</a> |
| 2410 |
</dd> |
| 2411 |
<dd class="break"></dd> |
| 2412 |
</dl> |
| 2413 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.2-12"> |
| 2414 |
<dt id="section-6.2-12.1">Field Name:</dt> |
| 2415 |
<dd style="margin-left: 1.5em" id="section-6.2-12.2">Encryption<a href="#section-6.2-12.2" class="pilcrow">¶</a> |
| 2416 |
</dd> |
| 2417 |
<dd class="break"></dd> |
| 2418 |
<dt id="section-6.2-12.3">Description:</dt> |
| 2419 |
<dd style="margin-left: 1.5em" id="section-6.2-12.4">link to a key to be used for encrypted communication<a href="#section-6.2-12.4" class="pilcrow">¶</a> |
| 2420 |
</dd> |
| 2421 |
<dd class="break"></dd> |
| 2422 |
<dt id="section-6.2-12.5">Multiple Appearances:</dt> |
| 2423 |
<dd style="margin-left: 1.5em" id="section-6.2-12.6">yes<a href="#section-6.2-12.6" class="pilcrow">¶</a> |
| 2424 |
</dd> |
| 2425 |
<dd class="break"></dd> |
| 2426 |
<dt id="section-6.2-12.7">Status:</dt> |
| 2427 |
<dd style="margin-left: 1.5em" id="section-6.2-12.8">current<a href="#section-6.2-12.8" class="pilcrow">¶</a> |
| 2428 |
</dd> |
| 2429 |
<dd class="break"></dd> |
| 2430 |
<dt id="section-6.2-12.9">Change controller:</dt> |
| 2431 |
<dd style="margin-left: 1.5em" id="section-6.2-12.10">IETF<a href="#section-6.2-12.10" class="pilcrow">¶</a> |
| 2432 |
</dd> |
| 2433 |
<dd class="break"></dd> |
| 2434 |
<dt id="section-6.2-12.11">Reference:</dt> |
| 2435 |
<dd style="margin-left: 1.5em" id="section-6.2-12.12">RFC 9116<a href="#section-6.2-12.12" class="pilcrow">¶</a> |
| 2436 |
</dd> |
| 2437 |
<dd class="break"></dd> |
| 2438 |
</dl> |
| 2439 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.2-13"> |
| 2440 |
<dt id="section-6.2-13.1">Field Name:</dt> |
| 2441 |
<dd style="margin-left: 1.5em" id="section-6.2-13.2">Hiring<a href="#section-6.2-13.2" class="pilcrow">¶</a> |
| 2442 |
</dd> |
| 2443 |
<dd class="break"></dd> |
| 2444 |
<dt id="section-6.2-13.3">Description:</dt> |
| 2445 |
<dd style="margin-left: 1.5em" id="section-6.2-13.4">link to the vendor's security-related job positions<a href="#section-6.2-13.4" class="pilcrow">¶</a> |
| 2446 |
</dd> |
| 2447 |
<dd class="break"></dd> |
| 2448 |
<dt id="section-6.2-13.5">Multiple Appearances:</dt> |
| 2449 |
<dd style="margin-left: 1.5em" id="section-6.2-13.6">yes<a href="#section-6.2-13.6" class="pilcrow">¶</a> |
| 2450 |
</dd> |
| 2451 |
<dd class="break"></dd> |
| 2452 |
<dt id="section-6.2-13.7">Status:</dt> |
| 2453 |
<dd style="margin-left: 1.5em" id="section-6.2-13.8">current<a href="#section-6.2-13.8" class="pilcrow">¶</a> |
| 2454 |
</dd> |
| 2455 |
<dd class="break"></dd> |
| 2456 |
<dt id="section-6.2-13.9">Change controller:</dt> |
| 2457 |
<dd style="margin-left: 1.5em" id="section-6.2-13.10">IETF<a href="#section-6.2-13.10" class="pilcrow">¶</a> |
| 2458 |
</dd> |
| 2459 |
<dd class="break"></dd> |
| 2460 |
<dt id="section-6.2-13.11">Reference:</dt> |
| 2461 |
<dd style="margin-left: 1.5em" id="section-6.2-13.12">RFC 9116<a href="#section-6.2-13.12" class="pilcrow">¶</a> |
| 2462 |
</dd> |
| 2463 |
<dd class="break"></dd> |
| 2464 |
</dl> |
| 2465 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.2-14"> |
| 2466 |
<dt id="section-6.2-14.1">Field Name:</dt> |
| 2467 |
<dd style="margin-left: 1.5em" id="section-6.2-14.2">Policy<a href="#section-6.2-14.2" class="pilcrow">¶</a> |
| 2468 |
</dd> |
| 2469 |
<dd class="break"></dd> |
| 2470 |
<dt id="section-6.2-14.3">Description:</dt> |
| 2471 |
<dd style="margin-left: 1.5em" id="section-6.2-14.4">link to security policy page<a href="#section-6.2-14.4" class="pilcrow">¶</a> |
| 2472 |
</dd> |
| 2473 |
<dd class="break"></dd> |
| 2474 |
<dt id="section-6.2-14.5">Multiple Appearances:</dt> |
| 2475 |
<dd style="margin-left: 1.5em" id="section-6.2-14.6">yes<a href="#section-6.2-14.6" class="pilcrow">¶</a> |
| 2476 |
</dd> |
| 2477 |
<dd class="break"></dd> |
| 2478 |
<dt id="section-6.2-14.7">Status:</dt> |
| 2479 |
<dd style="margin-left: 1.5em" id="section-6.2-14.8">current<a href="#section-6.2-14.8" class="pilcrow">¶</a> |
| 2480 |
</dd> |
| 2481 |
<dd class="break"></dd> |
| 2482 |
<dt id="section-6.2-14.9">Change controller:</dt> |
| 2483 |
<dd style="margin-left: 1.5em" id="section-6.2-14.10">IETF<a href="#section-6.2-14.10" class="pilcrow">¶</a> |
| 2484 |
</dd> |
| 2485 |
<dd class="break"></dd> |
| 2486 |
<dt id="section-6.2-14.11">Reference:</dt> |
| 2487 |
<dd style="margin-left: 1.5em" id="section-6.2-14.12">RFC 9116<a href="#section-6.2-14.12" class="pilcrow">¶</a> |
| 2488 |
</dd> |
| 2489 |
<dd class="break"></dd> |
| 2490 |
</dl> |
| 2491 |
<span class="break"></span><dl class="dlCompact dlParallel" id="section-6.2-15"> |
| 2492 |
<dt id="section-6.2-15.1">Field Name:</dt> |
| 2493 |
<dd style="margin-left: 1.5em" id="section-6.2-15.2">Preferred-Languages<a href="#section-6.2-15.2" class="pilcrow">¶</a> |
| 2494 |
</dd> |
| 2495 |
<dd class="break"></dd> |
| 2496 |
<dt id="section-6.2-15.3">Description:</dt> |
| 2497 |
<dd style="margin-left: 1.5em" id="section-6.2-15.4">list of preferred languages for security reports<a href="#section-6.2-15.4" class="pilcrow">¶</a> |
| 2498 |
</dd> |
| 2499 |
<dd class="break"></dd> |
| 2500 |
<dt id="section-6.2-15.5">Multiple Appearances:</dt> |
| 2501 |
<dd style="margin-left: 1.5em" id="section-6.2-15.6">no<a href="#section-6.2-15.6" class="pilcrow">¶</a> |
| 2502 |
</dd> |
| 2503 |
<dd class="break"></dd> |
| 2504 |
<dt id="section-6.2-15.7">Status:</dt> |
| 2505 |
<dd style="margin-left: 1.5em" id="section-6.2-15.8">current<a href="#section-6.2-15.8" class="pilcrow">¶</a> |
| 2506 |
</dd> |
| 2507 |
<dd class="break"></dd> |
| 2508 |
<dt id="section-6.2-15.9">Change controller:</dt> |
| 2509 |
<dd style="margin-left: 1.5em" id="section-6.2-15.10">IETF<a href="#section-6.2-15.10" class="pilcrow">¶</a> |
| 2510 |
</dd> |
| 2511 |
<dd class="break"></dd> |
| 2512 |
<dt id="section-6.2-15.11">Reference:</dt> |
| 2513 |
<dd style="margin-left: 1.5em" id="section-6.2-15.12">RFC 9116<a href="#section-6.2-15.12" class="pilcrow">¶</a> |
| 2514 |
</dd> |
| 2515 |
<dd class="break"></dd> |
| 2516 |
</dl> |
| 2517 |
</section> |
| 2518 |
</div> |
| 2519 |
</section> |
| 2520 |
</div> |
| 2521 |
<section id="section-7"> |
| 2522 |
<h2 id="name-references"> |
| 2523 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 2524 |
</h2> |
| 2525 |
<section id="section-7.1"> |
| 2526 |
<h3 id="name-normative-references"> |
| 2527 |
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 2528 |
</h3> |
| 2529 |
<dl class="references"> |
| 2530 |
<dt id="RFC2046">[RFC2046]</dt> |
| 2531 |
<dd> |
| 2532 |
<span class="refAuthor">Freed, N.</span> and <span class="refAuthor">N. Borenstein</span>, <span class="refTitle">"Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"</span>, <span class="seriesInfo">RFC 2046</span>, <span class="seriesInfo">DOI 10.17487/RFC2046</span>, <time datetime="1996-11" class="refDate">November 1996</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2046">https://www.rfc-editor.org/info/rfc2046</a>></span>. </dd> |
| 2533 |
<dd class="break"></dd> |
| 2534 |
<dt id="RFC2119">[RFC2119]</dt> |
| 2535 |
<dd> |
| 2536 |
<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> |
| 2537 |
<dd class="break"></dd> |
| 2538 |
<dt id="RFC2142">[RFC2142]</dt> |
| 2539 |
<dd> |
| 2540 |
<span class="refAuthor">Crocker, D.</span>, <span class="refTitle">"Mailbox Names for Common Services, Roles and Functions"</span>, <span class="seriesInfo">RFC 2142</span>, <span class="seriesInfo">DOI 10.17487/RFC2142</span>, <time datetime="1997-05" class="refDate">May 1997</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2142">https://www.rfc-editor.org/info/rfc2142</a>></span>. </dd> |
| 2541 |
<dd class="break"></dd> |
| 2542 |
<dt id="RFC2277">[RFC2277]</dt> |
| 2543 |
<dd> |
| 2544 |
<span class="refAuthor">Alvestrand, H.</span>, <span class="refTitle">"IETF Policy on Character Sets and Languages"</span>, <span class="seriesInfo">BCP 18</span>, <span class="seriesInfo">RFC 2277</span>, <span class="seriesInfo">DOI 10.17487/RFC2277</span>, <time datetime="1998-01" class="refDate">January 1998</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2277">https://www.rfc-editor.org/info/rfc2277</a>></span>. </dd> |
| 2545 |
<dd class="break"></dd> |
| 2546 |
<dt id="RFC3339">[RFC3339]</dt> |
| 2547 |
<dd> |
| 2548 |
<span class="refAuthor">Klyne, G.</span> and <span class="refAuthor">C. Newman</span>, <span class="refTitle">"Date and Time on the Internet: Timestamps"</span>, <span class="seriesInfo">RFC 3339</span>, <span class="seriesInfo">DOI 10.17487/RFC3339</span>, <time datetime="2002-07" class="refDate">July 2002</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3339">https://www.rfc-editor.org/info/rfc3339</a>></span>. </dd> |
| 2549 |
<dd class="break"></dd> |
| 2550 |
<dt id="RFC3629">[RFC3629]</dt> |
| 2551 |
<dd> |
| 2552 |
<span class="refAuthor">Yergeau, F.</span>, <span class="refTitle">"UTF-8, a transformation format of ISO 10646"</span>, <span class="seriesInfo">STD 63</span>, <span class="seriesInfo">RFC 3629</span>, <span class="seriesInfo">DOI 10.17487/RFC3629</span>, <time datetime="2003-11" class="refDate">November 2003</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3629">https://www.rfc-editor.org/info/rfc3629</a>></span>. </dd> |
| 2553 |
<dd class="break"></dd> |
| 2554 |
<dt id="RFC3966">[RFC3966]</dt> |
| 2555 |
<dd> |
| 2556 |
<span class="refAuthor">Schulzrinne, H.</span>, <span class="refTitle">"The tel URI for Telephone Numbers"</span>, <span class="seriesInfo">RFC 3966</span>, <span class="seriesInfo">DOI 10.17487/RFC3966</span>, <time datetime="2004-12" class="refDate">December 2004</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3966">https://www.rfc-editor.org/info/rfc3966</a>></span>. </dd> |
| 2557 |
<dd class="break"></dd> |
| 2558 |
<dt id="RFC3986">[RFC3986]</dt> |
| 2559 |
<dd> |
| 2560 |
<span class="refAuthor">Berners-Lee, T.</span>, <span class="refAuthor">Fielding, R.</span>, and <span class="refAuthor">L. Masinter</span>, <span class="refTitle">"Uniform Resource Identifier (URI): Generic Syntax"</span>, <span class="seriesInfo">STD 66</span>, <span class="seriesInfo">RFC 3986</span>, <span class="seriesInfo">DOI 10.17487/RFC3986</span>, <time datetime="2005-01" class="refDate">January 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3986">https://www.rfc-editor.org/info/rfc3986</a>></span>. </dd> |
| 2561 |
<dd class="break"></dd> |
| 2562 |
<dt id="RFC4880">[RFC4880]</dt> |
| 2563 |
<dd> |
| 2564 |
<span class="refAuthor">Callas, J.</span>, <span class="refAuthor">Donnerhacke, L.</span>, <span class="refAuthor">Finney, H.</span>, <span class="refAuthor">Shaw, D.</span>, and <span class="refAuthor">R. Thayer</span>, <span class="refTitle">"OpenPGP Message Format"</span>, <span class="seriesInfo">RFC 4880</span>, <span class="seriesInfo">DOI 10.17487/RFC4880</span>, <time datetime="2007-11" class="refDate">November 2007</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4880">https://www.rfc-editor.org/info/rfc4880</a>></span>. </dd> |
| 2565 |
<dd class="break"></dd> |
| 2566 |
<dt id="RFC5198">[RFC5198]</dt> |
| 2567 |
<dd> |
| 2568 |
<span class="refAuthor">Klensin, J.</span> and <span class="refAuthor">M. Padlipsky</span>, <span class="refTitle">"Unicode Format for Network Interchange"</span>, <span class="seriesInfo">RFC 5198</span>, <span class="seriesInfo">DOI 10.17487/RFC5198</span>, <time datetime="2008-03" class="refDate">March 2008</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5198">https://www.rfc-editor.org/info/rfc5198</a>></span>. </dd> |
| 2569 |
<dd class="break"></dd> |
| 2570 |
<dt id="RFC5234">[RFC5234]</dt> |
| 2571 |
<dd> |
| 2572 |
<span class="refAuthor">Crocker, D., Ed.</span> and <span class="refAuthor">P. Overell</span>, <span class="refTitle">"Augmented BNF for Syntax Specifications: ABNF"</span>, <span class="seriesInfo">STD 68</span>, <span class="seriesInfo">RFC 5234</span>, <span class="seriesInfo">DOI 10.17487/RFC5234</span>, <time datetime="2008-01" class="refDate">January 2008</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5234">https://www.rfc-editor.org/info/rfc5234</a>></span>. </dd> |
| 2573 |
<dd class="break"></dd> |
| 2574 |
<dt id="RFC5322">[RFC5322]</dt> |
| 2575 |
<dd> |
| 2576 |
<span class="refAuthor">Resnick, P., Ed.</span>, <span class="refTitle">"Internet Message Format"</span>, <span class="seriesInfo">RFC 5322</span>, <span class="seriesInfo">DOI 10.17487/RFC5322</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5322">https://www.rfc-editor.org/info/rfc5322</a>></span>. </dd> |
| 2577 |
<dd class="break"></dd> |
| 2578 |
<dt id="RFC5646">[RFC5646]</dt> |
| 2579 |
<dd> |
| 2580 |
<span class="refAuthor">Phillips, A., Ed.</span> and <span class="refAuthor">M. Davis, Ed.</span>, <span class="refTitle">"Tags for Identifying Languages"</span>, <span class="seriesInfo">BCP 47</span>, <span class="seriesInfo">RFC 5646</span>, <span class="seriesInfo">DOI 10.17487/RFC5646</span>, <time datetime="2009-09" class="refDate">September 2009</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5646">https://www.rfc-editor.org/info/rfc5646</a>></span>. </dd> |
| 2581 |
<dd class="break"></dd> |
| 2582 |
<dt id="RFC6068">[RFC6068]</dt> |
| 2583 |
<dd> |
| 2584 |
<span class="refAuthor">Duerst, M.</span>, <span class="refAuthor">Masinter, L.</span>, and <span class="refAuthor">J. Zawinski</span>, <span class="refTitle">"The 'mailto' URI Scheme"</span>, <span class="seriesInfo">RFC 6068</span>, <span class="seriesInfo">DOI 10.17487/RFC6068</span>, <time datetime="2010-10" class="refDate">October 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6068">https://www.rfc-editor.org/info/rfc6068</a>></span>. </dd> |
| 2585 |
<dd class="break"></dd> |
| 2586 |
<dt id="RFC6125">[RFC6125]</dt> |
| 2587 |
<dd> |
| 2588 |
<span class="refAuthor">Saint-Andre, P.</span> and <span class="refAuthor">J. Hodges</span>, <span class="refTitle">"Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)"</span>, <span class="seriesInfo">RFC 6125</span>, <span class="seriesInfo">DOI 10.17487/RFC6125</span>, <time datetime="2011-03" class="refDate">March 2011</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6125">https://www.rfc-editor.org/info/rfc6125</a>></span>. </dd> |
| 2589 |
<dd class="break"></dd> |
| 2590 |
<dt id="RFC6960">[RFC6960]</dt> |
| 2591 |
<dd> |
| 2592 |
<span class="refAuthor">Santesson, S.</span>, <span class="refAuthor">Myers, M.</span>, <span class="refAuthor">Ankney, R.</span>, <span class="refAuthor">Malpani, A.</span>, <span class="refAuthor">Galperin, S.</span>, and <span class="refAuthor">C. Adams</span>, <span class="refTitle">"X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP"</span>, <span class="seriesInfo">RFC 6960</span>, <span class="seriesInfo">DOI 10.17487/RFC6960</span>, <time datetime="2013-06" class="refDate">June 2013</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6960">https://www.rfc-editor.org/info/rfc6960</a>></span>. </dd> |
| 2593 |
<dd class="break"></dd> |
| 2594 |
<dt id="RFC7230">[RFC7230]</dt> |
| 2595 |
<dd> |
| 2596 |
<span class="refAuthor">Fielding, R., Ed.</span> and <span class="refAuthor">J. Reschke, Ed.</span>, <span class="refTitle">"Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"</span>, <span class="seriesInfo">RFC 7230</span>, <span class="seriesInfo">DOI 10.17487/RFC7230</span>, <time datetime="2014-06" class="refDate">June 2014</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7230">https://www.rfc-editor.org/info/rfc7230</a>></span>. </dd> |
| 2597 |
<dd class="break"></dd> |
| 2598 |
<dt id="RFC7231">[RFC7231]</dt> |
| 2599 |
<dd> |
| 2600 |
<span class="refAuthor">Fielding, R., Ed.</span> and <span class="refAuthor">J. Reschke, Ed.</span>, <span class="refTitle">"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"</span>, <span class="seriesInfo">RFC 7231</span>, <span class="seriesInfo">DOI 10.17487/RFC7231</span>, <time datetime="2014-06" class="refDate">June 2014</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7231">https://www.rfc-editor.org/info/rfc7231</a>></span>. </dd> |
| 2601 |
<dd class="break"></dd> |
| 2602 |
<dt id="RFC7405">[RFC7405]</dt> |
| 2603 |
<dd> |
| 2604 |
<span class="refAuthor">Kyzivat, P.</span>, <span class="refTitle">"Case-Sensitive String Support in ABNF"</span>, <span class="seriesInfo">RFC 7405</span>, <span class="seriesInfo">DOI 10.17487/RFC7405</span>, <time datetime="2014-12" class="refDate">December 2014</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7405">https://www.rfc-editor.org/info/rfc7405</a>></span>. </dd> |
| 2605 |
<dd class="break"></dd> |
| 2606 |
<dt id="RFC8174">[RFC8174]</dt> |
| 2607 |
<dd> |
| 2608 |
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>></span>. </dd> |
| 2609 |
<dd class="break"></dd> |
| 2610 |
<dt id="RFC8615">[RFC8615]</dt> |
| 2611 |
<dd> |
| 2612 |
<span class="refAuthor">Nottingham, M.</span>, <span class="refTitle">"Well-Known Uniform Resource Identifiers (URIs)"</span>, <span class="seriesInfo">RFC 8615</span>, <span class="seriesInfo">DOI 10.17487/RFC8615</span>, <time datetime="2019-05" class="refDate">May 2019</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8615">https://www.rfc-editor.org/info/rfc8615</a>></span>. </dd> |
| 2613 |
<dd class="break"></dd> |
| 2614 |
</dl> |
| 2615 |
</section> |
| 2616 |
<section id="section-7.2"> |
| 2617 |
<h3 id="name-informative-references"> |
| 2618 |
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 2619 |
</h3> |
| 2620 |
<dl class="references"> |
| 2621 |
<dt id="CERT.CVD">[CERT.CVD]</dt> |
| 2622 |
<dd> |
| 2623 |
<span class="refAuthor">Software Engineering Institute</span>, <span class="refTitle">"The CERT Guide to Coordinated Vulnerability Disclosure"</span>, <span class="refContent">Carnegie Mellon University, CMU/SEI-2017-SR-022</span>, <time datetime="2017-08" class="refDate">August 2017</time>. </dd> |
| 2624 |
<dd class="break"></dd> |
| 2625 |
<dt id="ISO.29147.2018">[ISO.29147.2018]</dt> |
| 2626 |
<dd> |
| 2627 |
<span class="refAuthor">ISO</span>, <span class="refTitle">"Information technology - Security techniques - Vulnerability disclosure"</span>, <span class="seriesInfo">ISO/IEC 29147:2018</span>, <time datetime="2018-10" class="refDate">October 2018</time>. </dd> |
| 2628 |
<dd class="break"></dd> |
| 2629 |
<dt id="ISO.8601-1">[ISO.8601-1]</dt> |
| 2630 |
<dd> |
| 2631 |
<span class="refAuthor">ISO</span>, <span class="refTitle">"Date and time - Representations for information interchange - Part 1: Basic rules"</span>, <span class="seriesInfo">ISO 8601-1:2019</span>, <time datetime="2019-02" class="refDate">February 2019</time>. </dd> |
| 2632 |
<dd class="break"></dd> |
| 2633 |
<dt id="ISO.8601-2">[ISO.8601-2]</dt> |
| 2634 |
<dd> |
| 2635 |
<span class="refAuthor">ISO</span>, <span class="refTitle">"Date and time - Representations for information interchange - Part 2: Extensions"</span>, <span class="seriesInfo">ISO 8601-2:2019</span>, <time datetime="2019-02" class="refDate">February 2019</time>. </dd> |
| 2636 |
<dd class="break"></dd> |
| 2637 |
<dt id="RFC0793">[RFC0793]</dt> |
| 2638 |
<dd> |
| 2639 |
<span class="refAuthor">Postel, J.</span>, <span class="refTitle">"Transmission Control Protocol"</span>, <span class="seriesInfo">STD 7</span>, <span class="seriesInfo">RFC 793</span>, <span class="seriesInfo">DOI 10.17487/RFC0793</span>, <time datetime="1981-09" class="refDate">September 1981</time>, <span><<a href="https://www.rfc-editor.org/info/rfc793">https://www.rfc-editor.org/info/rfc793</a>></span>. </dd> |
| 2640 |
<dd class="break"></dd> |
| 2641 |
<dt id="RFC2196">[RFC2196]</dt> |
| 2642 |
<dd> |
| 2643 |
<span class="refAuthor">Fraser, B.</span>, <span class="refTitle">"Site Security Handbook"</span>, <span class="seriesInfo">FYI 8</span>, <span class="seriesInfo">RFC 2196</span>, <span class="seriesInfo">DOI 10.17487/RFC2196</span>, <time datetime="1997-09" class="refDate">September 1997</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2196">https://www.rfc-editor.org/info/rfc2196</a>></span>. </dd> |
| 2644 |
<dd class="break"></dd> |
| 2645 |
<dt id="RFC2350">[RFC2350]</dt> |
| 2646 |
<dd> |
| 2647 |
<span class="refAuthor">Brownlee, N.</span> and <span class="refAuthor">E. Guttman</span>, <span class="refTitle">"Expectations for Computer Security Incident Response"</span>, <span class="seriesInfo">BCP 21</span>, <span class="seriesInfo">RFC 2350</span>, <span class="seriesInfo">DOI 10.17487/RFC2350</span>, <time datetime="1998-06" class="refDate">June 1998</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2350">https://www.rfc-editor.org/info/rfc2350</a>></span>. </dd> |
| 2648 |
<dd class="break"></dd> |
| 2649 |
<dt id="RFC3013">[RFC3013]</dt> |
| 2650 |
<dd> |
| 2651 |
<span class="refAuthor">Killalea, T.</span>, <span class="refTitle">"Recommended Internet Service Provider Security Services and Procedures"</span>, <span class="seriesInfo">BCP 46</span>, <span class="seriesInfo">RFC 3013</span>, <span class="seriesInfo">DOI 10.17487/RFC3013</span>, <time datetime="2000-11" class="refDate">November 2000</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3013">https://www.rfc-editor.org/info/rfc3013</a>></span>. </dd> |
| 2652 |
<dd class="break"></dd> |
| 2653 |
<dt id="RFC7485">[RFC7485]</dt> |
| 2654 |
<dd> |
| 2655 |
<span class="refAuthor">Zhou, L.</span>, <span class="refAuthor">Kong, N.</span>, <span class="refAuthor">Shen, S.</span>, <span class="refAuthor">Sheng, S.</span>, and <span class="refAuthor">A. Servin</span>, <span class="refTitle">"Inventory and Analysis of WHOIS Registration Objects"</span>, <span class="seriesInfo">RFC 7485</span>, <span class="seriesInfo">DOI 10.17487/RFC7485</span>, <time datetime="2015-03" class="refDate">March 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7485">https://www.rfc-editor.org/info/rfc7485</a>></span>. </dd> |
| 2656 |
<dd class="break"></dd> |
| 2657 |
<dt id="RFC8126">[RFC8126]</dt> |
| 2658 |
<dd> |
| 2659 |
<span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Leiba, B.</span>, and <span class="refAuthor">T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>></span>. </dd> |
| 2660 |
<dd class="break"></dd> |
| 2661 |
</dl> |
| 2662 |
</section> |
| 2663 |
</section> |
| 2664 |
<div id="contributors"> |
| 2665 |
<section id="appendix-A"> |
| 2666 |
<h2 id="name-acknowledgments-2"> |
| 2667 |
<a href="#name-acknowledgments-2" class="section-name selfRef">Acknowledgments</a> |
| 2668 |
</h2> |
| 2669 |
<p id="appendix-A-1">The authors would like to acknowledge the help provided during the |
| 2670 |
development of this document by <span class="contact-name">Tom Hudson</span>, <span class="contact-name">Jobert Abma</span>, |
| 2671 |
<span class="contact-name">Gerben Janssen van Doorn</span>, <span class="contact-name">Austin Heap</span>, <span class="contact-name">Stephane Bortzmeyer</span>, <span class="contact-name">Max Smith</span>, <span class="contact-name">Eduardo Vela</span>, and <span class="contact-name">Krzysztof Kotowicz</span>.<a href="#appendix-A-1" class="pilcrow">¶</a></p> |
| 2672 |
<p id="appendix-A-2">The authors would also like to acknowledge the feedback provided by multiple members of the IETF's |
| 2673 |
LAST CALL, SAAG, and SECDISPATCH lists.<a href="#appendix-A-2" class="pilcrow">¶</a></p> |
| 2674 |
<p id="appendix-A-3"><span class="contact-name">Yakov Shafranovich</span> would like to also thank L.T.S. (for everything).<a href="#appendix-A-3" class="pilcrow">¶</a></p> |
| 2675 |
</section> |
| 2676 |
</div> |
| 2677 |
<div id="authors-addresses"> |
| 2678 |
<section id="appendix-B"> |
| 2679 |
<h2 id="name-authors-addresses"> |
| 2680 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 2681 |
</h2> |
| 2682 |
<address class="vcard"> |
| 2683 |
<div dir="auto" class="left"><span class="fn nameRole">Edwin Foudil</span></div> |
| 2684 |
<div class="email"> |
| 2685 |
<span>Email:</span> |
| 2686 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2687 |
</div> |
| 2688 |
</address> |
| 2689 |
<address class="vcard"> |
| 2690 |
<div dir="auto" class="left"><span class="fn nameRole">Yakov Shafranovich</span></div> |
| 2691 |
<div dir="auto" class="left"><span class="org">Nightwatch Cybersecurity</span></div> |
| 2692 |
<div class="email"> |
| 2693 |
<span>Email:</span> |
| 2694 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2695 |
</div> |
| 2696 |
</address> |
| 2697 |
</section> |
| 2698 |
</div> |
| 2699 |
<script>const toc = document.getElementById("toc"); |
| 2700 |
toc.querySelector("h2").addEventListener("click", e => { |
| 2701 |
toc.classList.toggle("active"); |
| 2702 |
}); |
| 2703 |
toc.querySelector("nav").addEventListener("click", e => { |
| 2704 |
toc.classList.remove("active"); |
| 2705 |
}); |
| 2706 |
</script> |
| 2707 |
</body> |
| 2708 |
</html> |