Skip to content

Updated mission_impact.md #706

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.

Sign up for GitHub

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

Merged
ahouseholder merged 2 commits into from
Feb 20, 2025
Merged

Updated mission_impact.md #706

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d13bf5c
Updated mission_impact.md
sei-bkoo Feb 20, 2025
c66d056
Merge branch 'main' into 273-improve-mission-impact-description
sei-bkoo Feb 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions docs/reference/decision_points/mission_impact.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,15 +33,12 @@ In that sense they all function quite similarly within SSVC. Organizations shoul
## Gathering Information About Mission Impact

The factors that influence the mission impact level are diverse.
This paper does not exhaustively discuss how a stakeholder should answer a question; that is a topic for future work.
The material here does not exhaustively discuss how a stakeholder should answer a question; that is a topic for future work.
At a minimum, understanding mission impact should include gathering information about the critical paths that involve vulnerable components, viability of contingency measures, and resiliency of the systems that support the mission.
There are various sources of guidance on how to gather this information; see for example the FEMA guidance in Continuity Directive 2 [@FCD2_2017] or OCTAVE FORTE [@tucker2018octave].
This is part of risk management more broadly.
It should require the vulnerability management team to interact with more senior management to understand mission priorities and other aspects of risk mitigation.

As a heuristic, [Utility](utility.md) might constrain [*Mission Impact*](mission_impact.md) if both are not used in the same decision tree.
For example, if the [Utility](utility.md) is [*super effective*](utility.md), then [*Mission Impact*](mission_impact.md) is at least [*MEF support crippled*](mission_impact.md).

## Prior Versions

```python exec="true" idprefix=""
Expand Down