Software Risk Management Standard
Purpose听
This听standard听establishes听a consistent,听risk鈥�based听process for evaluating, approving, and managing software that may introduce significant operational, security, privacy, compliance, or reputational risks to 福利亚洲国产精品. It supports the university鈥檚 goals of protecting institutional data, ensuring responsible technology adoption, and enabling academic and administrative innovation.听
Scope听
This Standard applies to all:听
- University鈥�owned, leased, or managed devices听
- Cloud鈥�based听and听on鈥�premises听software solutions听
- Academic, administrative, research, and auxiliary units听
- Faculty, staff, contractors, student employees, and affiliates who听procure听or deploy software on behalf of 福利亚洲国产精品听
It covers:听
- New software acquisition听
- Renewal of existing software听
- Third鈥�party听integrations听
- Free or freemium tools used with institutional data听
- Software that is currently blocked by the university due to industry听identified听risks听
Definitions听
Software With Significant Risk
Software is considered听high鈥�risk听if it meets any of the following criteria:听
- Handles听sensitive or听regulated听data (e.g., FERPA, HIPAA, GLBA, research data, personal information).听
- Integrates with enterprise systems or Single Sign-On (SSO).听
- Transfers university data to external parties.听
- Has access to large volumes of institutional or personal data.听
- Impacts听critical university operations (academic, financial, safety, or research systems).听
- Is听AI听or machine learning听technologies听that process institutional听data.听
Exception
A documented, approved deviation from this听standard听will be听granted when compensating controls or business justification sufficiently听reduce听risk.听
听
Software Risk Management Standards听
- All software posing potential risk must undergo an assessment before听purchase, renewal, or deployment. Assessments are managed by听Information Security, with coordination from听IT Operations,听Procurement, and听Business Owners.听
- Depending on the听use case, the following may be听required:听
- Formal听Security Risk Assessment (SRA);听Information Security reviews application security, data flows, authentication/authorization, encryption, incident response, vendor security posture, vulnerabilities, and system architecture.听
- Privacy/Data Protection Review:听Compliance Managers听validates听compliance with FERPA, GDPR,听PCI,听state privacy laws, contractual terms, data retention, and consent requirements.听
- Accessibility Review:听Compliance ensures compliance with WCAG 2.1 AA and institutional accessibility policies.听
- IT Operations Review:听Information Technology will听determine听operational maintainability, including:听
- Hosting/environment suitability听
- Authentication Requirements听
- Data Location Requirements听
- Logging & Monitoring Requirements听
- Integration Standard听
- APIs must use secure protocols and validated schemas听
- Change Management Coordination听
- Disaster Recovery Expectations / Backup/restore expectations听
- System performance or bandwidth requirements听
- Patch management and update expectations听
- Supportability by existing IT teams听
- Risk decisions should align with听Elon鈥檚 security and compliance听frameworks to ensure consistency and rigor.听
- The university reserves the right to rescind approval if new risks听emerge听(e.g., vendor breach, audit findings, or change in functionality).听
- Approved software may require听annual or biennial reassessments, security review upon major feature changes, incident reporting obligations for vendors, patch/vulnerability management听review,听or review of听third鈥�party听attestations (SOC 2, ISO, penetration tests)听based on the data being used,听transmitted,听or processed within the application.听听
- When a business need justifies use of听higher鈥�risk听software, the business owner must听document听their听Exception Request.听听Information听in the request should听include听a听business听justification, risk acceptance rationale, data听involved听and the compensating听controls听necessary to mitigate the risk. The controls may include restricted data use, limited user access, network segmentation, enhanced monitoring/logging,听or vendor security audit听requirements.听
- 听All听application requests, risk reviews, exception requests and use decisions will be logged听in听Elon鈥檚 electronic ticketing system.听听
Noncompliance with this听standard may result in听denial of procurement, disabling integrations or SSO, removal听or blocking of听software from institutional networks听and/or escalation to听leadership.听