Building secure software: how to avoid security problems the right way

By Ken Frazer. SOEN, 2002

636 citations recorded by the source corpus.

Subfields: Information Systems

View Paper: https://www.semanticscholar.org/paper/907be53c586e747a4146c1dfb28bd05143de545d

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

1. Michael W. Hicks
2. Michelle L. Mazurek
3. Jordan L. Boyd-Graber
4. Joseph Bonneau

Citations in the corpus

• Elaborating security requirements by construction of intentional anti-models (2004, neutral): “The state of the art in security enginering at the application layer is much more limited [42, 41].”
• Build It, Break It, Fix It: Contesting Secure Development (2016, background): “ecycle (SDL) [35] describes possible strategies for incorporating security concerns into the development process. Several authors make recommendations about development lifecycle and coding practices [10,15,34,40,57,66]. Acar et al. collect and categorize 19 such resources [4]. Studies of secure sof”
• Security Requirements Engineering: A Framework for Representation and Analysis (2008, neutral): “is the analyst’s set of trust assumptions [79], [80].”
• Security of smart manufacturing systems (2018, neutral): “Thus consideration of security is vital at each phase of the system's life cycle [25].”