Skip to Content

9-4 Information Technology Professionals Policy - Section VII: Information Systems Acquisition, Development and Maintenance Policy

Information Systems Department

Return to Information Technology Professionals Policy Table of Contents

What’s on this Page

Section VII: Information Systems Acquisition, Development and Maintenance Policy

Read next: Section VIII: Information Technology (IT) Resource Management Policy

VII. Information Systems Acquisition, Development and Maintenance Policy

This Policy provides direction for the integration of information security into the lifecycle of information systems that hold and process Local Agency data.

  1. Security Requirements of Information Systems
    1. To ensure security is built into all Local Agency information systems, all security requirements must be identified and documented at the design stage for new information systems or enhancements to existing systems.
    2. Security controls must be commensurate with the risks and the relative sensitivity of the system and the information it stores and/or processes.
  2. Separation of Development, Test and Production Environments
    1. Development and test environments must be logically or physically separated from production environments.
    2. Media used for development and test activities must be clearly labeled as such and must not be used on production systems unless all test data has been removed.
    3. Local Agency data that is used for development and test activities must be protected and controlled.
    4. If production data is used in a test environment, the following must be adhered to:
      1. Production data used in a test environment must be protected as if it is still production data.
      2. A copy of the production data must be made so that live data cannot be altered.
      3. The physical or electronic output of tests using the production data must be strictly controlled and promptly destroyed when no longer needed.
  3. System Planning and Acceptance
    1. Advance planning and preparation must be performed to ensure the availability of adequate capacity and resources. The security requirements of new systems must be established, documented, and tested prior to their acceptance and use.
    2. The capacity demands of Local Agency IT resources must be monitored and projections made of future capacity requirements to ensure adequate power and data storage requirements can be filled.
    3. Acceptance criteria must be developed and documented for new information systems or enhancements to existing systems.
    4. Acceptance testing must be performed to ensure security requirements are met prior to the system being migrated to the production environment.
  4. Correct Processing in Applications
    To prevent errors, loss and unauthorized modification or misuse of information in application systems; processes must be established and maintained for:
    1. Input data validation - Data input to an information system must be validated to ensure it is correct and appropriate.
    2. Internal processing - Internal processing checks must be performed to minimize the risk of processing failures or deliberate acts leading to a loss of integrity.
    3. Output data validation – Data output from an information system must be validated to ensure the processing of stored information is correct and appropriate.
    4. Message integrity - Message integrity controls must be used for information systems where there is a security requirement to protect the authenticity of the message content.
    5. Error response – Responsibilities and procedures must be defined for responding to detected errors.
  5. Software Maintenance
    1. When technically feasible, all system software must be maintained at a vendor-supported level to ensure software accuracy and integrity.
    2. Modification of commercial-off-the-shelf software security controls is limited to essential changes that are strictly controlled and documented.
    3. All known security patches must be reviewed, evaluated, and appropriately applied in a timely manner. See also Section XII. Technical Vulnerability Management Policy.
  6. Change Control
    Changes to software must be controlled by the use a formal change control procedure as specified in Section V. Change Management Policy.

Back to top