-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Mission Impact description #250
Conversation
Improve text description for Mission Impact.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fine as submitted, but have we considered the DOD's MEF definition and how it aligns with CISAs concept? I understand that the current context is CISA-based so this is appropriate. Just a question--not a show stopper.
The cited MEF documents are FEMA actually, so it's definitely a US federal civilian focus, but it's broader than just CISA. But anyway, it's a good point in general to add additional contexts, and the Defense use case is a good one. Do you want to suggest a sentence to add in the paragraph that notes the NCF and business continuity use cases as being distinct? Just add another paragraph about the relevant DoD documentation for mission continuity planning? |
@cgyarbrough check my Google digging, but I found:
...which refers to
...and
In DOD DIRECTIVE 3020.26 DOD CONTINUITY POLICY Is that what you're referring to, or is there another definition elsewhere? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems fine to me.
In the interest of merging this PR, I'm going to spawn a separate issue #255 to address @cgyarbrough's comment above about DoD's MEF definition. |
… feature/fix-246 * 'feature/fix-246' of https://github.com/CERTCC/SSVC: add subsubsection header for tree versioning Update link to SSVC_Provision.schema.json Update link to SSVC_Computed.schema.json Update 055_decision-points_2.md (#250) Two small typo fixes (#253) Replace Utility with Automatable in Deployer tree (#248) Add detail about customization, tree sharing, and decision point scope (#242) add text to point ahead to "Information Changes over Time" bulletize list # Conflicts: # ssvc-calc/SSVC_Computed.schema.json # ssvc-calc/SSVC_Provision.schema.json
Improve text description for Mission Impact.
There's not an associated issue with this, reflects some private feedback I received about better aligning with relevant documentation.