Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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: 5 additions & 0 deletions docs/_includes/default_mission_impact_values.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
!!! tip "Default Mission Impact Values"

Similarly, with [*Mission Impact*](/reference/decision_points/mission_impact.md), the deployer should assume that the software is in use at the
organization for a reason, and that it supports essential functions unless they have evidence otherwise.
With a total lack of information, assume [*support crippled*](/reference/decision_points/mission_impact.md) as a default.
6 changes: 1 addition & 5 deletions docs/howto/bootstrap/collect.md
Original file line number Diff line number Diff line change
Expand Up @@ -118,11 +118,7 @@ we can suggest something like defaults for some decision points.
This position is conservative, but software is thoroughly embedded in daily life now, so we suggest that the decision
maker provide evidence that no one’s well-being will suffer.

!!! tip "Default Mission Impact Values"

Similarly, with [*Mission Impact*](../../reference/decision_points/mission_impact.md), the deployer should assume that the software is in use at the
organization for a reason, and that it supports essential functions unless they have evidence otherwise.
With a total lack of information, assume [*support crippled*](../../reference/decision_points/mission_impact.md) as a default.
{% include-markdown "../../_includes/default_mission_impact_values.md" %}

!!! example "Using Defaults"

Expand Down
2 changes: 2 additions & 0 deletions docs/howto/gathering_info/mission_impact.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,3 +12,5 @@ At a minimum, understanding mission impact should include gathering information
There are various sources of guidance on how to gather this information; see for example the FEMA guidance in [Continuity Directive 2](https://www.fema.gov/sites/default/files/2020-07/Federal_Continuity_Directive-2_June132017.pdf) or [OCTAVE FORTE](https://insights.sei.cmu.edu/insider-threat/2018/06/octave-forte-and-fair-connect-cyber-risk-practitioners-with-the-boardroom.html).
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.

{% include-markdown "../../_includes/default_mission_impact_values.md" %}
2 changes: 2 additions & 0 deletions docs/reference/decision_points/mission_impact.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ print(example_block(LATEST))

See this [HowTo](../../howto/gathering_info/mission_impact.md) for advice on gathering information about the Mission Impact decision point.

{% include-markdown "../../_includes/default_mission_impact_values.md" %}

!!! tip "See also"

Mission Impact combines with [Safety Impact](./safety_impact.md) to inform
Expand Down
Loading