You all know by now that the BSIMM is a descriptive model and not a prescriptive one. We’re happy to give prescriptive advice about software security based on our experience as well. It’s what we do for a living. In fact, every prescriptive model (think the Touchpoints) needs to be measured with a measuring stick like the BSIMM.
Without further ado, the ten commandments for software security as invented by our Principals:
Thou shalt lead thy software security initiative (SSI) with a software security group (SSG).
Thou shalt rely on risk management and objective measurement using the BSIMM—not “top ten lists” and vulnerability counts—to define SSI success.
Thou shalt communicate with executives, directly linking SSI success to business value and comparing thy firm against its peers.
Thou shalt create and adopt an SSDL methodology like the Microsoft SDL or our Touchpoints that integrates security controls (including architecture risk analysis, code review, and penetration testing) and people smarter about software security than the tools they run.
Thou shalt not limit software security activity to only technical SDLC activities and especially not to penetration testing alone.
Thou shalt grow and nurture software security professionals for thy SSG (since there are not enough qualified people to go around).
Thou shalt consume direction from the business and intelligence from operations and incident response staff, and adjust SSI controls accordingly.
Thou shalt track thy data carefully and know where the data live regardless of how cloudy thy architecture gets.
Thou shalt not rely solely on security features and functions to build secure software as security is an emergent property of the entire system and thus relies on building and integrating all parts properly.
Thou shalt fix thy identified software defects: both bugs and flaws.
Read more in this month’s [in]security column on SearchSecurity: Ten commandments for software security
We welcome your reaction.