New Module 16 Secure Developer Environment and Security Awareness#49
Open
DamirRT wants to merge 1 commit intoOWASP:mainfrom
Open
New Module 16 Secure Developer Environment and Security Awareness#49DamirRT wants to merge 1 commit intoOWASP:mainfrom
DamirRT wants to merge 1 commit intoOWASP:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello Team,
i would like to propose a new module. In this module, I would like to focus on the developer themselves.
Chapter 16 is intended to make developers aware that they, too, can provide an attack vector, whether through their behavior or the tools they use.
As an example lets say the developer works on authorization, following the best practices, but to make the development faster he/she uses a 3rd party website to parse/debug the JWT. Now he/she trusts a "Free" online service without having control over the data in that case -> where the data is going -> who is seeing this data and for what the data is used ...
The same applies for your tooling ...