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

- control_key: PL-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 Security 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 proecures (which must
        facilitate the implementation of the policies and associated
        controls).>'
    - key: b
      text: |
        '<The customer will be responsible for reviewing and updating the
        Security Planning policy every 3 years, and procedures annually. A
        successful control 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: PL-2
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - key: a
      text: |
        '<The customer will be responsible for developing a system security
        plan (this document) in accordance with the above requirements. A
        successful control response will need to address each of the
        requirements and how this document meets them.

        The customer may with to consult NIST Special Publication 800-18, 
        Revision 1, Guide for Developing Security Plans for Federal Information
        Systems, which contains guidance on security planning. Portions of this
        system security plan will discuss controls inherited from infrastructure
        providers, such as Microsoft Azure, and will refer to the
        infrastructure providers SSP.>'
    - key: b
      text: |
        '<The customer will be responsible for distributing the system security
        plan to relevant personnel and keeping those personnel informed of
        subsequent changes. A successful control response will need to address
        identifying personnel who should receive a copy of the system security
        plan, as well as ensuring all such personnel are notified
        appropriately.>'
    - key: c
      text: |
        '<The customer will be responsible for reviewing the system security
        plan at the required frequency. A successful control response will need
        to address the initiation of the review process and the roles or
        individuals responsible for review.>'
    - key: d
      text: |
        '<The customer will be responsible for updating the system security
        plan to address changes to the information system and its environment
        or any problems identified during implementation or security
        assessments. A successful control response will need to discuss the
        roles or individuals responsible for updating the plan, as well as
        the process for approval of any updates.>'
    - key: e
      text: |
        '<The customer will be responsible for protecting the security plan from
        unauthorized disclosure or modification. A successful control response
        will need to address policy, procedural, and technical safeguards that
        are in place to protect the system security plan.>'

- control_key: PL-2 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - text: |
        '<The customer will be responsible for planning and coordinating
        security-related activities so as to reduce the impact on other
        organizational entities. These activities may include security
        assessments, audits, maintenance, patch management, and contingency
        plan testing. A successful control response will need to address the
        process by which other organizational entities are notified of and
        consulted regarding such activities.>'

- control_key: PL-4
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - key: a
      text: |
        '<The customer will be responsible for defining, documenting, and
        distributing rules of behavior. A successful control response will need
        to outline the rules of behavior and discuss the process for making them
        available to users requiring access to the system.>'
    - key: b
      text: |
        '<The customer will be repsonsible for obtaining signed acknowledgement
        of the rules of behavior from its users. A successful control response
        will need to address the process for withholding authorization until
        signatures are obtained.>'
    - key: c
      text: |
        '<The customer will be responsible for reviewing and updating the rules
        of behavior at the required frequency. A successful control response
        will need to address the process for initiating review, as well as the
        individuals or roles for carrying out the review, managing updates, and
        approving the final version.>'
    - key: d
      text: |
        '<The customer will be responsible for obtaining signed acknowledgement
        of the updated rules of behavior. A successful control response will
        need to address the process for removing authorization if signatures
        are not obtained in a timely manner.>'

- control_key: PL-4 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - text: |
        '<The customer will be responsible for incorporating explicit
        restrictions on the use of social media/networking sites and posting
        organizational information on public websites into the rules of
        behavior. A successful control response will need to outline the
        relevant portions of the rules of behavior.>'

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

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

- control_key: PL-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 Security 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 proecures (which must
        facilitate the implementation of the policies and associated
        controls).>'
    - key: b
      text: |
        '<The customer will be responsible for reviewing and updating the
        Security Planning policy every 3 years, and procedures annually. A
        successful control 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: PL-2
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - key: a
      text: |
        '<The customer will be responsible for developing a system security
        plan (this document) in accordance with the above requirements. A
        successful control response will need to address each of the
        requirements and how this document meets them.

        The customer may with to consult NIST Special Publication 800-18, 
        Revision 1, Guide for Developing Security Plans for Federal Information
        Systems, which contains guidance on security planning. Portions of this
        system security plan will discuss controls inherited from infrastructure
        providers, such as Microsoft Azure, and will refer to the
        infrastructure providers SSP.>'
    - key: b
      text: |
        '<The customer will be responsible for distributing the system security
        plan to relevant personnel and keeping those personnel informed of
        subsequent changes. A successful control response will need to address
        identifying personnel who should receive a copy of the system security
        plan, as well as ensuring all such personnel are notified
        appropriately.>'
    - key: c
      text: |
        '<The customer will be responsible for reviewing the system security
        plan at the required frequency. A successful control response will need
        to address the initiation of the review process and the roles or
        individuals responsible for review.>'
    - key: d
      text: |
        '<The customer will be responsible for updating the system security
        plan to address changes to the information system and its environment
        or any problems identified during implementation or security
        assessments. A successful control response will need to discuss the
        roles or individuals responsible for updating the plan, as well as
        the process for approval of any updates.>'
    - key: e
      text: |
        '<The customer will be responsible for protecting the security plan from
        unauthorized disclosure or modification. A successful control response
        will need to address policy, procedural, and technical safeguards that
        are in place to protect the system security plan.>'

- control_key: PL-2 (3)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - text: |
        '<The customer will be responsible for planning and coordinating
        security-related activities so as to reduce the impact on other
        organizational entities. These activities may include security
        assessments, audits, maintenance, patch management, and contingency
        plan testing. A successful control response will need to address the
        process by which other organizational entities are notified of and
        consulted regarding such activities.>'

- control_key: PL-4
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - key: a
      text: |
        '<The customer will be responsible for defining, documenting, and
        distributing rules of behavior. A successful control response will need
        to outline the rules of behavior and discuss the process for making them
        available to users requiring access to the system.>'
    - key: b
      text: |
        '<The customer will be repsonsible for obtaining signed acknowledgement
        of the rules of behavior from its users. A successful control response
        will need to address the process for withholding authorization until
        signatures are obtained.>'
    - key: c
      text: |
        '<The customer will be responsible for reviewing and updating the rules
        of behavior at the required frequency. A successful control response
        will need to address the process for initiating review, as well as the
        individuals or roles for carrying out the review, managing updates, and
        approving the final version.>'
    - key: d
      text: |
        '<The customer will be responsible for obtaining signed acknowledgement
        of the updated rules of behavior. A successful control response will
        need to address the process for removing authorization if signatures
        are not obtained in a timely manner.>'

- control_key: PL-4 (1)
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - text: |
        '<The customer will be responsible for incorporating explicit
        restrictions on the use of social media/networking sites and posting
        organizational information on public websites into the rules of
        behavior. A successful control response will need to outline the
        relevant portions of the rules of behavior.>'

- control_key: PL-8
  standard_key: NIST-800-53
  covered_by: []
  implimentation_status: none
  narrative:
    - key: a
      text: |
        '<The customer will be responsible for developing their information
        security architecture. A successful contrl response will need to
        discuss the guiding principles used to protect confidentiality,
        integrity, and availability of system information and the dependencies
        on external services (such as Microsoft Azure). Additionally, a
        description of the information security architecture should be included
        in the introductory sections of this system security plan.>'
    - key: b
      text: |
        '<The customer will be responsible for reviewing and updating the
        security architecture at a required frequency. A succesful control
        response will need to address the process for initiating review, as well
        as the individuals or roles responsible for carrying out the review,
        managing updates, and approving the final version.>'
    - key: c
      text: |
        '<The customer will be responsible for incorporating changes to the
        security architecture into this system security plan as well as
        related materials. A successful control response will need to address
        the process for aligning the contents of the system security plan
        with the information security architecture, including the
        individuals or roles responsible for that alignment.>'
{'fraction_non_alphanumeric': 0.04000290930249473, 'fraction_numerical': 0.007127791112080879, 'mean_word_length': 2.826885610910103, 'pattern_counts': {'":': 0, '<': 32, '<?xml version=': 0, '>': 32, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6194822', 'n_tokens_mistral': 3089, 'n_tokens_neox': 3061, 'n_words': 1657}