-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat(templates): add support for a templates directory #308
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
partial review but this may be better in uds-package-template
- control-id: ac-6.9 | ||
description: <how the specified control may be implemented if the containing component or capability is instantiated in a system security plan> | ||
remarks: |- | ||
ASSESSMENT-OBJECTIVE: | ||
the execution of privileged functions is logged. | ||
uuid: {{ uuid }} | ||
- control-id: au-12 | ||
description: <how the specified control may be implemented if the containing component or capability is instantiated in a system security plan> | ||
remarks: | | ||
ASSESSMENT-OBJECTIVE: | ||
AU-12a. audit record generation capability for the event types the system is capable of auditing (defined in AU-02_ODP[01]) is provided by [Assignment: organization-defined system components]; | ||
AU-12b. [Assignment: organization-defined personnel or roles] is/are allowed to select the event types that are to be logged by specific components of the system; | ||
AU-12c. audit records for the event types defined in AU-02_ODP[02] that include the audit record content defined in AU-03 are generated. | ||
uuid: {{ uuid }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we want to make these controls a set we expect most apps to answer if they say met the silver standard and integrated with Istio/Prometheus/Loki?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we rename to oscal-somponent.yaml in case there are other "component" related things in here?
Closing to create a design doc and possibly place the template in another location. |
Description
In response to resolving #252 - this adds a
templates
directory to allow for more provenant OSCAL creation through centralized OSCAL templating vs more generic generation.Lula allows the templating artifact to be a remote (network) location - test this locally with:
There is built in support for
uuid
andtimestamp
generation and this process both meets parity with the previous generation process as well as allows us to centralize entries such asmetadata.parties
to ensure consistency across the organization.Checklist before merging