Skip to content

Support Gemara Layer 3 mapping to generate OSCAL Component Definitions #348

@hbraswelrh

Description

@hbraswelrh

Is your feature request related to a problem? Please describe.
Adds support for mapping Gemara Layer 3 to Gemara

Describe the solution you'd like

The Gemara Layer 3 Policy should be used to create an OSCAL Component Definition. The Gemara schema changes allow for the validation component to be populated using the assessment requirement-id that is associated with the control-id. The existing Gemara Layer 2 Catalog does not have data that can be used for the validation component in the OSCAL Component Definition.

Describe alternatives you've considered
The Gemara Layer 2 Catalog was considered for generating the OSCAL Component Definitions. The Layer 2 Catalog cannot

Additional context
Initial Diagrams for prep work

Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions