Secure Programming

Graff, M. G. & van Wyk, K. R. (2003) Secure coding: Principles and practice. Sebastopol, CA: O’Reilly. ISBN: 0-596-00242-4

Howard. M., LeBlanc, D., & Viega, J. (2010). 24 deadly sins of software security: Programming flaws and how to fix them. New York: McGraw Hill. ISBN: 978-0-07-162675-0

Required paper

#3
This report, on some discussion topics associated with Web vulnerabilities and hazards, is sourced in Howard, Leblanc & Vega, Part I – Web Application Sins. The discussion topics ought to be interesting aspects, which you note, and a question, of what is written about the vulnerabilities. If you have professional experience (you do web design or have done web design), or user experience in these vulnerabilities, you should relate the topics to the experiences. Besides the text, the report ought to be sourced also in www.mitre.org and www.cert.org as places of deeper explanations. Each chapter on a particular sin provides other sources to use in your investigation. Sources of given topics for discussion should be indicated by something like (www.cert.org).
The report ought to be sourced also in www.mitre.org and www.cert.org

#4
This report, on some discussion topics associated with Web vulnerabilities and hazards, is sourced in Howard, Leblanc & Vega, Part II – Implementation Sins, specifically Buffer overruns, Format string problems, Integer overflows, Command injection, Race conditions and Executing code with too much privilege. The discussion topics ought to be interesting aspects, which you note, and a question, of what is written about the vulnerabilities. If you have professional experience (you program or have programmed in a particular language), or user experience in these vulnerabilities, you should relate the topics to the experiences. Besides the text, the report ought to be sourced also in www.mitre.org and www.cert.org as places of deeper explanations. Each chapter on a particular sin provides other sources to use in your investigation. Sources of given topics for discussion should be indicated by something like (www.cert.org).
The report ought to be sourced also in www.mitre.org and www.cert.org

#5
This report, on some discussion topics associated with Web vulnerabilities and hazards, is sourced in Howard, Leblanc & Vega, Part III – Crypographic Sins. The discussion topics ought to be interesting aspects, which you note, and a question, of what is written about the vulnerabilities. If you have professional experience (you do crypography or have done crypography), or user experience in these vulnerabilities, you should relate the topics to the experiences. Besides the text, the report ought to be sourced also in www.mitre.org and www.cert.org as places of deeper explanations. Each chapter on a particular sin provides other sources to use in your investigation. Sources of given topics for discussion should be indicated by something like (www.cert.org).
The report ought to be sourced also in www.mitre.org and www.cert.org

#6
This report, on some discussion topics associated with Web vulnerabilities and hazards, is sourced in Howard, Leblanc & Vega, Part IV – Networking Sins. The discussion topics ought to be interesting aspects, which you note, and a question, of what is written about the vulnerabilities. If you have professional experience (you do networking or have done networking), or user experience in these vulnerabilities, you should relate the topics to the experiences. Besides the text, the report ought to be sourced also in www.mitre.org and www.cert.org as places of deeper explanations. Each chapter on a particular sin provides other sources to use in your investigation. Sources of given topics for discussion should be indicated by something like (www.cert.org).
The report ought to be sourced also in www.mitre.org and www.cert.org

#7
The discussion topics which are possible in this report are sourced retroactively in the past 7 sessions and associated readings. They are rethinking some untouched ideas. Topics ought to include legal and moral aspects of the vulnerabilities and their contexts. Topics to be discussed and a question to be raised should cover lessons learned (if any). Sources of given topics for discussion should be indicated by something like (www.cert.org).
The report ought to be sourced also in www.mitre.org and www.cert.org

Secure Programming Discussion Topics Reports
These are narrative presentations of observations and summaries based on reading about & researching secure programming and security of information systems (using www, articles, newspapers, books). The focus of each report are the readings, i.e., the topic of the session. They may be representative of your particular area of expertise and concerns. They should be inquisitive and informative, to yourself and to the instructor. They are aimed at describing, understanding, and clarifying aspects, issues, concerns, and problems of various languages and secure coding issues. Identify one question or issue you want to raise in class. These are aimed at raising issues and problems etc, and will be used as a basis for class discussion and learning. Length of document should be no less than four pages and may be as long as you need the document to be.

TO GET YOUR ASSIGNMENTS DONE AT A CHEAPER PRICE,PLACE YOUR ORDER WITH US NOW