Rules of Developing Secure Applications

INTRODUCTION

Document is based on OWASP (Open Web application Security Project) technology standarts.

The Open Web Application Security Project (OWASP) is a worldwide free and open community focused on improving the security of application software. Their mission is to make application security "visible," so that people and organizations can make informed decisions about application security risks.
(www.owasp.org)

Document also considers Payment Card Industry (PCI) Payment Application Data Security Standards (PA - DSS).

PA-DSS is the Council-managed program formerly under the supervision of the Visa Inc. program known as the Payment Application Best Practices (PABP). The goal of PA-DSS is to help software vendors and others develop secure payment applications that do not store prohibited data, such as full magnetic stripe, CVV2 or PIN data, and ensure their payment applications support compliance with the PCI DSS.
(https://www.pcisecuritystandards.org/security_standards/pa_dss.shtml)

After explanations of OWASP Top Ten 2007 and how we take care about it. On resource section you will find articles and some books about application security.

Documents text is a summary from wikipedia.

Before you start to read I would like to remind that;

Security is not a one-time event.

A secure coding initiative must deal with all stages of a program’s lifecycle.

Payment Card Industry (PCI) Data Security Standard
Build and Maintain a Secure Network
Requirement 1:
Install and maintain a firewall configuration to protect cardholder data
Requirement 2:
Do not use vendor-supplied defaults for system passwords and other security parameters

Protect Cardholder Data
Requirement 3:
Protect stored cardholder data
Requirement 4:
Encrypt transmission of cardholder data across open, public networks

Maintain a Vulnerability Management Program
Requirement 5:
Use and regularly update anti-virus software
Requirement 6:
Develop and maintain secure systems and applications

Implement Strong Access Control Measures
Requirement 7:
Restrict access to cardholder data by business need-to-know
Requirement 8:
Assign a unique ID to each person with computer access
Requirement 9:
Restrict physical access to cardholder data

Regularly Monitor and Test Networks
Requirement 10:
Track and monitor all access to network resources and cardholder data
Requirement 11:
Regularly test security systems and processes

Maintain an Information Security Policy
Requirement 12:
Maintain a policy that addresses information security