Secure coding by windows98SE
1 like661 views
This document discusses secure coding practices and provides a checklist and quick reference guide. The checklist includes 14 secure coding rules with input validation, output encoding, authentication, access control, and error handling recommended. The quick reference guide recommends checking input, process, and output. It describes validating all client data, managing authentication, sessions, privileges, and ensuring safe output for the intended interpreter. The document provides a reference to the OWASP secure coding practices guide.
Secure coding by windows98SE
- 1. SECURE CODING HOW TO …
- 2. #WHOAMI ตาเล็ก วินโด้เก้าแปดเอสอี (WINDOWS98SE) ▸ 2010 – 2011 : Developer, OPKwin Developing robot scripts to work with Ragnarok Online Game ▸ 2012 – 2014 : Senior Programmer, CyberGames Corporation Co., Ltd Developing software in Python for players to create and store playing statistic and achievement in DotA1 game. Handling server and installation for the statistic & achievement module ▸ current : Administrator, own business Create e-learning contents for those who are interested in learning Perl programming. ▸ fb : fb.com/windows98se.fanpage
- 3. IF YOU DON'T KNOW HOW TO HACK, HOW COULD U PROTECT UR SYSTEM ? ตาเล็ก วินโด้เก้าแปดเอสอี #QUOTE
- 4. #SECURE CODING PRACTICES CHECKLIST RULES 1. Input Validation* 2. Output Encoding* 3. Authentication and Password Management* 4. Session Management 5. Access Control* 6. Cryptographic Practices 7. Error Handling and Logging* 8. Data Protection 9. Communication Security 10.System Configuration* 11.Database Security 12.File Management 13.Memory Management 14.General Coding Practices * RECOMMENDED
- 5. #QUICK VERSION RECOMMENDED 1. check input 2. check process 3. check output
- 6. #CHECK INPUT INPUT VALIDATION ▸ Identify & validate all client provided data ▸ Character set
- 7. #CHECK PROCESS PROCESS FLOW ▸ Authentication ▸ Session (and cookie) management controls ▸ Privilege
- 8. #CHECK OUTPUT OUTPUT HANDLING ▸ Safe for the intended interpreter ▸ Failure & error responses