Align severity descriptions with internal documentation #21
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
jlschlepp
approved these changes
Sep 5, 2024
jray-payit
approved these changes
Sep 5, 2024
awilson-payit
approved these changes
Sep 5, 2024
bath-tub
changed the title
bath-tub
changed the title
bcurtis-payit
approved these changes
Sep 5, 2024
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.
Description
this isn't all that helpful for people who might be new to incidents and are unaware of internal sev levels, we should have this text align with what our internal documentation says. additionally provide a link so examples can be easily referred to during the event of a severity dispute (which happens every now and then)
Compliance Checklist
I have verified that this is not a new project. If it is a new project (new service, new application, new repository), I have submitted a ticket to InfoSec to review the new project and gained approval.
I have verified that the backout plan for this change conforms to our standard engineering backout plan located here. If it does not, I have documented an alternative backout plan below:
I have verified that this change is backwards compatible. If it is not, I have specified the breaking changes and how they will be handled below:
I have verified that this change will not impact the security controls built into the application or introduce any new security vulnerabilities. If it will, I have defined the security impact below:
I have verified that this change will not result in downtime. If it will, I have noted the impact below:
I have verified that no new dependencies were introduced. If they were, I have vetted them below:
I have verified that all applicable tests were updated to ensure complete test coverage of any new or modified code.
I have verified that any relevant documentation such as the README is still up to date and not impacted by my changes. If documentation needs updating for accuracy, I have done so.