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

Fully Deploy OSCAL Metaschema Constraints #1530

Open
1 of 72 tasks
david-waltermire opened this issue Oct 30, 2022 · 1 comment
Open
1 of 72 tasks

Fully Deploy OSCAL Metaschema Constraints #1530

david-waltermire opened this issue Oct 30, 2022 · 1 comment
Labels
Aged A label for issues older than 2023-01-01 Epic A collection of issues to be worked on over a series of sprints

Comments

@david-waltermire
Copy link
Contributor

david-waltermire commented Oct 30, 2022

Goals

  • Design and implement a solution to manage core OSCAL constraints.
  • Review existing constraints for all models
    • Ensure all constraints have an identifier (Add Constraint IDs/Names for All Constraints in Model #1430)
    • oscal_assessment-common_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_assessment-plan_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_assessment-results_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_catalog_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_complete_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_component_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_control-common_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_implementation-common_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_mapping_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_mapping-common_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_meta-constraints.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_metadata_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_poam_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_profile_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
    • oscal_ssp_metaschema.xml
      • Ensure that all identifier cross-references are properly constrained
      • Ensure that all allowed values are properly constrained
      • Ensure that all data type restrictions are properly constrained
@david-waltermire david-waltermire added the Epic A collection of issues to be worked on over a series of sprints label Oct 30, 2022
@david-waltermire david-waltermire added this to the OSCAL 1.1.0 milestone Oct 30, 2022
@david-waltermire david-waltermire self-assigned this Oct 30, 2022
@aj-stein-nist aj-stein-nist removed this from the v1.1.0 milestone Jul 27, 2023
@aj-stein-nist
Copy link
Contributor

As an epic predating #1688 board reorganization, I will want to label this as needs refinement for now until it can be broken down, rescoped, and or closed.

@aj-stein-nist aj-stein-nist moved this from Todo to Needs Refinement 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 Epic A collection of issues to be worked on over a series of sprints
Projects
Status: Needs Refinement
Development

No branches or pull requests

3 participants