Hi [[ session.user.profile.firstName ]]

Software Development Life Cycle: Who's responsible for security?

From "start-up" through "acquisition & development", "implementation", and "operations & maintenance" to "decommissioning", it's far too easy to lay the responsibility for the secure software life cycle at the feet of the application dev
From "start-up" through "acquisition & development", "implementation", and "operations & maintenance" to "decommissioning", it's far too easy to lay the responsibility for the secure software life cycle at the feet of the application developers. What about all the other professionals involved in the software development life cycle (SDLC)? Question: What responsibility do the application owners, procurement officers, business unit heads, delivery personnel, senior managers, business analysts, quality assurance managers, program managers, technical architects, security specialists, and IT managers have with respect to the SDLC? Answer: They all have either a legal or fiduciary responsibility to be aware of basic secure coding principles. Don't be the one who is "made an example out of" when an application development project goes awry!
Recorded Jun 3 2010
49 mins
Your place is confirmed,
we'll send you email reminders
Presented by
Dow A. Williamson CISSP, CSSLP; SCIPP International, Executive Director
Presentation preview: Software Development Life Cycle:  Who's responsible for security?
Recommended for you:
  • Date
  • Rating
  • Views

Embed in website or blog

Successfully added emails: 0
Remove all
  • Title: Software Development Life Cycle: Who's responsible for security?
  • Live at: Jun 3 2010 6:00 pm
  • Presented by: Dow A. Williamson CISSP, CSSLP; SCIPP International, Executive Director
  • From:
Your email has been sent.
or close
You must be logged in to email this