M. Howard and D. LeBlanc. Writing Secure Code. Microsoft Press, 2001. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
DPS: An Architectural Style for Development of Secure.. - Fenkam, Gall, Jazayeri.. (2002) (Correct)
....paper. 2 Related Work Building secure software is starting to draw well deserved attention. Up to now, most computer security articles published in industry magazines focussed on fixing security problems [7] Among the few that propose principles for building secure software systems, we consider [10, 18, 23, 25, 27, 28] particularly interesting. In [18] McGraw and Felten propose twelve rules for writing secure Java programs: 1) programs should not depend on initialization, 2) Use of visibility restrictors, 3) everything should be made final unless there is a good reason not to, 4) programs should not depend on ....
Michael Howard and David LeBlanc. Writing Secure Code. Microsoft Press, 2001.
General Method of Program Code Obfuscation - Wroblewski (2002) (5 citations) (Correct)
....The obtained results give the first estimation of the maximum possible eciency of the obfuscation process. Keywords: obfuscation, security, reverse engineer ing, machine code I Introduction Although the security through obscurity method seems to be not very popular in current software science ([3]) obfuscation is present al most everywhere. Each time someone wants to store important data he encodes it, which in fact is just pure obfuscation (doing this he assumes that an intruder can access his data) It looks somehow strange that no one obfuscates important pieces of programs or does it ....
Michael Howard, David LeBlanc, Writing Secure Code, Microsoft Press, 2002
Finding Security Vulnerabilities in Java Applications - With Static Analysis (Correct)
No context found.
M. Howard and D. LeBlanc. Writing Secure Code. Microsoft Press, 2001.
Enhancing Security through Hardware-assisted Run-time .. - Arora, Raghunathan.. (2005) (Correct)
No context found.
M. Howard and D. LeBlanc. Writing Secure Code. Microsoft Press, 2002.
Assessing the Risk of Using Vulnerable - Components Davide Balzarotti (Correct)
No context found.
Michael Howard and David Leblanc. Writing secure Code. Microsoft Press, 2003.
Software Protection and Application Security: Understanding .. - Main, van Oorschot (Correct)
No context found.
M. Howard, D.C. LeBlanc, Writing Secure Code, 2nd ed., Microsoft Press, 2002.
Finding Security Vulnerabilities in Java Applications with.. - Livshits, Lam (2005) (1 citation) (Correct)
No context found.
M. Howard and D. LeBlanc. Writing Secure Code. Microsoft Press, 2001.
Software Security: Experiments on the .NET Common.. - Piessens, Jacobs, Joosen (2003) (Correct)
No context found.
M. Howard and D. LeBlanc. Writing secure code. Microsoft Press, second edition, 2003. 11
Code Inection in C and CPP: A Survey of Vulnerabilities.. - Younan, Joosen, Piessens (2004) (Correct)
No context found.
Michael Howard and David LeBlanc. Writing Secure Code. Microsoft Press, 2001. (Cited on page 3.)
The essence of data access in Cω - The power is in.. - Bierman, Meijer, Schulte (Correct)
No context found.
M. Howard and D. LeBlanc. Writing Secure Code. Microsoft Press, 2003.
An Overview of Common Programming Security Vulnerabilities and.. - Younan (2003) (Correct)
No context found.
Michael Howard and David LeBlanc. Writing Secure Code. Microsoft Press, 2001.
Open and Closed Systems are Equivalent (that is, in an ideal world) - Anderson (Correct)
No context found.
M Howard, D LeBlanc, `Writing Secure Code', Microsoft Press 2002 (second edition 2003), ISBN 0-7356-1588-8
Software Security: Thought leadership in information security - McGraw (Correct)
No context found.
Michael Howard and David Lablanc. Writing Secure Code. Microsoft Press. Redmond, WA, 2002.
Computer Security Strength & Risk: A Quantitative Approach - Schechter (2004) (1 citation) (Correct)
No context found.
Michael Howard and David LeBlanc. Writing secure code. Microsoft Press, Redmond, Washington, 2nd edition, December 2002.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC