Towards a taxonomy for information security metrics
Proceedings of the 2007 ACM workshop on Quality of protection
Secure Software Engineering: Learning from the Past to Address Future Challenges
Information Security Journal: A Global Perspective
Open source vs. closed source software: towards measuring security
Proceedings of the 2009 ACM symposium on Applied Computing
GoCoMM: a governance and compliance maturity model
Proceedings of the first ACM workshop on Information security governance
Context sensitive adaptive authentication
EuroSSC'07 Proceedings of the 2nd European conference on Smart sensing and context
Beyond heuristics: learning to classify vulnerabilities and predict exploits
Proceedings of the 16th ACM SIGKDD international conference on Knowledge discovery and data mining
Security and performance in service-oriented applications: Trading off competing objectives
Decision Support Systems
Towards quantitative risk management for next generation networks
Telecommunication Economics
Prioritization of software security intangible attributes
ACM SIGSOFT Software Engineering Notes
Taxonomy of quality metrics for assessing assurance of security correctness
Software Quality Control
Aggregating vulnerability metrics in enterprise networks using attack graphs
Journal of Computer Security
| Hi-index | 0.00 |
How secure is a computer system? Bridges have a load limit, but it isn't determined (as "Calvin andHobbes" would have it) by building an identical bridge and running trucks over it until it collapses. In amore relevant vein, safes are rated for how long they'll resist attack under given circumstances. Can we dothe same for software?