Add Script to Import DISA STIG to Policy Specific Content #11611
Conversation
Mab879
added
Infrastructure
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
Start a new ephemeral environment with changes proposed in this pull request: Fedora Environment Oracle Linux 8 Environment |
|
🤖 A k8s content image for this PR is available at: Click here to see how to deploy itIf you alread have Compliance Operator deployed: Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and: |
Mab879
force-pushed
the
import_disa_changes_to_policy
branch
from
5f3acdb to
069969e
Compare
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
/packit build |
| rule_dir_json = get_rule_dir_json(args.json) | ||
| srgs = ssg.build_stig.parse_srgs(stig_filename) | ||
|
|
||
| for stig_id, stig_rule in srgs.items(): |
There was a problem hiding this comment.
I suggest splitting the main function to multiple smaller functions to improve code complexity.
There was a problem hiding this comment.
I have cleaned up the main method a bit, but moving the code the edits the file results in very ugly method signatures.
|
Code Climate has analyzed commit f50aaa1 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 33.3% (50% is the threshold). This pull request will bring the total coverage in the repository to 58.3% (0.1% change). View more on Code Climate. |
|
/packit retest-failed |
1 similar comment
|
/packit retest-failed |
Description:
This PR adds a script that takes the SRG Requirement, Fix text, check text, and Vulnerability discussion from the DISA STIG XML files and imports them to the Policy Specific Content (PSC) files.
Rationale:
Help prep for the next STIG.
Review Hints:
Observe that under the rules used by the STIG the PSC content is updated.