lula
lula copied to clipboard
Profile Model Support
Enable option in the CLI to accept which profile is being evaluated in an OSCAL file.
Moving to low priority and would like to see some requests for this before implementation.
Profiles serve as an option for augmenting Catalogs. The use of source
in a component definitions control-implementation
states:
A reference to an OSCAL catalog or profile providing the referenced control or subcontrol definition.
Lula should support profiles as a potential entry for this field.
Need to consider the Profile Resolution process and possibly document a follow-on issue for performing this activity (IE catalog generation?)
Otherwise we need to understand the implications for:
- Using profile as the source for a control implementation
- Generic use for the model -> how is it intended to be used