Add CISA Secure by Design Cheat Sheet #1799
Open
+267
−0
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
Prasad-JB
force-pushed
the
add-cisa-secure-by-design-cs
branch
from
a9817f0 to
e05342d
Compare
Prasad-JB
force-pushed
the
add-cisa-secure-by-design-cs
branch
from
e05342d to
96036e9
Compare
|
Is this PR superseded by #1800? |
…1, and trailing newlines
|
@szh No, this PR (#1799) is the main one for the CISA Secure by Design cheat sheet. PR #1800 was a mistake that I've now closed. I've fixed all the lint errors (MD025 duplicate heading issues) and the markdown lint checks should now pass. This PR is ready for review. This cheat sheet provides practical guidance for implementing CISA's Secure by Design principles, complementing the existing Secure Product Design cheat sheet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a new cheat sheet based on CISA’s Secure by Design principles.
This should give teams a dedicated resource for applying the Secure by Design principles, while complementing the existing Secure Product Design cheat sheet.
Looking forward to feedback from the community