D487 - Secure Software Design questions with
|\ |\ |\ |\ |\ |\ |\
answers
SDLC Phase 1 |\ |\
planning - a vision and next steps are created
|\ |\ |\ |\ |\ |\ |\ |\
SDLC Phase 2 |\ |\
requirements - necessary software requirements are determined |\ |\ |\ |\ |\ |\
SDLC Phase 3 |\ |\
design - requirements are prepared for the technical design
|\ |\ |\ |\ |\ |\ |\ |\
SDLC Phase 4 |\ |\
implementation - the resources involved in the application from a |\ |\ |\ |\ |\ |\ |\ |\ |\
known resource are determined
|\ |\ |\ |\
SDLC Phase 5 |\ |\
testing - software is tested to verify its functions through a
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\ |\
known environment |\
SDLC Phase 6 |\ |\
deployment - security is pushed out |\ |\ |\ |\ |\
SDLC Phase 7 |\ |\
maintenance - ongoing security monitoring is implemented |\ |\ |\ |\ |\ |\
SDLC Phase 8 |\ |\
end of life - the proper steps for removing software completely
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\ |\
are considered
|\
BSIMM
, a study of real-world software security that allows you to develop
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\
your software security over time
|\ |\ |\ |\ |\
OWASP SAMM |\
flexible framework for building security into a software
|\ |\ |\ |\ |\ |\ |\ |\
development organization |\
Static Analysis |\
the analysis of computer software that is performed without
|\ |\ |\ |\ |\ |\ |\ |\ |\
executing programs |\
Dynamic Analysis |\
the analysis of computer software that is performed when
|\ |\ |\ |\ |\ |\ |\ |\ |\
executing programs on a real or virtual processor in real time
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\
Fuzz Testing |\
automated or semi-automated testing that provides invalid,
|\ |\ |\ |\ |\ |\ |\
unexpected, or random data to the computer software program |\ |\ |\ |\ |\ |\ |\ |\
Waterfall Development |\
software development methodology that breaks down
|\ |\ |\ |\ |\ |\
development activities into linear sequential phases; each phase |\ |\ |\ |\ |\ |\ |\
depends on the deliverables of the previous one and corresponds
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\
to a specialization of tasks
|\ |\ |\ |\ |\
Waterfall Phases (typical) |\ |\
plan -> build -> test -> review -> deploy
|\ |\ |\ |\ |\ |\ |\ |\
Iterative Waterfall Development |\ |\
each phase of a project is broken down into its own waterfall
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\ |\ |\
phases
Agile Development |\
|\ |\ |\ |\ |\ |\ |\
answers
SDLC Phase 1 |\ |\
planning - a vision and next steps are created
|\ |\ |\ |\ |\ |\ |\ |\
SDLC Phase 2 |\ |\
requirements - necessary software requirements are determined |\ |\ |\ |\ |\ |\
SDLC Phase 3 |\ |\
design - requirements are prepared for the technical design
|\ |\ |\ |\ |\ |\ |\ |\
SDLC Phase 4 |\ |\
implementation - the resources involved in the application from a |\ |\ |\ |\ |\ |\ |\ |\ |\
known resource are determined
|\ |\ |\ |\
SDLC Phase 5 |\ |\
testing - software is tested to verify its functions through a
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\ |\
known environment |\
SDLC Phase 6 |\ |\
deployment - security is pushed out |\ |\ |\ |\ |\
SDLC Phase 7 |\ |\
maintenance - ongoing security monitoring is implemented |\ |\ |\ |\ |\ |\
SDLC Phase 8 |\ |\
end of life - the proper steps for removing software completely
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\ |\
are considered
|\
BSIMM
, a study of real-world software security that allows you to develop
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\
your software security over time
|\ |\ |\ |\ |\
OWASP SAMM |\
flexible framework for building security into a software
|\ |\ |\ |\ |\ |\ |\ |\
development organization |\
Static Analysis |\
the analysis of computer software that is performed without
|\ |\ |\ |\ |\ |\ |\ |\ |\
executing programs |\
Dynamic Analysis |\
the analysis of computer software that is performed when
|\ |\ |\ |\ |\ |\ |\ |\ |\
executing programs on a real or virtual processor in real time
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\
Fuzz Testing |\
automated or semi-automated testing that provides invalid,
|\ |\ |\ |\ |\ |\ |\
unexpected, or random data to the computer software program |\ |\ |\ |\ |\ |\ |\ |\
Waterfall Development |\
software development methodology that breaks down
|\ |\ |\ |\ |\ |\
development activities into linear sequential phases; each phase |\ |\ |\ |\ |\ |\ |\
depends on the deliverables of the previous one and corresponds
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\
to a specialization of tasks
|\ |\ |\ |\ |\
Waterfall Phases (typical) |\ |\
plan -> build -> test -> review -> deploy
|\ |\ |\ |\ |\ |\ |\ |\
Iterative Waterfall Development |\ |\
each phase of a project is broken down into its own waterfall
|\ |\ |\ |\ |\ |\ |\ |\ |\ |\ |\ |\
phases
Agile Development |\
