REVIEW-14: SDIACT-237 Provide OSG a dedicated CILogon CA instance via REST web interface - Design/Security Review

General design and security risk review for the OSG CILogon CA instance

• MOU was missing John Towns' signature.
  • MOU signed and updated.
• Question about where/when the SSL Client Certificate (Section F.1.1) is generated/sent.
  • Clarifying text added to Section F.1.1.
• Can XSEDE obtain xsede.org host certificates from OSG?
  • Yes, in the event that the InCommon Cert Service is unavailable. https://www.xsede.org/security/certificates/ is still the preferred method of getting host certificates for XSEDE.
• Should the CP/CPS reference XSEDE in addition to OSG?
  • Since OSG manages the CA front-end and controls the subject namespace, and certificate requesters must be registered with OSG, it is clearer for the policy documents to specify OSG only. XSEDE members need to register with OSG to use this CA.
• Will this activity be delivering new CA certificates?
  • No, the CILogon OSG CA certificate is already in the XSEDE CA distribution.
• CILogonOSGCPCPS.pdf contains broken links.
  • Please use CILogonOSGCPCPS.docx instead.
• Formatting updates to CILogon-OSG-CA-Design.pdf.

• https://software.xsede.org/svn/sdi/activities/sdiact-237/trunk/Plans/XSEDE_OSG_MOU_CILOGON.pdf (updated with John Towns signature)
• https://software.xsede.org/svn/sdi/activities/sdiact-237/trunk/Plans/CILogon-OSG-CA-Design.pdf (Paragraph added to start of Section F.1.1 and formatting fixes).
• https://software.xsede.org/svn/sdi/activities/sdiact-237/trunk/Plans/CILogonOSGCPCPS.docx (Word version with working hyperlinks.)

https://software.xsede.org/svn/sdi/activities/sdiact-237/trunk/Plans/XSEDE_OSG_MOU_CILOGON.pdf
https://software.xsede.org/svn/sdi/activities/sdiact-237/trunk/Plans/CILogon-OSG-CA-Design.pdf
https://software.xsede.org/svn/sdi/activities/sdiact-237/trunk/Plans/CILogonOSGCPCPS.pdf

Please focus on these questions:

1. Does the proposed design satisfy the functional user requirements?
2. Does the design satisfy the requirements from the XSEDE-OSG MOU (see Review Materials)
3. Are the protocols and interfaces selected appropriate and secure?
4. Are the services operated in a secure way and are the procedures appropriate to deal with planned and unplanned outages and unplanned incidents?

and the following solution supported scenarios:

1. Issue user/host/service certificate
2. Revoke user/host/service certificate
3. Publish certificate revocation list (CRL)