Update notes in ANSSI R3 #11680
Update notes in ANSSI R3 #11680
Conversation
We have investigated various options of automating this requirement. For example checking the status by reading `/dev/kmsg` or `/sys/firmware/efi/efivars/`. We have discovered that these items can't be read using OVAL or its OpenSCAP implementation. Implementing new behaviors in OpenSCAP, likely followed by complex rules, would require too much effort and complexity to the benefit provided by automating this rule. So we have concluded to keep this control manual and we only update the notes section in the control.
|
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: |
|
Code Climate has analyzed commit c7dc467 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 59.8% (0.0% change). View more on Code Climate. |
|
/packit retest-failed |
Mab879
added
the
Update Profile
2 participants
We have investigated various options of automating this requirement. For example checking the status by reading
/dev/kmsgor/sys/firmware/efi/efivars/. We have discovered that these items can't be read using OVAL or its OpenSCAP implementation. Implementing new behaviors in OpenSCAP, likely followed by complex rules, would require too much effort and complexity to the benefit provided by automating this rule. So we have concluded to keep this control manual and we only update the notes section in the control.