Skip to content

Commit

Permalink
Fixed language per Shannon
Browse files Browse the repository at this point in the history
  • Loading branch information
nckroy committed Feb 17, 2020
1 parent 84b6b59 commit 26212a8
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 9 deletions.
9 changes: 3 additions & 6 deletions docs/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -555,11 +555,11 @@ <h3 id="_change_log">Change Log</h3>
<td class="tableblock halign-left valign-top"><p class="tableblock">Nicholas Roy</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Draft</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Added information about PGP key usage</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">February 17, 2020</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">1.6</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Nicholas Roy</p></td>
</tr>
</tbody>
</table>
Expand Down Expand Up @@ -646,10 +646,7 @@ <h3 id="_initial_contactnotification_and_triage">Initial Contact/Notification an
<p><strong><em>Inquiries from any law enforcement agency regarding a security incident, including formal legal process such as subpoenas and warrants, must be directed to the General Counsel of Internet2.</em></strong></p>
</div>
<div class="paragraph">
<p><strong>IF YOU HAVE A PGP KEY</strong> You can use InCommon&#8217;s PGP public key to encrypt sensitive information you send to us via email. Information on this key is available at: <a href="https://incommon.org/incident-reponse/">https://incommon.org/incident-reponse/</a></p>
</div>
<div class="paragraph">
<p><strong>IF YOU DO NOT HAVE A PGP KEY, DO NOT</strong> communicate any sensitive information via these channels. Internet2 staff will set up a secure communications channel with you, if need be, after your initial request is received</p>
<p>You can use InCommon&#8217;s PGP public key to encrypt sensitive information you send to us via email. Information on this key is available at: <a href="https://incommon.org/incident-reponse/">https://incommon.org/incident-reponse/</a>. <strong>DO NOT</strong> send sensitive information in unecrypted email.</p>
</div>
<div class="paragraph">
<p>The CSIRT will accept, evaluate and reply (when necessary and deemed appropriate) to valid submissions as soon as possible, but in no event later than 24 hours after receipt of the notice.</p>
Expand Down Expand Up @@ -1062,7 +1059,7 @@ <h3 id="_appendix_b_acknowledgements">Appendix B: Acknowledgements</h3>
</div>
<div id="footer">
<div id="footer-text">
Last updated 2020-02-17 13:51:21 -0700
Last updated 2020-02-17 14:29:12 -0700
</div>
</div>
</body>
Expand Down
4 changes: 1 addition & 3 deletions main.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -90,9 +90,7 @@ Any party may make the CSIRT aware of a relevant security incident or disclosure

*_Inquiries from any law enforcement agency regarding a security incident, including formal legal process such as subpoenas and warrants, must be directed to the General Counsel of Internet2._*

*IF YOU HAVE A PGP KEY* You can use InCommon's PGP public key to encrypt sensitive information you send to us via email. Information on this key is available at: https://incommon.org/incident-reponse/[https://incommon.org/incident-reponse/]

*IF YOU DO NOT HAVE A PGP KEY, DO NOT* communicate any sensitive information via these channels. Internet2 staff will set up a secure communications channel with you, if need be, after your initial request is received
You can use InCommon's PGP public key to encrypt sensitive information you send to us via email. Information on this key is available at: https://incommon.org/incident-reponse/[https://incommon.org/incident-reponse/]. *DO NOT* send sensitive information in unecrypted email.

The CSIRT will accept, evaluate and reply (when necessary and deemed appropriate) to valid submissions as soon as possible, but in no event later than 24 hours after receipt of the notice.

Expand Down
Binary file modified pdf/inc-security-incident-handling-framework.pdf
Binary file not shown.

0 comments on commit 26212a8

Please sign in to comment.