<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Gary+David+Robinson</id>
		<title>OWASP - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Gary+David+Robinson"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/Gary_David_Robinson"/>
		<updated>2026-04-21T15:02:12Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:OWASP_Presentation_-_Encryption_and_Digital_Certificates_-_Published.pdf&amp;diff=244227</id>
		<title>File:OWASP Presentation - Encryption and Digital Certificates - Published.pdf</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:OWASP_Presentation_-_Encryption_and_Digital_Certificates_-_Published.pdf&amp;diff=244227"/>
				<updated>2018-10-14T21:04:43Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Slides from OWASP Belfast presentation during October.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Slides from OWASP Belfast presentation during October.&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=243698</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=243698"/>
				<updated>2018-09-25T09:16:54Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Updated for a new session&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:siobhan.gallagher@owasp.org Siobhan Gallagher]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter October Session - Wednesday, October 10, 2018'''&lt;br /&gt;
&lt;br /&gt;
6:30pm @ Queens Bernard Crossland Building (https://www.google.com/maps/search/?api=1&amp;amp;query=54.568462%2C-5.948391)&lt;br /&gt;
&lt;br /&gt;
https://www.meetup.com/OWASP-Belfast/events/254737546/&lt;br /&gt;
&lt;br /&gt;
'''Encryption and Digital Certificates – A Guide for Software Developers'''&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast are delighted to announce their October session on Wednesday 10th in the Queens Computer Science building. This session will be a great talk by David Cochrane on encryption and digitial certificates, and will include the usual pizza and drinks.&lt;br /&gt;
&lt;br /&gt;
''Talk: Encryption and Digital Certificates – A Guide for Software Developers''&lt;br /&gt;
&lt;br /&gt;
''Abstract'': This presentation is a tutorial covering the basics of these important technologies but rapidly moving into practical use cases and some more in-depth information to assist troubleshooting. It also includes a case study entitled “Building your own Certifying Authority” that highlights some practical techniques for secure development.&lt;br /&gt;
&lt;br /&gt;
''Speaker Bio'': David Cochrane has responsibility for IT security and risk across the Viridian Group of companies. Viridian Group is an energy utility that owns Power NI and Energia, with over half a million customers throughout Ireland, two power stations and a large portfolio of wind farms. In addition to IT security management, David’s experience includes software design and development, infrastructure design, project management, technical architecture and a range of management roles.&lt;br /&gt;
&lt;br /&gt;
Thanks to Viridian Group for providing the pizzas and drinks for the event, and to Queens University for providing the venue.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Gary_Robinson_2018_Bio_and_Why_me&amp;diff=243461</id>
		<title>Gary Robinson 2018 Bio and Why me</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Gary_Robinson_2018_Bio_and_Why_me&amp;diff=243461"/>
				<updated>2018-09-16T08:15:15Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: /* Bio */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Bio ===&lt;br /&gt;
Hi, I'm Gary Robinson and I've been involved with OWASP since 2011 in most aspects of the organization, including running a chapter, chairing a conference, co-leading a project, and attending numerous conferences, committees, and other behind-the-scene activities.&lt;br /&gt;
&lt;br /&gt;
As a professional, I'd worked for over 15 years as a software developer, pushing security as a discipline and wrapping it into the SDLC.  More recently I've acted as a Senior Application Security Architect at CitiGroup, been a web application penetration tester, and consultant to a number of companies.&lt;br /&gt;
&lt;br /&gt;
I joined OWASP in 2011 to work on the OWASP Code Review Guide v2, and ever since then I've been impressed by the people and passion in the OWASP community.  Some of the highlights of my time in OWASP include:&lt;br /&gt;
* Becoming co-project leader of the OWASP Code Review Guide v2 - https://www.owasp.org/images/5/53/OWASP_Code_Review_Guide_v2.pdf&lt;br /&gt;
* Starting the OWASP Belfast chapter in 2014, for it to become one of the largest chapters in Europe, with over 1000 members (on meetup) and regularly attracting over 100 attendees to our sessions, despite Belfast being a relatively small city. (https://www.meetup.com/OWASP-Belfast/)&lt;br /&gt;
* Chairing OWASP AppSec EU 2017 conference, again in Belfast, which attracted over 700 attendees to become the largest AppSec Europe.&lt;br /&gt;
* Being voted onto the OWASP Europe Board back in 2016.&lt;br /&gt;
&lt;br /&gt;
=== Why Me? ===&lt;br /&gt;
Essentially - I understand the many aspects of what makes OWASP (chapters, projects, conferences) having been heavily involved with these in the past, and going forward I want to represent and enable some potential changes, or research, for OWASP to enable it to function better going forward.  I think it's important to have been involved in all of these OWASP aspects, as it can allow you to know how they feed into each other, how they enable each other, and spot some opportunities for improvement.&lt;br /&gt;
&lt;br /&gt;
In terms of an agenda, there are 3 main things I want to look at:&lt;br /&gt;
# Finances: We have had a few issues over the past few years, which have been very well debated over the leaders list.  These include the Israel/London AppSec conference, the nature of OWASP member/free tickets to these conferences, and the nature of existing funds in chapter accounts. IMO all of these have come down to OWASP finances, and the potential lack of such finances which causes such issues.  I'd like to look at ways OWASP can increase it's finances outside of these areas, such as government funding (worldwide), extra corporate funding (without selling our soul), the nature of the OWASP membership, and other areas.  I know work has already been partially done in these areas, and if we manage to increase the funding to OWASP, we can better enable the community, and OWASP employees, to deliver the OWASP mission.&lt;br /&gt;
# Communication:  Let's face it - it's been lacking.  I want to conduct some focused sessions examining what has gone wrong in the past, what can be done to improve it, and as Picard says &amp;quot;Make it so&amp;quot;.&lt;br /&gt;
# Quality: Project review committees have been attempted in the past, and other aspects of OWASP quality have been talked about, hence I'd like to see if there are ways to do this better in the future.  Perhaps not with volunteers, but with paid employees if we had extra finance or sponsorship (see 1) above).  Having worked on the code review guide, and spent a portion of our funds on review/quality, I know how hard this is to do, and for an industry respected document to have typos and other issues, unfortunately reflects on OWASP as an organization.&lt;br /&gt;
Again, having worked on the team, logistics, and quality of a project, herded the cats and finances of a large conference, and built up a successful chapter, I believe I can represent these aspects of OWASP in the board, and move OWASP forward as an organization.&lt;br /&gt;
&lt;br /&gt;
Thank you,&lt;br /&gt;
&lt;br /&gt;
Gary&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=GSOC2018_Ideas&amp;diff=238083</id>
		<title>GSOC2018 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=GSOC2018_Ideas&amp;diff=238083"/>
				<updated>2018-02-25T14:35:16Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: /* Removing OWASP Code Review Guide */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''OWASP Foundation has been selected as an organization to be part of the GOOGLE SUMMER CODE 2018''' &lt;br /&gt;
&lt;br /&gt;
=OWASP Project Requests=&lt;br /&gt;
&lt;br /&gt;
'''Tips to get you started in no particular order:'''  &lt;br /&gt;
 '''* Read [https://developers.google.com/open-source/gsoc/ Google Summer of Code Program(GSOC)]`'''&lt;br /&gt;
 '''* Read the [[GSoC SAT]] '''&lt;br /&gt;
 * Read the [https://www.owasp.org/index.php/GSoC GSOC Student Guidelines]&lt;br /&gt;
 * Contact us through the mailing list or irc channel.&lt;br /&gt;
 * Check our [https://github.com/OWASP github organization]&lt;br /&gt;
==OWASP ZAP==&lt;br /&gt;
[[OWASP Zed Attack Proxy Project]] (ZAP) The OWASP Zed Attack Proxy (ZAP) is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers. Previous GSoC students have implemented key parts of the ZAP core functionality and have been offered (and accepted) jobs based on their work on ZAP.&lt;br /&gt;
&lt;br /&gt;
We have just included a few of the ideas we have here, for a more complete list see the issues on the ZAP bug tracker with the [https://github.com/zaproxy/zaproxy/issues?q=is%3Aopen+is%3Aissue+label%3Aproject project] label.&lt;br /&gt;
===Active Scanning WebSockets===&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
ZAP has good support for websockets, and allows them to be intercepted, changed and fuzzed. Unfortunately it doesnt current support active scanning (automated attacking) of websockets.&lt;br /&gt;
&lt;br /&gt;
We would like to add active scanning support to websockets, ideally in a generic way which would allow us to reuse as many of our existing rules as are relevant. Adding additional websocket specific attacks would also be very useful.&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
* An plugable infrastructure that allows us to active scan websockets&lt;br /&gt;
* Converting the relevant existing scan rules to work with websockets&lt;br /&gt;
* Implementing new websocket specific scan rules&lt;br /&gt;
&lt;br /&gt;
''' Getting started: '''&lt;br /&gt;
&lt;br /&gt;
* Have a look at the ZAP [https://github.com/zaproxy/zaproxy/blob/develop/CONTRIBUTING.md CONTRIBUTING.md] file, especially the 'Coding section.&lt;br /&gt;
* We like to see students who have already contributed to ZAP, so try fixing one of the bugs flagged as [https://github.com/zaproxy/zaproxy/issues?q=is%3Aopen+is%3Aissue+label%3AIdealFirstBug IdealFirstBug].&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* ZAP is written in Java, so a good knowledge of this language is recommended. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
'''Mentors:''' [https://www.owasp.org/index.php/User:Psiinon Simon Bennetts] [mailto:psiinon@gmail.com @] and the rest of the ZAP Core Team&lt;br /&gt;
&lt;br /&gt;
=== React Handling  ===&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
ZAP doesnt understand React applications as well as it should be able to.&lt;br /&gt;
&lt;br /&gt;
It would be great if ZAP had a much better understanding of such applications, including how to explore and attack them more effectively.&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
* ZAP able to explore React applications more effectively&lt;br /&gt;
* ZAP able to attack React applications more effectively&lt;br /&gt;
&lt;br /&gt;
''' Getting started: '''&lt;br /&gt;
&lt;br /&gt;
* Have a look at the ZAP [https://github.com/zaproxy/zaproxy/blob/develop/CONTRIBUTING.md CONTRIBUTING.md] file, especially the 'Coding section.&lt;br /&gt;
* We like to see students who have already contributed to ZAP, so try fixing one of the bugs flagged as [https://github.com/zaproxy/zaproxy/issues?q=is%3Aopen+is%3Aissue+label%3AIdealFirstBug IdealFirstBug].&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* As React is written in JavaScript, good knowledge of this language is recommended. ZAP is written in Java, so some knowledge of this language would be useful. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
'''Mentors:''' [https://www.owasp.org/index.php/User:Psiinon Simon Bennetts] [mailto:psiinon@gmail.com @] and the rest of the ZAP Core Team&lt;br /&gt;
&lt;br /&gt;
=== Automated authentication detection and configuration  ===&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
Currently a user must manually configure ZAP to handle authentication, eg as per &amp;lt;nowiki&amp;gt;https://github.com/zaproxy/zaproxy/wiki/FAQformauth&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is time consuming and error prone.&lt;br /&gt;
&lt;br /&gt;
Ideally ZAP would help detect login and registration pages and provide more assistance when configuring authentication, ideally being able to completely automate the task for as many sort of webapps as possible.&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
* Detect login and registration pages&lt;br /&gt;
* Provide a wizard to walk users through the process of setting up authentication, with as much assistance as possible&lt;br /&gt;
* An option to completely automate the authentication process, for as many authentication mechanisms as possible&lt;br /&gt;
&lt;br /&gt;
''' Getting started: '''&lt;br /&gt;
&lt;br /&gt;
* Have a look at the ZAP [https://github.com/zaproxy/zaproxy/blob/develop/CONTRIBUTING.md CONTRIBUTING.md] file, especially the 'Coding section.&lt;br /&gt;
* We like to see students who have already contributed to ZAP, so try fixing one of the bugs flagged as [https://github.com/zaproxy/zaproxy/issues?q=is%3Aopen+is%3Aissue+label%3AIdealFirstBug IdealFirstBug].&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* ZAP is written in Java, so a good knowledge of this language is recommended. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
'''Mentors:''' [https://www.owasp.org/index.php/User:Psiinon Simon Bennetts] [mailto:psiinon@gmail.com @] and the rest of the ZAP Core Team&lt;br /&gt;
&lt;br /&gt;
=== Zest Text Representation and Parser ===&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
Zest is a graphical scripting language from the Mozilla Security team, and is used as the ZAP macro language.&lt;br /&gt;
&lt;br /&gt;
A standardized text representation and parser would be very useful and help its adoption.&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
* A documented definition of a text representation for Zest&lt;br /&gt;
* A parser that converts the text representation into a working Zest script&lt;br /&gt;
* An option in the Zest java implementation to output Zest scripts text format&lt;br /&gt;
&lt;br /&gt;
''' Getting started: '''&lt;br /&gt;
&lt;br /&gt;
* Have a look at the ZAP [https://github.com/zaproxy/zaproxy/blob/develop/CONTRIBUTING.md CONTRIBUTING.md] file, especially the 'Coding section.&lt;br /&gt;
* We like to see students who have already contributed to ZAP, so try fixing one of the bugs flagged as [https://github.com/zaproxy/zaproxy/issues?q=is%3Aopen+is%3Aissue+label%3AIdealFirstBug IdealFirstBug].&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* The Zest reference implementation is written in Java, so a good knowledge of this language is recommended. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
'''Mentors:''' [https://www.owasp.org/index.php/User:Psiinon Simon Bennetts] [mailto:psiinon@gmail.com @] and the rest of the ZAP Core Team&lt;br /&gt;
&lt;br /&gt;
=== Develop Bamboo Addon ===&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
It would be great to have an official ZAP add-on for [https://www.atlassian.com/software/bamboo Bamboo], equivalent to the one we now have for [https://wiki.jenkins.io/display/JENKINS/zap+plugin Jenkins]&lt;br /&gt;
&lt;br /&gt;
For more information about Bamboo plugins see the [https://developer.atlassian.com/server/bamboo/bamboo-plugin-guide/ Bamboo plugin guide].&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
&lt;br /&gt;
A Bamboo addon that supports:&lt;br /&gt;
* Spidering (using the traditional and Ajax spiders)&lt;br /&gt;
* Active Scanning&lt;br /&gt;
* Authentication&lt;br /&gt;
&lt;br /&gt;
''' Getting started: '''&lt;br /&gt;
&lt;br /&gt;
* Have a look at the ZAP [https://github.com/zaproxy/zaproxy/blob/develop/CONTRIBUTING.md CONTRIBUTING.md] file, especially the 'Coding section.&lt;br /&gt;
* We like to see students who have already contributed to ZAP, so try fixing one of the bugs flagged as [https://github.com/zaproxy/zaproxy/issues?q=is%3Aopen+is%3Aissue+label%3AIdealFirstBug IdealFirstBug].&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* ZAP and Bamboo are written in Java, so a good knowledge of this language is recommended. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
'''Mentors:''' [https://www.owasp.org/index.php/User:Psiinon Simon Bennetts] [mailto:psiinon@gmail.com @] and the rest of the ZAP Core Team&lt;br /&gt;
&lt;br /&gt;
=== Your Idea ===&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
ZAP is a great framework for building new and innovative security testing solutions. If you have an idea that is not on this list then don't worry, you can still submit it, we have accepted original projects in previous years and have even paid a student to work on their idea when we did not get enough GSoC slots to accept all of the projects we wanted.&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
* A new feature that makes ZAP even better&lt;br /&gt;
* Code that conforms to our Development Rules and Guidelines&lt;br /&gt;
&lt;br /&gt;
''' Getting started: '''&lt;br /&gt;
&lt;br /&gt;
* Have a look at the ZAP [https://github.com/zaproxy/zaproxy/blob/develop/CONTRIBUTING.md CONTRIBUTING.md] file, especially the 'Coding section.&lt;br /&gt;
* We like to see students who have already contributed to ZAP, so try fixing one of the bugs flagged as [https://github.com/zaproxy/zaproxy/issues?q=is%3Aopen+is%3Aissue+label%3AIdealFirstBug IdealFirstBug].&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* ZAP is written in Java, so a good knowledge of this language is recommended. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
'''Mentors:''' [https://www.owasp.org/index.php/User:Psiinon Simon Bennetts] [mailto:psiinon@gmail.com @] and the rest of the ZAP Core Team&lt;br /&gt;
&lt;br /&gt;
== OWASP Juice Shop ==&lt;br /&gt;
&lt;br /&gt;
[[OWASP Juice Shop Project]] is an intentionally insecure webapp for security trainings written entirely in Javascript which encompasses the entire OWASP Top Ten and other severe security flaws. Juice Shop is written in Node.js, Express and AngularJS. The application contains more than 30 challenges of varying difficulty where the user is supposed to exploit the underlying vulnerabilities. Apart from the hacker and awareness training use case, pentesting proxies or security scanners can use Juice Shop as a &amp;quot;guinea pig&amp;quot;-application to check how well their tools cope with Javascript-heavy application frontends and REST APIs.&lt;br /&gt;
&lt;br /&gt;
=== Challenge Pack 2018 ===&lt;br /&gt;
&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
Ideas for potential new hacking challenges are collected in [https://github.com/bkimminich/juice-shop/issues?q=is%3Aissue+is%3Aopen+label%3Achallenge GitHub issues labeled &amp;quot;challenge&amp;quot;]. This project could implement a whole bunch of challenges one by one and release them over the course of several small releases. This would allow the student to work in a professional Continuous Delivery kind of way while bringing benefit to the Juice Shop over the duration of the project.&lt;br /&gt;
&lt;br /&gt;
Coming up with additional ideas for challenges would be part of the project scope, as the list of pre-existing ideas might not be sufficient for a GSoC project.&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
* 10 or more new challenges for OWASP Juice Shop (including required functional enhancements to place the challenges in, e.g. the [https://github.com/bkimminich/juice-shop/issues/244 Order Dashboard] user story])&lt;br /&gt;
* Each challenge comes with full functional unit and integration tests&lt;br /&gt;
* Each challenge is verified to be exploitable by corresponding end-to-end tests&lt;br /&gt;
* Hint and solution sections for each new challenge are added to the &amp;quot;Pwning OWASP Juice Shop&amp;quot; ebook&lt;br /&gt;
* Code follows existing styleguides and passes all existing quality gates regarding code smells, test coverage etc.&lt;br /&gt;
&lt;br /&gt;
''' Getting started: '''&lt;br /&gt;
* Get familiar with the architecture and code base of the application's rich Javascript frontend and RESTful backend&lt;br /&gt;
* Get a feeling for the high code &amp;amp; test quality bar by inspecting the existing test suites and static code analysis results&lt;br /&gt;
* Get familiar with the CI/CD process based on Travis-CI and several associated 3rd party services&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* Javascript, Unit/Integration testing, experience with (or willingness to learn) AngularJS (1.x) and NodeJS/Express, some security knowledge would be preferable.&lt;br /&gt;
&lt;br /&gt;
'''Mentors:'''&lt;br /&gt;
* [[User:Bjoern_Kimminich|Bjoern Kimminich]] - OWASP Juice Shop Project Leader&lt;br /&gt;
* [[User:Timo Pagel|Timo Pagel]] - OWASP Juice Shop Project Collaborator&lt;br /&gt;
* Jannik Hollenbach - OWASP Juice Shop Project Collaborator&lt;br /&gt;
&lt;br /&gt;
=== Frontend Technology Update ===&lt;br /&gt;
&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
Development of OWASP Juice Shop started in 2014 and was based on - back then - quite recent Javascript frontend framework AngularJS 1.x along with Bootstrap 3. Several major releases later, there now are [https://github.com/bkimminich/juice-shop/issues/165 Angular 5] and [https://github.com/bkimminich/juice-shop/issues/400 Bootstrap 4] available as well as other mature web frontend frameworks. Migrating the OWASP Juice Shop to the latest version of Angular and Bootstrap is an important step to keep the application relevant as ''the most modern'' intentionally broken web application. Moving to entirely different frameworks might be taken into considerationas well.&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
* High-level target client-architecture overview including a migration plan with intermediary milestones&lt;br /&gt;
* Execution of migration without breaking functionality or losing tests along the way&lt;br /&gt;
* Code follows existing (or new) styleguides and passes all existing (or new) quality gates regarding code smells, test coverage etc.&lt;br /&gt;
&lt;br /&gt;
''' Getting started: '''&lt;br /&gt;
* Get familiar with the architecture and code base of the application's rich Javascript frontend and RESTful backend&lt;br /&gt;
* Get a feeling for the high code &amp;amp; test quality bar by inspecting the existing test suites and static code analysis results&lt;br /&gt;
* Get familiar with the CI/CD process based on Travis-CI and several associated 3rd party services&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* Javascript, experience with latest Javascript frameworks for frontend, testing and building&lt;br /&gt;
&lt;br /&gt;
'''Mentors:'''&lt;br /&gt;
* [[User:Bjoern_Kimminich|Bjoern Kimminich]] - OWASP Juice Shop Project Leader&lt;br /&gt;
* Jannik Hollenbach - OWASP Juice Shop Project Collaborator&lt;br /&gt;
&lt;br /&gt;
=== UI/Graphics Design Update ===&lt;br /&gt;
&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
The UI of OWASP Juice Shop was written following recommendations from Twitter Bootstrap to be responsive, but it never had an actual designer or graphics artist take a look or add some insight. Currently the look &amp;amp; feel comes &amp;quot;out of the box&amp;quot; from a [https://bootswatch.com Bootswatch] theme and [https://fontawesome.com Font Awesome 5] icons. This gives it a quite modern look, but also leaves it very generic. The project could greatly benefit from involvement of someone with actual UI/UX Design expertise. Having a matching theme for [https://ctfd.io CTFd] would be another big achievement for the Juice Shop.&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
* Design concepts to pick or have the user community vote on (including color schemes, sample screens, icons etc.)&lt;br /&gt;
* Overhauling the overall UI look &amp;amp; feel, e.g. by making an individual Bootswatch theme or designing some individual icons&lt;br /&gt;
* &amp;lt;del&amp;gt;Getting rid of the stock images by providing individually designed product images for the standard inventory of the shop&amp;lt;/del&amp;gt; ([https://github.com/bkimminich/juice-shop/issues/315 #315] in progress)&lt;br /&gt;
* Add more flexibility and options to the existing theming/customization of the UI (see [https://github.com/bkimminich/juice-shop/issues/379 #379])&lt;br /&gt;
* Design a [https://github.com/bkimminich/juice-shop-ctf/issues/9 &amp;quot;Juice Shop&amp;quot; CTFd-theme] playing well with the look &amp;amp; feel of the application&lt;br /&gt;
* Execution of migration without breaking functionality or client-side unit and end-to-end tests along the way&lt;br /&gt;
&lt;br /&gt;
''' Getting started: '''&lt;br /&gt;
* Get familiar with the existing HTML views and CSS of the frontend&lt;br /&gt;
* Get a feeling for the high quality bar by inspecting the existing client-side unit and e2e test suites&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* Strong web and graphic design experience&lt;br /&gt;
* Sophisticated HTML and CSS experience&lt;br /&gt;
&lt;br /&gt;
'''Mentors:'''&lt;br /&gt;
* [[User:Bjoern_Kimminich|Bjoern Kimminich]] - OWASP Juice Shop Project Leader&lt;br /&gt;
* [[User:Timo Pagel|Timo Pagel]] - OWASP Juice Shop Project Collaborator&lt;br /&gt;
* Jannik Hollenbach - OWASP Juice Shop Project Collaborator&lt;br /&gt;
&lt;br /&gt;
=== Your idea ===&lt;br /&gt;
&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
You have an awesome idea to improve OWASP Juice Shop that is not on this list? Great, please submit it!&lt;br /&gt;
&lt;br /&gt;
''' Getting started '''&lt;br /&gt;
* Get in touch with [https://www.owasp.org/index.php/User:Bjoern_Kimminich Bjoern Kimminich]&lt;br /&gt;
&lt;br /&gt;
'''Expected Results:'''&lt;br /&gt;
* A new feature that makes OWASP Juice Shop even better&lt;br /&gt;
* Code follows existing styleguides and passes all existing quality gates regarding code smells, test coverage etc.&lt;br /&gt;
&lt;br /&gt;
'''Knowledge Prerequisites:'''&lt;br /&gt;
* Javascript, Unit/Integration testing, experience with (or willingness to learn) AngularJS and NodeJS/Express, some security knowledge would be preferable.&lt;br /&gt;
&lt;br /&gt;
'''Mentors:''' &lt;br /&gt;
* [[User:Bjoern_Kimminich|Bjoern Kimminich]] - OWASP Juice Shop Project Leader&lt;br /&gt;
&lt;br /&gt;
==OWASP Security Knowledge Framework - Chatbot machine learning feature==&lt;br /&gt;
&lt;br /&gt;
=== Brief Explanation ===&lt;br /&gt;
We want to create a SKF Chatbot service using the knowledge already inside SKF like the knowledge base items, code examples and the security controls like ASVS and PCI DSS.&lt;br /&gt;
&lt;br /&gt;
The chatbot service and core of this new feature can be consumed by website’s as an addon, IDE of developers and website chat channels like Gitter.im.&lt;br /&gt;
&lt;br /&gt;
The core of the SKF Chatbot will be using machine learning to accomplish the hard task of correlating data and merging different sources as a response/answer.&lt;br /&gt;
&lt;br /&gt;
=== Expected Results ===&lt;br /&gt;
# A Defined Knowledge Base (Data Structure / DB) which can be used to define and search for entities. For example: if a query is:&lt;br /&gt;
## How to mitigate CSRF in PHP   the system should be able to understand or translate it to:  {How: intent} to {mitigate: solution} {CSRF: attack} in {PHP: programming language}  This kind of query can be further user to fetch right information in the knowledge base and provide right solution (code example) for mitigating CSRF in PHP.&lt;br /&gt;
## What is CSRF?   the system should be able to understand or translate it to:  {What: intent} is {CSRF: attack/defense}  This kind of query can be further user to fetch right information in the knowledge base that explains CSRF and provide the security control from example ASVS&lt;br /&gt;
# An ETL process to convert existing SKF Knowledge data and ASVS data to above mentioned data structure.&lt;br /&gt;
# A Chatbot (using existing frameworks) to:&lt;br /&gt;
## Understand at least two intent like (How to, What is …..) and be able to enrich the user query as mentioned above.&lt;br /&gt;
## Based on enriched query fetch relevant information from knowledge base and return.&lt;br /&gt;
# An integration to some chat system like Gitter.im, IRC, Slack etc.&lt;br /&gt;
&lt;br /&gt;
=== Knowledge Prerequisites ===&lt;br /&gt;
* Programming languages:&lt;br /&gt;
** OWASP-SKF API is build in Python 3.6/3.7&lt;br /&gt;
** OWASP-SKF Frontend is build with Angular 4 TS&lt;br /&gt;
* Machine learning enthusiastic/interest&lt;br /&gt;
&lt;br /&gt;
=== Proposal from student ===&lt;br /&gt;
* We want to ask from the student to write a proposal on how to approach the problem we described.&lt;br /&gt;
'''Mentors''':&lt;br /&gt;
&lt;br /&gt;
Riccardo ten Cate [mailto:riccardo.ten.cate@owasp.org] Glenn ten Cate [mailto:glenn.ten.cate@owasp.org] Minhaz [mailto:minhaz@owasp.org]&lt;br /&gt;
&lt;br /&gt;
==OWASP Nettacker==&lt;br /&gt;
===Brief Explanation===&lt;br /&gt;
OWASP Nettacker project is created to automate information gathering, vulnerability scanning and eventually generating a report for networks, including services, bugs, vulnerabilities, misconfigurations, and other information. This software will utilize TCP SYN, ACK, ICMP and many other protocols in order to detect and bypass Firewall/IDS/IPS devices. By leveraging a unique method in OWASP Nettacker for discovering protected services and devices such as SCADA. It would make a competitive edge compared to other scanner making it one of the bests.&lt;br /&gt;
&lt;br /&gt;
if you need more details please visit the [https://github.com/viraintel/OWASP-Nettacker GitHub page] or contact a leader([mailto:ali.razmjoo@owasp.org Ali Razmjoo Qalaei], [mailto:reza.espargham@owasp.org Reza Espargham]).&lt;br /&gt;
&lt;br /&gt;
===Getting started===&lt;br /&gt;
&lt;br /&gt;
* You may read the available documents in the [https://github.com/viraintel/OWASP-Nettacker/wiki wiki page]. Developers and users documents are separated.&lt;br /&gt;
&lt;br /&gt;
'''A Better Penetration Testing Automated Framework'''&lt;br /&gt;
&lt;br /&gt;
===Expected Results===&lt;br /&gt;
The expected results are to contribute the OWASP Nettacker framework [https://github.com/viraintel/OWASP-Nettacker/issues issues] (mostly help wanted or enhancement). Please check the GitHub repo to learn more.&lt;br /&gt;
&lt;br /&gt;
===Knowledge Prerequisites===&lt;br /&gt;
&lt;br /&gt;
* The whole framework was written in Python language. You must be familiar with Python 2.x, 3.x.&lt;br /&gt;
* Good knowledge of computer security (and penetration testing)&lt;br /&gt;
* Knowledge of OS (Linux, Windows, Mac...) and Services&lt;br /&gt;
* Familiar with IDS/IPS/Firewalls and ...&lt;br /&gt;
* To develop the API you should be familiar with HTTP, Database...&lt;br /&gt;
&lt;br /&gt;
===Mentors===&lt;br /&gt;
Mentors are: [mailto:ali.razmjoo@owasp.org Ali Razmjoo Qalaei], [mailto:abiusx@owasp.org Abbas Naderi Afooshteh]&lt;br /&gt;
&lt;br /&gt;
==OWASP OWTF==&lt;br /&gt;
'''[https://github.com/owtf/owtf Offensive Web Testing Framework (OWTF)]''' is a project focused on penetration testing efficiency and alignment of security tests to security standards like the OWASP Testing Guide (v3 and v4), the OWASP Top 10, PTES and NIST. Most of the ideas below focus on rewrite of some major components of OWTF to make it more modular. OWTF is moving to a fresh codebase with a fully Docker testing and deployment environment. If you want to get a jumpstart, check out https://github.com/owtf/owtf/tree/new-arch.&lt;br /&gt;
===OWASP OWTF - MiTM proxy interception and replay capabilities===&lt;br /&gt;
'''Brief Explanation:'''&lt;br /&gt;
&lt;br /&gt;
The OWTF man-in-the-middle proxy is written completely in Python (based on the excellent Tornado framework) and was benchmarked to be the fastest MiTM python proxy. However it lacks the useful and much need interception and replay capabilities of mitmproxy (https://github.com/mitmproxy/mitmproxy).&lt;br /&gt;
&lt;br /&gt;
The current implementation of the MiTM proxy serves its purpose very well. Its fast but its not extensible. There are a number of good use cases for being extensible&lt;br /&gt;
*ability to intercept the transactions&lt;br /&gt;
*modify or replay transaction on the fly&lt;br /&gt;
*add additional capabilities to the proxy (such as session marking/changing) without polluting the main proxy code&lt;br /&gt;
Bonus:&lt;br /&gt;
*Design and implement a proxy plugin (middleware) architecture so that the plugins can be defined separately and the user can choose what plugins to include dynamically (from the web interface).&lt;br /&gt;
*Replace the current Requester (based on urllib, urllib2) with a more robust Requester based on the new urllib3 with support for a real headless browser factory. The typical flow when requested for an authenticated browser instance (using PhantomJS)&lt;br /&gt;
&lt;br /&gt;
*The &amp;quot;Requester&amp;quot; module checks if there is any login parameters provided (i.e form-based or script - look at https://github.com/owtf/login-sessions-plugin)&lt;br /&gt;
*Create a browser instance and do the necessary login procedure&lt;br /&gt;
*Handle the browser for the URI&lt;br /&gt;
*When called to close the browser, do a clean logout and kill the browser instance.&lt;br /&gt;
'''Expected results:'''&lt;br /&gt;
*'''IMPORTANT: [http://legacy.python.org/dev/peps/pep-0008/ PEP-8 compliant code] in all modified code and surrounding areas.'''&lt;br /&gt;
*'''IMPORTANT: [https://github.com/7a/owtf/wiki/Contributor%27s-README OWTF contributor README compliant code]'''&lt;br /&gt;
*'''IMPORTANT: [http://sphinx-doc.org/ Sphinx-friendly python comments] [http://owtf.github.io/ptp/_modules/ptp/tools/w3af/parser.html#W3AFXMLParser example Sphinx-friendly python comments here]'''&lt;br /&gt;
*CRITICAL: Excellent reliability&lt;br /&gt;
*Good performance&lt;br /&gt;
*Unit tests / Functional tests&lt;br /&gt;
*Good documentation&lt;br /&gt;
'''Knowledge Prerequisite:''' Python proficiency, some previous exposure to security concepts and penetration testing is welcome but not strictly necessary as long as there is will to learn.&lt;br /&gt;
&lt;br /&gt;
'''OWASP OWTF Mentors:''' Contact: [mailto:Abraham.Aranguren@owasp.org Abraham Aranguren][mailto:viyat.bhalodia@owasp.org Viyat Bhalodia][mailto:bharadwaj.machiraju@gmail.com Bharadwaj Machiraju] OWASP OWTF Project Leaders&lt;br /&gt;
===OWASP OWTF - Web interface enhancements===&lt;br /&gt;
'''Brief explanation:'''&lt;br /&gt;
&lt;br /&gt;
The current web interface is a mixture of Tornado Jinja templates and ReactJS. A complete UI change to a stable ReactJS-based interface should be the deliverable for this project.  Most of the hard part for the change has already been done and added in a separate branch at https://github.com/owtf/owtf/tree/develop.&lt;br /&gt;
&lt;br /&gt;
For background on OWASP OWTF please see: https://www.owasp.org/index.php/OWASP_OWTF&lt;br /&gt;
&lt;br /&gt;
'''Expected results:'''&lt;br /&gt;
*'''IMPORTANT:Clean, maintainable (ES6 compatible and using recommended design patterns) React (JavaScript) code. ([https://github.com/getsentry/zeus/tree/master/webapp This] is a good example!)'''&lt;br /&gt;
*'''IMPORTANT: Thoroughly documented code along with API examples and example future components.'''&lt;br /&gt;
*'''CRITICAL''': Excellent reliability and performance.&lt;br /&gt;
*Unit tests / Functional tests and easy to setup testing environment (preferably automated).&lt;br /&gt;
'''Knowledge Prerequisite:''' Python (reading API source code and endpoints), React.JS (high proficiency) and general JavaScript proficiency.&lt;br /&gt;
&lt;br /&gt;
'''OWASP OWTF Mentors:''' Contact: [mailto:Abraham.Aranguren@owasp.org Abraham Aranguren][mailto:viyat.bhalodia@owasp.org Viyat Bhalodia][mailto:bharadwaj.machiraju@gmail.com Bharadwaj Machiraju] OWASP OWTF Project Leaders&lt;br /&gt;
===OWASP OWTF - New plugin architecture===&lt;br /&gt;
'''Brief explanation:'''&lt;br /&gt;
&lt;br /&gt;
The current plugin system is not very useful and it is painful to browse many plugins. Most of the plugins do have much code and most of is repeated - much refactoring needed there.&lt;br /&gt;
&lt;br /&gt;
This issue is documented in detail at https://github.com/owtf/owtf/issues/905.&lt;br /&gt;
&lt;br /&gt;
For background on OWASP OWTF please see: https://www.owasp.org/index.php/OWASP_OWTF&lt;br /&gt;
&lt;br /&gt;
'''Expected results:'''&lt;br /&gt;
*'''IMPORTANT: [http://legacy.python.org/dev/peps/pep-0008/ PEP-8 compliant code] in all modified code and surrounding areas.'''&lt;br /&gt;
*'''IMPORTANT: [https://github.com/7a/owtf/wiki/Contributor%27s-README OWTF contributor README compliant code]'''&lt;br /&gt;
*'''IMPORTANT: [http://sphinx-doc.org/ Sphinx-friendly python comments] [http://owtf.github.io/ptp/_modules/ptp/tools/w3af/parser.html#W3AFXMLParser example Sphinx-friendly python comments here]'''&lt;br /&gt;
*CRITICAL: Excellent reliability&lt;br /&gt;
*Good performance&lt;br /&gt;
*Unit tests / Functional tests&lt;br /&gt;
*Good documentation&lt;br /&gt;
&lt;br /&gt;
== OWASP CSRF Protector ==&lt;br /&gt;
[[CSRFProtector Project|OWASP CSRF Protector Project]] is a project started with the goal to help developer to mitigate CSRF in web applications with ease. It's based on [[Cross-Site Request Forgery (CSRF) Prevention Cheat Sheet|Synchronizer Token Pattern]] and leverages an injected java-script code to provide CSRF mitigation without much developer intervention. So far it has been implemented as a [https://github.com/mebjas/CSRF-Protector-PHP PHP Library] and an [[CSRFProtector Project|Apache 2.2.x module]]. Although different libraries and frameworks provide CSRF mitigation these days - all of them require developer to explicitly inject tokens with every form. &lt;br /&gt;
===OWASP CSRF Protector - Extending the design as a python package to work with Flask and an Express JS (Node.JS) middleware===&lt;br /&gt;
'''Brief explanation:'''&lt;br /&gt;
&lt;br /&gt;
The design of CSRF Protector involves a server side middle-ware that intercepts every incoming request and validates them for CSRF attacks. If the validation is successful the flow of control goes to business logic and the tokens are refreshed. In case of failed validation configured actions are taken. Post that, another middle ware takes care of injecting a JavaScript code (refer [https://github.com/mebjas/CSRF-Protector-PHP/blob/master/js/csrfprotector.js CSRF Protector PHP JS Code]) to HTML output. On the client side this code ensures that, for every request that require validation - the correct token is sent along with the request.&lt;br /&gt;
&lt;br /&gt;
Check [https://github.com/mebjas/CSRF-Protector-PHP/wiki GitHub Wiki] for some reference;&lt;br /&gt;
&lt;br /&gt;
The goal of this project would be to:&lt;br /&gt;
# Port this design to a python module that can be used easily with Flask - [https://github.com/mebjas/CSRF-Protector-py/projects/1?add_cards_query=is%3Aopen Kanban Board]&lt;br /&gt;
# Port this design to a node js module that can work well with express js (a popular Node.JS based framework). - [https://github.com/mebjas/CSRF-Protector-JS Initial Repo Link]&lt;br /&gt;
# Fix some outstanding issues with java-script code used in library: [https://github.com/mebjas/CSRF-Protector-PHP/issues?q=is%3Aopen+is%3Aissue+label%3AJS Issues] &lt;br /&gt;
'''Expected results:'''&lt;br /&gt;
*'''IMPORTANT: Clean, maintainable (ES6 compatible and using recommended design patterns) in case of Node.JS'''&lt;br /&gt;
*'''IMPORTANT: [http://legacy.python.org/dev/peps/pep-0008/ PEP-8 compliant code] in all modified code and surrounding areas.'''&lt;br /&gt;
*'''IMPORTANT: Thoroughly documented code along with API examples and example future components.'''&lt;br /&gt;
*'''CRITICAL''': Excellent reliability and performance.&lt;br /&gt;
*Unit tests / Functional tests and easy to setup testing environment (preferably automated).&lt;br /&gt;
'''Knowledge Prerequisite:''' Javascript (Client Side), Python (having worked with flask preferable), Node.JS (having worked with node.js and middle wares preferable)&lt;br /&gt;
&lt;br /&gt;
'''Mentors:''' Contact: [mailto:minhaz@owasp.org;minhazv@microsoft.com Minhaz A V]&lt;br /&gt;
== OWASP BLT (Bug Logging Tool) ==&lt;br /&gt;
===Brief Explanation:===&lt;br /&gt;
&lt;br /&gt;
BLT lets anyone report issues they find on the internet. Found something out of place on Amazon.com ?  Let them know.  Companies are held accountable and shows their response time and history.  Get points for reporting bugs and help keep the internet bug free.&lt;br /&gt;
&lt;br /&gt;
Check OWASP WIKI PAGE [https://www.owasp.org/index.php/OWASP_Bug_Logging_Tool] for some reference;&lt;br /&gt;
&lt;br /&gt;
===Expected Results:===&lt;br /&gt;
* Fuse app to allow easy bug reporting from phone.&lt;br /&gt;
* BUG cryptocurrency rewarded for each bug reported - requires a way to verify bugs are valid and not duplicates&lt;br /&gt;
* Allow for companies to do private (paid) bug bounties&lt;br /&gt;
* allow for bug reporting via email &lt;br /&gt;
* build a referral program&lt;br /&gt;
* integrate an idea / suggestion feature&lt;br /&gt;
&lt;br /&gt;
===Knowledge Prerequisite:===&lt;br /&gt;
BLT is written in Python / Django, so a good knowledge of this language and framework is recommended, as is knowledge of HTML. Some knowledge of application security would be useful, but not essential. Fusetools will be used for the app and C++ (Bitcoin based) or Ethereum will be used for the cryptocurrency part.&lt;br /&gt;
&lt;br /&gt;
===Proposals from student:===&lt;br /&gt;
* Proposal on new features &lt;br /&gt;
* Recommendations on how to use social applications to promote OWASP BLT&lt;br /&gt;
&lt;br /&gt;
'''Mentors:'''&lt;br /&gt;
* Sean Auriti [https://www.owasp.org/index.php/User:Sauriti Sean Auriti] [mailto:sean.auriti@owasp.org @] &lt;br /&gt;
* Sourav Badami [https://www.owasp.org/index.php/User:Souravbadami Sourav Badami] [mailto:souravbadami@gmail.com @]&lt;br /&gt;
&lt;br /&gt;
==OWASP RailsGoat - 2017 OWASP Top Ten==&lt;br /&gt;
&lt;br /&gt;
===Brief Explanation:===&lt;br /&gt;
Add support for multiple OWASP Top Ten versions, such as 2017 and 2010.&lt;br /&gt;
Currently RailsGoat supports only the 2013 version of OWASP Top Ten.&lt;br /&gt;
&lt;br /&gt;
===Expected Results:===&lt;br /&gt;
* Wonderful experience for Student Developers, Mentors, and Technical Advisors&lt;br /&gt;
* A new feature that supports additional version(s) of OWASP Top Ten&lt;br /&gt;
* Code that conforms to our Development Rules and Guidelines&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
* Have a look at the RailsGoat https://github.com/OWASP/railsgoat/blob/master/README.md file, especially the 'Getting Started' section. We like to see student developers who have already contributed to RailsGoat, so try fixing one of the bugs.&lt;br /&gt;
* We have created a dedicated wiki for the OWASP GSOC initiative: https://github.com/OWASP/railsgoat/wiki/RailsGoat-Summer-of-Code-Type-Project-Information&lt;br /&gt;
* Issue 305 [https://github.com/OWASP/railsgoat/issues/305] has more details. &lt;br /&gt;
&lt;br /&gt;
===Knowledge Prerequisite:===&lt;br /&gt;
* RailsGoat is written in Ruby and Ruby-on-Rails, so a good knowledge of this language ecosystem is recommended. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
&lt;br /&gt;
'''Mentors:'''&lt;br /&gt;
* Frank Rietta [mailto:frank@rietta.com] - OWASP RailsGoat Mentor&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Ken Ken Johnson @] - OWASP RailsGoat &amp;quot;Technical Advisor, potentially mentor&amp;quot;&lt;br /&gt;
* Al Snow [mailto:jasnow@hotmail.com] - OWASP RailsGoat Project Coordinator&lt;br /&gt;
&lt;br /&gt;
==OWASP RailsGoat - Capture-The-Flag RailsGoat Image Creation Automation==&lt;br /&gt;
&lt;br /&gt;
===Brief Explanation:===&lt;br /&gt;
Create automation to build a Capture-The-Flag competition (CTF) image (VM, ISO, etc) which contains everything needed, such as [Operating System, Rails Stack, RailsGoat], so RailsGoat can easily be used in more Capture-The-Flag competitions.&lt;br /&gt;
&lt;br /&gt;
===Expected Results:===&lt;br /&gt;
* Wonderful experience for Student Developers, Mentors, and Technical Advisors&lt;br /&gt;
* A new feature that automates the process of building RailsGoat CTF images.&lt;br /&gt;
* Code that conforms to our Development Rules and Guidelines&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
* Have a look at the RailsGoat https://github.com/OWASP/railsgoat/blob/master/README.md file, especially the 'Getting Started' section. We like to see student developers who have already contributed to RailsGoat, so try fixing one of the bugs.&lt;br /&gt;
* We have created a dedicated wiki for the OWASP GSOC initiative: https://github.com/OWASP/railsgoat/wiki/RailsGoat-Summer-of-Code-Type-Project-Information&lt;br /&gt;
* Issue 306 [https://github.com/OWASP/railsgoat/issues/306] has more details. &lt;br /&gt;
&lt;br /&gt;
===Knowledge Prerequisite:===&lt;br /&gt;
* Some background in creating VMs/ISOs would be helpful.&lt;br /&gt;
* RailsGoat is written in Ruby and Ruby-on-Rails, so a good knowledge of this language ecosystem is recommended. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
&lt;br /&gt;
'''Mentors:'''&lt;br /&gt;
* Frank Rietta [mailto:frank@rietta.com] - OWASP RailsGoat Mentor&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Ken Ken Johnson @] - OWASP RailsGoat &amp;quot;Technical Advisor, potentially mentor&amp;quot;&lt;br /&gt;
* Al Snow [mailto:jasnow@hotmail.com] - OWASP RailsGoat Project Coordinator&lt;br /&gt;
&lt;br /&gt;
==OWASP RailsGoat - Merge &amp;quot;Security on Rails&amp;quot; book's lunchedin examples into RailsGoat==&lt;br /&gt;
&lt;br /&gt;
===Brief Explanation:===&lt;br /&gt;
Merge &amp;quot;Security on Rails&amp;quot; book's lunchedin examples into RailsGoat. Need to get permission from publisher. @jasnow got permission previously.&lt;br /&gt;
&lt;br /&gt;
===Expected Results:===&lt;br /&gt;
* Wonderful experience for Student Developers, Mentors, and Technical Advisors&lt;br /&gt;
* More teaching RailsGoat examples based on &amp;quot;Security on Rails&amp;quot; book's lunchedin project.&lt;br /&gt;
* Code that conforms to our Development Rules and Guidelines&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
* Have a look at the RailsGoat https://github.com/OWASP/railsgoat/blob/master/README.md file, especially the 'Getting Started' section. We like to see student developers who have already contributed to RailsGoat, so try fixing one of the bugs.&lt;br /&gt;
* We have created a dedicated wiki for the OWASP GSOC initiative: https://github.com/OWASP/railsgoat/wiki/RailsGoat-Summer-of-Code-Type-Project-Information&lt;br /&gt;
* Issue 307 [https://github.com/OWASP/railsgoat/issues/307] has more details. &lt;br /&gt;
&lt;br /&gt;
===Knowledge Prerequisite:===&lt;br /&gt;
* RailsGoat is written in Ruby and Ruby-on-Rails, so a good knowledge of this language ecosystem is recommended. Some knowledge of application security&lt;br /&gt;
would be useful, but not essential.&lt;br /&gt;
&lt;br /&gt;
'''Mentors:'''&lt;br /&gt;
* Frank Rietta [mailto:frank@rietta.com] - OWASP RailsGoat Mentor&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Ken Ken Johnson @] - OWASP RailsGoat &amp;quot;Technical Advisor, potentially mentor&amp;quot;&lt;br /&gt;
* Al Snow [mailto:jasnow@hotmail.com] - OWASP RailsGoat Project Coordinator&lt;br /&gt;
&lt;br /&gt;
==OWASP RailsGoat - Add Devise Gem Support and Vulnerabilities to RailsGoat==&lt;br /&gt;
&lt;br /&gt;
===Brief Explanation:===&lt;br /&gt;
Add Devise Support to RailsGoat along with adding Devise-related vulnerabilities.&lt;br /&gt;
&lt;br /&gt;
===Expected Results:===&lt;br /&gt;
* Wonderful experience for Student Developers, Mentors, and Technical Advisors&lt;br /&gt;
* Using Devise gem inside RailsGoat plus Devise-related vulnerabilities.&lt;br /&gt;
* Code that conforms to our Development Rules and Guidelines&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
* Have a look at the RailsGoat https://github.com/OWASP/railsgoat/blob/master/README.md file, especially the 'Getting Started' section. We like to see student developers who have already contributed to RailsGoat, so try fixing one of the bugs.&lt;br /&gt;
* We have created a dedicated wiki for the OWASP GSOC initiative: https://github.com/OWASP/railsgoat/wiki/RailsGoat-Summer-of-Code-Type-Project-Information&lt;br /&gt;
* Issue 207 [https://github.com/OWASP/railsgoat/issues/207] and * Issue 243 [https://github.com/OWASP/railsgoat/issues/243] has more details.&lt;br /&gt;
&lt;br /&gt;
===Knowledge Prerequisite:===&lt;br /&gt;
* RailsGoat is written in Ruby and Ruby-on-Rails, so a good knowledge of this language ecosystem is recommended. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
&lt;br /&gt;
'''Mentors:'''&lt;br /&gt;
* Frank Rietta [mailto:frank@rietta.com] - OWASP RailsGoat Mentor&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Ken Ken Johnson @] - OWASP RailsGoat &amp;quot;Technical Advisor, potentially mentor&amp;quot;&lt;br /&gt;
* Al Snow [mailto:jasnow@hotmail.com] - OWASP RailsGoat Project Coordinator&lt;br /&gt;
&lt;br /&gt;
==OWASP RailsGoat - Generic Idea==&lt;br /&gt;
&lt;br /&gt;
===Brief Explanation:===&lt;br /&gt;
RailsGoat is a great framework for learning about OWASP Top 10 2013 using a vulnerable version of the Ruby on Rails (versions 3 to 5), as well as some &amp;quot;extras&amp;quot; that the initial project contributors felt worthwhile to share. This project is designed to educate both developers, as well as security professionals. Feel free to check out the [Railsgoat Github site](https://github.com/OWASP/railsgoat) for more details. If you have an idea that is not on this list then don't worry, you can still submit it.&lt;br /&gt;
&lt;br /&gt;
===Expected Results:===&lt;br /&gt;
* Wonderful experience for Student Developers, Mentors, and Technical Advisors&lt;br /&gt;
* A new feature that makes RailsGoat even better&lt;br /&gt;
* Code that conforms to our Development Rules and Guidelines&lt;br /&gt;
&lt;br /&gt;
=== Needs: ===&lt;br /&gt;
* Student Developers&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
* Have a look at the RailsGoat https://github.com/OWASP/railsgoat/blob/master/README.md file, especially the 'Getting Started' section. We like to see student developers who have already contributed to RailsGoat, so try fixing one of the bugs.&lt;br /&gt;
&lt;br /&gt;
===Knowledge Prerequisite:===&lt;br /&gt;
* RailsGoat is written in Ruby and Ruby-on-Rails, so a good knowledge of this language ecosystem is recommended. Some knowledge of application security would be useful, but not essential.&lt;br /&gt;
'''Mentors:'''&lt;br /&gt;
* Frank Rietta [mailto:frank@rietta.com] - OWASP RailsGoat Mentor&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Ken Ken Johnson @] - OWASP RailsGoat &amp;quot;Technical Advisor, potentially mentor&amp;quot;&lt;br /&gt;
* Al Snow [mailto:jasnow@hotmail.com] - OWASP RailsGoat Project Coordinator&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=235991</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=235991"/>
				<updated>2017-12-04T11:45:56Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Update for Dec session&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:siobhan.gallagher@owasp.org Siobhan Gallagher]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter December Session - Tuesday, December 5th 2017'''&lt;br /&gt;
&lt;br /&gt;
6:30pm @ Liberty IT&lt;br /&gt;
&lt;br /&gt;
https://www.meetup.com/OWASP-Belfast/events/245434502/&lt;br /&gt;
&lt;br /&gt;
'''Have you got what it takes to be one of Ireland’s most secure coders?'''&lt;br /&gt;
&lt;br /&gt;
Join the FIRST EVER All-Ireland OWASP Secure Coding Tournament, with venues in Belfast, along with Dublin &amp;amp; Cork. Whether you are eager to prove your web application AppSec knowledge of the OWASP Top 10 ….and watch as you climb to the top of the Leader board or simply want to learn more at your ease about how to code more securely.&lt;br /&gt;
&lt;br /&gt;
Note that this is a practical session - EVERYONE is welcome.&lt;br /&gt;
&lt;br /&gt;
In each challenge, participants will be presented with a series of vulnerable code snippets and will be required to identify the problem, locate the insecure code, and fix the vulnerability. Select from various software languages to complete the tournament, including: Java EE, Java Spring, C# MVC, C# WebForms, Ruby on Rails, Python Django &amp;amp; Node.Js.&lt;br /&gt;
&lt;br /&gt;
Watch as you climb to the top of the leaderboard and be crowned a 'Secure Code Warrior.'  Prizes will be provided to the top three warriors. Please ensure you come with your laptop fully charged, there will be some charging facilities but it would be better for you to arrive prepared.&lt;br /&gt;
&lt;br /&gt;
To learn more about what to expect during the Tournament and sharpen your skills beforehand, register your account and work through challenges on our Training Mode. Simply, use the link and token key below:&lt;br /&gt;
&lt;br /&gt;
Registration is available in the weeks before the session, we recommend you register before the session starts:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;nowiki&amp;gt;https://portal.securecodewarrior.com/#/register&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Token Key: 027 549 455 533&lt;br /&gt;
&lt;br /&gt;
Big thanks to Liberty IT for their sponsorship of this session through use of their facilities, as well as providing pizza and drinks during the session.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=234358</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=234358"/>
				<updated>2017-10-13T14:45:43Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: /* Local News */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:siobhan.gallagher@owasp.org Siobhan Gallagher]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter November Session - Wednesday, November 15th 2017'''&lt;br /&gt;
&lt;br /&gt;
6:00pm @ 6th Floor, Lombard House, Belfast&lt;br /&gt;
&lt;br /&gt;
https://www.meetup.com/OWASP-Belfast/events/244109993/&lt;br /&gt;
&lt;br /&gt;
'''Cyber Incident Detection in an Emergency'''&lt;br /&gt;
&lt;br /&gt;
Ever wondered how to know if you’re being hacked in the middle of an emergency?&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast’s November session can help you out.  In this session we’ll be covering Cyber Incident Detection in the middle of an emergency.  This talk will be given by David McGlade, Cyber Security Lead at Kainos, one of Northern Irelands most successful software companies.&lt;br /&gt;
&lt;br /&gt;
This session will be held on the 6th floor or Lombard House, through the kind hosting of Entrepreneurial Spark and Ulster Bank.  This also allows us to recognize Global Entrepreneurship Week and the many support facilities available to Northern Irish companies, including cyber security start-ups.&lt;br /&gt;
&lt;br /&gt;
Join us on Wednesday 15th November, from 6pm to 8pm, for pizza, drinks and talks.  Special thanks to Kainos for sponsoring food and drinks on the night.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=234195</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=234195"/>
				<updated>2017-10-07T14:50:25Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Updated for Oct session&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:siobhan.gallagher@owasp.org Siobhan Gallagher]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter October Session - Monday, October 9th 2017'''&lt;br /&gt;
&lt;br /&gt;
6:00pm @ Queens Ashby building, Belfast&lt;br /&gt;
&lt;br /&gt;
https://www.meetup.com/OWASP-Belfast/events/243114644/&lt;br /&gt;
&lt;br /&gt;
'''Security Biometrics'''&lt;br /&gt;
&lt;br /&gt;
In this session we're going to take a look at biometrics technology with the local security company B-secur.  They have invented electrocardiogram (ECG) biometric technology that utilizes a person’s unique heartbeat for authentication.&lt;br /&gt;
&lt;br /&gt;
This talk will discuss biometrics and their own biometric technology, how it works, how it was developed, and where it can go in the future.  We'll also learn how the cyber security market reacts to this new technology.&lt;br /&gt;
&lt;br /&gt;
Thanks to Hays for their sponsorship of pizza and drinks for this session.  Thanks also to Queens University for allowing us use of the Ashby building again.&lt;br /&gt;
&lt;br /&gt;
'''Adrian Condon (CTO, B-secur)'''&lt;br /&gt;
&lt;br /&gt;
Adrian has significant experience and an impressive track record in new product design, leading technical teams and delivering strategic new technology across the industrial, automotive, aeronautical and medical industries.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Code_review_feedback&amp;diff=231820</id>
		<title>Code review feedback</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Code_review_feedback&amp;diff=231820"/>
				<updated>2017-07-23T11:42:05Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: CRG update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= OWASP Code Review Feedback Page=&lt;br /&gt;
&lt;br /&gt;
The purpose of this page is to record feedback and issues with the OWASP Code Review Guide version 2.0.   Whilst a lot of time was spent towards the end of the project to remove these issues, and many issues were removed.  As with any collaborated document development, especially of a document this size, there will be typos and the like, with technical issues. &lt;br /&gt;
&lt;br /&gt;
We appreciate the help of the community in providing feedback on any issues spotted so that we can improve this document.  &lt;br /&gt;
&lt;br /&gt;
If you have access to the OWASP Wiki, please update this page with a list of issues you have spotted.  If you do not have access to edit the wiki, then please e-mail the code review team at [mailto:owasp-codereview-project@owasp.org owasp-codereview-project@owasp.org].  &lt;br /&gt;
&lt;br /&gt;
== Feedback to date ==&lt;br /&gt;
&lt;br /&gt;
The following feedback items have been received so far regarding v2.0 of the Code Review Guide.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Page Number&lt;br /&gt;
|Issue Description&lt;br /&gt;
|Suggested Resolution&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Word 'thru' used twice&lt;br /&gt;
|Change to 'through'&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Typo 'project life cycle will that code reviews should be done'&lt;br /&gt;
|Change to 'project life cycle code reviews should be done'&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Typo 'manfully feedback'&lt;br /&gt;
|Change to 'meaningful feedback'&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Typo 'on the type of code review do you want to accomplish'&lt;br /&gt;
|Change to 'on the type of code review you want to accomplish'&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Typo 'can be assistance to you'&lt;br /&gt;
|Change to 'can assist you'&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Typo 'whichh'&lt;br /&gt;
|Change to 'which'&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Typo 'prove code methods works'&lt;br /&gt;
|Change to 'prove code methods work'&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Typo 'in to the organizations'&lt;br /&gt;
|Change to 'into the organizations'&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Following section is unclear 'This book will also work as a reference guide for the code review as code is in the review process'&lt;br /&gt;
|Change to 'This book will also work as a reference guide for the secure review of code during the code review process'&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Why does the numbering start at 5?&lt;br /&gt;
|This is due to it technically being the 5th section, though the previous sections are not clearly numbered.  Is this an issue...?&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|Sentence unclear 'If informed decisions are being made based on a measurement of risk in the enterprise, which will be fully&lt;br /&gt;
supported.'&lt;br /&gt;
|Change to 'If informed decisions are being made based on a measurement of risk in the enterprise, this risk based approach should be fully supported by feedback from code reviews.'&lt;br /&gt;
|-&lt;br /&gt;
|Numerious places (starting with page 13)&lt;br /&gt;
|HIPPA spelt incorrectly (it's HIPAA)&lt;br /&gt;
|Change to HIPAA - 3 instances.&lt;br /&gt;
|-&lt;br /&gt;
|15&lt;br /&gt;
|Typo 'encase'&lt;br /&gt;
|Change to 'in case'&lt;br /&gt;
|-&lt;br /&gt;
|15&lt;br /&gt;
|Typo 'par-ticular'&lt;br /&gt;
|Change to 'particular'&lt;br /&gt;
|-&lt;br /&gt;
|18&lt;br /&gt;
|Typo 'Requirement 6.5 address'&lt;br /&gt;
|Change to 'Requirement 6.5 addresses'&lt;br /&gt;
|-&lt;br /&gt;
|44&lt;br /&gt;
|Issue with SQL 'Select custName, address1,address2,city,postalCode WHERE custID= '&lt;br /&gt;
|Change to 'SELECT custName, address1 FROM cust_table WHERE custID= '&lt;br /&gt;
|-&lt;br /&gt;
|57&lt;br /&gt;
|Formatting of text 'fields, drop down lists, and other web components are properly validated.' &lt;br /&gt;
|This seems to be its own bullet point, however it should be a line continuation of the last bullet point.&lt;br /&gt;
|-&lt;br /&gt;
|60&lt;br /&gt;
|Sample 8.1 text needs to be changed from '‘’’flters.Add(new RequireHttpsAttribute());’’’'&lt;br /&gt;
|Change to 'flters.Add(new RequireHttpsAttribute());' (i.e. remove the ''' at either end)&lt;br /&gt;
|-&lt;br /&gt;
|64&lt;br /&gt;
|Formatting issue with text 'However this can be hard to enforce. a. If possible give users the choice of band they wish to use.' &lt;br /&gt;
|Change to 'However this can be hard to enforce. If possible give users the choice of band they wish to use.'  (i.e. remove the 'a.' and keep it all in the same paragraph.&lt;br /&gt;
|-&lt;br /&gt;
|68&lt;br /&gt;
|Formatting issues&lt;br /&gt;
|A number of the bullet points have newlines where they are not needed (3rd, 4th &amp;amp; 5th bullet points).&lt;br /&gt;
|-&lt;br /&gt;
|68&lt;br /&gt;
|Session Fixation points should be bullet points and not numbered (numbers are wrong anyway).  &lt;br /&gt;
|2nd bullet point should be &amp;quot;All the session-ids should be generated by the application, and then stored in a pool to be checked later for. Application is the sole authority for session generation.&amp;quot; - i.e. all 1 paragraph, no new line.&lt;br /&gt;
|-&lt;br /&gt;
|68&lt;br /&gt;
|Formatting issue&lt;br /&gt;
|2nd bullet point under session fixation has an unnecessary new line.&lt;br /&gt;
|-&lt;br /&gt;
|72 &lt;br /&gt;
|Typo with 'Another level of to help prevent XSS is to use an Anti-XSS library'&lt;br /&gt;
|Change to 'Another level of help to prevent XSS is to use an Anti-XSS library'&lt;br /&gt;
|-&lt;br /&gt;
|73&lt;br /&gt;
|Typo with 'OWASP_Zed_Attack_Proxy_Project'&lt;br /&gt;
|Change to 'OWASP Zed Attack Proxy Project'&lt;br /&gt;
|-&lt;br /&gt;
|90&lt;br /&gt;
|Formatting issue&lt;br /&gt;
|Need a newline (whitespace) before title &amp;quot;JBoss AS&amp;quot;, and sample 11.8 appears mid-sentence&lt;br /&gt;
|-&lt;br /&gt;
|90&lt;br /&gt;
|Formatting issue&lt;br /&gt;
|Title &amp;quot;Oracle WebLogic&amp;quot; is at the bottom of the page, needs to be moved to the top of the next page.&lt;br /&gt;
|-&lt;br /&gt;
|91&lt;br /&gt;
|Formatting issue&lt;br /&gt;
|Remove text &amp;quot;Principal object&amp;quot;&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Code_review&amp;diff=231819</id>
		<title>Code review</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Code_review&amp;diff=231819"/>
				<updated>2017-07-23T11:11:50Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Update to code review page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;width:100%;height:90px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File: lab_big.jpg|link=OWASP_Project_Stages#tab.3DLab_Projects]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;&lt;br /&gt;
{{OWASP Defenders}} {{OWASP Book|5691953}} &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 5px; padding: 5px; float: left; width:70%&amp;quot;&amp;gt;{{Social Media Links}} &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
=Code Review Guide=&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==The Release Candidate for the OWASP Code Review Guide is now available!==&lt;br /&gt;
Please forward to all the developers and development teams you know!! We would like to immediately start raising awareness about this OWASP resource. &lt;br /&gt;
We plan to release the final version in Aug. 2017 after a public comment period ending July 31, 2017.&lt;br /&gt;
&lt;br /&gt;
Thank you,&lt;br /&gt;
Larry Conklin, Gary Robinson&lt;br /&gt;
OWASP Code Review Guides Co-Leaders&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
OWASP Code Review Guide is a technical book written for those responsible for code reviews (management, developers, security professionals). The primarily focus of this book has been divided into two main sections. Section one is why and how of code reviews and sections two is devoted to what vulnerabilities need to be to look for during a manual code review. While security scanners are improving every day the need for manual security code reviews still needs to have a prominent place in organizations SDLC (Secure development life cycle) that desires good secure code in production.&lt;br /&gt;
&lt;br /&gt;
Second sections deals with vulnerabilities. It is based on the poplar OWASP 2013 top 10.  Here you will find most of the code examples for both on what not to do and on what to do. A word of caution on code examples; Perl is famous for its saying that there are 10,000 ways to do one thing. The same is true for C#, PHP and Java or any other computer language. Now add in &amp;quot;Object-Oriented Programming&amp;quot; and if we are using design patterns or even what designs patterns are being used and sample code becomes very “iff” in what to write. We tried to keep the sample code so code reviews can see red flags and not “do it my way or else”.&lt;br /&gt;
&lt;br /&gt;
The last section is the appendix. Here we have content like code reviewer check list, etc. of items that really don’t flow in book form but needed to be included to make the code review guide compete.&lt;br /&gt;
&lt;br /&gt;
==Review of Code Review Guide 2.0==&lt;br /&gt;
Constructive comments on this OWASP Code Review Release Candidate should be forwarded via email to  owasp-codereview-project@owasp.org. Private comments may be sent to larry.conklin@owasp.org or gary.robinson@owasp.org . All comments are welcome. All comments should indicate the specific relevant page and section.&lt;br /&gt;
&lt;br /&gt;
All feedback is critical to the continued success of the OWASP Code Review Guide.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
OWASP Code Review Guide is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
* Larry Conklin [mailto:larry.conklin@owasp.org]&lt;br /&gt;
* Gary Robinson [mailto:gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
== Project Email ==&lt;br /&gt;
* Project Email [mailto:Owasp-codereview-project@lists.owasp.org]&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
[[File:Owasp-defenders-small.png|link=]]&lt;br /&gt;
&lt;br /&gt;
[[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]&lt;br /&gt;
&lt;br /&gt;
[[File:Project_Type_Files_DOC.jpg|link=]]&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
OWASP Testing Guide [https://www.owasp.org/index.php/OWASP_Testing_Project]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
== Quick Download ==&lt;br /&gt;
* [https://www.owasp.org/index.php/File:OWASP_Code_Review_Guide_v2.pdf Code Review Guide 2.0]&lt;br /&gt;
&lt;br /&gt;
== Feedback Page ==&lt;br /&gt;
&lt;br /&gt;
To leave feedback on the OWASP Code Review Guide V2.0, please use the following [[code_review_feedback|feedback page]], or e-mail the team at [mailto:owasp-codereview-project@owasp.org owasp-codereview-project@owasp.org]&lt;br /&gt;
&lt;br /&gt;
== In Print ==&lt;br /&gt;
Code Review Guide 2.0 will be available in Lulu in the near future.&lt;br /&gt;
&lt;br /&gt;
[http://www.lulu.com/content/5678680 Code Review Guide V1.1] on Lulu.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
The OWASP Code Review project was conceived by Eoin Keary, the OWASP Ireland Founder and Chapter Lead.&lt;br /&gt;
&lt;br /&gt;
 Code Review Mailing list[mailto:Owasp-codereview-project@lists.owasp.org]&lt;br /&gt;
&lt;br /&gt;
 Project leaders [mailto:larry.conklin@owasp.org larry.conklin@owasp.org] or [mailto:gary.robinson@owasp.org gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Code_review&amp;diff=231817</id>
		<title>Code review</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Code_review&amp;diff=231817"/>
				<updated>2017-07-23T10:59:11Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;width:100%;height:90px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File: lab_big.jpg|link=OWASP_Project_Stages#tab.3DLab_Projects]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;&lt;br /&gt;
{{OWASP Defenders}} {{OWASP Book|5691953}} &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 5px; padding: 5px; float: left; width:70%&amp;quot;&amp;gt;{{Social Media Links}} &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
=Code Review Guide=&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==The Release Candidate for the OWASP Code Review Guide is now available!==&lt;br /&gt;
Please forward to all the developers and development teams you know!! We would like to immediately start raising awareness about this OWASP resource. &lt;br /&gt;
We plan to release the final version in Aug. 2017 after a public comment period ending July 31, 2017.&lt;br /&gt;
&lt;br /&gt;
Thank you,&lt;br /&gt;
Larry Conklin, Gary Robinson&lt;br /&gt;
OWASP Code Review Guides Co-Leaders&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
OWASP Code Review Guide is a technical book written for those responsible for code reviews (management, developers, security professionals). The primarily focus of this book has been divided into two main sections. Section one is why and how of code reviews and sections two is devoted to what vulnerabilities need to be to look for during a manual code review. While security scanners are improving every day the need for manual security code reviews still needs to have a prominent place in organizations SDLC (Secure development life cycle) that desires good secure code in production.&lt;br /&gt;
&lt;br /&gt;
Second sections deals with vulnerabilities. It is based on the poplar OWASP 2013 top 10.  Here you will find most of the code examples for both on what not to do and on what to do. A word of caution on code examples; Perl is famous for its saying that there are 10,000 ways to do one thing. The same is true for C#, PHP and Java or any other computer language. Now add in &amp;quot;Object-Oriented Programming&amp;quot; and if we are using design patterns or even what designs patterns are being used and sample code becomes very “iff” in what to write. We tried to keep the sample code so code reviews can see red flags and not “do it my way or else”.&lt;br /&gt;
&lt;br /&gt;
The last section is the appendix. Here we have content like code reviewer check list, etc. of items that really don’t flow in book form but needed to be included to make the code review guide compete.&lt;br /&gt;
&lt;br /&gt;
==Review of Code Review Guide 2.0==&lt;br /&gt;
Constructive comments on this OWASP Code Review Release Candidate should be forwarded via email to  owasp-codereview-project@owasp.org. Private comments may be sent to larry.conklin@owasp.org or gary.robinson@owasp.org . All comments are welcome. All comments should indicate the specific relevant page and section.&lt;br /&gt;
&lt;br /&gt;
All feedback is critical to the continued success of the OWASP Code Review Guide.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
OWASP Code Review Guide is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
* Larry Conklin [mailto:larry.conklin@owasp.org]&lt;br /&gt;
* Gary Robinson [mailto:gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
== Project Email ==&lt;br /&gt;
* Project Email [mailto:Owasp-codereview-project@lists.owasp.org]&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
[[File:Owasp-defenders-small.png|link=]]&lt;br /&gt;
&lt;br /&gt;
[[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]&lt;br /&gt;
&lt;br /&gt;
[[File:Project_Type_Files_DOC.jpg|link=]]&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
OWASP Testing Guide [https://www.owasp.org/index.php/OWASP_Testing_Project]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
== Quick Download ==&lt;br /&gt;
* [https://www.owasp.org/index.php/File:OWASP_Code_Review_Guide_v2.pdf Code Review Guide 2.0]&lt;br /&gt;
&lt;br /&gt;
== In Print ==&lt;br /&gt;
Code Review Guide 2.0 will be available in Lulu in the near future.&lt;br /&gt;
&lt;br /&gt;
[http://www.lulu.com/content/5678680 Code Review Guide V1.1] on Lulu.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
The OWASP Code Review project was conceived by Eoin Keary, the OWASP Ireland Founder and Chapter Lead.&lt;br /&gt;
&lt;br /&gt;
 Code Review Mailing list[mailto:Owasp-codereview-project@lists.owasp.org]&lt;br /&gt;
&lt;br /&gt;
 Project leaders [mailto:larry.conklin@owasp.org larry.conklin@owasp.org] or [mailto:gary.robinson@owasp.org gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=231756</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=231756"/>
				<updated>2017-07-19T10:45:46Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Adding summer social event&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:siobhan.gallagher@owasp.org Siobhan Gallagher]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter August Session - Thursday, August 3 2017'''&lt;br /&gt;
&lt;br /&gt;
6:30pm @ Allstate NI building, Lanyon Place, Belfast&lt;br /&gt;
&lt;br /&gt;
https://www.meetup.com/OWASP-Belfast/events/241017867/&lt;br /&gt;
&lt;br /&gt;
'''Security by Design: Continuous Delivery, Integration, and Audit'''&lt;br /&gt;
&lt;br /&gt;
We are interrupting our summer break to take advantage of a visit by Nathan Gibson, Information Security &amp;amp; Privacy Professional at AllState.&lt;br /&gt;
&lt;br /&gt;
Nathan will be giving an session on maintaining, analyzing, confirming, and reporting on the status of required information security, compliance, and privacy controls is a difficult and significant task for software and security engineers. This talk discusses real world applications and examples for integrating Security by Design with your Continuous Deployment environment. Tools include the use of Jenkins, Chef, Metasploit, Fuzzers, vulnerability scanning (Nexpose), test driven development and system hardening.&lt;br /&gt;
&lt;br /&gt;
Refreshments will be provided, all are welcome.  This event will contain the one session by Nathan, and there will be time for questions and discussions afterwards.&lt;br /&gt;
&lt;br /&gt;
'''Nathan Gibson'''&lt;br /&gt;
&lt;br /&gt;
Nathan is an Information Security &amp;amp; Privacy Professional who specializes in continuous integration, inspection, and deployment environments. He brings information security and risk management concepts into the product portfolio realization pipeline and embeds the behavior naturally into design, develop, test, and refactor pipelines as a member of the technical team.&lt;br /&gt;
&lt;br /&gt;
Nathan enjoys coding, studying software development methodologies, and keeping up to date on the latest information security trends and methodologies.&lt;br /&gt;
&lt;br /&gt;
Nathan’s  professional qualifications include over 15 years experience in the industry where he has successfully managed secure information systems in dynamic, multinational environments. Nathan is experienced in all aspects of enterprise wide security with tasks ranging from governance and risk assessments through writing code and configuring systems.&lt;br /&gt;
&lt;br /&gt;
To compliment this background, Nathan maintains numerous certifications and academic training covering everything from governance to cryptography.  He holds a Masters In Information Security and a Bachelors in Computer Science.&lt;br /&gt;
&lt;br /&gt;
'''Northern Ireland Cyber Cluster – Cyber Mixer event (23rd August)'''&lt;br /&gt;
&lt;br /&gt;
In combination with ISACA, BCS and CSIT, OWASP Belfast are putting on Northern Ireland Cyber Cluster – Cyber Mixer event.  This event will be free to attend and provide food, drinks, and the ability to mix with the local cyber-security cluster.&lt;br /&gt;
&lt;br /&gt;
There'll be no presentations, no sponsors, no formality.  It's simply a networking event to get to know your fellow security professionals at ISACA, BCS and CSIT over food and a few drinks.&lt;br /&gt;
&lt;br /&gt;
This event will be on Wednesday 23rd August in The Gallary (Dublin Road) at 6pm.  You can sign-up at https://www.eventbrite.co.uk/e/northern-ireland-cyber-cluster-cyber-mixer-event-tickets-36265505102&lt;br /&gt;
&lt;br /&gt;
Please sign-up using the OWASP 'ticket type'.&lt;br /&gt;
&lt;br /&gt;
'''Please Note''': numbers are limited to 100, so we at OWASP Belfast have 25 tickets to use, so please only sign-up if you are absolutely able to make it.  If you sign-up and then can't make it, please update eventbrite so that someone else from OWASP can attend.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=231738</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=231738"/>
				<updated>2017-07-18T09:12:08Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Updated for August Session&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:siobhan.gallagher@owasp.org Siobhan Gallagher]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter August Session - Thursday, August 3 2017'''&lt;br /&gt;
&lt;br /&gt;
6:30pm @ Allstate NI building, Lanyon Place, Belfast&lt;br /&gt;
&lt;br /&gt;
https://www.meetup.com/OWASP-Belfast/events/241017867/&lt;br /&gt;
&lt;br /&gt;
'''Security by Design: Continuous Delivery, Integration, and Audit'''&lt;br /&gt;
&lt;br /&gt;
We are interrupting our summer break to take advantage of a visit by Nathan Gibson, Information Security &amp;amp; Privacy Professional at AllState.&lt;br /&gt;
&lt;br /&gt;
Nathan will be giving an session on maintaining, analyzing, confirming, and reporting on the status of required information security, compliance, and privacy controls is a difficult and significant task for software and security engineers. This talk discusses real world applications and examples for integrating Security by Design with your Continuous Deployment environment. Tools include the use of Jenkins, Chef, Metasploit, Fuzzers, vulnerability scanning (Nexpose), test driven development and system hardening.&lt;br /&gt;
&lt;br /&gt;
Refreshments will be provided, all are welcome.  This event will contain the one session by Nathan, and there will be time for questions and discussions afterwards.&lt;br /&gt;
&lt;br /&gt;
'''Nathan Gibson'''&lt;br /&gt;
&lt;br /&gt;
Nathan is an Information Security &amp;amp; Privacy Professional who specializes in continuous integration, inspection, and deployment environments. He brings information security and risk management concepts into the product portfolio realization pipeline and embeds the behavior naturally into design, develop, test, and refactor pipelines as a member of the technical team.&lt;br /&gt;
&lt;br /&gt;
Nathan enjoys coding, studying software development methodologies, and keeping up to date on the latest information security trends and methodologies.&lt;br /&gt;
&lt;br /&gt;
Nathan’s  professional qualifications include over 15 years experience in the industry where he has successfully managed secure information systems in dynamic, multinational environments. Nathan is experienced in all aspects of enterprise wide security with tasks ranging from governance and risk assessments through writing code and configuring systems.&lt;br /&gt;
&lt;br /&gt;
To compliment this background, Nathan maintains numerous certifications and academic training covering everything from governance to cryptography.  He holds a Masters In Information Security and a Bachelors in Computer Science.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:OWASP_Code_Review_Guide_v2.pdf&amp;diff=231678</id>
		<title>File:OWASP Code Review Guide v2.pdf</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:OWASP_Code_Review_Guide_v2.pdf&amp;diff=231678"/>
				<updated>2017-07-14T10:31:30Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Category:OWASP_Code_Review_Project&amp;diff=231677</id>
		<title>Category:OWASP Code Review Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Category:OWASP_Code_Review_Project&amp;diff=231677"/>
				<updated>2017-07-14T10:29:44Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Slight update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;width:100%;height:90px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File: lab_big.jpg|link=OWASP_Project_Stages#tab.3DLab_Projects]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;&lt;br /&gt;
{{OWASP Defenders}} {{OWASP Book|5691953}} &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 5px; padding: 5px; float: left; width:70%&amp;quot;&amp;gt;{{Social Media Links}} &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
=Code Review Guide=&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==The Release Candidate for the OWASP Code Review Guide is now available!==&lt;br /&gt;
Please forward to all the developers and development teams you know!! We would like to immediately start raising awareness about this OWASP resource. &lt;br /&gt;
We plan to release the final version in Aug. 2017 after a public comment period ending July 31, 2017.&lt;br /&gt;
&lt;br /&gt;
Thank you,&lt;br /&gt;
Larry Conklin, Gary Robinson&lt;br /&gt;
OWASP Code Review Guides Co-Leaders&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
OWASP Code Review Guide is a technical book written for those responsible for code reviews (management, developers, security professionals). The primarily focus of this book has been divided into two main sections. Section one is why and how of code reviews and sections two is devoted to what vulnerabilities need to be to look for during a manual code review. While security scanners are improving every day the need for manual security code reviews still needs to have a prominent place in organizations SDLC (Secure development life cycle) that desires good secure code in production.&lt;br /&gt;
&lt;br /&gt;
Second sections deals with vulnerabilities. It is based on the poplar OWASP 2013 top 10.  Here you will find most of the code examples for both on what not to do and on what to do. A word of caution on code examples; Perl is famous for its saying that there are 10,000 ways to do one thing. The same is true for C#, PHP and Java or any other computer language. Now add in &amp;quot;Object-Oriented Programming&amp;quot; and if we are using design patterns or even what designs patterns are being used and sample code becomes very “iff” in what to write. We tried to keep the sample code so code reviews can see red flags and not “do it my way or else”.&lt;br /&gt;
&lt;br /&gt;
The last section is the appendix. Here we have content like code reviewer check list, etc. of items that really don’t flow in book form but needed to be included to make the code review guide compete.&lt;br /&gt;
&lt;br /&gt;
==Review of Code Review Guide 2.0==&lt;br /&gt;
Constructive comments on this OWASP Code Review Release Candidate should be forwarded via email to  owasp-codereview-project@owasp.org. Private comments may be sent to larry.conklin@owasp.org or gary.robinson@owasp.org . All comments are welcome. All comments should indicate the specific relevant page and section.&lt;br /&gt;
&lt;br /&gt;
All feedback is critical to the continued success of the OWASP Code Review Guide.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
OWASP Code Review Guide is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
* Larry Conklin [mailto:larry.conklin@owasp.org]&lt;br /&gt;
* Gary Robinson [mailto:gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
== Project Email ==&lt;br /&gt;
* Project Email [mailto:owasp-codereview-project@owasp.org]&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
[[File:Owasp-defenders-small.png|link=]]&lt;br /&gt;
&lt;br /&gt;
[[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]&lt;br /&gt;
&lt;br /&gt;
[[File:Project_Type_Files_DOC.jpg|link=]]&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
OWASP Testing Guide [https://www.owasp.org/index.php/OWASP_Testing_Project]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
== Quick Download ==&lt;br /&gt;
* [https://www.owasp.org/index.php/File:OWASP_Code_Review_Guide_v2.pdf Code Review Guide 2.0]&lt;br /&gt;
&lt;br /&gt;
== In Print ==&lt;br /&gt;
Code Review Guide 2.0 will be available in Lulu in the near future.&lt;br /&gt;
&lt;br /&gt;
[http://www.lulu.com/content/5678680 Code Review Guide V1.1] on Lulu.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
The OWASP Code Review project was conceived by Eoin Keary, the OWASP Dublin Founder and Chapter Lead.&lt;br /&gt;
&lt;br /&gt;
 Code Review Mailing list[mailto:owasp-codereview-project@owasp.org]&lt;br /&gt;
&lt;br /&gt;
 Project leaders [mailto:larry.conklin@owasp.org larry.conklin@owasp.org] or [mailto:gary.robinson@owasp.org gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Category:OWASP_Code_Review_Project&amp;diff=231676</id>
		<title>Category:OWASP Code Review Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Category:OWASP_Code_Review_Project&amp;diff=231676"/>
				<updated>2017-07-14T10:28:32Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Updating link to release version&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;width:100%;height:90px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File: lab_big.jpg|link=OWASP_Project_Stages#tab.3DLab_Projects]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;&lt;br /&gt;
{{OWASP Defenders}} {{OWASP Book|5691953}} &lt;br /&gt;
&amp;lt;div style=&amp;quot;margin: 5px; padding: 5px; float: left; width:70%&amp;quot;&amp;gt;{{Social Media Links}} &amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
=Code Review Guide=&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
==The Release Candidate for the OWASP Code Review Guide is now available!==&lt;br /&gt;
Please forward to all the developers and development teams you know!! We would like to immediately start raising awareness about this OWASP resource. &lt;br /&gt;
We plan to release the final version in Aug. 2017 after a public comment period ending July 31, 2017.&lt;br /&gt;
&lt;br /&gt;
Thank you,&lt;br /&gt;
Larry Conklin, Gary Robinson&lt;br /&gt;
OWASP Code Review Guides Co-Leaders&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
OWASP Code Review Guide is a technical book written for those responsible for code reviews (management, developers, security professionals). The primarily focus of this book has been divided into two main sections. Section one is why and how of code reviews and sections two is devoted to what vulnerabilities need to be to look for during a manual code review. While security scanners are improving every day the need for manual security code reviews still needs to have a prominent place in organizations SDLC (Secure development life cycle) that desires good secure code in production.&lt;br /&gt;
&lt;br /&gt;
Second sections deals with vulnerabilities. It is based on the poplar OWASP 2013 top 10.  Here you will find most of the code examples for both on what not to do and on what to do. A word of caution on code examples; Perl is famous for its saying that there are 10,000 ways to do one thing. The same is true for C#, PHP and Java or any other computer language. Now add in &amp;quot;Object-Oriented Programming&amp;quot; and if we are using design patterns or even what designs patterns are being used and sample code becomes very “iff” in what to write. We tried to keep the sample code so code reviews can see red flags and not “do it my way or else”.&lt;br /&gt;
&lt;br /&gt;
The last section is the appendix. Here we have content like code reviewer check list, etc. of items that really don’t flow in book form but needed to be included to make the code review guide compete.&lt;br /&gt;
&lt;br /&gt;
==Review of Code Review Guide 2.0==&lt;br /&gt;
Constructive comments on this OWASP Code Review Release Candidate should be forwarded via email to  owasp-codereview-project@owasp.org. Private comments may be sent to larry.conklin@owasp.org or gary.robinson@owasp.org . All comments are welcome. All comments should indicate the specific relevant page and section.&lt;br /&gt;
&lt;br /&gt;
All feedback is critical to the continued success of the OWASP Code Review Guide.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
OWASP Code Review Guide is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
* Larry Conklin [mailto:larry.conklin@owasp.org]&lt;br /&gt;
* Gary Robinson [mailto:gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
== Project Email ==&lt;br /&gt;
* Project Email [mailto:owasp-codereview-project@owasp.org]&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
[[File:Owasp-defenders-small.png|link=]]&lt;br /&gt;
&lt;br /&gt;
[[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]&lt;br /&gt;
&lt;br /&gt;
[[File:Project_Type_Files_DOC.jpg|link=]]&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
OWASP Testing Guide [https://www.owasp.org/index.php/OWASP_Testing_Project]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
== Quick Download ==&lt;br /&gt;
* [https://www.owasp.org/index.php/File:OWASP_Code_Review_Guide_v2.pdf Code Review Guide 2.0]&lt;br /&gt;
&lt;br /&gt;
== In Print ==&lt;br /&gt;
Code Review Guide 2.0 will be available in Lulu in the near future.&lt;br /&gt;
&lt;br /&gt;
[http://www.lulu.com/content/5678680 Code Review Guide V1.1] on Lulu.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
The OWASP Code Review project was conceived by Eoin Keary, the OWASP Ireland Founder and Chapter Lead.&lt;br /&gt;
&lt;br /&gt;
 Code Review Mailing list[mailto:owasp-codereview-project@owasp.org]&lt;br /&gt;
&lt;br /&gt;
 Project leaders [mailto:larry.conklin@owasp.org larry.conklin@owasp.org] or [mailto:gary.robinson@owasp.org gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=228716</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=228716"/>
				<updated>2017-04-16T19:35:05Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:siobhan.gallagher@owasp.org Siobhan Gallagher]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Monday May 8th'''&lt;br /&gt;
&lt;br /&gt;
6pm @ Waterfront Conference Center, Belfast&lt;br /&gt;
&lt;br /&gt;
https://www.meetup.com/OWASP-Belfast/events/238434511/&lt;br /&gt;
&lt;br /&gt;
OWASP Belfasts' May session with be held in conjunction with the Women Who Code Belfast Chapter, and will form part of the OWASP AppSec EU Conference program.&lt;br /&gt;
&lt;br /&gt;
'''OWASP Women in AppSec &amp;amp; Women Who Code: An Evening with the Pros!'''&lt;br /&gt;
&lt;br /&gt;
Kicking off our OWASP AppSec EU Conference in May, we are holding a youth outreach event during the day (further details on the website 2017.appsec.eu) and an evening networking/mentoring session which we are running together with Women Who Code Belfast.&lt;br /&gt;
&lt;br /&gt;
This joint OWASP and WWCode meetup will highlight the successes of women in the tech &amp;amp; security community, how to get into cyber security, and why you should care. There will be a range of talks from professionals within the industry who have come from all over Europe to attend AppSec EU, and a chance to rub shoulders with the big names in the industry. &lt;br /&gt;
&lt;br /&gt;
We hope to see you all there! Refreshments will be provided.&lt;br /&gt;
&lt;br /&gt;
YOU DO NOT NEED AN APPSEC EU CONFERENCE TICKET TO ATTEND THIS EVENT. The event is open to all and free to attend but you will need to register and places may be limited.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=218845</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=218845"/>
				<updated>2016-07-12T16:01:16Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:siobhan.gallagher@owasp.org Siobhan Gallagher]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Monday July 18th'''&lt;br /&gt;
&lt;br /&gt;
6:45 PM Queens Ashby Building&lt;br /&gt;
Stranmillis Rd, Belfast BT9 5AG, Belfast&lt;br /&gt;
&lt;br /&gt;
http://www.meetup.com/OWASP-Belfast/events/231770209/&lt;br /&gt;
&lt;br /&gt;
OWASP Belfasts' July session will be a full session on secure coding with lots of examples and some code, along with the usual pizza and beers (kindly sponsored by Vanrath).&lt;br /&gt;
&lt;br /&gt;
'''Rails Secure Coding - Owen Mooney'''&lt;br /&gt;
&lt;br /&gt;
Learn the pitfalls of secure code development with Ruby based on the experience of the edgescan development team. The workshop shall cover many of the most common application security vulnerabilities and additional considerstions for developers when building applications in Ruby for deployment to the public Internet or the cloud.This 2.5 hour workshop shall be delivered by Owen Mooney, lead developer for edgescan.com, the cloud based full stack vulnerability management SaaS. &lt;br /&gt;
&lt;br /&gt;
Please note that the session will begin at the earlier time of 18:45. There will be a break half way through for pizza &amp;amp; beers and the session will finish at 21:45. No equipment is required for attendance. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Category:OWASP_Code_Review_Project&amp;diff=218282</id>
		<title>Category:OWASP Code Review Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Category:OWASP_Code_Review_Project&amp;diff=218282"/>
				<updated>2016-06-26T09:15:01Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:90px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File: lab_big.jpg|link=OWASP_Project_Stages#tab.3DLab_Projects]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
==OWASP Code Review Guide Project==&lt;br /&gt;
&lt;br /&gt;
{{OWASP Book|5678680}}&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
The code review guide is currently at release version 1.1 and the second best selling OWASP book in 2008. Many positive comments have been feedback regarding this initial version and believe it’s a key enabler for the OWASP fight against software insecurity. It has even inspired individuals to build tools based on its information. The combination of a book on secure code review and tools to support such an activity is very powerful as it gives the developer community a place to start regarding secure application development.&lt;br /&gt;
Going forward I hope to further integrate with the ASVS and other guides such as the testing and ASDR guides shall be perfromed for version 2.0.t&lt;br /&gt;
&lt;br /&gt;
==Alpha Release OWASP Code Review 2.0==&lt;br /&gt;
'''OWASP Code Review Guide 2.0 Alpha release is now available.''' It is a technical book written for those responsible for code reviews (management, developers, security professionals). The primarily focus of this book has been divided into two main sections. Section one is why and how of code reviews and sections two is devoted to what vulnerabilities need to be to look for during a manual code review. While security scanners are improving every day the need for manual security code reviews still needs to have a prominent place in organizations SDLC (Secure development life cycle) that desires good secure code in production.&lt;br /&gt;
&lt;br /&gt;
The document is divided into two main sections. One section covers the why (reasons for doing secure code reviews) and how. This section main focus is IT management and project leads.&lt;br /&gt;
&lt;br /&gt;
Second sections deals with vulnerabilities. It is based on the poplar OWASP top 10.  Here you will find most of the code examples for both on what not to do and on what to do. A word of caution on code examples; Perl is famous for its saying that there are 10,000 ways to do one thing. The same is true for C#, PHP and Java or any other computer language. Now add in &amp;quot;Object-Oriented Programming&amp;quot; and if we are using design patterns or even what designs patterns are being used and sample code becomes very “iff” in what to write. We tried to keep the sample code so code reviews can see red flags and not “do it my way or else”.&lt;br /&gt;
&lt;br /&gt;
The last big section is the appendix. Here we have content like code reviewer list, etc. of items that really don’t flow in book form but needed to be included to make the code review guide compete.&lt;br /&gt;
&lt;br /&gt;
==Alpha Peer Review of Code Review Guide 2.0==&lt;br /&gt;
We have a small amount of content that is not in the code review guide. Both Gary and I are working on completing this. One thing we have tried to do is to have the code review guide flow as a book than a collection of separate articles based on a major topic. &lt;br /&gt;
&lt;br /&gt;
'''Code Review Guide 2.0 needs the following to be peer reviewed:'''  &lt;br /&gt;
&lt;br /&gt;
#Grammar, spelling.&lt;br /&gt;
#Review content that is easily understandable, not complex to be understood and or followed. &lt;br /&gt;
#Code is correct. &lt;br /&gt;
#No outdated code or components.  I.e code sample shows.Net, Java, PHP of release that is at least 8 years old in how current software is being written.  This is very subjective; a good example is java struts where java struts 2.0 would be coded entirely different.&lt;br /&gt;
#Missing content. Did we exclude or gloss over some content that needs to be included? We can’t include everything or we would never get done but if you feel we need to include something please ay so.&lt;br /&gt;
#We are looking for good useable, and complete feedback.&lt;br /&gt;
&lt;br /&gt;
'''''On the editing process, it will be of great help if a reviewer could send of the corrected paragraph or code block along with the chapter, and page numbers. '''''&lt;br /&gt;
&lt;br /&gt;
Because of some unforeseen issues we are not able to provide a word document. I apologize for that, however editing the PDF is very possible and should not stop the review process.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
OWASP Code Review Guide is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== What is the Code Review Guide? ==&lt;br /&gt;
&lt;br /&gt;
OWASP Code Review Guide provides:&lt;br /&gt;
&lt;br /&gt;
* [[OWASP Code Review Guide Table of Contents]] from v1&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&lt;br /&gt;
* Larry Conklin [mailto:larry.conklin@owasp.org]&lt;br /&gt;
* Gary Robinson [mailto:gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
OWASP Testing Guide [https://www.owasp.org/index.php/OWASP_Testing_Project]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
== Quick Download ==&lt;br /&gt;
* [https://www.owasp.org/index.php/File:OWASP_CRG_BetaReview.docx Beta review version of OWASP Code Review Guide for AppSec EU 2016 Summit]&lt;br /&gt;
* [https://www.owasp.org/images/2/2e/OWASP_Code_Review_Guide-V1_1.pdf Code Review Guide V1.1]&lt;br /&gt;
* [https://www.owasp.org/images/7/78/OWASP_AlphaRelease_CodeReviewGuide2.0.pdf Alpha Release Code Review Guide 2.0 ]&lt;br /&gt;
* [https://www.owasp.org/index.php/File:Change_Journal.docx Word doc to track changes/additions/deletions to Alpha Release Code review Guide 2.0]&lt;br /&gt;
&lt;br /&gt;
== Email List ==&lt;br /&gt;
&lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-codereview Sign up]&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
'''''Code Review Guide 2.0 Alpha Release is now available'''''&lt;br /&gt;
----&lt;br /&gt;
'''OWASP New York Chapter'''&lt;br /&gt;
'''''March 2 2016'''''&lt;br /&gt;
&lt;br /&gt;
First before anything else both Gary and I want to thank the '''New York OWASP Chapter''' for being willing to have a working session on reviewing the work of the Code Review Guide team. I know its much more exciting to learn new hacking techniques or procedures to prevent it. Never less reviewing the book is a very much-needed effort and Gary and I very much appreciate everyone in New York taking time to do this. &lt;br /&gt;
&lt;br /&gt;
I also want to give out a big shout of thanks to Ken Belva for help in pushing both Gary and myself to get the document ready for everyone. Last but not least we both also want to thank Helen Gao and Charles Beganskas.&lt;br /&gt;
&lt;br /&gt;
== In Print ==&lt;br /&gt;
[http://www.lulu.com/content/5678680 Code Review Guide V1.1] on Lulu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; rowspan=&amp;quot;2&amp;quot;| [[File:Midlevel projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-builders-small.png|link=]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-defenders-small.png|link=]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  | [[File:Project_Type_Files_CODE.jpg|link=]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Volunteers==&lt;br /&gt;
The OWASP Code Review project was conceived by Eoin Keary, the OWASP Ireland Founder and Chapter Lead. Current project leaders are Larry Conklin and Gary Robinson If you are interested in volunteering for the project, or have a comment, question, or suggestion, please drop me a line [mailto:larry.conklin@owasp.org larry.conklin@owasp.org] or [mailto:gary.robinson@owasp.org gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
==Get Involved==&lt;br /&gt;
All of the OWASP Guides are living documents that will continue to change as the threat and security landscape changes.&lt;br /&gt;
We welcome everyone to join the Code Review Guide Project and help us make this document great. The best way to get started is to subscribe to the mailing list by following the link below or contact the project leaders listed below.&lt;br /&gt;
&lt;br /&gt;
Please introduce yourself and ask to see if there is anything you can help with. We are always looking for new contributions. If there is a topic that you’d like to research and contribute, please let us know!&lt;br /&gt;
&lt;br /&gt;
 Code Review Mailing list[mailto:owasp-codereview@lists.owasp.org owasp-codereview@lists.owasp.org]&lt;br /&gt;
&lt;br /&gt;
 Project leaders [mailto:larry.conklin@owasp.org larry.conklin@owasp.org] or [mailto:gary.robinson@owasp.org gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
=Project About=&lt;br /&gt;
{{:Projects/OWASP Code Review Project| Project About}}&lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]] [[Category:OWASP Project|Code Review Project]]&lt;br /&gt;
[[Category:OWASP Document]]&lt;br /&gt;
[[Category:OWASP Release Quality Document]]&lt;br /&gt;
[[Category:SAMM-CR-1]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=File:OWASP_CRG_BetaReview.docx&amp;diff=218281</id>
		<title>File:OWASP CRG BetaReview.docx</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=File:OWASP_CRG_BetaReview.docx&amp;diff=218281"/>
				<updated>2016-06-26T09:13:17Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Beta review version for OWASP AppSecEU 2016 conference summit.

Instructions for review are at the top of the document.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Beta review version for OWASP AppSecEU 2016 conference summit.&lt;br /&gt;
&lt;br /&gt;
Instructions for review are at the top of the document.&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=217130</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=217130"/>
				<updated>2016-05-20T16:01:21Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:siobhan.gallagher@owasp.org Siobhan Gallagher]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Monday May 9th'''&lt;br /&gt;
&lt;br /&gt;
7:00 PM Queens Ashby Building&lt;br /&gt;
Stranmillis Rd, Belfast BT9 5AG, Belfast&lt;br /&gt;
&lt;br /&gt;
Register at http://www.meetup.com/OWASP-Belfast/events/230568917/&lt;br /&gt;
&lt;br /&gt;
OWASP Belfasts' May session has two talks planned, along with the usual pizza and beers (kindly sponsored by Veracode).&lt;br /&gt;
&lt;br /&gt;
'''Secure Design'''&lt;br /&gt;
&lt;br /&gt;
Gary Robinson, OWASP Belfast Chapter Leader&lt;br /&gt;
&lt;br /&gt;
When it comes to high risk applications, secure design considerations can be included before a line of code is written.  This talk will give a brief introduction to the concept of Secure Design, where it fits into the SDLC, and some of the covering principals that the industry relies upon.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Threat detection and identification along the kill chain'''&lt;br /&gt;
&lt;br /&gt;
Hugh Njemanze - CEO and Founder of Anomali&lt;br /&gt;
&lt;br /&gt;
https://www.anomali.com/company/leadership/hugh-njemanze &lt;br /&gt;
&lt;br /&gt;
A brief overview of the evolution of SIEM, the emergence of Threat Intelligence feeds, and the arrival of Threat Intelligence Platforms that integrate the two with the goal of increasing the effectiveness of Cyber Security Operations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Code_review_V2_AppSecEU_Agenda&amp;diff=216895</id>
		<title>OWASP Code review V2 AppSecEU Agenda</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Code_review_V2_AppSecEU_Agenda&amp;diff=216895"/>
				<updated>2016-05-15T12:57:20Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Created page with &amp;quot;== OWASP AppSec EU 2016 Agenda ==  The OWASP Code Review Guide (v2) is attending the AppSec EU Project Summit in Rome during June 2016.  At this summit we will be inviting par...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== OWASP AppSec EU 2016 Agenda ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Code Review Guide (v2) is attending the AppSec EU Project Summit in Rome during June 2016.  At this summit we will be inviting participants to spend some of their time to review the Beta version of the guide.&lt;br /&gt;
&lt;br /&gt;
High level agenda is as follows:&lt;br /&gt;
* Copies of the guide will be available as PDF, either downloadable from the Internet, or on CD&lt;br /&gt;
* Participants will be asked to scan the document ToC, determine a section they have experience in, and review.&lt;br /&gt;
* Review comments will be collected and fed back into the beta review cycle.&lt;br /&gt;
* As incentive, the Code Review Guide will bring a 10 year old Irish Whiskey, to be raffled among the participants taking part in the review.&lt;br /&gt;
&lt;br /&gt;
Any questions, contact the OWASP Code Review Guide leaders.&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=216027</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=216027"/>
				<updated>2016-04-27T08:32:30Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:johnathan.kuskos@owasp.org Johnathan Kuskos]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Monday May 9th'''&lt;br /&gt;
&lt;br /&gt;
7:00 PM Queens Ashby Building&lt;br /&gt;
Stranmillis Rd, Belfast BT9 5AG, Belfast&lt;br /&gt;
&lt;br /&gt;
Register at http://www.meetup.com/OWASP-Belfast/events/230568917/&lt;br /&gt;
&lt;br /&gt;
OWASP Belfasts' May session has two talks planned, along with the usual pizza and beers (kindly sponsored by Veracode).&lt;br /&gt;
&lt;br /&gt;
'''Secure Design'''&lt;br /&gt;
&lt;br /&gt;
Gary Robinson, OWASP Belfast Chapter Leader&lt;br /&gt;
&lt;br /&gt;
When it comes to high risk applications, secure design considerations can be included before a line of code is written.  This talk will give a brief introduction to the concept of Secure Design, where it fits into the SDLC, and some of the covering principals that the industry relies upon.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Threat detection and identification along the kill chain'''&lt;br /&gt;
&lt;br /&gt;
Hugh Njemanze - CEO and Founder of Anomali&lt;br /&gt;
&lt;br /&gt;
https://www.anomali.com/company/leadership/hugh-njemanze &lt;br /&gt;
&lt;br /&gt;
A brief overview of the evolution of SIEM, the emergence of Threat Intelligence feeds, and the arrival of Threat Intelligence Platforms that integrate the two with the goal of increasing the effectiveness of Cyber Security Operations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=215846</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=215846"/>
				<updated>2016-04-23T09:40:25Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:johnathan.kuskos@owasp.org Johnathan Kuskos]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Monday May 9th'''&lt;br /&gt;
&lt;br /&gt;
7:00 PM Queens Ashby Building&lt;br /&gt;
Stranmillis Rd, Belfast BT9 5AG, Belfast&lt;br /&gt;
&lt;br /&gt;
Register at http://www.meetup.com/OWASP-Belfast/events/230568917/&lt;br /&gt;
&lt;br /&gt;
OWASP Belfasts' May session has two talks planned, along with the usual pizza and beers (kindly sponsored by Veracode).&lt;br /&gt;
&lt;br /&gt;
'''Secure Design'''&lt;br /&gt;
&lt;br /&gt;
Gary Robinson, OWASP Belfast Chapter Leader&lt;br /&gt;
&lt;br /&gt;
When it comes to high risk applications, secure design considerations can be included before a line of code is written.  This talk will give a brief introduction to the concept of Secure Design, where it fits into the SDLC, and some of the covering principals that the industry relies upon.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Threat detection and identification along the kill chain'''&lt;br /&gt;
&lt;br /&gt;
Hugh Njemanze - CEO and Founder of Anomali&lt;br /&gt;
&lt;br /&gt;
https://www.anomali.com/company/leadership/hugh-njemanze &lt;br /&gt;
&lt;br /&gt;
Brief of talk TBC. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=215845</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=215845"/>
				<updated>2016-04-23T09:38:08Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:johnathan.kuskos@owasp.org Johnathan Kuskos]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Monday May 9th'''&lt;br /&gt;
&lt;br /&gt;
7:00 PM Queens Ashby Building&lt;br /&gt;
Stranmillis Rd, Belfast BT9 5AG, Belfast&lt;br /&gt;
&lt;br /&gt;
Register at http://www.meetup.com/OWASP-Belfast/events/230568917/&lt;br /&gt;
&lt;br /&gt;
OWASP Belfasts' May session has two talks planned, along with the usual pizza and beers (kindly sponsored by Veracode).&lt;br /&gt;
&lt;br /&gt;
'''Secure Design'''&lt;br /&gt;
&lt;br /&gt;
Gary Robinson, OWASP Belfast Chapter Leader&lt;br /&gt;
&lt;br /&gt;
When it comes to high risk applications, secure design considerations can be included before a line of code is written.  This talk will give a brief introduction to the concept of Secure Design, where it fits into the SDLC, and some of the covering principals that the industry relies upon.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Threat detection and identification along the kill chain'''&lt;br /&gt;
&lt;br /&gt;
ugh Njemanze - CEO and Founder of Anomali&lt;br /&gt;
&lt;br /&gt;
https://www.anomali.com/company/leadership/hugh-njemanze &lt;br /&gt;
&lt;br /&gt;
Brief of talk TBC. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=210904</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=210904"/>
				<updated>2016-03-10T14:01:02Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:johnathan.kuskos@owasp.org Johnathan Kuskos]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Monday March 14th'''&lt;br /&gt;
&lt;br /&gt;
7:00 PM Queens Ashby Building&lt;br /&gt;
Stranmillis Rd, Belfast BT9 5AG, Belfast&lt;br /&gt;
&lt;br /&gt;
Register at http://www.meetup.com/OWASP-Belfast/events/228894486/&lt;br /&gt;
&lt;br /&gt;
OWASP Belfasts' March session has two great talks planned, along with the usual pizza and beers (kindly sponsored by Vertical Structure).&lt;br /&gt;
&lt;br /&gt;
'''Top 10 WebHacks of 2015'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Kuskos - Threat Center Manager at Whitehat&lt;br /&gt;
&lt;br /&gt;
Every year the security community produces a stunning number of new Web hacking techniques that are published in various white papers, blog posts, magazine articles, mailing list emails, conference presentations, etc. Within the thousands of pages are the latest ways to attack websites, Web browsers, Web proxies, and their mobile platform equivalents. Beyond individual vulnerabilities with CVE numbers or system compromises, we are solely focused on new and creative methods of Web-based attack. Now in its tenth year, the Top 10 Web Hacking Techniques list encourages information sharing, provides a centralized knowledge base, and recognizes researchers who contribute excellent research.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Open Source Security – What Security Testing Tools Miss'''&lt;br /&gt;
&lt;br /&gt;
Mike Pittenger - VP of Security Strategy for Blackduck&lt;br /&gt;
&lt;br /&gt;
Static analysis, dynamic analysis, and other testing tools are all essential weapons against adversaries. But for the 80%+ of companies worldwide that use open source software in their application development these tools are ineffective in identifying and mitigating open source security risks . This presentation will cover: &lt;br /&gt;
• The value of static and dynamic tools, and where they best fit in the Secure Development Lifecycle &lt;br /&gt;
• Why these tools are not useful in identifying known vulnerabilities in open source components &lt;br /&gt;
• Controls development and security professionals can deploy to select, detect, manage and monitor open source for existing and newly disclosed vulnerabilities. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Category:OWASP_Code_Review_Project&amp;diff=210149</id>
		<title>Category:OWASP Code Review Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Category:OWASP_Code_Review_Project&amp;diff=210149"/>
				<updated>2016-03-01T07:33:51Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:90px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File: lab_big.jpg|link=OWASP_Project_Stages#tab.3DLab_Projects]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
==OWASP Code Review Guide Project==&lt;br /&gt;
&lt;br /&gt;
{{OWASP Book|5678680}}&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
&lt;br /&gt;
The code review guide is currently at release version 1.1 and the second best selling OWASP book in 2008. Many positive comments have been feedback regarding this initial version and believe it’s a key enabler for the OWASP fight against software insecurity. It has even inspired individuals to build tools based on its information. The combination of a book on secure code review and tools to support such an activity is very powerful as it gives the developer community a place to start regarding secure application development.&lt;br /&gt;
Going forward I hope to further integrate with the ASVS and other guides such as the testing and ASDR guides shall be perfromed for version 2.0.t&lt;br /&gt;
&lt;br /&gt;
==Alpha Release OWASP Code Review 2.0==&lt;br /&gt;
'''OWASP Code Review Guide 2.0 Alpha release is now available.''' It is a technical book written for those responsible for code reviews (management, developers, security professionals). The primarily focus of this book has been divided into two main sections. Section one is why and how of code reviews and sections two is devoted to what vulnerabilities need to be to look for during a manual code review. While security scanners are improving every day the need for manual security code reviews still needs to have a prominent place in organizations SDLC (Secure development life cycle) that desires good secure code in production.&lt;br /&gt;
&lt;br /&gt;
The document is divided into two main sections. One section covers the why (reasons for doing secure code reviews) and how. This section main focus is IT management and project leads.&lt;br /&gt;
&lt;br /&gt;
Second sections deals with vulnerabilities. It is based on the poplar OWASP top 10.  Here you will find most of the code examples for both on what not to do and on what to do. A word of caution on code examples; Perl is famous for its saying that there are 10,000 ways to do one thing. The same is true for C#, PHP and Java or any other computer language. Now add in &amp;quot;Object-Oriented Programming&amp;quot; and if we are using design patterns or even what designs patterns are being used and sample code becomes very “iff” in what to write. We tried to keep the sample code so code reviews can see red flags and not “do it my way or else”.&lt;br /&gt;
&lt;br /&gt;
The last big section is the appendix. Here we have content like code reviewer list, etc. of items that really don’t flow in book form but needed to be included to make the code review guide compete.&lt;br /&gt;
&lt;br /&gt;
==Alpha Peer Review of Code Review Guide 2.0==&lt;br /&gt;
We have a small amount of content that is not in the code review guide. Both Gary and I are working on completing this. One thing we have tried to do is to have the code review guide flow as a book than a collection of separate articles based on a major topic. &lt;br /&gt;
&lt;br /&gt;
'''Code Review Guide 2.0 needs the following to be peer reviewed:'''  &lt;br /&gt;
&lt;br /&gt;
#Grammar, spelling.&lt;br /&gt;
#Review content that is easily understandable, not complex to be understood and or followed. &lt;br /&gt;
#Code is correct. &lt;br /&gt;
#No outdated code or components.  I.e code sample shows.Net, Java, PHP of release that is at least 8 years old in how current software is being written.  This is very subjective; a good example is java struts where java struts 2.0 would be coded entirely different.&lt;br /&gt;
#Missing content. Did we exclude or gloss over some content that needs to be included? We can’t include everything or we would never get done but if you feel we need to include something please ay so.&lt;br /&gt;
#We are looking for good useable, and complete feedback.&lt;br /&gt;
&lt;br /&gt;
'''''On the editing process, it will be of great help if a reviewer could send of the corrected paragraph or code block along with the chapter, and page numbers. '''''&lt;br /&gt;
&lt;br /&gt;
Because of some unforeseen issues we are not able to provide a word document. I apologize for that, however editing the PDF is very possible and should not stop the review process.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
OWASP Code Review Guide is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== What is the Code Review Guide? ==&lt;br /&gt;
&lt;br /&gt;
OWASP Code Review Guide provides:&lt;br /&gt;
&lt;br /&gt;
* [[OWASP Code Review Guide Table of Contents]] from v1&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&lt;br /&gt;
* Larry Conklin [mailto:larry.conklin@owasp.org]&lt;br /&gt;
* Gary Robinson [mailto:gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&lt;br /&gt;
OWASP Testing Guide [https://www.owasp.org/index.php/OWASP_Testing_Project]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
== Quick Download ==&lt;br /&gt;
* [https://www.owasp.org/images/2/2e/OWASP_Code_Review_Guide-V1_1.pdf Code Review Guide V1.1]&lt;br /&gt;
* [https://www.owasp.org/images/7/78/OWASP_AlphaRelease_CodeReviewGuide2.0.pdf Alpha Release Code Review Guide 2.0 ]&lt;br /&gt;
&lt;br /&gt;
== Email List ==&lt;br /&gt;
&lt;br /&gt;
[http://lists.owasp.org/mailman/listinfo/owasp-codereview Sign up]&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
'''''Code Review Guide 2.0 Alpha Release is now available'''''&lt;br /&gt;
----&lt;br /&gt;
'''OWASP New York Chapter'''&lt;br /&gt;
'''''March 2 2016'''''&lt;br /&gt;
&lt;br /&gt;
First before anything else both Gary and I want to thank the '''New York OWASP Chapter''' for being willing to have a working session on reviewing the work of the Code Review Guide team. I know its much more exciting to learn new hacking techniques or procedures to prevent it. Never less reviewing the book is a very much-needed effort and Gary and I very much appreciate everyone in New York taking time to do this. &lt;br /&gt;
&lt;br /&gt;
I also want to give out a big shout of thanks to Ken Belva for help in pushing both Gary and myself to get the document ready for everyone. Last but not least we both also want to thank Helen Gao and Charles Beganskas.&lt;br /&gt;
&lt;br /&gt;
== In Print ==&lt;br /&gt;
[http://www.lulu.com/content/5678680 Code Review Guide V1.1] on Lulu.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; rowspan=&amp;quot;2&amp;quot;| [[File:Midlevel projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-builders-small.png|link=]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-defenders-small.png|link=]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  | [[File:Project_Type_Files_CODE.jpg|link=]]&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Volunteers==&lt;br /&gt;
The OWASP Code Review project was conceived by Eoin Keary, the OWASP Ireland Founder and Chapter Lead. Current project leaders are Larry Conklin and Gary Robinson If you are interested in volunteering for the project, or have a comment, question, or suggestion, please drop me a line [mailto:larry.conklin@owasp.org larry.conklin@owasp.org] or [mailto:gary.robinson@owasp.org gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
==Get Involved==&lt;br /&gt;
All of the OWASP Guides are living documents that will continue to change as the threat and security landscape changes.&lt;br /&gt;
We welcome everyone to join the Code Review Guide Project and help us make this document great. The best way to get started is to subscribe to the mailing list by following the link below or contact the project leaders listed below.&lt;br /&gt;
&lt;br /&gt;
Please introduce yourself and ask to see if there is anything you can help with. We are always looking for new contributions. If there is a topic that you’d like to research and contribute, please let us know!&lt;br /&gt;
&lt;br /&gt;
 Code Review Mailing list[mailto:owasp-codereview@lists.owasp.org owasp-codereview@lists.owasp.org]&lt;br /&gt;
&lt;br /&gt;
 Project leaders [mailto:larry.conklin@owasp.org larry.conklin@owasp.org] or [mailto:gary.robinson@owasp.org gary.robinson@owasp.org]&lt;br /&gt;
&lt;br /&gt;
=Project About=&lt;br /&gt;
{{:Projects/OWASP Code Review Project| Project About}}&lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]] [[Category:OWASP Project|Code Review Project]]&lt;br /&gt;
[[Category:OWASP Document]]&lt;br /&gt;
[[Category:OWASP Release Quality Document]]&lt;br /&gt;
[[Category:SAMM-CR-1]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Category:OWASP_Github_Documentation&amp;diff=208966</id>
		<title>Category:OWASP Github Documentation</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Category:OWASP_Github_Documentation&amp;diff=208966"/>
				<updated>2016-02-15T21:25:02Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Proposal to transport OWASP wiki content Documentation to a centralize system==&lt;br /&gt;
&lt;br /&gt;
===Problem Definition===&lt;br /&gt;
The issues that can arise from our current method of developing our various docs include:&lt;br /&gt;
*Draft content that exists in the wiki.  This may be in varying states (correct, incorrect, lousy, confused, etc.) and is visible to the internet and typically not clearly labelled as draft.  Google ‘owasp purple monkey dishwasher’ for an example of a draft wiki page visible to the internet.  This content also needs to get cleaned up after a project release.&lt;br /&gt;
*Substandard descriptions/content can get into our docs.  Getting people to review every line/example/diagram/appendix is difficult with a volunteer organization (as other threads have discussed)&lt;br /&gt;
*Duplications happen, as 10 different projects create/copy/paste their definitions of topics such as XSS, SQLi, CSRF, etc.  This wastes effort in an organization already constrained of active volunteers.&lt;br /&gt;
*Content gets out-of-date.  The work to create a new version of a doc project takes years.&lt;br /&gt;
&lt;br /&gt;
==Proposal Details==&lt;br /&gt;
* We dump all of the content from our wiki, current docs, descriptions in code tools, etc.  We put it into markup (as some projects are already doing) and add it to source code repositories.&lt;br /&gt;
* We share doc markup files across ALL docs and code projects.  For example, imagine we have a folder for SQLi.  This directory contains the OWASP ‘golden source’ for SQLi definition, examples, code, tests, etc.  * Repeat for all other AppSec issues (CSRF, cert pinning, etc.).  We use a mechanism to ‘compile’ these markdown files into PDFs and integrate into code project HTML pages.&lt;br /&gt;
* Similar to good coding projects, we control who can edit the files under certain directories – people we know have expertise in an area.  Edits get peer reviewed before submission.  Other people can suggest edits and prove their experience to the existing team to join it.&lt;br /&gt;
*We allow anyone to ‘include’ this markup file into their project.  So if the Code Review Guide wants to add a section on SQLi, and needs a definition, I don’t write it (or copy from wiki), I simply include the relevant markup file.  Same for testing guide, dev guide, ZAP hints page, security shepherd info page, cheetsheet, and on and on.&lt;br /&gt;
*We allow all of our docs, plus the wiki, plus all code projects, to dynamically use an markup file update.  We make this ‘real time’.  This needs an example.  Say in March a massive change occurs in the world of SQLi.  Right now any project that talks about SQLi would need to manually go in and update, and those updates will be of varying quality and content.  If, instead, one (true) source file was update, all those other projects could spot the change and automatically rebuild themselves, meaning the next person to download a development guide PDF, or view the wiki, would get the updated SQLi information.&lt;br /&gt;
&lt;br /&gt;
This is a big change.  This may be a controversial change.  However it would greatly reduce our workload (only one markup document needs to get updated).  It will also greatly reduce review tasks, as everyone is sharing core content which is reviewed once.  It also improves our image to the world, as all projects have the same great descriptions and content.&lt;br /&gt;
  This change also improves our responsiveness.  Imagine a heartbleed type issue being reflected in all OWASP code and documentation projects, as well as the wiki/cheetsheets, within a few days?  (simply the time for the team to agree updates to the text/examples/descriptions, review, and submit)&lt;br /&gt;
 We should also make these markup files available to anyone on the internet (read only).  This way the source descriptions become an OWASP resource it itself, and anyone out there needing to spread the word on AppSec has easy access to rock solid, up-to-date definitions.&lt;br /&gt;
This changes the model, from people like myself who run ‘projects’, to smaller expert teams who know ‘technologies’ (such as SQLi or IIS secure configuration).  It focuses people where they want to be on docs projects, but easily shares that knowledge across all OWASP (and more) projects.  It also means there’d never be another need to clean-up the wiki – it would always be based off the markup content.&lt;br /&gt;
&lt;br /&gt;
Big downside: there’s a large piece of work to start it off.  All content would need to get organized, put into sensible structure, converted to markdown, argued over, ‘experts’ defined and assigned, etc.  I doubt this would be a volunteer effort, and may need contractor involvement.  Could this be combined with the OWASP wiki redesign?&lt;br /&gt;
&lt;br /&gt;
==Draft Plan==&lt;br /&gt;
&lt;br /&gt;
==Volunteers==&lt;br /&gt;
&lt;br /&gt;
Gary Robinson&lt;br /&gt;
&lt;br /&gt;
==Participating Document Projects==&lt;br /&gt;
&lt;br /&gt;
Code Review Project&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=203245</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=203245"/>
				<updated>2015-11-09T21:49:13Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Sponsorship Opportunities ==&lt;br /&gt;
&lt;br /&gt;
There are many ways you can help the OWASP Belfast Chapter spread the word about computer security and secure coding.  Including the following:&lt;br /&gt;
* If you have a room available to hold a meeting, let us know.&lt;br /&gt;
* Companies can cover the OWASP membership costs of their employees.&lt;br /&gt;
* Supply a speaker on a topic of interest to the OWASP Belfast members, or cover their costs to present.&lt;br /&gt;
* Sponsor food and drink for a session.&lt;br /&gt;
* Further sponsorship can be provided directly to the OWASP Belfast Chapter itself, using the link above.  Direct sponsorship allows the OWASP Belfast Board to use the funds as needed to run events.&lt;br /&gt;
&lt;br /&gt;
In return for any sponsorship we can add your company to our list of sponsors on the OWASP Wiki and Meetup sites, and share communications with session attendees.  Contact the OWASP Belfast Board (below) for more details.&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:johnathan.kuskos@owasp.org Johnathan Kuskos]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Wednesday November 25th'''&lt;br /&gt;
&lt;br /&gt;
'''Hands on Hacking with OWASP Security Shepherd'''&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast's November session will be a presentation and hands on hacking experience with the OWASP Security Shepherd team.  &lt;br /&gt;
&lt;br /&gt;
We are excited to have Mark and Paul, the creators of Security Shepherd, joining us for the night to talk us through the web site hacking tool that educates the user while allowing them to hack their specialized site.&lt;br /&gt;
&lt;br /&gt;
We will be meeting in the large lecture theatre in Queen's Ashby Building for the night.  Participants should bring their laptops along as Mark and Paul talk us through the Security Shepherd tool and allow us to hack our way through it.  No previous experience of hacking web sites is required (in fact the tool starts the user from basic hacks up to the most advanced).&lt;br /&gt;
&lt;br /&gt;
Participants without laptops can still attend and learn about the tool and hacking techniques involved.  Participants can also form teams to share their laptops and hack the site faster.  The session is expected to run from 6:30pm to around 8pm.&lt;br /&gt;
&lt;br /&gt;
Unfortunately there will not be any pizza at this session, however there will be an opportunity to socialize with Mark, Paul and the other attendees afterwards.&lt;br /&gt;
&lt;br /&gt;
Note: To prepare your laptop for the session, please install the Firefox browser (or Google Chrome) and a proxy such as OWASP ZAP (free) or Burp. &lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/events/226561409/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=203081</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=203081"/>
				<updated>2015-11-05T10:33:08Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:johnathan.kuskos@owasp.org Johnathan Kuskos]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Wednesday November 25th'''&lt;br /&gt;
&lt;br /&gt;
'''Hands on Hacking with OWASP Security Shepherd'''&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast's November session will be a presentation and hands on hacking experience with the OWASP Security Shepherd team.  &lt;br /&gt;
&lt;br /&gt;
We are excited to have Mark and Paul, the creators of Security Shepherd, joining us for the night to talk us through the web site hacking tool that educates the user while allowing them to hack their specialized site.&lt;br /&gt;
&lt;br /&gt;
We will be meeting in the large lecture theatre in Queen's Ashby Building for the night.  Participants should bring their laptops along as Mark and Paul talk us through the Security Shepherd tool and allow us to hack our way through it.  No previous experience of hacking web sites is required (in fact the tool starts the user from basic hacks up to the most advanced).&lt;br /&gt;
&lt;br /&gt;
Participants without laptops can still attend and learn about the tool and hacking techniques involved.  Participants can also form teams to share their laptops and hack the site faster.  The session is expected to run from 6:30pm to around 8pm.&lt;br /&gt;
&lt;br /&gt;
Unfortunately there will not be any pizza at this session, however there will be an opportunity to socialize with Mark, Paul and the other attendees afterwards.&lt;br /&gt;
&lt;br /&gt;
Note: To prepare your laptop for the session, please install the Firefox browser (or Google Chrome) and a proxy such as OWASP ZAP (free) or Burp. &lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/events/226561409/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=CRV2_Forward&amp;diff=201007</id>
		<title>CRV2 Forward</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=CRV2_Forward&amp;diff=201007"/>
				<updated>2015-09-23T15:45:58Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''The OWASP Code Review Guide:'''&lt;br /&gt;
&lt;br /&gt;
The OWASP Code Review guide is the result of initially contributing and leading the Testing Guide. Initially, it was thought to place Code review and testing into the same guide; it seemed like a good idea at the time. But the topic called security code review got too big and evolved into its own stand-alone guide.&lt;br /&gt;
 &lt;br /&gt;
The Code Review guide was started in 2006 by [https://www.owasp.org/index.php/Eoin_Keary Eoin Keary]. &lt;br /&gt;
This current version was started in April 2013 via the OWASP Project Reboot initiative.&lt;br /&gt;
&lt;br /&gt;
The [[OWASP Code Review team]] consists of a small, but talented, group of volunteers who should really get out more often.&lt;br /&gt;
 &lt;br /&gt;
It is common knowledge that more secure software can be produced and developed in a more cost effective way when bugs are detected early on in the systems development life-cycle. Organizations with a proper code review functions integrated into the software development life-cycle (SDLC) produced remarkably better code from a security standpoint. Simply put &amp;quot;We can't hack ourselves secure&amp;quot;. Attackers have more time to fine vulnerabilities on a system than the time allocated to a defender. Hacking our way secure amounts to a uneven battlefield; Asymmetric warfare, a loosing battle.&lt;br /&gt;
&lt;br /&gt;
By necessity, this guide does not cover all languages; it mainly focuses on .NET and Java, but has a little C/C++ and PHP thrown in also. However, the techniques advocated in the book can be easily adapted to almost any code environment. Fortunately, the security flaws in web applications are remarkably consistent across programming languages.&lt;br /&gt;
&lt;br /&gt;
Purple Monkey Dishwasher&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=200301</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=200301"/>
				<updated>2015-09-09T20:58:38Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:johnathan.kuskos@owasp.org Johnathan Kuskos]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Thursday October 1st'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Thursday 1st October at the Radisson Blu (near the GasWorks).  The event is free to attend and will have a great talk on Mobile Pentesting followed by time to ask general questions and socialize.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
* 7:00pm - Introductions and information&lt;br /&gt;
* 7:15pm - Mobile Pentesting presentation by Leo McCavana &lt;br /&gt;
* 8:00pm - Discussion and socializing&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/events/225232883/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=200174</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=200174"/>
				<updated>2015-09-07T18:17:58Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
* [mailto:johnathan.kuskos@owasp.org Johnathan Kuskos]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Thursday October 1st'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Thursday 1st October at the Radisson Blu (near the GasWorks).  The event is free to attend and will have a great talk on Mobile Pentesting followed by time to ask general questions and socialize.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=200173</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=200173"/>
				<updated>2015-09-07T18:16:44Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - Thursday October 1st'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Thursday 1st October at the Radisson Blu (near the GasWorks).  The event is free to attend and will have a great talk on Mobile Pentesting followed by time to ask general questions and socialize.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=191413</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=191413"/>
				<updated>2015-03-14T14:03:13Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - March 2015'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Wednesday 18th March at the Citi building, 60 Sydenham Rd (beside the Odyssey).  The event is free to attend and will have 2 great talks on the current state of the security industry, and as usual pizza and soft drinks will be provided.  There will also be the opportunity to avail of some free OWASP merchandise.  This event will be held in association with ISACA Ireland.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
* 6:30pm - Mark Schloesser from Rapid7 will discuss &amp;quot;Conducting internet-wide research&amp;quot;.  Mark Schloesser (@repmovsb) is a security researcher at Rapid7, analyzing threats and developing countermeasures to help defenders understand and protect against the risks they face. He is deeply involved in developing open-source software and in his free time likes reverse engineering malware and botnets and participating in CTF competitions. He regularly speaks at industry events, most recently Black Hat USA and Black Hat Asia.&lt;br /&gt;
* 7:10pm - PSNI Dective Inspector Dougie Grant will provide an update on Cyber Security Crime within Northern Ireland, the Police Service of Northern Ireland's Non-Emergency Cyber Incident Report system for businesses, and the Cyber Security Information Sharing Partnership (CISP) Northern Ireland group&lt;br /&gt;
* 7:50pm - Discussion and debate over pizza and soft drinks&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast would like to thank InvestNI for their sponsoring of this event and the OWASP Belfast Chapter, and Citi for the use of their venue for this event.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190764</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190764"/>
				<updated>2015-03-04T06:59:43Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - March 2015'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Wednesday 18th March at the Citi building, 60 Sydenham Rd (beside the Odyssey).  The event is free to attend and will have 2 great talks on the current state of the security industry, and as usual Pizza and soft drinks will be provided.  There will also be the opportunity to avail of some free OWASP merchandise.  This event will be held in association with ISACA Ireland.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
* 6:30pm - Mark Schloesser from Rapid7 will discuss &amp;quot;Conducting internet-wide research&amp;quot;.  Mark Schloesser (@repmovsb) is a security researcher at Rapid7, analyzing threats and developing countermeasures to help defenders understand and protect against the risks they face. He is deeply involved in developing open-source software and in his free time likes reverse engineering malware and botnets and participating in CTF competitions. He regularly speaks at industry events, most recently Black Hat USA and Black Hat Asia.&lt;br /&gt;
* 7:05pm - A representative of the PSNI Cyber Security Division will discuss upcoming Cyber Security initiatives specific to Northern Ireland&lt;br /&gt;
* 7:40pm - Discussion and debate over Pizza and soft drinks&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast would like to thank InvestNI for their sponsoring of this event and the OWASP Belfast Chapter, and Citi for the use of their venue for this event.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190533</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190533"/>
				<updated>2015-03-02T12:07:42Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - March 2015'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Wednesday 18th March at the Citi building, 60 Sydenham Rd (beside the Odyssey).  The event is free to attend and will have 2 great talks on the current state of the security industry, and as usual Pizza and soft drinks will be provided.  There will also be the opportunity to avail of some free OWASP merchandise.  This event will be held in association with ISACA Ireland.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
* 6:30pm - Mark Schloesser from Rapid7 will discuss &amp;quot;Modern security scalability challenges&amp;quot;.  Mark Schloesser (@repmovsb) is a security researcher at Rapid7, analyzing threats and developing countermeasures to help defenders understand and protect against the risks they face. He is deeply involved in developing open-source software and in his free time likes reverse engineering malware and botnets and participating in CTF competitions. He regularly speaks at industry events, most recently Black Hat USA and Black Hat Asia.&lt;br /&gt;
* 7:05pm - A representative of the PSNI Cyber Security Division will discuss upcoming Cyber Security initiatives specific to Northern Ireland&lt;br /&gt;
* 7:40pm - Discussion and debate over Pizza and soft drinks&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast would like to thank InvestNI for their sponsoring of this event and the OWASP Belfast Chapter, and Citi for the use of their venue for this event.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190532</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190532"/>
				<updated>2015-03-02T12:02:57Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - March 2015'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Wednesday 18th March at the Citi building, 60 Sydenham Rd (beside the Odyssey).  The event is free to attend and will have 2 great talks on the current state of the security industry, and as usual Pizza and soft drinks will be provided.  There will also be the opportunity to avail of some free OWASP merchandise.  This event will be held in association with ISACA Ireland.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
* 6:30pm - Mark Schloesser from Rapid7 will discuss &amp;quot;Modern security scalability challenges&amp;quot;&lt;br /&gt;
* 7:05pm - A representative of the PSNI Cyber Security Division will discuss upcoming Cyber Security initiatives specific to Northern Ireland&lt;br /&gt;
* 7:40pm - Discussion and debate over Pizza and soft drinks&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast would like to thank InvestNI for their sponsoring of this event and the OWASP Belfast Chapter, and Citi for the use of their venue for this event.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190505</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190505"/>
				<updated>2015-03-01T17:17:03Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - March 2015'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Wednesday 18th March at the Citi building, 60 Sydenham Rd (beside the Odyssey).  The event will have 2 great talks on the current state of the security industry, and as usual Pizza and soft drinks will be provided.  There will also be the opportunity to avail of some free OWASP merchandise.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
* 6:30pm - Mark Schloesser from Rapid7 will discuss &amp;quot;Modern security scalability challenges&amp;quot;&lt;br /&gt;
* 7:05pm - A representative of the PSNI Cyber Security Division will discuss upcoming Cyber Security initiatives specific to Northern Ireland&lt;br /&gt;
* 7:40pm - Discussion and debate over Pizza and soft drinks&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast would like to thank InvestNI for their sponsoring of this event and the OWASP Belfast Chapter, and Citi for the use of their venue for this event.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190504</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190504"/>
				<updated>2015-03-01T17:15:04Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - March 2015'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Wednesday 18th March at the Citi building, 60 Sydenham Rd (beside the Odyssey).  The event will have 2 great talks on the current state of the security industry, and as usual Pizza and soft drinks will be provided.  There will also be the opportunity to avail of some free OWASP merchandise.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
* 6:30pm - Mark Schloesser from Rapid7 will discuss &amp;quot;Modern security scalability challenges&amp;quot;&lt;br /&gt;
* 7:05pm - A representative of the PSNI Cyber Security Division will discuss upcoming Cyber Security specific to Northern Ireland&lt;br /&gt;
* 7:40pm - Discussion and debate over Pizza and soft drinks&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast would like to thank InvestNI for their sponsoring of this event and the OWASP Belfast Chapter, and Citi for the use of their venue for this event.&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190503</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=190503"/>
				<updated>2015-03-01T17:13:50Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - March 2015'''&lt;br /&gt;
&lt;br /&gt;
The next OWASP Belfast Chapter session will be taking place on Wednesday 18th March at the Citi building, 60 Sydenham Rd (beside the Odyssey).  The event will have 2 great talks on the current state of the security industry, and as usual Pizza and soft drinks will be provided.  There will also be the opportunity to avail of some free OWASP merchandise.&lt;br /&gt;
&lt;br /&gt;
Itinerary of events:&lt;br /&gt;
* 6:30pm - Mark Schloesser from Rapid7 will discuss &amp;quot;Modern security scalability challenges&amp;quot;&lt;br /&gt;
* 7:05pm - A representative of the PSNI Cyber Security Division will discuss upcoming Cyber Security specific to Northern Ireland&lt;br /&gt;
* 7:40pm - Discussion and debate over Pizza and soft drinks&lt;br /&gt;
&lt;br /&gt;
You can RSVP for the event at the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=CRV2_CodeReviewTools&amp;diff=190084</id>
		<title>CRV2 CodeReviewTools</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=CRV2_CodeReviewTools&amp;diff=190084"/>
				<updated>2015-02-22T17:10:22Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
As discussed in Code Review Guide there are many reason to automate the process of code reviews within the organization SDLC practices. We won't review all those reasons here again but we would like to share with the reader a list of the tools both commercial and open source. OWASP is vendor natural for that reason the text below is supplied by the vendors themselves unless otherwise stated. OWASP does not endorse commercial or open source tools outside of OWASP own projects.&lt;br /&gt;
&lt;br /&gt;
==Commercial Code Review Tools==&lt;br /&gt;
===Crucible by Atlassian Software===&lt;br /&gt;
* https://www.atlassian.com/software/crucible/overview&lt;br /&gt;
====Begin Atlassian supplied description of their Code Review tool====&lt;br /&gt;
&lt;br /&gt;
Crucible is Atlassian’s on-premises code review solution for enterprise teams. Crucible makes it easy to review code changes, make comments and record outcomes thoroughly and efficiently. It encourages developers to carry out more code reviews – improving code quality and fostering collaboration. It is code review made easy for Subversion, CVS, Perforce and other systems.&lt;br /&gt;
&lt;br /&gt;
The flexible code review process allows you to configure your reviews based on workflows or participants. Whether used to perform ad-hoc reviews or in a formal process, Crucible removes the administrative overhead and enables distributive teams to work together. As reviews are inherently iterative, Crucible’s fully threaded comments let teams discuss code regardless of time and location and provide comments directly on specific source lines and files. &lt;br /&gt;
&lt;br /&gt;
When using Crucible, individuals can create reviews directly from the command line, build quick reviews with cut-and-paste snippets and perform one-click reviews from changesets or issues. These reviews can be carried out before check-ins, ensuring the quality of code going into production. As files are always kept up-to-date, developers do not have to worry they are reviewing code that is outdated.  With the added bonus of notifications &amp;amp; reminders, audit trails, and reports, Crucible is here to help you produce the best source code possible.&lt;br /&gt;
&lt;br /&gt;
====End Atlassian supplied description of their Code Review tool====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===ReviewBoard by reviewboard.org===&lt;br /&gt;
* http://www.reviewboard.org/&lt;br /&gt;
====Begin ReviewBoard description by Gary Robinson====&lt;br /&gt;
ReviewBoard is a freely available (MIT license) open source tool supporting many of the review functions required for all sizes of projects, from small team projects to large company repositories.  &lt;br /&gt;
The ReviewBoard server is cross platform (runs on Python) and supports SVN, CVS, GIT, Perforce repositories, as well as integrating with your companies LDAP infastructure to control authenticated users.  It allows code diffs to be submitted pre-commit and post-commit with facilities for coder documentation/annotation and integration with bug tracking software (e.g. bugzilla) to allow reviewers to have more context during the review.&lt;br /&gt;
Code reviewers can collaborate in two ways; reviewers comments are displayed in-line in a diff viewing of the code via the web interface, and are sent via e-mail to the code submitter and other reviewers.&lt;br /&gt;
ReviewBoard also offers to host a review tool in the cloud for a fee.&lt;br /&gt;
&lt;br /&gt;
====End ReviewBoard description by Gary David Robinson====&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=189733</id>
		<title>CRV2 SecCommsHTTPHdrs</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=189733"/>
				<updated>2015-02-15T17:33:35Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= This is a draft version =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
HTTP headers allow the server to dictate or advise the user agent and intermediary servers how to handle the content being provided.  Some of these headers can aid a web site in securing itself; these include the standard Cache-Control headers, and newer specifications like HSTS and Content Security Policy headers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&lt;br /&gt;
From a security point of view controlling the HTTP headers sent with web site content can tell the users browser how to store the content, how to access further content, and how to trust various parts of the content received by the browser.  &lt;br /&gt;
&lt;br /&gt;
Two points to note up front:&lt;br /&gt;
&lt;br /&gt;
# Headers can only be trusted over a HTTPS session&lt;br /&gt;
# This section only covers HTTP response headers&lt;br /&gt;
&lt;br /&gt;
Without HTTPS between the web server and the users browser an attacker can modify the content or the associated headers.  Thus if you were returning headers specifying that your web site should only be access over HTTPS, an attacker could remove these headers and the browser would not receive the information.  A web site should not trust HTTP request headers for security decisions as there are many ways an attacker could modify these headers (or construct the whole request themselves), so there is nothing to cover for secure headers coming from the client, as they are inherently insecure.  Of course the cookie header is an exception to this, but that is because our web site has set the cookie header to a random value that should only be known during the browsing session. This section will not cover the cookie header as this is covered in the session management topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Caching Headers ===&lt;br /&gt;
&lt;br /&gt;
For business web sites that allow sensitive or confidential information to be downloaded to the client device, the caching of that sensitive data will become a security issue.  A user accessing their bank account details does not want an intermediary proxy caching their web pages.  A legal web site does not want copies of sensitive PDF documents stored on the laptop or smartphone disk storage, only for that device to be lost and the documents visible to an attacker.&lt;br /&gt;
&lt;br /&gt;
The 'Cache-Control' header tells the users browser how to handle the content being downloaded.  Some browsers can interpret the header values differently thus the understood header settings to return with content that must not be cached are:&lt;br /&gt;
&lt;br /&gt;
 Cache-Control: no-store, no-cache&lt;br /&gt;
 Pragma: no-cache&lt;br /&gt;
 Expires: 0&lt;br /&gt;
&lt;br /&gt;
This should be understood by all browsers (including mobile webviews) that the content being returned must not be stored to disk cache.  Note that it is possible for intermediate proxies to ignore caching headers and still cache the content, which is another reason why using end-to-end HTTPS sessions is important, as the proxies will only have encrypted versions of the sensitive content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Content Security Policy ===&lt;br /&gt;
&lt;br /&gt;
Cross Site Scripting (XSS) is still one of the most frequent security issues experienced on web sites, it's A3 on the OWASP Top 10 (2013), and it covers a variety of ways attackers can bypass the browser same origin policy to trick the browsers into executing the attackers code. Content Security Policy headers are designed to allow a web site to inform the browser where scripts, frames, etc can be sourced from, and are a good way of mitigating XSS issues.&lt;br /&gt;
&lt;br /&gt;
The structure of the header is as follows:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: &amp;lt;directive&amp;gt; &amp;lt;sources&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where the directive tells the browser what type of content is being controlled, and the source lists the places where the content can validly be obtained from, for example:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' https://www.example.com&lt;br /&gt;
&lt;br /&gt;
... tells the browser that javascript code files (i.e. *.js files) can only be sourced from 'self' (i.e. the current web site, note the single quotes are necessary) or https://www.example.com.  If the browser rendering the page finds javascript from some other site, it will fail to render and flag an error message to the end user.  In this way the web site has prevented the attacker from injecting links to their own javascript (e.g. &amp;quot;&amp;lt;script src='http://badguy.com/bad.js'&amp;gt;&amp;lt;/script&amp;gt;&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The directives controlled by the Content Security Policy include:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Directive&lt;br /&gt;
|Description&lt;br /&gt;
|-&lt;br /&gt;
|script-src&lt;br /&gt;
|Lists the sources where javascript files are allowed to be sourced from.&lt;br /&gt;
|-&lt;br /&gt;
|object-src&lt;br /&gt;
|Lists the sources where flash and other plugin objects are allowed from. &lt;br /&gt;
|-&lt;br /&gt;
|frame-src&lt;br /&gt;
|Lists the sources where frames are allowed from. &lt;br /&gt;
|-&lt;br /&gt;
|style-src&lt;br /&gt;
|Lists the sources where CSS files are allowed from. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
If a directive is not specified then the default is wide open, all sources are allowed.  If you do not wish to provide a directive for all options then you can specify a default-src which will then apply to all unspecified directives, for example:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: default-src 'self'&lt;br /&gt;
&lt;br /&gt;
... forces all scripts, frames, objects, etc to be sourced from the current web site.  When specifying a URL the scheme is enforced, so stating https://www.example.com will prevent any items coming from www.example.com over HTTP (i.e. without SSL).  You can also provide a wildcard on the leftmost portion of the domain, e.g. https://*.example.com.  Multiple directives are separated by semi-colons, e.g.&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' https://www.example.com; frame-src 'self' https://frames.example.com&lt;br /&gt;
&lt;br /&gt;
If you wished to completely disable an option, for example you don't want any frames in your page, you can disable a directive using the 'none' keyword:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: frame-src 'none'&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Preventing Inlining ====&lt;br /&gt;
&lt;br /&gt;
A further feature of Content Security Policy is to tell the browser not to allow inline javascript code, or evals.  As well as driving better programming practices by separating scripting code from the display markup, this option allows inline scripting to be disabled (a major vector of XSS, e.g. &amp;lt;script&amp;gt;alert(1);&amp;lt;/script&amp;gt;).  By providing a script-src or style-src (in the case of CSS) the Content Security Policy automatically bans inline scripts (javascript and CSS).  If you wish to allow inline scripting, or inline use of the eval function (which can construct javascript) you have to explicitly specify 'unsafe-inline' or 'unsafe-eval', e.g.&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' 'unsafe-inline'&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Applying CSP To Web Pages ====&lt;br /&gt;
&lt;br /&gt;
When using Content Security Policy, note that the header has to be included in every web page.  This can easily be achieved through configuration of common frameworks (e.g. mod_headers in Apache) if the policy is the same for the entire site.  If the Content Security Policy header is being dynamically created for each web page, be aware that directives cannot be repeated, if the header specifies the directive the second listing will be ignored.&lt;br /&gt;
&lt;br /&gt;
The header varies slightly between IE and other browsers, for IE you must specify &amp;quot;X-Content-Security-Policy&amp;quot;, whilst all other browsers use &amp;quot;Content-Security-Policy&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Using Content Security Policy Reporting  ====&lt;br /&gt;
&lt;br /&gt;
The Content Security Policy allows the browser to report any violations of the defined sources.  The CSP header can include the &amp;quot;report-uri&amp;quot; directive as in the following:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: default-src 'self'; report-uri /csp_receiver;&lt;br /&gt;
&lt;br /&gt;
With this directive, if the browser experiences any page/content that violates the directive it will send a JSON report to the defined URL similar to the following:&lt;br /&gt;
&lt;br /&gt;
 {&lt;br /&gt;
   &amp;quot;csp-report&amp;quot;: {&lt;br /&gt;
     &amp;quot;document-uri&amp;quot;: &amp;quot;https://www.example.com/default.html&amp;quot;,&lt;br /&gt;
     &amp;quot;referrer&amp;quot;: &amp;quot;https://www.example.com/&amp;quot;,&lt;br /&gt;
     &amp;quot;blocked-uri&amp;quot;: &amp;quot;https://bad.guy.com/bad_guy.js&amp;quot;,&lt;br /&gt;
     &amp;quot;violated-directive&amp;quot;: &amp;quot;script-src 'self' https://www.example.com&amp;quot;,&lt;br /&gt;
     &amp;quot;original-policy&amp;quot;: &amp;quot;script-src 'self' https://www.example.com; report-uri https://www.example.com/csp_receiver&amp;quot;&lt;br /&gt;
   }&lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
This reporting feature can be used to determine any attacks occurring on your content.  Also note that if you specify HTTPS in the report-uri scheme, and the receiver URI is on the current web server, the report JSON can be authenticated as the cookie will be passed over the secure session.&lt;br /&gt;
&lt;br /&gt;
If you simply wish to trail the CSP headers, i.e. not actually have the browser enforce the constraints encase it breaks anything, you can instead use the &amp;quot;Content-Security-Policy-Report-Only&amp;quot; header.  This will tell the browser to understand the directives and monitor for policy violations, but in the case of a violation the browser will still render the page as if the header was not specified, instead it will send the JSON report.  This is a great way to trail the CSP headers on live traffic to see what breaches are currently occurring, or to ensure you have configured your CSP headers before deployment.  An example of this is:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy-Report-Only: default-src 'self'; report-uri /csp_receiver;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== HTTP Strict Transport Security ===&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header. When the browser receives the HSTS header it will prevent any subsequent requests from being sent over HTTP to the web site, instead only using HTTPS, for the timeframe specified in the header. It also prevents HTTPS click through prompts on browsers.&lt;br /&gt;
&lt;br /&gt;
Simple example, using a long (1 year) max-age:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000&lt;br /&gt;
&lt;br /&gt;
If all present and future subdomains will be HTTPS:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains&lt;br /&gt;
&lt;br /&gt;
If the site owner would like their domain to be included in the  maintained by Chrome (and used by Firefox and Safari), then use:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains; preload&lt;br /&gt;
&lt;br /&gt;
The 'preload' flag indicates the site owner's consent to have their domain preloaded. The site owner still needs to then go and submit the domain to the list.&lt;br /&gt;
&lt;br /&gt;
Use caution when setting excessively strict STS policies. Including subdomains should only be used in environments where all sites within your organization for the given domain name require ssl. Max-age limits should be carefully considered as infrequent visitors may find your site inaccessible if you relax your policy.&lt;br /&gt;
&lt;br /&gt;
Before enabling includeSubDomains, also consider the impact of any existing DNS CNAME records for CDNs, email services, or other 3rd party services. Since includeSubDomains will force such CNAME subdomains to https:// it's likely the browser will throw a domain-mismatch error, which is hard to reverse because of the browser caching nature of HSTS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What to Review ==&lt;br /&gt;
&lt;br /&gt;
When reviewing code modules from an HTTP header security point of view, some common issues to look out for include:&lt;br /&gt;
&lt;br /&gt;
* Do not perform security decisions based on client request HTTP headers (apart from the cookie headers specified as HTTPOnly)&lt;br /&gt;
* Do not trust request headers not passed over HTTPS connections.&lt;br /&gt;
* Ensure you validate the format (length, characters, etc) of the header value before processing it.&lt;br /&gt;
* For sensitive content, remember to specify the relevant caching headers so standard browsers do not store the content to disk.  Remember, however, that non-standard browsers or intermediate proxies can ignore the caching headers, thus delivering sensitive content over HTTPS provides more protection.&lt;br /&gt;
* Consider providing Content Security Policy headers for your site.&lt;br /&gt;
* Ensure CSP headers are provided for all web pages, typically using web framework configuration.&lt;br /&gt;
* Test the CSP header settings using the &amp;quot;Content-Security-Policy-Report-Only&amp;quot; header to ensure current web usage is not affected.&lt;br /&gt;
* Include CSP header testing in testing, adding specific test cases to ensure violations are caught.&lt;br /&gt;
* If CSP headers are being used to prevent inline XSS, do not relax other protections such as input validation or output encoding.&lt;br /&gt;
* Note there are two ways to ensure a web sites' pages are loaded using HTTPS only:&lt;br /&gt;
** Setting &amp;quot;Strict-Transport-Security&amp;quot; headers, which only need to be specified once per 'max-age' timeframe and is remembered by the browser for subsequent get requests&lt;br /&gt;
** Setting CSP header to specify an HTTPS domain, e.g. &amp;quot;Content-Security-Policy: default-src 'self' https:&amp;quot;, which must be specified on every page, and only affects artifacts loaded for the current page, not subsequent get requests.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* https://www.owasp.org/index.php/HTTP_Strict_Transport_Security&lt;br /&gt;
* http://content-security-policy.com/&lt;br /&gt;
* http://www.html5rocks.com/en/tutorials/security/content-security-policy/&lt;br /&gt;
* http://www.w3.org/TR/CSP/&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=189732</id>
		<title>CRV2 SecCommsHTTPHdrs</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=189732"/>
				<updated>2015-02-15T17:21:01Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= This is a draft version =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
HTTP headers allow the server to dictate or advise the user agent and intermediary servers how to handle the content being provided.  Some of these headers can aid a web site in securing itself; these include the standard Cache-Control headers, and newer specifications like HSTS and Content Security Policy headers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&lt;br /&gt;
From a security point of view controlling the HTTP headers sent with web site content can tell the users browser how to store the content, how to access further content, and how to trust various parts of the content received by the browser.  &lt;br /&gt;
&lt;br /&gt;
Two points to note up front:&lt;br /&gt;
&lt;br /&gt;
# Headers can only be trusted over a HTTPS session&lt;br /&gt;
# This section only covers HTTP response headers&lt;br /&gt;
&lt;br /&gt;
Without HTTPS between the web server and the users browser an attacker can modify the content or the associated headers.  Thus if you were returning headers specifying that your web site should only be access over HTTPS, an attacker could remove these headers and the browser would not receive the information.  A web site should not trust HTTP request headers for security decisions as there are many ways an attacker could modify these headers (or construct the whole request themselves), so there is nothing to cover for secure headers coming from the client, as they are inherently insecure.  Of course the cookie header is an exception to this, but that is because our web site has set the cookie header to a random value that should only be known during the browsing session. This section will not cover the cookie header as this is covered in the session management topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Caching Headers ===&lt;br /&gt;
&lt;br /&gt;
For business web sites that allow sensitive or confidential information to be downloaded to the client device, the caching of that sensitive data will become a security issue.  A user accessing their bank account details does not want an intermediary proxy caching their web pages.  A legal web site does not want copies of sensitive PDF documents stored on the laptop or smartphone disk storage, only for that device to be lost and the documents visible to an attacker.&lt;br /&gt;
&lt;br /&gt;
The 'Cache-Control' header tells the users browser how to handle the content being downloaded.  Some browsers can interpret the header values differently thus the understood header settings to return with content that must not be cached are:&lt;br /&gt;
&lt;br /&gt;
 Cache-Control: no-store, no-cache&lt;br /&gt;
 Pragma: no-cache&lt;br /&gt;
 Expires: 0&lt;br /&gt;
&lt;br /&gt;
This should be understood by all browsers (including mobile webviews) that the content being returned must not be stored to disk cache.  Note that it is possible for intermediate proxies to ignore caching headers and still cache the content, which is another reason why using end-to-end HTTPS sessions is important, as the proxies will only have encrypted versions of the sensitive content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Content Security Policy ===&lt;br /&gt;
&lt;br /&gt;
Cross Site Scripting (XSS) is still one of the most frequent security issues experienced on web sites, it's A3 on the OWASP Top 10 (2013), and it covers a variety of ways attackers can bypass the browser same origin policy to trick the browsers into executing the attackers code. Content Security Policy headers are designed to allow a web site to inform the browser where scripts, frames, etc can be sourced from, and are a good way of mitigating XSS issues.&lt;br /&gt;
&lt;br /&gt;
The structure of the header is as follows:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: &amp;lt;directive&amp;gt; &amp;lt;sources&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where the directive tells the browser what type of content is being controlled, and the source lists the places where the content can validly be obtained from, for example:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' https://www.example.com&lt;br /&gt;
&lt;br /&gt;
... tells the browser that javascript code files (i.e. *.js files) can only be sourced from 'self' (i.e. the current web site, note the single quotes are necessary) or https://www.example.com.  If the browser rendering the page finds javascript from some other site, it will fail to render and flag an error message to the end user.  In this way the web site has prevented the attacker from injecting links to their own javascript (e.g. &amp;quot;&amp;lt;script src='http://badguy.com/bad.js'&amp;gt;&amp;lt;/script&amp;gt;&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The directives controlled by the Content Security Policy include:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Directive&lt;br /&gt;
|Description&lt;br /&gt;
|-&lt;br /&gt;
|script-src&lt;br /&gt;
|Lists the sources where javascript files are allowed to be sourced from.&lt;br /&gt;
|-&lt;br /&gt;
|object-src&lt;br /&gt;
|Lists the sources where flash and other plugin objects are allowed from. &lt;br /&gt;
|-&lt;br /&gt;
|frame-src&lt;br /&gt;
|Lists the sources where frames are allowed from. &lt;br /&gt;
|-&lt;br /&gt;
|style-src&lt;br /&gt;
|Lists the sources where CSS files are allowed from. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
If a directive is not specified then the default is wide open, all sources are allowed.  If you do not wish to provide a directive for all options then you can specify a default-src which will then apply to all unspecified directives, for example:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: default-src 'self'&lt;br /&gt;
&lt;br /&gt;
... forces all scripts, frames, objects, etc to be sourced from the current web site.  When specifying a URL the scheme is enforced, so stating https://www.example.com will prevent any items coming from www.example.com over HTTP (i.e. without SSL).  You can also provide a wildcard on the leftmost portion of the domain, e.g. https://*.example.com.  Multiple directives are separated by semi-colons, e.g.&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' https://www.example.com; frame-src 'self' https://frames.example.com&lt;br /&gt;
&lt;br /&gt;
If you wished to completely disable an option, for example you don't want any frames in your page, you can disable a directive using the 'none' keyword:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: frame-src 'none'&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Preventing Inlining ====&lt;br /&gt;
&lt;br /&gt;
A further feature of Content Security Policy is to tell the browser not to allow inline javascript code, or evals.  As well as driving better programming practices by separating scripting code from the display markup, this option allows inline scripting to be disabled (a major vector of XSS, e.g. &amp;lt;script&amp;gt;alert(1);&amp;lt;/script&amp;gt;).  By providing a script-src or style-src (in the case of CSS) the Content Security Policy automatically bans inline scripts (javascript and CSS).  If you wish to allow inline scripting, or inline use of the eval function (which can construct javascript) you have to explicitly specify 'unsafe-inline' or 'unsafe-eval', e.g.&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' 'unsafe-inline'&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Applying CSP To Web Pages ====&lt;br /&gt;
&lt;br /&gt;
When using Content Security Policy, note that the header has to be included in every web page.  This can easily be achieved through configuration of common frameworks (e.g. mod_headers in Apache) if the policy is the same for the entire site.  If the Content Security Policy header is being dynamically created for each web page, be aware that directives cannot be repeated, if the header specifies the directive the second listing will be ignored.&lt;br /&gt;
&lt;br /&gt;
The header varies slightly between IE and other browsers, for IE you must specify &amp;quot;X-Content-Security-Policy&amp;quot;, whilst all other browsers use &amp;quot;Content-Security-Policy&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Using Content Security Policy Reporting  ====&lt;br /&gt;
&lt;br /&gt;
The Content Security Policy allows the browser to report any violations of the defined sources.  The CSP header can include the &amp;quot;report-uri&amp;quot; directive as in the following:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: default-src 'self'; report-uri /csp_receiver;&lt;br /&gt;
&lt;br /&gt;
With this directive, if the browser experiences any page/content that violates the directive it will send a JSON report to the defined URL similar to the following:&lt;br /&gt;
&lt;br /&gt;
 {&lt;br /&gt;
   &amp;quot;csp-report&amp;quot;: {&lt;br /&gt;
     &amp;quot;document-uri&amp;quot;: &amp;quot;https://www.example.com/default.html&amp;quot;,&lt;br /&gt;
     &amp;quot;referrer&amp;quot;: &amp;quot;https://www.example.com/&amp;quot;,&lt;br /&gt;
     &amp;quot;blocked-uri&amp;quot;: &amp;quot;https://bad.guy.com/bad_guy.js&amp;quot;,&lt;br /&gt;
     &amp;quot;violated-directive&amp;quot;: &amp;quot;script-src 'self' https://www.example.com&amp;quot;,&lt;br /&gt;
     &amp;quot;original-policy&amp;quot;: &amp;quot;script-src 'self' https://www.example.com; report-uri https://www.example.com/csp_receiver&amp;quot;&lt;br /&gt;
   }&lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
This reporting feature can be used to determine any attacks occurring on your content.  Also note that if you specify HTTPS in the report-uri scheme, and the receiver URI is on the current web server, the report JSON can be authenticated as the cookie will be passed over the secure session.&lt;br /&gt;
&lt;br /&gt;
If you simply wish to trail the CSP headers, i.e. not actually have the browser enforce the constraints encase it breaks anything, you can instead use the &amp;quot;Content-Security-Policy-Report-Only&amp;quot; header.  This will tell the browser to understand the directives and monitor for policy violations, but in the case of a violation the browser will still render the page as if the header was not specified, instead it will send the JSON report.  This is a great way to trail the CSP headers on live traffic to see what breaches are currently occurring, or to ensure you have configured your CSP headers before deployment.  An example of this is:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy-Report-Only: default-src 'self'; report-uri /csp_receiver;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== HTTP Strict Transport Security ===&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header. When the browser receives the HSTS header it will prevent any subsequent requests from being sent over HTTP to the web site, instead only using HTTPS, for the timeframe specified in the header. It also prevents HTTPS click through prompts on browsers.&lt;br /&gt;
&lt;br /&gt;
Simple example, using a long (1 year) max-age:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000&lt;br /&gt;
&lt;br /&gt;
If all present and future subdomains will be HTTPS:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains&lt;br /&gt;
&lt;br /&gt;
If the site owner would like their domain to be included in the  maintained by Chrome (and used by Firefox and Safari), then use:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains; preload&lt;br /&gt;
&lt;br /&gt;
The 'preload' flag indicates the site owner's consent to have their domain preloaded. The site owner still needs to then go and submit the domain to the list.&lt;br /&gt;
&lt;br /&gt;
Use caution when setting excessively strict STS policies. Including subdomains should only be used in environments where all sites within your organization for the given domain name require ssl. Max-age limits should be carefully considered as infrequent visitors may find your site inaccessible if you relax your policy.&lt;br /&gt;
&lt;br /&gt;
Before enabling includeSubDomains, also consider the impact of any existing DNS CNAME records for CDNs, email services, or other 3rd party services. Since includeSubDomains will force such CNAME subdomains to https:// it's likely the browser will throw a domain-mismatch error, which is hard to reverse because of the browser caching nature of HSTS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What to Review ==&lt;br /&gt;
&lt;br /&gt;
When reviewing code modules from an HTTP header sercurity point of view, some common issues to look out for include:&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* https://www.owasp.org/index.php/HTTP_Strict_Transport_Security&lt;br /&gt;
* http://content-security-policy.com/&lt;br /&gt;
* http://www.html5rocks.com/en/tutorials/security/content-security-policy/&lt;br /&gt;
* http://www.w3.org/TR/CSP/&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=189729</id>
		<title>CRV2 SecCommsHTTPHdrs</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=189729"/>
				<updated>2015-02-15T16:29:00Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= This is a draft version =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
HTTP headers allow the server to dictate or advise the user agent and intermediary servers how to handle the content being provided.  Some of these headers can aid a web site in securing itself; these include the standard Cache-Control headers, and newer specifications like HSTS and Content Security Policy headers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&lt;br /&gt;
From a security point of view controlling the HTTP headers sent with web site content can tell the users browser how to store the content, how to access further content, and how to trust various parts of the content received by the browser.  &lt;br /&gt;
&lt;br /&gt;
Two points to note up front:&lt;br /&gt;
&lt;br /&gt;
# Headers can only be trusted over a HTTPS session&lt;br /&gt;
# This section only covers HTTP response headers&lt;br /&gt;
&lt;br /&gt;
Without HTTPS between the web server and the users browser an attacker can modify the content or the associated headers.  Thus if you were returning headers specifying that your web site should only be access over HTTPS, an attacker could remove these headers and the browser would not receive the information.  A web site should not trust HTTP request headers for security decisions as there are many ways an attacker could modify these headers (or construct the whole request themselves), so there is nothing to cover for secure headers coming from the client, as they are inherently insecure.  Of course the cookie header is an exception to this, but that is because our web site has set the cookie header to a random value that should only be known during the browsing session. This section will not cover the cookie header as this is covered in the session management topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Caching Headers ===&lt;br /&gt;
&lt;br /&gt;
For business web sites that allow sensitive or confidential information to be downloaded to the client device, the caching of that sensitive data will become a security issue.  A user accessing their bank account details does not want an intermediary proxy caching their web pages.  A legal web site does not want copies of sensitive PDF documents stored on the laptop or smartphone disk storage, only for that device to be lost and the documents visible to an attacker.&lt;br /&gt;
&lt;br /&gt;
The 'Cache-Control' header tells the users browser how to handle the content being downloaded.  Some browsers can interpret the header values differently thus the understood header settings to return with content that must not be cached are:&lt;br /&gt;
&lt;br /&gt;
 Cache-Control: no-store, no-cache&lt;br /&gt;
 Pragma: no-cache&lt;br /&gt;
 Expires: 0&lt;br /&gt;
&lt;br /&gt;
This should be understood by all browsers (including mobile webviews) that the content being returned must not be stored to disk cache.  Note that it is possible for intermediate proxies to ignore caching headers and still cache the content, which is another reason why using end-to-end HTTPS sessions is important, as the proxies will only have encrypted versions of the sensitive content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Content Security Policy ===&lt;br /&gt;
&lt;br /&gt;
Cross Site Scripting (XSS) is still one of the most frequent security issues experienced on web sites, it's A3 on the OWASP Top 10 (2013), and it covers a variety of ways attackers can bypass the browser same origin policy to trick the browsers into executing the attackers code. Content Security Policy headers are designed to allow a web site to inform the browser where scripts, frames, etc can be sourced from, and are a good way of mitigating XSS issues.&lt;br /&gt;
&lt;br /&gt;
The structure of the header is as follows:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: &amp;lt;directive&amp;gt; &amp;lt;sources&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where the directive tells the browser what type of content is being controlled, and the source lists the places where the content can validly be obtained from, for example:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' https://www.example.com&lt;br /&gt;
&lt;br /&gt;
... tells the browser that javascript code files (i.e. *.js files) can only be sourced from 'self' (i.e. the current web site, note the single quotes are necessary) or https://www.example.com.  If the browser rendering the page finds javascript from some other site, it will fail to render and flag an error message to the end user.  In this way the web site has prevented the attacker from injecting links to their own javascript (e.g. &amp;quot;&amp;lt;script src='http://badguy.com/bad.js'&amp;gt;&amp;lt;/script&amp;gt;&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The directives controlled by the Content Security Policy include:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Directive&lt;br /&gt;
|Description&lt;br /&gt;
|-&lt;br /&gt;
|script-src&lt;br /&gt;
|Lists the sources where javascript files are allowed to be sourced from.&lt;br /&gt;
|-&lt;br /&gt;
|object-src&lt;br /&gt;
|Lists the sources where flash and other plugin objects are allowed from. &lt;br /&gt;
|-&lt;br /&gt;
|frame-src&lt;br /&gt;
|Lists the sources where frames are allowed from. &lt;br /&gt;
|-&lt;br /&gt;
|style-src&lt;br /&gt;
|Lists the sources where CSS files are allowed from. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
If a directive is not specified then the default is wide open, all sources are allowed.  If you do not wish to provide a directive for all options then you can specify a default-src which will then apply to all unspecified directives, for example:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: default-src 'self'&lt;br /&gt;
&lt;br /&gt;
... forces all scripts, frames, objects, etc to be sourced from the current web site.  When specifying a URL the scheme is enforced, so stating https://www.example.com will prevent any items coming from www.example.com over HTTP (i.e. without SSL).  You can also provide a wildcard on the leftmost portion of the domain, e.g. https://*.example.com.  Multiple directives are separated by semi-colons, e.g.&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' https://www.example.com; frame-src 'self' https://frames.example.com&lt;br /&gt;
&lt;br /&gt;
If you wished to completely disable an option, for example you don't want any frames in your page, you can disable a directive using the 'none' keyword:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: frame-src 'none'&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Preventing Inlining ====&lt;br /&gt;
&lt;br /&gt;
A further feature of Content Security Policy is to tell the browser not to allow inline javascript code, or evals.  As well as driving better programming practices by separating scripting code from the display markup, this option allows inline scripting to be disabled (a major vector of XSS, e.g. &amp;lt;script&amp;gt;alert(1);&amp;lt;/script&amp;gt;).  By providing a script-src or style-src (in the case of CSS) the Content Security Policy automatically bans inline scripts (javascript and CSS).  If you wish to allow inline scripting, or inline use of the eval function (which can construct javascript) you have to explicitly specify 'unsafe-inline' or 'unsafe-eval', e.g.&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' 'unsafe-inline'&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Applying CSP To Web Pages ====&lt;br /&gt;
&lt;br /&gt;
When using Content Security Policy, note that the header has to be included in every web page.  This can easily be achieved through configuration of common frameworks (e.g. mod_headers in Apache) if the policy is the same for the entire site.  If the Content Security Policy header is being dynamically created for each web page, be aware that directives cannot be repeated, if the header specifies the directive the second listing will be ignored.&lt;br /&gt;
&lt;br /&gt;
The header varies slightly between IE and other browsers, for IE you must specify &amp;quot;X-Content-Security-Policy&amp;quot;, whilst all other browsers use &amp;quot;Content-Security-Policy&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Using Content Security Policy Reporting  ====&lt;br /&gt;
&lt;br /&gt;
The Content Security Policy allows the browser to report any violations of the defined sources.  The CSP header can include the &amp;quot;report-uri&amp;quot; directive as in the following:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: default-src 'self'; report-uri /csp_receiver;&lt;br /&gt;
&lt;br /&gt;
With this directive, if the browser experiences any page/content that violates the directive it will send a JSON report to the defined URL similar to the following:&lt;br /&gt;
&lt;br /&gt;
 {&lt;br /&gt;
   &amp;quot;csp-report&amp;quot;: {&lt;br /&gt;
     &amp;quot;document-uri&amp;quot;: &amp;quot;https://www.example.com/default.html&amp;quot;,&lt;br /&gt;
     &amp;quot;referrer&amp;quot;: &amp;quot;https://www.example.com/&amp;quot;,&lt;br /&gt;
     &amp;quot;blocked-uri&amp;quot;: &amp;quot;https://bad.guy.com/bad_guy.js&amp;quot;,&lt;br /&gt;
     &amp;quot;violated-directive&amp;quot;: &amp;quot;script-src 'self' https://www.example.com&amp;quot;,&lt;br /&gt;
     &amp;quot;original-policy&amp;quot;: &amp;quot;script-src 'self' https://www.example.com; report-uri https://www.example.com/csp_receiver&amp;quot;&lt;br /&gt;
   }&lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
This reporting feature can be used to determine any attacks occurring on your content.  Also note that if you specify HTTPS in the report-uri scheme, and the receiver URI is on the current web server, the report JSON can be authenticated as the cookie will be passed over the secure session.&lt;br /&gt;
&lt;br /&gt;
trail...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== HTTP Strict Transport Security ===&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header. When the browser receives the HSTS header it will prevent any subsequent requests from being sent over HTTP to the web site, instead only using HTTPS, for the timeframe specified in the header. It also prevents HTTPS click through prompts on browsers.&lt;br /&gt;
&lt;br /&gt;
Simple example, using a long (1 year) max-age:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000&lt;br /&gt;
&lt;br /&gt;
If all present and future subdomains will be HTTPS:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains&lt;br /&gt;
&lt;br /&gt;
If the site owner would like their domain to be included in the  maintained by Chrome (and used by Firefox and Safari), then use:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains; preload&lt;br /&gt;
&lt;br /&gt;
The 'preload' flag indicates the site owner's consent to have their domain preloaded. The site owner still needs to then go and submit the domain to the list.&lt;br /&gt;
&lt;br /&gt;
Use caution when setting excessively strict STS policies. Including subdomains should only be used in environments where all sites within your organization for the given domain name require ssl. Max-age limits should be carefully considered as infrequent visitors may find your site inaccessible if you relax your policy.&lt;br /&gt;
&lt;br /&gt;
Before enabling includeSubDomains, also consider the impact of any existing DNS CNAME records for CDNs, email services, or other 3rd party services. Since includeSubDomains will force such CNAME subdomains to https:// it's likely the browser will throw a domain-mismatch error, which is hard to reverse because of the browser caching nature of HSTS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What to Review ==&lt;br /&gt;
&lt;br /&gt;
When reviewing code modules from an HTTP header sercurity point of view, some common issues to look out for include:&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* https://www.owasp.org/index.php/HTTP_Strict_Transport_Security&lt;br /&gt;
* http://content-security-policy.com/&lt;br /&gt;
* http://www.html5rocks.com/en/tutorials/security/content-security-policy/&lt;br /&gt;
* http://www.w3.org/TR/CSP/&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=189727</id>
		<title>CRV2 SecCommsHTTPHdrs</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=189727"/>
				<updated>2015-02-15T16:03:22Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= This is a draft version =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
HTTP headers allow the server to dictate or advise the user agent and intermediary servers how to handle the content being provided.  Some of these headers can aid a web site in securing itself; these include the standard Cache-Control headers, and newer specifications like HSTS and Content Security Policy headers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&lt;br /&gt;
From a security point of view controlling the HTTP headers sent with web site content can tell the users browser how to store the content, how to access further content, and how to trust various parts of the content received by the browser.  &lt;br /&gt;
&lt;br /&gt;
Two points to note up front:&lt;br /&gt;
&lt;br /&gt;
# Headers can only be trusted over a HTTPS session&lt;br /&gt;
# This section only covers HTTP response headers&lt;br /&gt;
&lt;br /&gt;
Without HTTPS between the web server and the users browser an attacker can modify the content or the associated headers.  Thus if you were returning headers specifying that your web site should only be access over HTTPS, an attacker could remove these headers and the browser would not receive the information.  A web site should not trust HTTP request headers for security decisions as there are many ways an attacker could modify these headers (or construct the whole request themselves), so there is nothing to cover for secure headers coming from the client, as they are inherently insecure.  Of course the cookie header is an exception to this, but that is because our web site has set the cookie header to a random value that should only be known during the browsing session. This section will not cover the cookie header as this is covered in the session management topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Caching Headers ===&lt;br /&gt;
&lt;br /&gt;
For business web sites that allow sensitive or confidential information to be downloaded to the client device, the caching of that sensitive data will become a security issue.  A user accessing their bank account details does not want an intermediary proxy caching their web pages.  A legal web site does not want copies of sensitive PDF documents stored on the laptop or smartphone disk storage, only for that device to be lost and the documents visible to an attacker.&lt;br /&gt;
&lt;br /&gt;
The 'Cache-Control' header tells the users browser how to handle the content being downloaded.  Some browsers can interpret the header values differently thus the understood header settings to return with content that must not be cached are:&lt;br /&gt;
&lt;br /&gt;
 Cache-Control: no-store, no-cache&lt;br /&gt;
 Pragma: no-cache&lt;br /&gt;
 Expires: 0&lt;br /&gt;
&lt;br /&gt;
This should be understood by all browsers (including mobile webviews) that the content being returned must not be stored to disk cache.  Note that it is possible for intermediate proxies to ignore caching headers and still cache the content, which is another reason why using end-to-end HTTPS sessions is important, as the proxies will only have encrypted versions of the sensitive content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Content Security Policy ===&lt;br /&gt;
&lt;br /&gt;
Cross Site Scripting (XSS) is still one of the most frequent security issues experienced on web sites, it's A3 on the OWASP Top 10 (2013), and it covers a variety of ways attackers can bypass the browser same origin policy to trick the browsers into executing the attackers code. Content Security Policy headers are designed to allow a web site to inform the browser where scripts, frames, etc can be sourced from, and are a good way of mitigating XSS issues.&lt;br /&gt;
&lt;br /&gt;
The structure of the header is as follows:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: &amp;lt;directive&amp;gt; &amp;lt;sources&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where the directive tells the browser what type of content is being controlled, and the source lists the places where the content can validly be obtained from, for example:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' https://www.example.com&lt;br /&gt;
&lt;br /&gt;
... tells the browser that javascript code files (i.e. *.js files) can only be sourced from 'self' (i.e. the current web site, note the single quotes are necessary) or https://www.example.com.  If the browser rendering the page finds javascript from some other site, it will fail to render and flag an error message to the end user.  In this way the web site has prevented the attacker from injecting links to their own javascript (e.g. &amp;quot;&amp;lt;script src='http://badguy.com/bad.js'&amp;gt;&amp;lt;/script&amp;gt;&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
The directives controlled by the Content Security Policy include:&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|Directive&lt;br /&gt;
|Description&lt;br /&gt;
|-&lt;br /&gt;
|script-src&lt;br /&gt;
|Lists the sources where javascript files are allowed to be sourced from.&lt;br /&gt;
|-&lt;br /&gt;
|object-src&lt;br /&gt;
|Lists the sources where flash and other plugin objects are allowed from. &lt;br /&gt;
|-&lt;br /&gt;
|frame-src&lt;br /&gt;
|Lists the sources where frames are allowed from. &lt;br /&gt;
|-&lt;br /&gt;
|style-src&lt;br /&gt;
|Lists the sources where CSS files are allowed from. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
If a directive is not specified then the default is wide open, all sources are allowed.  If you do not wish to provide a directive for all options then you can specify a default-src which will then apply to all unspecified directives, for example:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: default-src 'self'&lt;br /&gt;
&lt;br /&gt;
... forces all scripts, frames, objects, etc to be sourced from the current web site.  When specifying a URL the scheme is enforced, so stating https://www.example.com will prevent any items coming from www.example.com over HTTP (i.e. without SSL).  You can also provide a wildcard on the leftmost portion of the domain, e.g. https://*.example.com.  Multiple directives are separated by semi-colons, e.g.&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' https://www.example.com; frame-src 'self' https://frames.example.com&lt;br /&gt;
&lt;br /&gt;
If you wished to completely disable an option, for example you don't want any frames in your page, you can disable a directive using the 'none' keyword:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: frame-src 'none'&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Preventing Inlining ====&lt;br /&gt;
&lt;br /&gt;
A further feature of Content Security Policy is to tell the browser not to allow inline javascript code, or evals.  As well as driving better programming practices by separating scripting code from the display markup, this option allows inline scripting to be disabled (a major vector of XSS, e.g. &amp;lt;script&amp;gt;alert(1);&amp;lt;/script&amp;gt;).  By providing a script-src or style-src (in the case of CSS) the Content Security Policy automatically bans inline scripts (javascript and CSS).  If you wish to allow inline scripting, or inline use of the eval function (which can construct javascript) you have to explicitly specify 'unsafe-inline' or 'unsafe-eval', e.g.&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: script-src 'self' 'unsafe-inline'&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Applying CSP To Web Pages ====&lt;br /&gt;
&lt;br /&gt;
When using Content Security Policy, note that the header has to be included in every web page.  This can easily be achieved through configuration of common frameworks (e.g. mod_headers in Apache) if the policy is the same for the entire site.  If the Content Security Policy header is being dynamically created for each web page, be aware that directives cannot be repeated, if the header specifies the directive the second listing will be ignored.&lt;br /&gt;
&lt;br /&gt;
The header varies slightly between IE and other browsers, for IE you must specify &amp;quot;X-Content-Security-Policy&amp;quot;, whilst all other browsers use &amp;quot;Content-Security-Policy&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Using Content Security Policy Reporting  ====&lt;br /&gt;
&lt;br /&gt;
The Content Security Policy allows the browser to report any violations of the defined sources.  The CSP header can include the &amp;quot;report-uri&amp;quot; directive as in the following:&lt;br /&gt;
&lt;br /&gt;
 Content-Security-Policy: default-src 'self'; report-uri /csp_receiver;&lt;br /&gt;
&lt;br /&gt;
With this directive, if the browser experiences any page/content that violates the directive it will send a JSON report to the defined URL similar to the following:&lt;br /&gt;
&lt;br /&gt;
 {&lt;br /&gt;
   &amp;quot;csp-report&amp;quot;: {&lt;br /&gt;
     &amp;quot;document-uri&amp;quot;: &amp;quot;https://www.example.com/default.html&amp;quot;,&lt;br /&gt;
     &amp;quot;referrer&amp;quot;: &amp;quot;https://www.example.com/&amp;quot;,&lt;br /&gt;
     &amp;quot;blocked-uri&amp;quot;: &amp;quot;https://bad.guy.com/bad_guy.js&amp;quot;,&lt;br /&gt;
     &amp;quot;violated-directive&amp;quot;: &amp;quot;script-src 'self' https://www.example.com&amp;quot;,&lt;br /&gt;
     &amp;quot;original-policy&amp;quot;: &amp;quot;script-src 'self' https://www.example.com; report-uri https://www.example.com/csp_receiver&amp;quot;&lt;br /&gt;
   }&lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
This reporting feature can be used to determine any attacks occurring on your content.  Also note that if you specify HTTPS in the report-uri scheme, and the &lt;br /&gt;
&lt;br /&gt;
=== HTTP Strict Transport Security ===&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header. When the browser receives the HSTS header it will prevent any subsequent requests from being sent over HTTP to the web site, instead only using HTTPS, for the timeframe specified in the header. It also prevents HTTPS click through prompts on browsers.&lt;br /&gt;
&lt;br /&gt;
Simple example, using a long (1 year) max-age:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000&lt;br /&gt;
&lt;br /&gt;
If all present and future subdomains will be HTTPS:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains&lt;br /&gt;
&lt;br /&gt;
If the site owner would like their domain to be included in the  maintained by Chrome (and used by Firefox and Safari), then use:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains; preload&lt;br /&gt;
&lt;br /&gt;
The 'preload' flag indicates the site owner's consent to have their domain preloaded. The site owner still needs to then go and submit the domain to the list.&lt;br /&gt;
&lt;br /&gt;
Use caution when setting excessively strict STS policies. Including subdomains should only be used in environments where all sites within your organization for the given domain name require ssl. Max-age limits should be carefully considered as infrequent visitors may find your site inaccessible if you relax your policy.&lt;br /&gt;
&lt;br /&gt;
Before enabling includeSubDomains, also consider the impact of any existing DNS CNAME records for CDNs, email services, or other 3rd party services. Since includeSubDomains will force such CNAME subdomains to https:// it's likely the browser will throw a domain-mismatch error, which is hard to reverse because of the browser caching nature of HSTS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What to Review ==&lt;br /&gt;
&lt;br /&gt;
When reviewing code modules from an HTTP header sercurity point of view, some common issues to look out for include:&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* https://www.owasp.org/index.php/HTTP_Strict_Transport_Security&lt;br /&gt;
* http://content-security-policy.com/&lt;br /&gt;
* http://www.html5rocks.com/en/tutorials/security/content-security-policy/&lt;br /&gt;
* http://www.w3.org/TR/CSP/&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Belfast&amp;diff=189040</id>
		<title>Belfast</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Belfast&amp;diff=189040"/>
				<updated>2015-02-04T17:08:08Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Chapter Template|chaptername=Belfast|extra= |mailinglistsite=http://lists.owasp.org/mailman/listinfo/owasp-Belfast|emailarchives=http://lists.owasp.org/pipermail/owasp-Belfast}}&lt;br /&gt;
&lt;br /&gt;
== OWASP Belfast Board ==&lt;br /&gt;
&lt;br /&gt;
The OWASP Belfast Chapter Leaders are:&lt;br /&gt;
* [mailto:michelle.simpson@owasp.org Michelle Simpson]&lt;br /&gt;
* [mailto:philip.okane@owasp.org Philip O'Kane]&lt;br /&gt;
* [mailto:gary.robinson@owasp.org Gary Robinson]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== About OWASP Belfast ==&lt;br /&gt;
&lt;br /&gt;
==== What is OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast is just one of over 100 OWASP Chapters around the world, including 4 in Ireland and 12 in the UK, where people meet to learn about and discuss software security topics. The OWASP organization also has lots of active projects that volunteers can participate in to create code and documents for the worldwide security community.  The OWASP Top 10 project is the most famous of those projects.&lt;br /&gt;
&lt;br /&gt;
==== Who is OWASP Belfast for? ====&lt;br /&gt;
&lt;br /&gt;
It's for programmers, testers, students, project managers, development managers and security experts to collaborate and drive discussion on application security topics.  Participation in the mailing lists and attendance at the OWASP Belfast sessions are free, in fact many of the events will provide food and drinks to attendees.&lt;br /&gt;
&lt;br /&gt;
==== Why be part of OWASP Belfast? ====&lt;br /&gt;
&lt;br /&gt;
* The community organizes sessions where experts from across the industry (and globe) give presentations and seminars about application security topics.&lt;br /&gt;
* Attendance and participation in the community increases knowledge and skills, allowing people to stand out from the crowd.&lt;br /&gt;
* Opportunity to network with other Software Professionals and keep in touch with job opportunities in the region.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Local News ==&lt;br /&gt;
&lt;br /&gt;
'''OWASP Belfast Chapter Session - March 2015'''&lt;br /&gt;
&lt;br /&gt;
OWASP Belfast are currently planning their next session, currently planned for 18th March 2015.&lt;br /&gt;
&lt;br /&gt;
Follow the OWASP Belfast Meetup group at http://www.meetup.com/OWASP-Belfast/&lt;br /&gt;
&lt;br /&gt;
Sign-up for the OWASP Belfast mailing list for more information about this session, and other security related topics, at http://lists.owasp.org/mailman/listinfo/owasp-Belfast&lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Chapter]]&lt;br /&gt;
[[Category:Europe]]&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=188898</id>
		<title>CRV2 SecCommsHTTPHdrs</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=188898"/>
				<updated>2015-02-02T17:51:20Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= This is a draft version =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
HTTP headers allow the server to dictate or advise the user agent and intermediary servers how to handle the content being provided.  Some of these headers can aid a web site in securing itself; these include the standard Cache-Control headers, and newer specifications like HSTS and Content Security Policy headers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&lt;br /&gt;
From a security point of view controlling the HTTP headers sent with web site content can tell the users browser how to store the content, how to access further content, and how to trust various parts of the content received by the browser.  &lt;br /&gt;
&lt;br /&gt;
Two point to note up front:&lt;br /&gt;
&lt;br /&gt;
# Headers can only be trusted over a HTTPS session&lt;br /&gt;
# This section only covers HTTP response headers&lt;br /&gt;
&lt;br /&gt;
Without HTTPS between the web server and the users browser an attacker can modify the content or the associated headers.  Thus if you were returning headers specifying that your web site should only be access over HTTPS, an attacker could remove these headers and the browser would not receive the information.  A web site should not trust HTTP request headers for security decisions as there are many ways an attacker could modify these headers (or construct the whole request themselves), so there is nothing to cover for secure headers coming from the client, as they are inherently insecure.  Of course the cookie header is an exception to this, but that is because our web site has set the cookie header to a random value that should only be known during the browsing session. This section will not cover the cookie header as this is covered in the session management topic.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Caching Headers ===&lt;br /&gt;
&lt;br /&gt;
For business web sites that allow sensitive or confidential information to be downloaded to the client device, the caching of that sensitive data will become a security issue.  A user accessing their bank account details does not want an intermediary proxy caching their web pages.  A legal web site does not want copies of sensitive PDF documents stored on the laptop or smartphone disk storage, only for that device to be lost and the documents visible to an attacker.&lt;br /&gt;
&lt;br /&gt;
The 'Cache-Control' header tells the users browser how to handle the content being downloaded.  Some browsers can interpret the header values differently thus the understood header settings to return with content that must not be cached are:&lt;br /&gt;
&lt;br /&gt;
 Cache-Control: no-store, no-cache&lt;br /&gt;
 Pragma: no-cache&lt;br /&gt;
 Expires: 0&lt;br /&gt;
&lt;br /&gt;
This should be understood by all browsers (including mobile webviews) that the content being returned must not be stored to disk cache.  Note that it is possible for intermediate proxies to ignore caching headers and still cache the content, which is another reason why using end-to-end HTTPS sessions is important, as the proxies will only have encrypted versions of the sensitive content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Content Security Policy ===&lt;br /&gt;
&lt;br /&gt;
Cross Site Scripting (XSS) is still one of the most frequent security issue experienced on web sites, it's A3 on the OWASP Top 10 (2013), and it covers a variety of ways attackers can bypass the browser same origin policy to trick the browsers into executing the attackers code. TBD&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== HTTP Strict Transport Security ===&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header. When the browser receives the HSTS header it will prevent any subsequent requests from being sent over HTTP to the web site, instead only using HTTPS, for the timeframe specified in the header. It also prevents HTTPS click through prompts on browsers.&lt;br /&gt;
&lt;br /&gt;
Simple example, using a long (1 year) max-age:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000&lt;br /&gt;
&lt;br /&gt;
If all present and future subdomains will be HTTPS:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains&lt;br /&gt;
&lt;br /&gt;
If the site owner would like their domain to be included in the  maintained by Chrome (and used by Firefox and Safari), then use:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains; preload&lt;br /&gt;
&lt;br /&gt;
The 'preload' flag indicates the site owner's consent to have their domain preloaded. The site owner still needs to then go and submit the domain to the list.&lt;br /&gt;
&lt;br /&gt;
Use caution when setting excessively strict STS policies. Including subdomains should only be used in environments where all sites within your organization for the given domain name require ssl. Max-age limits should be carefully considered as infrequent visitors may find your site inaccessible if you relax your policy.&lt;br /&gt;
&lt;br /&gt;
Before enabling includeSubDomains, also consider the impact of any existing DNS CNAME records for CDNs, email services, or other 3rd party services. Since includeSubDomains will force such CNAME subdomains to https:// it's likely the browser will throw a domain-mismatch error, which is hard to reverse because of the browser caching nature of HSTS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What to Review ==&lt;br /&gt;
&lt;br /&gt;
When reviewing code modules from an HTTP header sercurity point of view, some common issues to look out for include:&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* https://www.owasp.org/index.php/HTTP_Strict_Transport_Security&lt;br /&gt;
* http://content-security-policy.com/&lt;br /&gt;
* http://www.html5rocks.com/en/tutorials/security/content-security-policy/&lt;br /&gt;
* http://www.w3.org/TR/CSP/&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Code_Review_V2_Table_of_Contents&amp;diff=188884</id>
		<title>OWASP Code Review V2 Table of Contents</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Code_Review_V2_Table_of_Contents&amp;diff=188884"/>
				<updated>2015-02-02T15:42:34Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: /* HTTP Headers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
= '''OWASP Code Review Guide v2.0:''' =&lt;br /&gt;
&lt;br /&gt;
==Forward==&lt;br /&gt;
# Author - Eoin Keary&lt;br /&gt;
# Previous version to be updated:[[https://www.owasp.org/index.php/Code_Review_Guide_History]]&lt;br /&gt;
'''[[CRV2_Forward|Content here]]'''&lt;br /&gt;
&lt;br /&gt;
== Code Review Guide Introduction==&lt;br /&gt;
# Author - Eoin Keary&lt;br /&gt;
# Previous version to be updated:[[https://www.owasp.org/index.php/Code_Review_Introduction]]&lt;br /&gt;
'''[[CRV2_Introduction|Content here]]'''&lt;br /&gt;
&lt;br /&gt;
=== What is source code review and Static Analysis ===&lt;br /&gt;
=== What is Code Review ===&lt;br /&gt;
# Author - Zyad Mghazli, Eoin Keary&lt;br /&gt;
# New Section&lt;br /&gt;
''' [[CRV2_WhatIsCodeReview|Content here]]'''&lt;br /&gt;
&lt;br /&gt;
=== Manual Review - Pros and Cons ===&lt;br /&gt;
# Author - Zyad Mghazli, Eoin Keary,Gary David Robinson&lt;br /&gt;
# New Section&lt;br /&gt;
# Suggestion: Benchmark of different Stataic Analysis Tools  Zyad Mghazli&lt;br /&gt;
# [[CRV2_ManualReviewProsCons|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=== Advantages of Code Review to Development Practices ===&lt;br /&gt;
# Author - Gary David Robinson&lt;br /&gt;
# New Section&lt;br /&gt;
# [[CRV2_AdvantagesToDevPractices|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=== Why code review ===&lt;br /&gt;
==== Scope and Objective of secure code review ====&lt;br /&gt;
# Author - Ashish Rao&lt;br /&gt;
# [[CRV2_WhyCodeReview|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=== We can't hack ourselves secure ===&lt;br /&gt;
# Author - Eoin Keary&lt;br /&gt;
# New Section&lt;br /&gt;
# [[CRV2_CantHackSecure|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=== 360 Review: Coupling source code review and Testing / Hybrid Reviews===&lt;br /&gt;
# Author - eoin Keary&lt;br /&gt;
# New Section&lt;br /&gt;
# [[CRV2_360Review|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=== Can static code analyzers do it all? ===&lt;br /&gt;
# Author - Ashish Rao&lt;br /&gt;
# New Section&lt;br /&gt;
# [[CRV2_CanStaticAnalyzersDoAll|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=Methodology=&lt;br /&gt;
===The code review approach===&lt;br /&gt;
#Author -  Johanna Curiel&lt;br /&gt;
# [[CRV2_CodeReviewApproach|Put content here]]&lt;br /&gt;
&lt;br /&gt;
==== Preparation and context ====&lt;br /&gt;
# Author - Gary David Robinson&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Code_Review_Preparation]]&lt;br /&gt;
# [[CRV2_PrepContext|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Application Threat Modeling====&lt;br /&gt;
#Author - Larry Conklin&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/OCRG1.1:Application_Threat_Modeling]]&lt;br /&gt;
# [[CRV2_AppThreatModeling|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Understanding Code layout/Design/Architecture====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_CodeLayoutDesignArch|Put content here]]&lt;br /&gt;
====Understanding Business Logic====&lt;br /&gt;
#[[CRV2_BusinessLogic|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===SDLC Integration===&lt;br /&gt;
#Author - Larry Conklin&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Security_Code_Review_in_the_SDLC]]&lt;br /&gt;
# [[CRV2_SDLCInt|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Deployment Models====&lt;br /&gt;
=====Secure deployment configurations=====&lt;br /&gt;
#Author - &lt;br /&gt;
# [[CRV2_SecDepConfig|Put content here]]&lt;br /&gt;
&lt;br /&gt;
# New Section&lt;br /&gt;
=====Metrics and code review=====&lt;br /&gt;
#Author -Anthony.Scotka@tea.state.tx.us&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Code_Review_Metrics]]&lt;br /&gt;
# [[CRV2_MetricsCodeRev|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Source and sink reviews=====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# New Section&lt;br /&gt;
# [[CRV2_SourceSinkRev|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Code review Coverage=====&lt;br /&gt;
#Author - Open&lt;br /&gt;
#Previous version to be updated: [[https://www.owasp.org/index.php/Code_Review_Coverage]]&lt;br /&gt;
# [[CRV2_CodeRevCoverage|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Design Reviews=====&lt;br /&gt;
#Author - Ashish Rao&lt;br /&gt;
*Why to review design?&lt;br /&gt;
**Building security in design - secure by design principle&lt;br /&gt;
**Design Areas to be reviewed&lt;br /&gt;
**Common Design Flaws&lt;br /&gt;
# [[CRV2_DesignRev|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====A Risk based approach to code review=====&lt;br /&gt;
#Author - Gary David Robinson&lt;br /&gt;
#New Section&lt;br /&gt;
*&amp;quot;Doing things right or doing the right things...&amp;quot;&lt;br /&gt;
**&amp;quot;Not all bugs are equal&lt;br /&gt;
# [[CRV2_RiskBasedApproach|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Crawling code====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Crawling_Code]]&lt;br /&gt;
*API of Interest:&lt;br /&gt;
**Java&lt;br /&gt;
**.NET&lt;br /&gt;
**PHP&lt;br /&gt;
**RUBY&lt;br /&gt;
*Frameworks:&lt;br /&gt;
**Spring&lt;br /&gt;
**.NET MVC&lt;br /&gt;
**Struts&lt;br /&gt;
**Zend&lt;br /&gt;
#New Section&lt;br /&gt;
*Searching for code in C/C++&lt;br /&gt;
#Author - Gary David Robinson&lt;br /&gt;
&lt;br /&gt;
# [[CRV2_CrawlingCode|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Code reviews and Compliance====&lt;br /&gt;
#Author -Open&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Code_Reviews_and_Compliance]]&lt;br /&gt;
# [[CRV2_CodeRevCompliance|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=Reviewing by Technical Control=&lt;br /&gt;
===Reviewing code for Authentication controls===&lt;br /&gt;
#Author - Gary Robinson&lt;br /&gt;
# [[CRV2_AuthControls|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Forgot password====&lt;br /&gt;
#Author Abbas Naderi, Larry Conklin&lt;br /&gt;
# [[CRV2_ForgotPassword|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====CAPTCHA====&lt;br /&gt;
#Author Larry Conklin, Joan Renchie&lt;br /&gt;
'''[[CRV2_CAPTCHA|Content here]]'''&lt;br /&gt;
&lt;br /&gt;
====Out of Band considerations====&lt;br /&gt;
#Author - Gary Robinson&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Authentication]]&lt;br /&gt;
# [[CRV2_OutofBand|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Reviewing code Authorization weakness===&lt;br /&gt;
#Author Eoin Keary .NET MVC added&lt;br /&gt;
# [[CRV2_AuthorizationWeaknesses|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Checking authz upon every request====&lt;br /&gt;
#Author - Abbas Naderi&lt;br /&gt;
# [[CRV2_CheckAuthzEachRequest|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Reducing the attack surface====&lt;br /&gt;
#Author Gary Robinson&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Authorization]]&lt;br /&gt;
# [[CRV2_ReducingAttSurf|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====SSL/TLS Implementations====&lt;br /&gt;
#Author - Eoin Keary&lt;br /&gt;
# [[CRV2_SSL-TLS|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Reviewing code for Session handling====&lt;br /&gt;
#Author - Abbas Naderi&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Session-Management]]&lt;br /&gt;
# [[CRV2_SessionHandling|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Reviewing client side code====&lt;br /&gt;
#New Section&lt;br /&gt;
# [[CRV2_ClientSideCodeIntro|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Javascript=====&lt;br /&gt;
#Author - Abbas Naderi&lt;br /&gt;
# [[CRV2_ClientSideCodeJScript|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====JSON=====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_ClientSideCodeJSon|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Content Security Policy=====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_ClientSideCodeContSecPolicy|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====&amp;quot;Jacking&amp;quot;/Framing=====&lt;br /&gt;
#Author - Eoin  Keary&lt;br /&gt;
# [[CRV2_ClientSideCodeJackingFraming|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====HTML 5?=====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_ClientSideCodeHTML5|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Browser Defenses=====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_ClientSideCodeBrowserDefPol|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====etc...=====&lt;br /&gt;
&lt;br /&gt;
====Review code for input validation====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_InputValIntro|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Regex Gotchas=====&lt;br /&gt;
#Author - Open&lt;br /&gt;
#New Section&lt;br /&gt;
# [[CRV2_InputValRegexGotchas|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====ESAPI=====&lt;br /&gt;
#Author - Open&lt;br /&gt;
#New Section&lt;br /&gt;
# Internal Link: [[https://www.owasp.org/index.php/Codereview-Input_Validation]]&lt;br /&gt;
# [[CRV2_InputValESAPI|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Microsoft Web Protection Library=====&lt;br /&gt;
#Author - Michael Hidalgo&lt;br /&gt;
#New Section&lt;br /&gt;
# Internal Link: [[https://www.owasp.org/index.php/Codereview-Input_Validation]]&lt;br /&gt;
# [[CRV2_InputValMicrosoftWebProtectionLibrary|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Reviewing code for contextual encoding====&lt;br /&gt;
[[Overall approach to content encoding and anti XSS]]&lt;br /&gt;
=====HTML Attribute=====&lt;br /&gt;
#Author - Eoin Keary&lt;br /&gt;
# [[CRV2_ContextEncHTMLAttribute|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====HTML Entity=====&lt;br /&gt;
#Author - Eoin Keary&lt;br /&gt;
# [[CRV2_ContextEncHTMLEntity|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Javascript Parameters=====&lt;br /&gt;
#Author - Eoin Keary&lt;br /&gt;
# [[CRV2_ContextEncJscriptParams|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====JQuery=====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_ContextEncJQuery|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Reviewing file and resource handling code====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_FileResourceHandling|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Resource Exhaustion - error handling====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_ResourceExhaustionErrHandling|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====native calls=====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_ResourceExhaustionNativeCalls|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Reviewing Logging code - Detective Security====&lt;br /&gt;
#Author - Gary Robinson&lt;br /&gt;
* Where to Log&lt;br /&gt;
* What to log&lt;br /&gt;
* What not to log&lt;br /&gt;
* How to log&lt;br /&gt;
# Internal link: [[https://www.owasp.org/index.php/Logging_Cheat_Sheet]]&lt;br /&gt;
# [[CRV2_LoggingCode|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Reviewing Error handling and Error messages====&lt;br /&gt;
#Author - Gary David Robinson&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Error-Handling]]&lt;br /&gt;
# [[CRV2_ErrorHandlingMessages|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Reviewing Security alerts====&lt;br /&gt;
#Author - Gary Robinson&lt;br /&gt;
# [[CRV2_SecurityAlerts|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Review for active defense====&lt;br /&gt;
#Author - Colin Watson&lt;br /&gt;
# [[CRV2_ActiveDefense|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Reviewing Secure Storage====&lt;br /&gt;
#Author - Open source&lt;br /&gt;
# New Section&lt;br /&gt;
# [[CRV2_SecureStorage|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Hashing &amp;amp; Salting - When, How and Where====&lt;br /&gt;
=====Encryption=====&lt;br /&gt;
======.NET======&lt;br /&gt;
#Author Larry Conklin, Joan Renchie&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Codereview-Cryptographic_Controls]]&lt;br /&gt;
*''Can we talk about key storage as well i.e. key management for encryption techniques used in the application? - Ashish Rao''&lt;br /&gt;
'''[[CRV2_HashingandSaltingdotNet|Content here]]'''&lt;br /&gt;
&lt;br /&gt;
=Reviewing by Vulnerability=&lt;br /&gt;
===Review Code for XSS===&lt;br /&gt;
#Author Examples added by Eoin Keary&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Reviewing_Code_for_Cross-Site_Scripting]]&lt;br /&gt;
# In reviewing code for XSS - we can give more patterns on &amp;quot;source to sink&amp;quot; patterns for ASP.NET wrf to difference versions and mechanisms to display data in a page - Ashish Rao&lt;br /&gt;
# [[CRV2_RevCodeXSS|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Persistent - The Anti pattern===&lt;br /&gt;
#Author &lt;br /&gt;
# [[CRV2_RevCodePersistentAntiPatternIntro|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====.NET====&lt;br /&gt;
#Author Johanna Curiel, Eoin Keary&lt;br /&gt;
# [[CRV2_RevCodePersistentAntiPatterndotNet|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====.Java====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_RevCodePersistentAntiPatternJava|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====PHP====&lt;br /&gt;
#Author Abbas Naderi&lt;br /&gt;
# [[CRV2_RevCodePersistentAntiPatternPHP|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Ruby====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_RevCodePersistentAntiPatternRuby|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Reflected - The Anti pattern===&lt;br /&gt;
# [[CRV2_RevCodeReflectedAntiPatternIntro|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====.NET====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_RevCodeReflectedAntiPatterndotNet|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====.Java====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_RevCodeReflectedAntiPatternJava|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====PHP====&lt;br /&gt;
#Author Abbas Naderi&lt;br /&gt;
# [[CRV2_RevCodeReflectedAntiPatternPHP|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Ruby====&lt;br /&gt;
# Author - Open&lt;br /&gt;
# [[CRV2_RevCodeReflectedAntiPatternIRuby|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Stored - The Anti pattern===&lt;br /&gt;
# Author - Johanna Curiel&lt;br /&gt;
# [[CRV2_RevCodeStoredAntiPatternIntro|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====.NET====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_RevCodeStoredAntiPatterndotNET|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====.Java====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_RevCodeStoredAntiPatternJava|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====PHP====&lt;br /&gt;
#Author Johanna Curiel &lt;br /&gt;
# [[CRV2_RevCodeStoredAntiPatternPHP|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Ruby====&lt;br /&gt;
#Author - Johanna Curiel&lt;br /&gt;
# [[CRV2_RevCodeStoredAntiPatternRuby|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===DOM XSS ===&lt;br /&gt;
#Author Larry Conklin&lt;br /&gt;
# [[CRV2_DOMXSS|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===JQuery mistakes===&lt;br /&gt;
#Author &lt;br /&gt;
# [[CRV2_JQueryMistakes|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Reviewing code for SQL Injection===&lt;br /&gt;
#Author Gary Robinson&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Reviewing_Code_for_SQL_Injection]]&lt;br /&gt;
# [[CRV2_RevCodeSQLInjection|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====PHP====&lt;br /&gt;
#Author - Mennouchi Islam Azeddine&lt;br /&gt;
# [[CRV2_SQLInjPHP|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Java====&lt;br /&gt;
#Author - Johanna Curiel&lt;br /&gt;
# [[CRV2_SQLInjJava|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====.NET====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_SQLInjdotNET|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====HQL====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_SQLInjHQL|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===The Anti pattern===&lt;br /&gt;
#Author Larry Conklin&lt;br /&gt;
#[[CRV2_AntiPattern| Content here]]&lt;br /&gt;
https://www.owasp.org/index.php/CRV2_AntiPattern&lt;br /&gt;
====PHP====&lt;br /&gt;
#Author - &lt;br /&gt;
# [[CRV2_AntiPatternPHP|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Java====&lt;br /&gt;
#Author - &lt;br /&gt;
#=&amp;gt; Searching for traditional SQL,JPA,JPSQL,Criteria,...&lt;br /&gt;
# [[CRV2_AntiPatternJava|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====.NET====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_AntiPatterndotNet|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Ruby====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_AntiPatternRuby|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Cold Fusion====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_AntiPatternColdFusion|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Reviewing code for CSRF Issues===&lt;br /&gt;
#Author Abbas Naderi&lt;br /&gt;
# Previous version to be updated: [[https://www.owasp.org/index.php/Reviewing_Code_for_Cross-Site_Request_Forgery]]&lt;br /&gt;
# This page needs to be deleted. [[CRV2_CSRFIssues|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===(This task has been deleted) Transactional logic / Non idempotent functions / State Changing Functions===&lt;br /&gt;
# [[CRV2_TransLogic|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Reviewing code for poor logic /Business logic/Complex authorization===&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_PoorLogic|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Reviewing Secure Communications===&lt;br /&gt;
====.NET Config====&lt;br /&gt;
#Author Johanna Curiel, Renchie Joan&lt;br /&gt;
# [[CRV2_SecCommsdotNet|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Spring Config====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_SecCommsSpringConfig|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====HTTP Headers====&lt;br /&gt;
#Author Gary Robinson&lt;br /&gt;
# [[CRV2_SecCommsHTTPHdrs|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Tech-Stack pitfalls===&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_TechStackPitfalls|Put content here]]&lt;br /&gt;
&lt;br /&gt;
===Framework specific Issues===&lt;br /&gt;
====Spring====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesSpring|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Struts====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesStruts|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Drupal====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesDurpal|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Ruby on Rails====&lt;br /&gt;
#Author - Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesROR|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Django====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesDjango|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====.NET Security / MVC====&lt;br /&gt;
#Author Johanna Curiel, Eoin Keary&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesdotNetMVC|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Security in ASP.NET applications====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPNet|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Strongly Named Assemblies=====&lt;br /&gt;
#Author Johanna Curiel, Larry Conklin&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPNetStrongAssembiles|Put content here]]&lt;br /&gt;
&lt;br /&gt;
======Round Tripping======&lt;br /&gt;
# Author - Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPNetRT|Put content here]]&lt;br /&gt;
&lt;br /&gt;
======How to prevent Round tripping======&lt;br /&gt;
# Author - Open&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPNetRTPrevention|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Setting the right Configurations=====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPNetConfigs|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Authentication Options=====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPNetAuth|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Code Review for Managed Code - .Net 1.0 and up=====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPNetManagedCode|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Using OWASP Top 10 as your guideline=====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPTop10|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=====Code review for Unsafe Code (C#)=====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPNetUnsafeCode|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====PHP Specific Issues====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesPHP|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Classic ASP====&lt;br /&gt;
#Author Johanna Curiel&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesASPClassic|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====C#====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesCsharp|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====C/C++====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesCplusplus|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Objective C====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesObectiveC|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Java====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesJava|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Android====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesAndroid|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====Coldfusion====&lt;br /&gt;
#Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesColdfusion|Put content here]]&lt;br /&gt;
&lt;br /&gt;
====CodeIgniter====&lt;br /&gt;
&lt;br /&gt;
# Author Open&lt;br /&gt;
# [[CRV2_FrameworkSpecIssuesCodeIgniter|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=Security code review for Agile development=&lt;br /&gt;
#Author Carlos Pantelides&lt;br /&gt;
# [[CRV2_CodeReviewAgile|Put content here]]&lt;br /&gt;
&lt;br /&gt;
=Code Review Tools=&lt;br /&gt;
https://www.owasp.org/index.php/CRV2_CodeReviewTools&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=188545</id>
		<title>CRV2 SecCommsHTTPHdrs</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=188545"/>
				<updated>2015-01-26T09:07:44Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= This is a draft version =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
HTTP headers allow the server to dictate or advise the user agent and intermediary servers how to handle the content being provided.  Some of these headers can aid a web site in securing itself; these include the standard Cache-Control headers, and newer specifications like HSTS and Content Security Policy headers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&lt;br /&gt;
From a security point of view controlling the HTTP headers sent with web site content can tell the users browser how to store the content, how to access further content, and how to trust various parts of the content received by the browser.  &lt;br /&gt;
&lt;br /&gt;
Two point to note up front:&lt;br /&gt;
&lt;br /&gt;
# Headers can only be trusted over a HTTPS session&lt;br /&gt;
# This section only covers HTTP response headers&lt;br /&gt;
&lt;br /&gt;
Without HTTPS between the web server and the users browser an attacker can modify the content or the associated headers.  Thus if you were returning headers specifying that your web site should only be access over HTTPS, an attacker could remove these headers and the browser would not receive the information.  A web site should not trust HTTP request headers for security decisions as there are many ways an attacker could modify these headers (or construct the whole request themselves), so there is nothing to cover for secure headers coming from the client, as they are inherently insecure.  Of course the cookie header is an exception to this, but that is because our web site has set the cookie header to a random value that should only be known during the browsing session. This section will not cover the cookie header as this is covered in the session management topic.&lt;br /&gt;
&lt;br /&gt;
For business web sites that allow sensitive or confidential information to be downloaded to the client device, the caching of that sensitive data will become a security issue.  A user accessing their bank account details does not want an intermediary proxy caching their web pages.  A legal web site does not want copies of sensitive PDF documents stored on the laptop or smartphone disk storage, only for that device to be lost and the documents visible to an attacker.&lt;br /&gt;
&lt;br /&gt;
The 'Cache-Control' header tells the users browser how to handle the content being downloaded.  Some browsers can interpret the header values differently thus the understood header settings to return with content that must not be cached are:&lt;br /&gt;
&lt;br /&gt;
 Cache-Control: no-store, no-cache&lt;br /&gt;
 Pragma: no-cache&lt;br /&gt;
 Expires: 0&lt;br /&gt;
&lt;br /&gt;
This should be understood by all browsers (including mobile webviews) that the content being returned must not be stored to disk cache.  Note that it is possible for intermediate proxies to ignore caching headers and still cache the content, which is another reason why using end-to-end HTTPS sessions is important, as the proxies will only have encrypted versions of the sensitive content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header. When the browser receives the HSTS header it will prevent any subsequent requests from being sent over HTTP to the web site, instead only using HTTPS, for the timeframe specified in the header. It also prevents HTTPS click through prompts on browsers.&lt;br /&gt;
&lt;br /&gt;
Simple example, using a long (1 year) max-age:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000&lt;br /&gt;
&lt;br /&gt;
If all present and future subdomains will be HTTPS:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains&lt;br /&gt;
&lt;br /&gt;
If the site owner would like their domain to be included in the  maintained by Chrome (and used by Firefox and Safari), then use:&lt;br /&gt;
&lt;br /&gt;
  Strict-Transport-Security: max-age=31536000; includeSubDomains; preload&lt;br /&gt;
&lt;br /&gt;
The `preload` flag indicates the site owner's consent to have their domain preloaded. The site owner still needs to then go and submit the domain to the list.&lt;br /&gt;
&lt;br /&gt;
Use caution when setting excessively strict STS policies. Including subdomains should only be used in environments where all sites within your organization for the given domain name require ssl. Max-age limits should be carefully considered as infrequent visitors may find your site inaccessible if you relax your policy.&lt;br /&gt;
&lt;br /&gt;
Before enabling includeSubDomains, also consider the impact of any existing DNS CNAME records for CDNs, email services, or other 3rd party services. Since includeSubDomains will force such CNAME subdomains to https:// it's likely the browser will throw a domain-mismatch error, which is hard to reverse because of the browser caching nature of HSTS.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What to Review ==&lt;br /&gt;
&lt;br /&gt;
When reviewing code modules from an HTTP header sercurity point of view, some common issues to look out for include:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&lt;br /&gt;
* https://www.owasp.org/index.php/HTTP_Strict_Transport_Security&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=188544</id>
		<title>CRV2 SecCommsHTTPHdrs</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=CRV2_SecCommsHTTPHdrs&amp;diff=188544"/>
				<updated>2015-01-26T08:53:45Z</updated>
		
		<summary type="html">&lt;p&gt;Gary David Robinson: Created page with &amp;quot;= This is a draft version =  == Overview ==  HTTP headers allow the server to dictate or advise the user agent and intermediary servers how to handle the content being provide...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= This is a draft version =&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
HTTP headers allow the server to dictate or advise the user agent and intermediary servers how to handle the content being provided.  Some of these headers can aid a web site in securing itself; these include the standard Cache-Control headers, and newer specifications like HSTS and Content Security Policy headers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&lt;br /&gt;
From a security point of view controlling the HTTP headers sent with web site content can tell the users browser how to store the content, how to access further content, and how to trust various parts of the content received by the browser.  &lt;br /&gt;
&lt;br /&gt;
Two point to note up front:&lt;br /&gt;
&lt;br /&gt;
# Headers can only be trusted over a HTTPS session&lt;br /&gt;
# This section only covers HTTP response headers&lt;br /&gt;
&lt;br /&gt;
Without HTTPS between the web server and the users browser an attacker can modify the content or the associated headers.  Thus if you were returning headers specifying that your web site should only be access over HTTPS, an attacker could remove these headers and the browser would not receive the information.  A web site should not trust HTTP request headers for security decisions as there are many ways an attacker could modify these headers (or construct the whole request themselves), so there is nothing to cover for secure headers coming from the client, as they are inherently insecure.  Of course the cookie header is an exception to this, but that is because our web site has set the cookie header to a random value that should only be known during the browsing session. This section will not cover the cookie header as this is covered in the session management topic.&lt;br /&gt;
&lt;br /&gt;
For business web sites that allow sensitive or confidential information to be downloaded to the client device, the caching of that sensitive data will become a security issue.  A user accessing their bank account details does not want an intermediary proxy caching their web pages.  A legal web site does not want copies of sensitive PDF documents stored on the laptop or smartphone disk storage, only for that device to be lost and the documents visible to an attacker.&lt;br /&gt;
&lt;br /&gt;
The 'Cache-Control' header tells the users browser how to handle the content being downloaded.  Some browsers can interpret the header values differently thus the understood header settings to return with content that must not be cached are:&lt;br /&gt;
&lt;br /&gt;
 Cache-Control: no-store, no-cache&lt;br /&gt;
 Pragma: no-cache&lt;br /&gt;
 Expires: 0&lt;br /&gt;
&lt;br /&gt;
This should be understood by all browsers (including mobile webviews) that the content being returned must not be stored to disk cache.  Note that it is possible for intermediate proxies to ignore caching headers and still cache the content, which is another reason why using end-to-end HTTPS sessions is important, as the proxies will only have encrypted versions of the sensitive content.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== What to Review ==&lt;br /&gt;
&lt;br /&gt;
When reviewing code modules from an HTTP header sercurity point of view, some common issues to look out for include:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;/div&gt;</summary>
		<author><name>Gary David Robinson</name></author>	</entry>

	</feed>