You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-6Lines changed: 20 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,16 +42,30 @@ OpenSSH and Cockpit are installed and running.
42
42
43
43
## Compliance
44
44
45
-
**The deployed system does not pass all ANSSI-BP-028-HIGH OpenSCAP tests**. The remaining tests rely on user configuration that varies on the user infrastructure and needs to pass successfully.
45
+
**The deployed system does not pass all ANSSI-BP-028-HIGH OpenSCAP tests out of the box.**
46
46
47
-
An OpenSCAP report (HTML format) can be found at the root of the repository showing the system's compliance. However, it does show some false positives:
47
+
An OpenSCAP report (HTML format) can be found at the root of the repository showing the system's compliance. You can recreate the report by running the following commands on a freshly installed system:
48
48
49
-
***Ensure a dedicated group owns sudo (R57)**: FALSE POSITIVE. You can manually verify this rule with `ls -l /usr/bin | grep sudo`. The group *wheel* owns the binary.
***Explicit arguments in sudo specifications (R63)**: FALSE POSITIVE. As described in the report, false positives happen due to bad parsing of the sudoers file.
***Don't target root user in the sudoers file (R60)**: It is up to the user to configure this file to suit their needs.
53
+
### False positives
54
54
55
-
***Configure TLS for rsyslog remote logging (R43)**: It is up to the user to configure the TLS certificates to match their infrastructure.
55
+
These checks are reported as failed, but should be reported as passing. This is due to issues with OpenSCAP.
56
+
57
+
***Ensure a dedicated group owns sudo (R57)**: You can manually verify this rule with the following command: `ls -l /usr/bin | grep sudo`. The group *wheel* owns the binary.
58
+
59
+
***IOMMU configuration directive (R11)**: You can manually verify iommu usage is enforced with the following command: `dmesg iommu=force`
60
+
61
+
### Depend on user configuration
62
+
63
+
The system requires configuration and secrets unique to the user's infrastructure for those checks to pass.
64
+
65
+
***Explicit arguments in sudo specifications (R63)**: sudo configuration should be brought in by the user.
66
+
67
+
***Don't target root user in the sudoers file (R60)**: sudo configuration should be brought in by the user.
68
+
69
+
***Configure TLS for rsyslog remote logging (R43)**: It is up to the user to configure the rsyslog server to match their infrastructure.
56
70
57
71
***Configure CA certificate for rsyslog remote logging (R43)**: It is up to the user to configure the TLS certificates to match their infrastructure.
0 commit comments