Skip to content

Update 06.00 - Objectives.md #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ManeleKh wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update 06.00 - Objectives.md #62

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
17 changes: 17 additions & 0 deletions 2.Curriculum/06.Error Handling/06.00 - Objectives.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,26 @@ After completing this module, developers will be able to:
---

## Knowledge
The student will need knowledge of the following topics for Module 6:
- What is secure error handling
- Security implications of improper error handling
- Information disclosure through stack traces and verbose errors
- Secure exception handling and propagation techniques
- Fail-secure versus fail-open design principles
- Global and centralized error handling approaches
- Secure logging practices and sensitive data sanitization
- Differences between development and production error modes


## Skills
- Ability to implement secure exception handling mechanisms
- Ability to identify insecure error messages and information leakage risks
- Ability to configure secure logging without exposing sensitive information
- Ability to apply fail-secure principles during application failures
- Ability to configure centralized and framework-specific error handling controls


## Competencies
With the above knowledge points, a developer would be able to securely manage application errors and exceptions while minimizing information disclosure and maintaining application security during failure conditions. This competency would support the development of resilient, secure, and production-ready applications aligned with secure coding best practices.