Difference between revisions of "Software Development Policies"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | [[ | + | [[Category: Software]] |
| − | [[ | + | [[Category: Policies]] |
=Policies= | =Policies= | ||
==External Software Components== | ==External Software Components== | ||
When users develop software on HiPerGator or in ResVault there is often the need to download software components from other places under various licenses in addition to writing software. There is no need to get a security review or risk assessment for such software. Only when software is exposed to the outside world, e.g. as part of PubApps, will a security review be required. Research Computing staff will need to be involved as well as Information Security Office. | When users develop software on HiPerGator or in ResVault there is often the need to download software components from other places under various licenses in addition to writing software. There is no need to get a security review or risk assessment for such software. Only when software is exposed to the outside world, e.g. as part of PubApps, will a security review be required. Research Computing staff will need to be involved as well as Information Security Office. | ||
Revision as of 18:51, 17 December 2018
Policies
External Software Components
When users develop software on HiPerGator or in ResVault there is often the need to download software components from other places under various licenses in addition to writing software. There is no need to get a security review or risk assessment for such software. Only when software is exposed to the outside world, e.g. as part of PubApps, will a security review be required. Research Computing staff will need to be involved as well as Information Security Office.