📝 Chore: add new security doc file #9200
Closed
+28
−0
Conversation
This file contains 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
|
|
|
hey @ishantiw thanks for assigning the reviewers! I have added a new change! I will be attentive to your comments! |
|
@luislucena16 We have bug bounty program for reporting security issues along with their severity here https://lisk.com/documentation/bug-bounty-program.html. Also, we will be transitioning L2 so this will be handled by future L1 Legacy team. |
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.
What was the problem?
this PR resolves #9199
How was it solved?
add entire file with documentation
How was it tested?
it's not technical, it's about documentation and software best practices!