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

Transform OSCO json produced by Arboretum fetcher into NIST OSCAL-like Assessment Results Observations list json file(s) as a trestle task #310

Closed
degenaro opened this issue Jan 22, 2021 · 0 comments · Fixed by #311

Comments

@degenaro
Copy link
Collaborator

Issue description / feature objectives

Assumptions:

input directory contains one or more OSCO Arboretum fetcher produced cluster resource json files
input directory contains, optionally, a metadata file comprising additional reference data named oscal-metadata.yaml
output directory exists or is creatable

Approach:

create the output directory, if necessary
for each input OSCO cluster resource json file:
    for each ConfigMap:
        discover the rule and result pair entries contained within
        construct an observation for each entry, including any additional related information from the metadata file if present
        create the corresponding output file, only if the file does not already exist or overwrite=true (the default)

Example CLI:
trestle task osco-to-oscal -c /home/degenaro/git/degenaro.evidence-locker/osco/demo-osco-to-oscal-arboretum.config

Example config:

[task.osco-to-oscal]

input-dir = /home/degenaro/git/degenaro.evidence-locker/osco-arboretum/input
output-dir = /home/degenaro/git/degenaro.evidence-locker/osco-arboretum/output
output-overwrite = true

References

See Arboretum ComplianceAsCode/auditree-arboretum#9 cluster resource fetcher.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant