Cited by 234Security and Verification in ComputingWeb Application Security VulnerabilitiesSoftware Engineering Techniques and Practices

The Trustworthy Computing Security Development Lifecycle

Lipner, S.·2005·20th Annual Computer Security Applications Conference

Abstract

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.

Integrity signals

Registry

Crossref · 10.1109/csac.2004.41

Cites

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

Cites

Still being checked.

Cited by

Sorted by citations

Authors
Lipner, S.
Affiliations
Microsoft (United States) (US)
Corresponding author
Lipner, S.
Venue
20th Annual Computer Security Applications Conference
Publisher
IEEE
Published
2005-04-06
Pages
2-13
ISSN
1063-9527 (ISSN-L)
OpenAlex
W1604658196
Cited by
234
References
0
Citations by year
2026: 3 · 2025: 6 · 2024: 7 · 2023: 8 · 2022: 8 · 2021: 8 · 2020: 11 · 2019: 5 · 2018: 13 · 2017: 7 · 2016: 6 · 2015: 16 · 2014: 21 · 2013: 16 · 2012: 12
FWCI
10.23
Type
conference paper
Language
en
Open access
closed
Locations
Annual Computer Security Applications Conference (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Artificial Intelligence › Security and Verification in Computing
  • Physical Sciences › Computer Science › Information Systems › Web Application Security Vulnerabilities
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
security development lifecycle, trustworthy computing, Microsoft, threat modeling, static code analysis, code review, security testing, software vulnerabilities, software development process

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review