Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 0 additions & 42 deletions 1. Introduction.md

This file was deleted.

91 changes: 0 additions & 91 deletions 2. Curriculum.md

This file was deleted.

11 changes: 0 additions & 11 deletions 3. OWASP Body of Knowledge.md

This file was deleted.

24 changes: 24 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Contributing to OCSD

Hi :-)

Welcome to the OCSD Curriculum project.

The curriculum is split into multiple domains.
Each domain has a dedicated folder and contains the following files:

* The “Objectives” file contains the curriculum for the domain.
* A file named after the domain that includes the list of topics a certified developer should know about.
* The “References” file that:
* contains material/references from other OWASP projects,
* and content from any other open source (not copyrighted) project, if a suitable license was used.
MIT and Apache 2.0 may be ok, but licenses that require attribution might be problematic, like CC-BY-4.
* The “Supplementary Reading” file contains more reading material for the exam.
* The “Parking Lot” file contains content that has not been included in the other files yet.

The topics are the high-level security constructs that a developer is expected to know.
For example, a foundation-level developer needs to know about threat modelling, but they may not necessarily know how to threat model.
Hence, adding content around threat modelling may not add to the body of knowledge.
But adding sub-topics on what a developer needs to know about threat modelling will help.

Please [open an issue](https://github.com/OWASP/OCSD/issues) if you have any questions.
23 changes: 0 additions & 23 deletions READ ME before contributing.md

This file was deleted.

59 changes: 55 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,56 @@
# OCSD
OWASP Certified Secure-Software Developer - the repository for the the proposed OCSD certification
# OWASP Certified Secure Developer (OCSD)


OWASP Project link: [https://owasp.org/www-project-certified-secure-developer/](https://owasp.org/www-project-certified-secure-developer/)
Welcome to the OCSD curriculum repository.
The scope of this certification is Web Application Security.
The OCSD is a foundation-level exam.
This is the official OWASP project link: <https://owasp.org/www-project-certified-secure-developer/>

This certification program is an answer to the questions a hiring manager for a developer might ask, to validate security knowledge of the candidate.
It is also for the developers who want to showcase their skills in developing secure code.

Remember:

* ***Writing secure code != testing the security of code with tools***
* ***If developers do not put security in the code, no one else will***

The questions we may want to ask are:

* If I am hiring a web application developer, what are the security related skills I would look for?
* If I were a web application developer, what security skills would I like to be validated for?

[CONTRIBUTING](./CONTRIBUTING.md) explains the structure of this repository.

## Curriculum Modules

Here are the curriculum modules that the working group for OCSD has arrived at:

1. Secure Architecture and Threat Modeling
2. Authentication and Credential Management
3. Authorisation
4. Input Validation and Output Encoding
5. Cryptography and Key Management
6. Error Handling
7. Secure Logging
8. Data Protection and Privacy
9. Secure Communications
10. Software Supply Chain Security
11. Business Logic Security
12. Secure File and Resource Handling
13. API and Web Service Security
14. Secure Configuration and Deployment
15. Security of and for AI
16. Secure Developer Environment and Security Awareness

## Body of Knowledge

We try to include references to established OWASP projects first, but are open to other open-source materials too, if the license is suitable for our use case.
Here is an excerpt of OWASP projects that we are referencing:

* <https://owasp.org/www-project-application-security-verification-standard/>
* <https://cheatsheetseries.owasp.org/index.html>
* <https://devguide.owasp.org/>
* <https://owaspsamm.org/>
* <https://owasp.org/www-project-mobile-app-security/>
* <https://owasp.org/www-project-top-ten/>
* <https://owasp.org/www-project-web-security-testing-guide/>
* <https://owasp.org/www-project-code-review-guide/>
Loading