Add security.txt to .well-known dictionary#7
Open
alanabehnken-afk wants to merge 1 commit into
Open
Conversation
Adds RFC 9116-compliant security.txt to the .well-known directory. - Provides machine-readable vulnerability disclosure contact for security researchers and automated scanners - Required maturity signal for enterprise and federal DevSecOps procurement evaluations - No visual or functional impact on the frontend Verification: https://argus.huntridgelabs.com/.well-known/security.txt should return 200 OK after merge and deployment.
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
1 participant
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.
Adds RFC 9116-compliant security.txt to the .well-known directory.
Verification: https://argus.huntridgelabs.com/.well-known/security.txt should return 200 OK after merge and deployment.