To define procedures for implementing and maintaining Data Communications (DC) software that will ensure integrity of data communications.
All data communications software in use at University of Houston.
Proper procedures shall be in place to ensure the integrity of the data communications software, and to ensure that no security exposure is posed by the software change control process that governs it.
- When selecting DC software, an evaluation and selection of security related options or features must be performed as part of standard procedures.
- If a DC software package has security weaknesses, additional security measures will be implemented to correct the security weakness.
- Communications software backup - Up-to-date backup of copies of all communications software will be maintained for use in the event of destruction or failure of the primary system. Storage should be on a secure off-site location.
- Source executable versions of the DC software must be protected by software mechanisms against unauthorized read and update access.
- Where DC software modifications are made to enhance capabilities (e.g., improving throughout), care must be taken that coding does not inadvertently weaken security and control.
- Communications hardware backup - Where practical, replacements should be available for critical communications hardware/circuitry, such as:
- Abnormal DC hardware, circuit, and software anomalies should be investigated to determine their cause. A permanent incident log should be maintained to detect trends that may reveal potential access penetration attempts.
- Automated techniques such as parity and redundancy checks should be used to help detect and correct data transmission errors.