Text Size Default Text SizeDefault Text Size Large Text SizeLarge Text Size Largest Text SizeLargest Text Size Print Print this Page

IT Systems Development Life Cycle Standard

I. Planning Phase

Requests for IT systems are developed into a Project Plan through the steps delineated by the ITS Project Documentation and Approval process.

II. Initiation Phase

Identify IT System Security Responsibilities:

Security roles and responsibilities are assigned:

  1. The Information Security Officer (ISO) designates a system owner and data owner(s).
  2. The system owner designates the system administrator(s).
  3. The data owner(s) designate the data custodian.

Diagram illustrating security roles

  1. Identify Risks and Controls:
     
    1. The system and data owner(s) or their designees perform an initial risk analysis based on initial requirements and objectives to establish security guidelines for system developers.
    2. The data owner(s) classifies the types of data the IT system will process and classify the data's sensitivity.
      1. For any data classified as sensitive the need for collection and maintenance of that data is re-evaluated.
      2. Sensitivity of the IT system is determined by the sensitivity of the data.
    3. For any system identified as sensitive, the system owner develops an initial draft of the IT System Security Plan that documents the controls that the system will enforce to provide protection against identified risks.
      Classes of security controls:
      1. Management Controls
      2. Operational Controls
      3. Technical Controls
    4. The IT System Security Plan is reviewed by the Information Security Office.

III. Definition and Construction Phase

  1. Design IT System Characteristics:
    1. The physical characteristics of the IT system are designed during this phase. The operating environment is established, inputs and outputs are defined and processes are allocated to resources.
    2. Design specifications for the security requirements of the IT System Security Plan are developed and documented.
    3. Everything requiring user input or approval is documented and reviewed by the user. The physical characteristics of the IT system are specified and a detailed design is prepared.
  2. Develop IT System:
     
    1. The detailed specifications produced during the design phase are translated into hardware, communications and executable software. Software components are unit tested, integrated and retested in a systematic manner. Hardware is assembled and tested.
    2. The incorporation of the security controls into the IT system design is verified and documented in the IT System Security Plan.
    3. At the discretion of the ISO, the ISO or his or her designee tests for proper and effective functioning of the security controls that may be tested prior to deployment. (Certain non-technical controls may not be effectively tested until the IT system is deployed.)

IV. Integration and Test Phase

  1. Integrate IT System Components:
    All of the IT system components (hardware, communications, software, security controls) are incorporated and systematically tested.
  2. Test Functionality and Security:
    1. The user ensures that the IT system's functional requirements are satisfied by the developed system.
    2. The IT system undergoes any necessary certification and accreditation activities.
    3. The Information Security Office conducts an IT system security evaluation to ensure that the security requirements, as defined in the IT System Security Plan, are satisfied by the developed or modified IT system.
    4. The IT system security controls are accepted by the system owner.

V. Implementation Phase

  1. Make IT System Operational:
    1. The IT system or IT system modifications are installed and made operational in a production environment.
    2. This phase continues until the IT system is operating in a production environment in accordance with the defined design specifications and security requirements.
  2. Document Risks and Controls:
    1. The system owner and data owner(s) or their designees will conduct a risk assessment of the system.
    2. The system owner or his or her designees will document the final IT System Security Plan to document the security controls implemented.
    3. The completed IT System Security Plan is approved by the ISO.

VI. Operations and Maintenance Phase

  1. Continue Operation of IT System:
    1. With the IT system operation ongoing, the IT system is monitored for continued performance in accordance with design specifications and security requirements. Operations continue as long as the IT system can be effectively adapted to respond to an organization's needs.
    2. The IT system is periodically assessed through In-Process Reviews to determine how the IT system can be made more efficient and effective.
    3. The security controls are periodically assessed through security evaluations.
  2. Modify IT System:
    1. Needed modifications are incorporated into the IT system.
    2. When major modifications or changes are identified, the IT system may reenter the Planning Phase.
    3. The IT System Security Plan will be updated by the system owner to document any changes to security controls implemented for the system and approved by the ISO. The IT System Security Plan will be reviewed and approved no less than once every three years.

VII. Disposition Phase

When a decision is made to cease use of an IT system the following requirements must be met in the disposition:

  1. Make Data Retention Decisions:
    Data handled by the IT system will be retained in accordance with University and/or Commonwealth of Virginia record retention requirements.
  2. Dispose of the IT System Components:
    Electronic media will be sanitized and hardware and software disposed of in accordance with University and/or Commonwealth of Virginia requirements.

Definitions

Data: Data is an arrangement of numbers, characters and/or images representing information, knowledge, facts, concepts or instructions.

Data Owner: A University employee designated as responsible for the policy and practice decisions regarding data.

Management Controls: A set of mechanisms designed to manage organizations to achieve desired objectives.

Operational Controls: IT security measures implemented through policies and procedures.

Risk Analysis: A systematic process to identify and quantify risks to IT systems and data and to determine the probability of the occurrence of those risks.

Risk Assessment (RA): The process of identifying and evaluating risks so as to assess their potential impact.

Security Evaluation: Procedures used in the analysis of security mechanisms to determine their effectiveness and to support or refute specific IT system weaknesses.

Sensitivity Classification: The process of determining whether and to what degree IT systems and data are sensitive.

Security Controls: The protection mechanisms prescribed to meet the security requirements specified for an IT system.

Sensitive Data: Sensitive data is any data in print or electronic form of which a compromise of confidentiality, integrity or availability would have a significant and noticeable impact on the University's achievement of its mission.

System: IT systems are interconnected sets of IT resources, including application systems which meet a defined set of business needs and support systems that provide services to other systems.

System Owner: A University employee designated as responsible for the operation and maintenance of a University IT system.

Technical Controls: IT security measures implemented through technical software or hardware.

Approved by the Chief Information Officer, November 18, 2008.