The document discusses the Secure Software Development Life Cycle (SSDLC) and provides recommendations for developers to integrate security into their processes. It recommends that developers understand common threats, perform penetration testing, implement logging of abnormal activity, secure all inputs and outputs, and consider security requirements throughout the entire development cycle from design to deployment. The document emphasizes that software security is important and is everyone's responsibility.

1. Secure Software Development Life Cycle (SSDLC) Chitpong Wuttanan

2. Not have Security Process or last priority to do it

3. Microsoft Security Development Lifecycle http://www.microsoft.com/security/sdl/discover/default.aspx

4. if your developed, what step to do security?

5. Goals of Basic Security C = Confidentiality

6. I = Integrity

7. A = Availability

8. What Developer must know? What's Threat (www.owasp.org) Cheat sheet and prevention cheat sheet Seach on google How to hacking and protect ( www.zone-h.com , www.xssed.com) Benchmark Security of Tools (www.cisecurity.org)

9. Penetration Test drive False negative Do correct, software respond incorrect False positive Do incorrect, software respond correct