Secure programming workshop: how to keep our students from causing buffer overflows
Journal of Computing Sciences in Colleges
Towards a structured unified process for software security
Proceedings of the 2006 international workshop on Software engineering for secure systems
Investigation of IS professionals' intention to practise secure development of applications
International Journal of Human-Computer Studies
Evaluating the cost reduction of static code analysis for software security
Proceedings of the third ACM SIGPLAN workshop on Programming languages and analysis for security
Towards analyzing complex operating system access control configurations
Proceedings of the 15th ACM symposium on Access control models and technologies
Trusted computing and provenance: better together
TAPP'10 Proceedings of the 2nd conference on Theory and practice of provenance
Systematizing security test case planning using functional requirements phrases
Proceedings of the 33rd International Conference on Software Engineering
Sociotechnical trust: an architectural approach
ER'11 Proceedings of the 30th international conference on Conceptual modeling
Mitigating multi-threats optimally in proactive threat management
ACM SIGSOFT Software Engineering Notes
OSDC: adapting ODC for developing more secure software
Proceedings of the 28th Annual ACM Symposium on Applied Computing
Trust-based specification of sociotechnical systems
Data & Knowledge Engineering
| Hi-index | 0.00 |
This paper discusses the Trustworthy Computing Security Development Lifecycle (or simply the SDL), a process that Microsoft has adopted for the development of software that needs to withstand malicious attack.The process encompasses the addition of a series of security-focused activities and deliverables to each of the phases of Microsoft's software development process.These activities and deliverables include the development of threat models during software design, the use of static analysis code-scanning tools during implementation, and the conduct of code reviews and security testing during a focused "security push".Before software subject to the SDL can be released, it must undergo a Final Security Review by a team independent from its development group.When compared to software that has not been subject to the SDL, software that has undergone the SDL has experienced a significantly reduced rate of external discovery of security vulnerabilities.This paper describes the SDL and discusses experience with its implementation across a range of Microsoft software.