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

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.

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

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)

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)

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