Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Tuesday May 08 2018, @07:37PM   Printer-friendly
from the obligatory-car-analogy dept.

Submitted via IRC for TheMightyBuzzard

The financial benefits of finding and fixing defects throughout the software development life cycle (SDLC), starting at the very beginning, ought to make doing it a no-brainer. It is both easier and cheaper. One should build secure software from the ground up.

[...] The findings of a 2016 Forrester Research study call to mind an ancient proverb: A stitch in time saves nine. Or, in the case of software development, fixing defects early in the SDLC could reduce remediation costs by a factor of anywhere from 5 to 15.

The study set a baseline example of 5 hours of work to fix a defect in the coding/development stage. Finding and fixing that same defect in the final testing phase would take 5–7 times longer. And waiting until after the product was on the market to discover and fix the same defect would take even longer and cost 10–15 times more.

That doesn't include the potential cost of damages from a bad guy discovering the defect first and exploiting it to attack users.

And to the frequently stated worry that ongoing security testing creates intolerable delays in time to market, Forrester found the opposite: that it cuts time to market by 25%.

Hat tip to the old slashcode crew who left us some very good tools for doing exactly this.

Source: https://www.helpnetsecurity.com/2018/05/08/build-secure-software/


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 5, Insightful) by arslan on Tuesday May 08 2018, @10:52PM

    by arslan (3462) on Tuesday May 08 2018, @10:52PM (#677218)

    Their KPI is on the delivery of the project on time and costs, not on cost of ownership or what happens after. They then move on to the next project. Add in the fact that they tend to be at the top of the pecking order in terms of decision making means decisions are always made in line with how they're incentivized - which more often than not are poor decisions for the product in the long run.

    I've worked in projects where PMs are relegated to doing book keeping on time and money spent and churning out charts but have absolutely no say in delivery & product decisions. Worked out a whole lot better for the product in the long run.

    Starting Score:    1  point
    Moderation   +3  
       Insightful=3, Total=3
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   5