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

Create a very basic example to trace one control through the OSCAL models. #141

Open
3 tasks
Compton-US opened this issue Sep 14, 2022 · 5 comments
Open
3 tasks
Labels
enhancement The issue adds a new feature, capability, or artifact to the repository. User Story The issue is a user story for a development task.

Comments

@Compton-US
Copy link

User Story:

As an OSCAL user, I would like an example that demonstrates how a single control is depicted in the OSCAL models.

Goals:

Using AC-8, System Use Notification, develop model content and documentation.

A minimal application script may accompany this content if needed. (Hello, World-style application)

Dependencies:

This example is based on initial workflow research in the BloSS@M project.

Acceptance Criteria

  • All readme documentation affected by the changes in this issue have been updated.
  • 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.
@Compton-US Compton-US added enhancement The issue adds a new feature, capability, or artifact to the repository. User Story The issue is a user story for a development task. labels Sep 14, 2022
@david-waltermire david-waltermire linked a pull request Sep 27, 2022 that will close this issue
7 tasks
@aj-stein-nist
Copy link
Contributor

Since we are still working on this, and partially putting it through its paces in a conference talk case study, it seems we are still working on this in the new sprint. Moving to Sprint 61. @Compton-NIST, feel free to correct or we can discuss unassigning this one and throwing it into the backlog for now.

@aj-stein-nist
Copy link
Contributor

We need to revisit this in the context of the case study: keep it separate, roll it in, how to align that work with this. AJ will try to plan a meeting with @Compton-NIST in the beginning of Sprint 63 in February to determine next steps and whether to move this forward.

@aj-stein-nist
Copy link
Contributor

@Compton-NIST and I were unable to sync this past week because of my tardiness on this, we will sync on this when he is available. Tentatively moving to Sprint 63 in the interim, possibly moving to backlog if we have prior priorities at the moment (seems we do!).

@aj-stein-nist
Copy link
Contributor

I talked with Chris today and we agreed that this is important, but not an urgent priority, and we will move it to the backlog. We will need to sync up at a later date, perhaps in the next few weeks.

  • We have to consider whether or not the current work as it stands in the blossom-oscal repo as-is or need to break off the automated assessment pieces accordingly, do we copy/pull it in modularly if so?
  • Wendell and AJ had been working on different parallel, related efforts regarding example control sets from different perspectives: do we align them or unify them into one effort?

We need to keep addressing these key concerns and then plan the road ahead, but later once we review the backlog and reorganize it a little. So into the backlog we go with this issue for now. :-)

@Arminta-Jenkins-NIST
Copy link

Arminta-Jenkins-NIST commented Nov 9, 2023

At the 11/9 Triage Meeting: we could make the Blossom example as an example...possible create a page on OSCAL Pages to explain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue adds a new feature, capability, or artifact to the repository. User Story The issue is a user story for a development task.
Projects
Status: Needs Triage
Development

Successfully merging a pull request may close this issue.

3 participants