Channels ▼


Secure Software Conference

(ISC)2, a nonprofit body of certified information security professionals, has announced the expansion of its Security Leadership conference series to address integrating security throughout the software development lifecycle (SDLC) to better protect enterprises and individuals.  

(ISC)2 will kick-off its SecureSDLC conference series on June 17 in Fremont, California.

Titled "SecureSDLC: Building Security into the Software Lifecycle," the day-long conference will feature a keynote at 9 a.m. from David Rice, author Geekonomics: The Real Cost of Insecure Software, who will discuss how insecure software contributes to the destruction of global economic wealth and enables pandemic cybercrime.

In addition, several members of the Silicon Valley’s Office of the CIO will participate in a panel discussion at 11 a.m. on the problems insecure software has caused their organizations and the solutions they’re seeking from vendors. The panel will be moderated by Dean Lane, author of CIO Wisdom: Best Practices from Silicon Valley. The panel will feature Lincoln Heacock, CIO of CyberSource; Allyn McGillicuddy, CIO of Golden Gate University; Max Rayner, CTO of Travelzoo; and Jim Trovato, CISO of Intuit.

According to Rice, "To this day, software remains one of the most defective products in the global market place. The software market is a market for lemons, where buyers cannot distinguish between ‘good’ and ‘bad’ software. Consequently, high-quality, secure software is driven from the market. This is bad for everyone -- governments, enterprises, businesses, customers, and citizens."

Other speakers scheduled for the event include Rafal Los, senior Web security specialist for Hewlett-Packard (HP) Software and blogger, who will speak about developing an execution-flow-based approach to application security testing; and Brad Arkin, director of product security and privacy for Adobe, who will speak about gaining acceptance for a secure approach to software development and how Adobe implemented its own Secure Product Lifecycle program.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.