CBK#4 Applications & Systems Development Security - Page 4

CBK#4 Applications & System Develop. - Page 1 2 3 4 5 6 7 8 9

System life cycle phases/software life cycle development process
System Life Cycle Phases:
- Project initiation:
      - Conception of project definition
      - Proposal and initial study
- Functional design analysis and planning
      - Requirements uncovered and defined
      - System environment specification determined
- System design specifications
      - Functional design review
      - Functionality broken down
      - Detailed planning put into place
      - Code design
- Software development
      - Developing and programming software
- Installation / implementation
      - Product installation
      - Testing and auditing
- Operational/maintenance
      - Product changes, fixes and minor modifications
- Disposal / Revision and replacement
      - Modifying the product with revisions or replacing it altogether

The Waterfall Model:
- System requirements
- Software requirements
- Analysis
- Program design
- Coding
- Testing
- Operations & Maintenance

Modified Waterfall Model incorporating V&V:
- System feasibility -> validation
- Software plans & requirements -> validation
- Product design -> verification
- Detailed design -> verification
- Coding -> unit test
- Integration Product -> verification
- Implementation -> system test
- Operations & Maintenance -> revalidation

Security concerns:
- Security should be addressed in each phase of system development. Security should not be addressed at the end of development because of the added cost, time, effort and lack of functionality.
- Separation of duties should be practiced in roles, environments and functionality pertaining to development of a product.
- A programmer should not have direct access to code in production.
- Certification deals with testing and assessing the security mechanism in a system
- Accreditation pertains to the management formally accepting the system and its security level.
- Changes must be authorized, tested and recorded. The changes must not affect the security level of the system or its capability to enforce the security policy.

CBK#4 Applications & System Develop. - Page 1 2 3 4 5 6 7 8 9

CISSP Summary 2002Related links | References

CBK#1 Access Control Systems & Methodology | CBK#2 Telecommunications & Network Security | CBK#3 Security Management Practices | CBK#4 Applications & Systems Development Security | CBK#5 Cryptography | CBK#6 Security Architecture & Models | CBK#7 Operations Security | CBK#8 Business Continuity Planning & Disaster Recovery Planning | CBK#9 Law, Investigations & Ethics | CBK#10 Physical Security

Contact:

E-mail: john.wallhoff@mailbox.swipnet.se
Written by: J.Wallhoff January - April 2002
Updated by: J.Wallhoff April 2002