-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Add foundational security documents #10447
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.
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
Merged
+374
−0
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| # .NET security framing guides | ||
|
|
||
| This folder contains a set of framing documents guiding the .NET team's security posture. These guides cover how we perform security designs for our components, the contracts these components have with users, and how we assess reported vulnerabilities in these components. They are specific to .NET's unique shape of being a provider of reusable libraries and SDK components rather than a standalone deployed application. | ||
|
|
||
| This folder also contains _prototype_ skills used to generate security design documents / threat models and to assess incoming vulnerability reports. | ||
|
|
||
| ## Primary documents | ||
|
|
||
| There are two primary documents located here. These documents serve as the foundation for all other documents present. | ||
|
|
||
| [**Baseline security assumptions**](baseline-security-assumptions.md) covers the implicit contract governing consumers' proper use of library components, expected environmental configuration, and the interaction between components in a system. It's the set of things incorporated by reference into all .NET security documentation, even if that documentation never explicitly says so. | ||
|
|
||
| [**Vulnerability theory**](vulnerability-theory.md) describes .NET's operating definition of what constitutes a theoretical product vulnerability. Because we define vulnerabilities in terms of excess privilege grants, this can be combined with the baseline document above to derive a non-exhaustive list of behaviors that are categorically _not_ vulnerabilities. | ||
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not seeing them in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My fault. :(
I forgot to remove that line before copying the docs into the public repo. Will clean it up in post so as not to block this merge.