diff --git a/docs/index.html b/docs/index.html index 6f360c0..808fbe9 100644 --- a/docs/index.html +++ b/docs/index.html @@ -445,8 +445,8 @@

Inte

Prepared by: Nicholas Roy, Director of Technology and Strategy, InCommon/Internet2 Trust and Identity Services
-Version: 1.5
-Date: September 26, 2019

+Version: 1.6
+Date: February 17, 2020

Document Title: Internet2 Trust and Identity Services Security Incident Handling Framework
@@ -457,11 +457,11 @@

Inte Publication Date: UPDATE
Sponsor: Vice President, Internet2 Trust and Identity Services
Superseded documents: None
-Proposed future review date: September 5, 2021
+Proposed future review date: February 17, 2022
Subject tags: security, incident, trust, identity, incommon, services

-

© 2019 Internet2
+

© 2020 Internet2
This work is licensed under a Creative Commons Attribution 4.0 International License.

@@ -554,6 +554,13 @@

Change Log

1.5

Nicholas Roy

+ +

Draft

+

Added information about PGP key usage

+

February 17, 2020

+

1.6

+

Nicholas Roy

+
@@ -639,7 +646,7 @@

Initial Contact/Notification an

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.

-

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/. 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.

@@ -1052,7 +1059,7 @@

Appendix B: Acknowledgements

diff --git a/main.adoc b/main.adoc index 93b99fa..2769cd0 100644 --- a/main.adoc +++ b/main.adoc @@ -3,8 +3,8 @@ == Internet2 Trust and Identity Services Incident Handling Framework *Prepared by:* Nicholas Roy, Director of Technology and Strategy, InCommon/Internet2 Trust and Identity Services + -*Version:* 1.5 + -*Date:* September 26, 2019 +*Version:* 1.6 + +*Date:* February 17, 2020 @@ -16,10 +16,10 @@ *Publication Date: UPDATE* + *Sponsor: Vice President, Internet2 Trust and Identity Services* + *Superseded documents: None* + -*Proposed future review date: September 5, 2021* + +*Proposed future review date: February 17, 2022* + *Subject tags: security, incident, trust, identity, incommon, services* -*© 2019 Internet2* + +*© 2020 Internet2* + *This work is licensed under a https://creativecommons.org/licenses/by/4.0/[Creative Commons Attribution 4.0 International License.]* === Change Log @@ -36,7 +36,8 @@ |Publication|Revisions to fix typos and add document repository information|February 27, 2018|1.2|Nicholas Roy |Draft|Support other InCommon services|July 15, 2019|1.3|Nicholas Roy |Draft|Changed from InCommon to Internet2 Trust and Identity Services|September 5, 2019|1.4|Nicholas Roy -|Draft|Added language about who can declare an incident|September 26, 2019|1.5|Nicholas Roy| +|Draft|Added language about who can declare an incident|September 26, 2019|1.5|Nicholas Roy +|Draft|Added information about PGP key usage|February 17, 2020|1.6|Nicholas Roy| |=== <<< @@ -89,7 +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._* -*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. diff --git a/pdf/inc-security-incident-handling-framework.pdf b/pdf/inc-security-incident-handling-framework.pdf index 0ba02f0..99f071e 100644 Binary files a/pdf/inc-security-incident-handling-framework.pdf and b/pdf/inc-security-incident-handling-framework.pdf differ