Skip to content

doc: clarify defense-in-depth issues #64215

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
mcollina wants to merge 1 commit into
base: main
Choose a base branch
from
Open

doc: clarify defense-in-depth issues #64215

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
8 changes: 8 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -276,6 +276,14 @@ the community they pose.

### Examples of non-vulnerabilities

#### Defense-in-depth issues

* Bugs whose fixes would only improve resilience after another security
boundary has already failed, or reduce the impact of an issue outside the
Node.js threat model, are considered defense-in-depth issues.
* Defense-in-depth issues are never treated as Node.js security vulnerabilities,
do not receive CVEs, and are handled as regular bugs or hardening improvements.

#### Malicious Third-Party Modules (CWE-1357)

* Code is trusted by Node.js. Therefore any scenario that requires a malicious
Expand Down
Loading