-
Notifications
You must be signed in to change notification settings - Fork 184
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
Tutorial: Extension Mechanisms #857
Comments
Also consider |
As a community member, I would love to contribute in whatever way you deem helpful on this effort. |
I have provided my ongoing work on an example component with an extension for security tool parameters in the OSCAL discussion forum and would love feedback and know how I can work with those assigned to further this effort, if this extension work will help. |
This work is in progress. For a preview of what will be covered in the tutorial, please see my draft outline here. I welcome any feedback. |
Provided some initial feedback as an outside peer, hope that helps and is not too forward. I looked at this because there is some overlap with FedRAMP Guidance in Section 3.1 in this document on page 28, along with other parts of this document and others here. These are slightly out of date, and the draft versions are in a shared drive we use with NIST (you have access). This is great and would like to align our resources with this once this is official. Thanks for publishing your outline! |
Tutorial is ready for review (see PR#1031). I do plan to expand on the final XML, JSON, YAML that is presented at the end of the tutorial to make sure it is a fully complete sample SSP. Once I have a full, well-formed OSCAL SSP (incorporating the props and links examples that are already in the tutorial), I will add another PR to add the item to the OSCAL-content repo. |
Interesting follow-up requests for clarity on best practices with using OSCAL https://gitter.im/usnistgov-OSCAL/Lobby?at=6273c50314df4e44f20e9e86 |
User Story:
As an OSCAL content creator or consumer, I need guidance on how to use the various OSCAL extension points (i.e., property and links) to provide extended data.
This relates to a question posed in #542.
Goals:
Dependencies:
None.
Acceptance Criteria
{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}
The text was updated successfully, but these errors were encountered: