<commit_before>documentation_complete: false
name: Contingency Planning
schema_version: 3.0.0
satisfies:

- control_key: CP-1
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-1 goes here.

        This answer can be multi-line.

- control_key: CP-2
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 goes here.

        This answer can be multi-line.

- control_key: CP-2 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 (1) goes here.

        This answer can be multi-line.

- control_key: CP-2 (2)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 (2) goes here.

        This answer can be multi-line.

- control_key: CP-2 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 (3) goes here.

        This answer can be multi-line.

- control_key: CP-2 (8)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 (8) goes here.

        This answer can be multi-line.

- control_key: CP-3
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-3 goes here.

        This answer can be multi-line.

- control_key: CP-4
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-4 goes here.

        This answer can be multi-line.

- control_key: CP-4 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-4 (1) goes here.

        This answer can be multi-line.

- control_key: CP-6
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-6 goes here.

        This answer can be multi-line.

- control_key: CP-6 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-6 (1) goes here.

        This answer can be multi-line.

- control_key: CP-6 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-6 (3) goes here.

        This answer can be multi-line.

- control_key: CP-7
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-7 goes here.

        This answer can be multi-line.

- control_key: CP-7 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-7 (1) goes here.

        This answer can be multi-line.

- control_key: CP-7 (2)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-7 (2) goes here.

        This answer can be multi-line.

- control_key: CP-7 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-7 (3) goes here.

        This answer can be multi-line.

- control_key: CP-8
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-8 goes here.

        This answer can be multi-line.

- control_key: CP-8 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-8 (1) goes here.

        This answer can be multi-line.

- control_key: CP-8 (2)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-8 (2) goes here.

        This answer can be multi-line.

- control_key: CP-9
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-9 goes here.

        This answer can be multi-line.

- control_key: CP-9 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-9 (1) goes here.

        This answer can be multi-line.

- control_key: CP-9 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-9 (3) goes here.

        This answer can be multi-line.

- control_key: CP-10
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-10 goes here.

        This answer can be multi-line.

- control_key: CP-10 (2)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-10 (2) goes here.

        This answer can be multi-line.
<commit_msg>through CP-1<commit_after>documentation_complete: false
name: Contingency Planning
schema_version: 3.0.0
satisfies:

- control_key: CP-1
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - key: a
      text: |
        '<The customer will be responsible for developing, documenting, and
        disseminating Contingency Planning policy and procedures. A
        successful control response will need to address the content of the
        policy (which must include purpose, scope, roles, responsibilities,
        management commitment, coordination, and compliance) and procedures
        (which must facilitate the implementation of the policies and associated
        controls).>'
    - key: b
      text: |
        '<The customer will be responsible for reviewing and updating the
        Contingency Planning policy every  years, and procedures annually.
        A successful response will need to address the review and update
        process, including the role(s) responsible for initiating the review
        process, updating the policy and procedures, and providing approval
        of the updates.>'

- control_key: CP-2
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 goes here.

        This answer can be multi-line.

- control_key: CP-2 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 (1) goes here.

        This answer can be multi-line.

- control_key: CP-2 (2)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 (2) goes here.

        This answer can be multi-line.

- control_key: CP-2 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 (3) goes here.

        This answer can be multi-line.

- control_key: CP-2 (8)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-2 (8) goes here.

        This answer can be multi-line.

- control_key: CP-3
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-3 goes here.

        This answer can be multi-line.

- control_key: CP-4
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-4 goes here.

        This answer can be multi-line.

- control_key: CP-4 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-4 (1) goes here.

        This answer can be multi-line.

- control_key: CP-6
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-6 goes here.

        This answer can be multi-line.

- control_key: CP-6 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-6 (1) goes here.

        This answer can be multi-line.

- control_key: CP-6 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-6 (3) goes here.

        This answer can be multi-line.

- control_key: CP-7
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-7 goes here.

        This answer can be multi-line.

- control_key: CP-7 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-7 (1) goes here.

        This answer can be multi-line.

- control_key: CP-7 (2)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-7 (2) goes here.

        This answer can be multi-line.

- control_key: CP-7 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-7 (3) goes here.

        This answer can be multi-line.

- control_key: CP-8
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-8 goes here.

        This answer can be multi-line.

- control_key: CP-8 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-8 (1) goes here.

        This answer can be multi-line.

- control_key: CP-8 (2)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-8 (2) goes here.

        This answer can be multi-line.

- control_key: CP-9
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-9 goes here.

        This answer can be multi-line.

- control_key: CP-9 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-9 (1) goes here.

        This answer can be multi-line.

- control_key: CP-9 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-9 (3) goes here.

        This answer can be multi-line.

- control_key: CP-10
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-10 goes here.

        This answer can be multi-line.

- control_key: CP-10 (2)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
   - text: |
        Narrative text on how product can be configured against CP-10 (2) goes here.

        This answer can be multi-line.

{'fraction_non_alphanumeric': 0.08019855735670518, 'fraction_numerical': 0.031800201659815404, 'mean_word_length': 2.6362098138747885, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6539114', 'n_tokens_mistral': 4309, 'n_tokens_neox': 4199, 'n_words': 1416}