REVIEW-72: XCI-231 Formalize the Community Software Area (CSA) Capability - Design/Security Review

Overview

General design and security risk review for the capability for SPs to offer Community Software Areas (CSAs) that allocated projects can request and use to maintain software they share with other XSEDE users.

Review Summary

Significant review comments that were addressed:

  1. Added to "E.2.13 Usage Tracking" a recommendation that SPs contact CSA owners at least annually to confirm that CSAs are active
  2. Added to  "E.1. Assumptions and Dependencies" that when a CSA related allocation expiries SPs may choose to delete CSAs after notifying the owner
  3. Noted that CSA owners can publish documentation URLs thru their software modules
  4. Improved how section "D. Behavior Design" is organized to match section E
  5. Clarified CSA performance expectation in "E.2.10. Performance requirements"
  6. Clarified how SP and CSA software will be distinguished in "F.1. Component Level Design"
  7. Described IPF changes that enable distinguishing between SP and CSA software in "G.1. Interfaces with other systems"
  8. Improved terminology by using the terms SPs, installation owners, and installation users, resources, CSAs, installation spaces, and installations

Review Output Documents (Final)

CSA_Design_and_Security_Description_v0.4.pdf (revised)

CSA_Design_and_Security_Description_v0.3.pdf (revised)

CSA_Design_and_Security_Description_v0.2.pdf (revised)

CSA_Design_and_Security_Description_v0.1.pdf (review input)

Review Input Documents

CSA_Design_and_Security_Description_v0.4.pdf (revised)

CSA_Design_and_Security_Description_v0.3.pdf (revised)

CSA_Design_and_Security_Description_v0.2.pdf (revised)

CSA_Design_and_Security_Description_v0.1.pdf (review input)

Review Criteria

Please focus on these questions:

  • Does the proposed design address SP needs
  • Does the proposed design enable uses to use the CSA capability
  • Does the proposed design address relevant security risks and concerns
  • Could the proposed design be improved

Schedule

Current Date: 2019-12-15
Current Status: Closed (Design and Security Review)
Target Date Actual Date Activity Milestone
  2019-05-23 Review launch date
2019-06-14 Written feedback due (Reviewers)
2019-06-18 2019-07-25 Written response date (Review Material Developers)
2019-07-12 2019-07-25 Final approval due and completion date (Reviewers)
Review Created: 2019-05-23 9:02 am
Review Last Updated: 2019-07-25 1:16 pm

 

Reviewers

If you are a reviewer, please login to sign or withdraw from this review.

Required

  • Rob Light
    VIEWED: 2019-06-06 16:54
    SIGNED: 2019-06-06 16:54
  • Shava Smallen
    VIEWED: 2019-07-25 13:27

Optional

  • David Carver
  • John Cazes
  • Trevor Cooper
    VIEWED: 2019-06-14 12:37
  • Maytal Dahan
  • David Hart
  • Victor Hazlewood
  • Brian Hom
    VIEWED: 2019-07-12 19:29
    SIGNED: 2019-07-12 19:29
  • Lee Liming
  • Jim Marsteller
  • Jeaime Powell
  • Sergiu Sanielevici
    VIEWED: 2019-05-28 14:19
    SIGNED: 2019-05-28 14:19
  • Derek Simmel
  • Robert Sinkovits
  • Jason Sommerfield
  • Ester Soriano
    VIEWED: 2019-06-07 13:12
  • Mahidhar Tatineni
    VIEWED: 2019-06-14 15:26
    SIGNED: 2019-06-14 15:26
  • Alexander Withers
    VIEWED: 2019-07-11 16:45

Review Material Developers

John-Paul Navarro

Review Facilitator

Shava Smallen

 

Please post your comments using the "New topic" or "Post reply" buttons in the forum below.