...
- Secured wiki site of UT System shared applications and their network profiles/desires.
- Network contact list of each institution and troubleshooting guidelines (how to start a debugging process), and listservs.
- Network review board for UT System shared applications (new applications and changes must pass the review board which can ensure implementable systems that are not security exclusive). Non-reviewed applications can of course be used (most will not be reviewed) but they won't have the same level of attention to ensure they work.
Wiki Markup - Email lists for notification and discussions regarding shared applications.
- Scheduled windows for changes to shared applications.
- Create templates for popular security devices to support shared applications (ex: Cisco/Juniper firewall configuration stanzas).
- Agreement on inter-institutional QOS traffic marking guidelines.unmigrated-wiki-markup
- Develop security blocking monitoring system. \ [Custom development. Deploy nodes to all institutions and application locations reporting back to a central server. Have the server and nodes probe the defined ports and escalate changing conditions (such as using nmap). Provide a console for all institutions to monitor and log these changes. Should institution X change port 8922 required by sanctioned applications that would be escalated to ensure that was intentional and alert all parties \ -\- including application owners.\] (ex: Multicast beacon, Internet weather-maps).
- Training/documentation and appropriate tools to assist in troubleshooting (ex: NDT, iperf, nmap). Not just networking staff, but application owners/debuggers.
- Common recommended testbed for networking and application staff to vett hardware and applications outside production environments.