This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Types of application security metrics"

Jump to: navigation, search
(Reverting to last version not containing links to
Line 1: Line 1:
[ webmap] [ african american history lecture note
] [ asian bangin
] [ automatic urinal flushers
] [ auto game play
] [ symantec antivirus could not communicate
] [ symantec antivirus corporate edition v 10
] [ west african kingdoms ghana
] [ norton antivirus serial crack
] [ auto lease traders
] [ mc afee antivirus updates] [ sitemap] [ norton antivirus 2006 downlod
] [ australian fuel injection
] [ africa ibo
] [ packaging automation ltd
] [ avp antivirus free download] [ links] [ macfee antivirus free
] [ panda titanium antivirus 2005 download
] [ south african airlines kathmandu
] [ asia video 45
] [ asian massage rhode island
] [ bronx auto auctions
] [ 2005 la auto show
] [ australian abn number search
] [ africas allied food site south union web worker] [ auto shop safety
] [ i dreamed of africa trailer
] [ left eye autopsy photo
] [ antivirus roundup
] [ australia brisbane page yellow] [ antivirus software test] [ ravantivirus
] [ yesasia coupon 2005
] [ removing norton antivirus from norton system works
] [ asian media development group
] [ page] [ elvis presley autopsy results
] [ africa volunteer projects
] [ asian childrens games
] [ symantec antivirus corporate edition v9.0.3
] [ capital city of australia
] [ auto automotriz] [ trend micro housecalls antivirus
] [ hire cars south africa
] [ african american braided hair styles
] [ avg antivirus windows xp
] [ south africa gold coin
] [ grand theft auto 3 hints cheats  
==Metrics Overview==
==Metrics Overview==

Revision as of 15:59, 27 May 2009

Metrics Overview


It's been said that you can't improve what you can't measure. We currently don't have any good metrics for application security. Everyone understands what we want to measure -- how secure is it? But we're really not sure what low-level measurements we should be making, nor do we know how to roll them up into something meaningful for the buyer or user of software.

The difficulty of this problem is essentially the same as determining if there are any loopholes in a legal contract. Like legalese, programming languages are arbitrarily complex. A malicious developer, like a crafty lawyer, will use all their skill to obfuscate their attack.

Direct Metrics

Ideally, we could just measure the software itself. If we could count all the vulnerabilities and determine their likelihood and impact, we'd know how secure it is. Unfortunately, even the best static analysis tools can't come close to doing this. Still, there are things we can measure, and perhaps we can figure out which of these things directly correlate with increased security.

  • How many lines of code?
  • What languages are used?
  • What libraries does this application use (and how)?
  • What type of network access is required (client, server, none)?
  • What security mechanisms are used?
  • What configuration files are associated with the application?
  • How are sensitive assets protected?
  • What vulnerabilities have been identified

Indirect Metrics

If you can't measure the security of software directly, another option is to measure the people, process, and technology that are associated with creating the software in the first place?

  • Is there security documentation (design, test results, vulnerabilities)?
  • Is the documentation accurate and complete?
  • Is there a process for reporting security flaws?
  • Who developed this code (training, experience, background check)?
  • What assurance activities were performed (threat modeling, analysis, code review, test, evaluation)?
  • What was the outcome of those assurance activities?