Skip to content
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

Documentation Update: Control Representations in SSP #819

Open
3 tasks
brian-ruf opened this issue Jan 24, 2021 · 2 comments
Open
3 tasks

Documentation Update: Control Representations in SSP #819

brian-ruf opened this issue Jan 24, 2021 · 2 comments
Labels
Aged A label for issues older than 2023-01-01 enhancement Scope: Documentation This issue relates to OSCAL documentation. Scope: Website Issues targeted at the OSCAL project website. User Story

Comments

@brian-ruf
Copy link
Contributor

User Story:

As an OSCAL SSP author, I need to understand options for representing controls that meet various organizational needs and circumstances, such as representing control responses for a whole control compared to representing content for individual statements within a control.

Goals:

  • Identify scenarios for control representation
  • Provide diagrams, examples, and explanations for each scenario
  • Clarify the least and most granular states (one component at the control vs. multiple components at the statement level)
  • Describe the transition from less granular to more granular.

Dependencies:

None.

Acceptance Criteria

  • All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
  • A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
  • The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.
@david-waltermire
Copy link
Contributor

This will be addressed by the tutorials resulting from #654.

@aj-stein-nist
Copy link
Contributor

Marking this as blocked until #1910 is completed, and then it will be ready for "Needs Refinement" and determination if we edit this issue or replace it with a different one.

@aj-stein-nist aj-stein-nist moved this from Todo to Blocked in NIST OSCAL Work Board Sep 27, 2023
@Compton-US Compton-US added the Aged A label for issues older than 2023-01-01 label Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aged A label for issues older than 2023-01-01 enhancement Scope: Documentation This issue relates to OSCAL documentation. Scope: Website Issues targeted at the OSCAL project website. User Story
Projects
Status: Blocked
Development

No branches or pull requests

5 participants