docs(devsecops): expand IDE extension verification guidance#466
Open
ElliotFriedman wants to merge 1 commit intosecurity-alliance:developfrom
Open
docs(devsecops): expand IDE extension verification guidance#466ElliotFriedman wants to merge 1 commit intosecurity-alliance:developfrom
ElliotFriedman wants to merge 1 commit intosecurity-alliance:developfrom
Conversation
Item 1 of the IDE hardening list previously said "trusted sources" without defining what verification looks like. Expand it into a short multi-channel check (publisher match, source-repo cross-reference, install counts / verified-publisher badges / signed releases) and add a one-line threat-model hook explaining why extensions are a high-yield target. Also adds a contributors frontmatter acknowledging historical authors (mattaereal, fredriksvantes) alongside the new contribution. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collaborator
|
Hey @ElliotFriedman, can you verify the commit pls 🙏🏻 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Item 1 of the IDE hardening list said extensions should come from "trusted sources" without defining what verification looks like. This PR expands it into a multi-channel check (publisher match, GitHub source repo cross-reference, install counts / verified-publisher badges / signed releases) and adds a threat-model line on why extensions are a high-yield target.
Also adds a contributors frontmatter acknowledging historical authors (mattaereal, fredriksvantes) alongside the new contribution.