{"id":69499,"date":"2026-02-02T14:44:08","date_gmt":"2026-02-02T22:44:08","guid":{"rendered":"https:\/\/policies.wsu.edu\/prf\/?page_id=69499"},"modified":"2026-08-25T12:53:09","modified_gmt":"2026-08-25T19:53:09","slug":"bppm-87-65","status":"publish","type":"page","link":"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-65\/","title":{"rendered":"87.65 Software Development"},"content":{"rendered":"\n<h1 class=\"wp-block-heading wsu-font-size--xxmedium\">University Policies and Procedures Manual<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Software Development<\/strong><\/h2>\n\n\n<div class=\"wsu-row wsu-row--single\" >\r\n    \n<div class=\"wsu-column\"  style=\"\">\r\n\t\n\n<p><strong>UPPM 87.65<\/strong><\/p>\n<p><strong>For more information contact:<\/strong><br>&nbsp; &nbsp;<a href=\"https:\/\/its.wsu.edu\/how-can-we-help-contact-its\/\">Information Technology Services<\/a><\/p>\n<hr>\n<div id=\"toc_container\">\n<h3>Contents<\/h3>\n<ul class=\"toc_list\">\n<li><a href=\"#One_0\">1.0 &nbsp;&nbsp; Overview and Purpose<\/a>\n<ul class=\"toc_list\">\n<li><a href=\"#One_1\">1.1 &nbsp;&nbsp; Information Assurance Policies Generally<\/a><\/li>\n<li><a href=\"#One_2\">1.2 &nbsp;&nbsp; Specific Policy Overview and Purpose<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#Two_0\">2.0 &nbsp;&nbsp; Applicability<\/a><\/li>\n<li><a href=\"#Three_0\">3.0 &nbsp;&nbsp; Roles and Responsibilities<\/a>\n<ul class=\"toc_list\">\n<li><a href=\"#Three_1\">3.1 &nbsp;&nbsp; Chief Information Officer<\/a><\/li>\n<li><a href=\"#Three_2\">3.2 &nbsp;&nbsp; Information Owners<\/a><\/li>\n<li><a href=\"#Three_3\">3.3 &nbsp;&nbsp; Office of Information Security and Assurance (OISA)<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#Four_0\">4.0 &nbsp;&nbsp; Requirements<\/a>\n<ul class=\"toc_list\">\n<li><a href=\"#Four_1\">4.1 &nbsp;&nbsp; General Requirements <\/a><\/li>\n<li><a href=\"#Four_2\">4.2 &nbsp;&nbsp; Moderate- and High-Impact System Requirements<\/a><\/li>\n<li><a href=\"#Four_3\">4.3 &nbsp;&nbsp; High-Impact System Requirements <\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#Five_0\">5.0 &nbsp;&nbsp; Training<\/a><\/li>\n<\/ul>\n<\/div>\n<h3 id=\"One_0\">1.0&nbsp;&nbsp;&nbsp;&nbsp; Overview and Purpose<\/h3>\n<h4 id=\"One_1\">1.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Information Assurance Policies Generally<\/h4>\n<p>The purposes of the information assurance policies in UPPM Chapter 87: Information Technology and Security are to:<\/p>\n<ul>\n<li>Set requirements to ensure the privacy, confidentiality, integrity, and availability of Washington State University (WSU) data;<\/li>\n<li>Support institutional goals and strategies with appropriate methods for administratively, technically, and operationally protecting data; and<\/li>\n<li>Define the criteria WSU follows to meet requirements for protecting data, which are determined by Information Owners<\/li>\n<\/ul>\n<p>The policies in this chapter comply with Federal Information Processing Standards (<a href=\"https:\/\/nvlpubs.nist.gov\/nistpubs\/fips\/nist.fips.199.pdf\">FIPS 199<\/a>), which are intended to help organizations achieve a common level of quality and interoperability in information technology (IT) by requiring categorization of systems as low-impact, moderate-impact, or high-impact for the stated security objectives of confidentiality, integrity, and availability. To determine the potential consequence of a loss event, the Federal Information Processing Standards:<\/p>\n<ul>\n<li>Define WSU Information Owners\u2019 impact categorization rating (Low, Moderate, or High);<\/li>\n<li>Dictate which security controls are mandatory based upon the categorization level;<\/li>\n<li>Define the strength, frequency, and formalization of those controls; and<\/li>\n<li>Influence audit burden and continuous monitoring rigor.<\/li>\n<\/ul>\n<p>See <a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-01\/\">UPPM 87.01<\/a> for definitions, general information, and violations related to this policy, as well as additional information regarding roles and responsibilities.<\/p>\n<h4 id=\"One_2\">1.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Specific Policy Overview and Purpose<\/h4>\n<p>All WSU software applications must be procured, designed, developed, used, and maintained in a manner that protects institutional data, systems, and user privacy. This policy establishes requirements to ensure that information security and user privacy considerations are integrated within the entire software development lifecycle.<\/p>\n<h3 id=\"Two_0\">2.0&nbsp;&nbsp;&nbsp; Applicability<\/h3>\n<p>This policy applies to all individuals, organizations, businesses, and groups, internal and external to WSU, that develop, maintain, and\/or monitor software applications used for WSU business. This policy also applies to procurement of all WSU software applications.<\/p>\n<p>This policy also applies to all WSU system users who have contact with, or potentially may have contact with, WSU data, applications, and computing resources.<\/p>\n<p>Security control exceptions to policy statements in UPPM Chapter 87 are managed and maintained in accordance with <a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-23\/\">UPPM 87.23<\/a>.<\/p>\n<h3 id=\"Three_0\">3.0&nbsp;&nbsp;&nbsp; Roles and Responsibilities<\/h3>\n<h4 id=\"Three_1\">3.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Chief Information Officer<\/h4>\n<p>The Chief Information Officer (CIO) of WSU, or designee, is responsible for administering this policy and reviewing it on an annual basis.<\/p>\n<h4 id=\"Three_2\">3.2&nbsp;&nbsp;&nbsp;&nbsp; Information System Owners<\/h4>\n<p>WSU Information System Owners, or their delegates, are responsible and accountable for developing appropriate Standard Operating Procedures (SOPs) for this policy&#8217;s implementation.&nbsp;<\/p>\n<h4 id=\"Three_3\">3.3&nbsp;&nbsp;&nbsp;&nbsp; Office of Information Security and Assurance (OISA)<\/h4>\n<p>WSU\u2019s Office of Information Security and Assurance (OISA) shall maintain the <a href=\"https:\/\/its.wsu.edu\/documents\/2026\/01\/software-development-standard.pdf\">standard (PDF)<\/a> associated with this policy and provide guidance for the associated procedures for the implementation of this policy (<a href=\"https:\/\/its.wsu.edu\/documents\/2026\/01\/software-development-procedure.pdf\"><u>see examples<\/u> (PDF)<\/a>).<\/p>\n<p><strong>Note:<\/strong> While all units are required to adhere to the standard established by OISA (<a href=\"https:\/\/csrc.nist.gov\/pubs\/sp\/800\/53\/r5\/upd1\/final\">NIST SP 800-53<\/a>), procedural examples for implementation are optional.<\/p>\n<h3 id=\"Four_0\">4.0&nbsp;&nbsp; Requirements<\/h3>\n<h4 id=\"Four_1\">4.1&nbsp;&nbsp;&nbsp;&nbsp; General Requirements<\/h4>\n<p>Information&nbsp;System&nbsp;Owners, or their delegates,&nbsp;must&nbsp;maintain&nbsp;a Software Development Life Cycle (SDLC) for&nbsp;WSU&nbsp;developed applications.&nbsp;&nbsp;<\/p>\n<p>During mission and business process planning, WSU&nbsp;Information&nbsp;Owners, or&nbsp;their&nbsp;delegates,&nbsp;must&nbsp;determine&nbsp;the&nbsp;high-level&nbsp;information&nbsp;security and privacy requirements for software applications.&nbsp;&nbsp;<\/p>\n<ul>\n<li>The resources&nbsp;required&nbsp;to protect the application&nbsp;are to&nbsp;be included as part of the capital planning and investment control process.&nbsp;<\/li>\n<li>A&nbsp;separate&nbsp;line&nbsp;item for&nbsp;information&nbsp;security and privacy&nbsp;is to&nbsp;be included in programming and budgeting documentation.&nbsp;&nbsp;<\/li>\n<\/ul>\n<p>Information&nbsp;System Owners, or&nbsp;their&nbsp;delegates,&nbsp;must&nbsp;approve the use of all software applications&nbsp;in their Area of responsibility&nbsp;in accordance with&nbsp;<a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-32\/\">UPPM 87.32<\/a>.<\/p>\n<p>WSU&nbsp;must&nbsp;acquire, develop, and manage software applications by employing a&nbsp;software&nbsp;development life cycle that integrates considerations for&nbsp;information&nbsp;security and privacy.&nbsp;<\/p>\n<ul>\n<li>Information&nbsp;security and privacy roles and responsibilities&nbsp;are to&nbsp;be defined and documented throughout the SDLC.&nbsp;<\/li>\n<\/ul>\n<ul>\n<li>Individuals having&nbsp;information&nbsp;security and privacy responsibilities&nbsp;are to&nbsp;be&nbsp;identified.&nbsp;<\/li>\n<li>SDLC activities&nbsp;are to&nbsp;be integrated into the WSU&nbsp;information&nbsp;security and privacy risk management process.&nbsp;&nbsp;<\/li>\n<\/ul>\n<p>Only applications currently supported by their developers&nbsp;are to&nbsp;be utilized in accordance with&nbsp;<a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-32\/\">UPPM 87.32<\/a>.&nbsp;<\/p>\n<p>Internal developers that provide application development services for the university&nbsp;must&nbsp;include security and privacy requirements, descriptions, and criteria, explicitly or by reference with interconnection agreements.<\/p>\n<p>Administrator documentation&nbsp;is to&nbsp;be obtained or developed for WSU applications. The documentation&nbsp;must&nbsp;describe:&nbsp;&nbsp;&nbsp;<\/p>\n<ul>\n<li>Secure configuration, installation, and operation of the application;&nbsp;<\/li>\n<\/ul>\n<ul>\n<li>Effective use and maintenance of security and privacy functions and mechanisms; and&nbsp;<\/li>\n<li>Known vulnerabilities&nbsp;regarding&nbsp;configuration and use of administrative or privileged functions.&nbsp;<\/li>\n<\/ul>\n<p>User documentation&nbsp;is to&nbsp;be obtained or developed for&nbsp;WSU&nbsp;applications. The documentation&nbsp;must&nbsp;describe:&nbsp;&nbsp;&nbsp;<\/p>\n<ul>\n<li>User-accessible security and privacy functions and mechanisms and how to effectively use them;&nbsp;<\/li>\n<\/ul>\n<ul>\n<li>Methods for user interaction, which&nbsp;enable&nbsp;individuals to use the application in a secure manner; and&nbsp;<\/li>\n<li>User responsibilities in&nbsp;maintaining&nbsp;security.&nbsp;<\/li>\n<\/ul>\n<p>Systems security and privacy engineering principles&nbsp;are to&nbsp;be applied during design, development, implementation, and modification of the system.&nbsp;<\/p>\n<p>A flaw remediation process&nbsp;is to&nbsp;be implemented to correct identified flaws&nbsp;in accordance with&nbsp;<a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-40\/\">UPPM 87.40<\/a>.&nbsp;<\/p>\n<p>When an&nbsp;Information&nbsp;System Owner, or&nbsp;their&nbsp;delegate,&nbsp;determines&nbsp;that the need for a business application is no longer necessary then the application and all associated systems&nbsp;are to&nbsp;be decommissioned&nbsp;in accordance with&nbsp;<a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-72\/\">UPPM 87.72<\/a>.&nbsp;<\/p>\n<h4 id=\"Four_2\">4.2&nbsp;&nbsp;&nbsp;&nbsp; Moderate- and High-Impact Systems<\/h4>\n<p>In addition to the above, the following requirements apply to moderate- and high-impact systems.<\/p>\n<p>For moderate- and high-impact applications,&nbsp;WSU&nbsp;application developers&nbsp;must&nbsp;provide a description of the functional properties of security and privacy controls to be implemented.&nbsp;<\/p>\n<p>For moderate- and high-impact applications,&nbsp;WSU&nbsp;application developers&nbsp;must&nbsp;provide design and implementation&nbsp;information&nbsp;for the&nbsp;security and privacy&nbsp;controls&nbsp;of the system.&nbsp;<\/p>\n<p>For moderate- and high-impact applications,&nbsp;WSU&nbsp;application developers&nbsp;must&nbsp;identify&nbsp;the functions, ports, protocols, and services early in the&nbsp;software&nbsp;development life cycle.&nbsp;<\/p>\n<p>Moderate- and high-impact applications&nbsp;are to&nbsp;be maintained in accordance with&nbsp;<a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-30\/\">UPPM 87.30<\/a>.&nbsp;<\/p>\n<p>Moderate- and high-impact application developers&nbsp;must&nbsp;develop and implement a plan for ongoing security and privacy assessments.&nbsp;<\/p>\n<p>The assessment results&nbsp;must&nbsp;include evidence of execution.&nbsp;<\/p>\n<p>Moderate- and high-impact application developers&nbsp;must&nbsp;follow a documented development process that&nbsp;identifies&nbsp;the standards and tools used in the development process.&nbsp;&nbsp;<\/p>\n<ul>\n<li>Changes to development tools are to be maintained in accordance with&nbsp;<a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-30\/\">UPPM 87.30<\/a>.&nbsp;<\/li>\n<li>The development process, standards, tools, tool options, and tool configurations&nbsp;are to&nbsp;be reviewed regularly to&nbsp;determine&nbsp;if tool configurations selected and employed&nbsp;still&nbsp;satisfy security and privacy requirements.&nbsp;<\/li>\n<\/ul>\n<p>Developers for moderate- and high- impact applications&nbsp;are to&nbsp;perform a criticality&nbsp;analysis at key decision points in the SDLC. The breadth and depth of criticality analysis&nbsp;is to&nbsp;be defined and&nbsp;maintained&nbsp;with the application documentation.&nbsp;<\/p>\n<h4 id=\"Four_3\">4.3&nbsp;&nbsp;&nbsp;&nbsp; High-Impact Systems<\/h4>\n<p>In addition to the above, the following requirements apply to high-impact systems.<\/p>\n<p>High-impact application developers&nbsp;must&nbsp;deliver the application with the security configuration implemented. The configuration&nbsp;is to&nbsp;be used as the default for any&nbsp;subsequent&nbsp;reinstallation or upgrade.&nbsp;&nbsp;<\/p>\n<h3 id=\"Five_0\">5.0&nbsp;&nbsp;&nbsp; Training<\/h3>\n<p>See <a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-21\/\">UPPM 87.21<\/a> for training requirements related to UPPM Chapter 87.<\/p>\n<p>In addition to the requirements in <a href=\"https:\/\/policies.wsu.edu\/prf\/index\/manuals\/business-policies-and-procedures-manual\/bppm-87-21\/\">UPPM 87.21<\/a>, Information System Owners are responsible for ensuring that users receive appropriate information security and privacy training commensurate with their roles, responsibilities, and authorized access to information systems under the Information System Owner\u2019s authority.<\/p>\n<p style=\"font-size: .8rem\">_______________________<br><strong>Revisions:<\/strong> Feb. 2026 (Rev. <a href=\"https:\/\/policies.wsu.edu\/prf\/bppm-manual-revisions\/bppm-revision-651\/\">651<\/a> &#8211; NEW).<\/p>\n\n<\/div>\r\n\n<\/div>","protected":false},"excerpt":{"rendered":"<p>University Policies and Procedures Manual Software Development<\/p>\n","protected":false},"author":49281,"featured_media":0,"parent":50633,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_wsuwp_accessibility_report":null},"wsuwp_university_location":[],"wsuwp_university_org":[],"_links":{"self":[{"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/pages\/69499"}],"collection":[{"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/users\/49281"}],"replies":[{"embeddable":true,"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/comments?post=69499"}],"version-history":[{"count":8,"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/pages\/69499\/revisions"}],"predecessor-version":[{"id":71366,"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/pages\/69499\/revisions\/71366"}],"up":[{"embeddable":true,"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/pages\/50633"}],"wp:attachment":[{"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/media?parent=69499"}],"wp:term":[{"taxonomy":"wsuwp_university_location","embeddable":true,"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/wsuwp_university_location?post=69499"},{"taxonomy":"wsuwp_university_org","embeddable":true,"href":"https:\/\/policies.wsu.edu\/prf\/wp-json\/wp\/v2\/wsuwp_university_org?post=69499"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}