Skip to content

Commit 0ce624e

Browse files
committed
doc: clarify defense-in-depth issues
Signed-off-by: Matteo Collina <hello@matteocollina.com>
1 parent ea60060 commit 0ce624e

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

SECURITY.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -276,6 +276,14 @@ the community they pose.
276276

277277
### Examples of non-vulnerabilities
278278

279+
#### Defense-in-depth issues
280+
281+
* Bugs whose fixes would only improve resilience after another security
282+
boundary has already failed, or reduce the impact of an issue outside the
283+
Node.js threat model, are considered defense-in-depth issues.
284+
* Defense-in-depth issues are never treated as Node.js security vulnerabilities,
285+
do not receive CVEs, and are handled as regular bugs or hardening improvements.
286+
279287
#### Malicious Third-Party Modules (CWE-1357)
280288

281289
* Code is trusted by Node.js. Therefore any scenario that requires a malicious

0 commit comments

Comments
 (0)