|
1 | 1 | --- |
| 2 | + |
2 | 3 | layout: col-sidebar |
3 | 4 | title: OWASP Secure Coding Practices-Quick Reference Guide |
4 | | -tags: downloads contributors |
| 5 | +tags: example-tag |
5 | 6 | level: 0 |
6 | 7 | type: documentation |
7 | | ---- |
8 | 8 |
|
9 | | -## Welcome to the Secure Coding Practices Quick Reference Guide Project |
| 9 | +auto-migrated: 1 |
10 | 10 |
|
11 | | -The Secure Coding Practices Quick Reference Guide is a technology agnostic set |
12 | | -of general software security coding practices, in a comprehensive checklist |
13 | | -format, that can be integrated into the development life-cycle. At only 17 pages |
14 | | -long, it is easy to read and digest. |
| 11 | +auto-migrated: 1 |
| 12 | + |
| 13 | +--- |
15 | 14 |
|
16 | | -The focus is on secure coding requirements, rather then on vulnerabilities and |
17 | | -exploits. It includes an introduction to Software Security Principles and a |
18 | | -glossary of key terms. |
19 | 15 |
|
20 | | -It is designed to serve as a secure coding kick-start tool and easy reference, |
21 | | -to help development teams quickly understand secure coding practices. |
| 16 | +<!-- Standard Chapter Page Template |
| 17 | +This is an example of a Project or Chapter page. |
| 18 | +Please change these items to indicate the actual information you wish to present. In addition to this information, the 'front-matter' above the text should be modified to reflect your actual information. An explanation of each of the front-matter items is below: |
22 | 19 |
|
23 | | -## Sections of the Guide |
| 20 | +{front matter for this file} |
24 | 21 |
|
25 | | -* Table of contents |
26 | | -* Introduction |
27 | | -* Software Security Principles Overview |
28 | | -* Secure Coding Practices Checklist |
29 | | -* Links to useful resources |
30 | | -* Glossary of important terminology |
| 22 | +``` |
| 23 | +- layout: This is the layout used by project and chapter pages. You should leave this value as col-sidebar |
| 24 | +- title: This is the title of your project or chapter page, usually the name. For example, OWASP Zed Attack Proxy or OWASP Baltimore |
| 25 | +- tags: This is a space-delimited list of tags you associate with your project or chapter. If you are using tabs, at least one of these tags should be unique in order to be used in the tabs files (an example tab is included in this repo) |
| 26 | +- region: This is the region you are in according to our data |
| 27 | +``` |
31 | 28 |
|
32 | | ------ |
| 29 | +{copy for this file (index.md)} |
| 30 | +Replace the text above the commented area with your information in the format below: |
| 31 | +``` |
| 32 | +## Welcome |
| 33 | +Include some information here about your chapter |
33 | 34 |
|
34 | | -## Feedback and Participation |
| 35 | +## Participation |
| 36 | +The Open Web Application Security Project (OWASP) is a nonprofit foundation that works to improve the security of software. All of our projects ,tools, documents, forums, and chapters are free and open to anyone interested in improving application security. |
35 | 37 |
|
36 | | -I hope you find the OWASP Secure Coding Practices Quick Reference Guide Project |
37 | | -useful. Please contribute to the Project by sending your comments, questions, |
38 | | -and suggestions to [keith.turpin@owasp.org]. |
| 38 | +Chapters are led by local leaders in accordance with the [Chapter Leader Handbook](/www-policy/rules-of-procedure/chapter-handbook). Financial contributions should only be made online using the authorized online donation button. To be a SPEAKER at ANY OWASP Chapter in the world simply review the [speaker agreement](/www-policy/speaker-agreement) and then contact the local chapter leader with details of what OWASP Project, independent research, or related software security topic you would like to present. |
39 | 39 |
|
40 | | -Project mailing list and archives: [subscription |
41 | | -page.](https://lists.owasp.org/mailman/listinfo/owasp-secure-coding-practices) |
| 40 | +Everyone is welcome and encouraged to participate in our [Projects](/projects), [Local Chapters](/chapters), [Events](/events), [Online Groups](https://groups.google.com/a/owasp.com/){:target='_blank'}, and [Community Slack Channel](https://owasp.slack.com/){:target='_blank'}. We especially encourage diversity in all our initiatives. OWASP is a fantastic place to learn about application security, to network, and even to build your reputation as an expert. We also encourage you to be [become a member](/membership) or consider a [donation](/donate) to support our ongoing work. |
42 | 41 |
|
43 | | -## Related Work |
| 42 | +## Local News |
| 43 | +- Meeting Location |
| 44 | +- Everyone is welcome to join us at our chapter meetings. |
44 | 45 |
|
45 | | -### Presentations |
| 46 | +``` |
| 47 | +{info.md} |
46 | 48 |
|
47 | | -* This slide deck incorporates many concepts from the Quick reference guide, but |
48 | | - also utilizes other OWASP resources. [Web Application Development Dos and |
49 | | - Donts - Presentation from the Royal Bank of Scotland][dosdonts] |
| 49 | +This separate file is where you should place links to your Google Group and Meetup page. It will be automatically rendered in the column sidebar. |
50 | 50 |
|
51 | | -### Projects |
| 51 | +{leaders.md} |
52 | 52 |
|
53 | | -* [Go programming language secure coding practices guide, based on the OWASP |
54 | | - Secure Coding Practices][owaspgoscp] |
| 53 | +Another separate file that should simply include each leaders name with mailto link as a list. It will also be automatically rendered in the column sidebar. |
55 | 54 |
|
56 | | -[keith.turpin@owasp.org]: mailto:Keith.Turpin@owasp.org |
57 | | -[dosdonts]: https://www.owasp.org/images/b/ba/Web_Application_Development_Dos_and_Donts.ppt |
58 | | -[owaspgoscp]: https://www2.owasp.org/www-project-go-secure-coding-practices-guide/ |
| 55 | +--> |
0 commit comments