前往小程序,Get更优阅读体验!
立即前往
首页
学习
活动
专区
工具
TVP
发布
社区首页 >专栏 >CISSP考试指南笔记:8.2 软件开发生命周期

CISSP考试指南笔记:8.2 软件开发生命周期

作者头像
血狼debugeeker
发布2021-09-10 10:43:07
3140
发布2021-09-10 10:43:07
举报
文章被收录于专栏:debugeeker的专栏debugeeker的专栏

There have been several software development life cycle (SDLC) models developed over the years, the crux of each model deals with the following phases:

  • Requirements gathering
  • Design
  • Development
  • Testing
  • Operations and maintenance

Project Management


Project management is an important part of product development, and security management is an important part of project management.

A security plan should be drawn up at the beginning of a development project and integrated into the functional plan to ensure that security is not overlooked.

The security plan and project management activities may likely be audited so security-related decisions can be understood.

If a software product is being developed for a specific customer, it is common for a Statement of Work (SOW) to be developed, which describes the product and customer requirements.

Sticking to what is outlined in the SOW is important so that scope creep does not take place.

A work breakdown structure (WBS) is a project management tool used to define and group a project’s individual work elements in an organized manner.

Requirements Gathering Phase


As it pertains to security, the following items should be accomplished in this phase:

  • Security requirements
  • Security risk assessment
  • Privacy risk assessment
  • Risk-level acceptance

The security requirements of the product should be defined in the categories of availability, integrity, and confidentiality.

An initial security risk assessment should be carried out to identify the potential threats and their associated consequences.

After a privacy risk assessment, a Privacy Impact Rating can be assigned, which indicates the sensitivity level of the data that will be processed or accessible. Some software vendors incorporate the following Privacy Impact Ratings in their software development assessment processes:

  • P1, High Privacy Risk
  • P2, Moderate Privacy Risk
  • P3, Low Privacy Risk

A clear risk-level acceptance criteria needs to be developed to make sure that mitigation efforts are prioritized.

剩余内容请关注本人公众号debugeeker, 链接为CISSP考试指南笔记:8.2 软件开发生命周期

本文参与 腾讯云自媒体分享计划,分享自作者个人站点/博客。
原始发表:2021-03-30 ,如有侵权请联系 cloudcommunity@tencent.com 删除

本文分享自 作者个人站点/博客 前往查看

如有侵权,请联系 cloudcommunity@tencent.com 删除。

本文参与 腾讯云自媒体分享计划  ,欢迎热爱写作的你一起参与!

评论
登录后参与评论
0 条评论
热度
最新
推荐阅读
目录
  • Project Management
  • Requirements Gathering Phase
领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档