...
Release 4 (Target Date November 30, 2020) Incubation Requirements:
| Month | 6/2020 | 7/2020 | 8/2020 | 9/2020 | 10/2020 | 11/2020 | 12/2020 | 1/2021 |
|---|---|---|---|---|---|---|---|---|
| Release | Rel. 4 | |||||||
Security Requirement Update | v. 1.0 | |||||||
Minimum Security Requirement | v. 1.0 | |||||||
Maximum Security Requirement | v. 1.0 | |||||||
Release 4 Minimum Security Requirement Lock Out Window | ||||||||
Maturity Review: Security Requirements Criteria
...
Current Maturity Requirements:
| Month | 6/2020 | 7/2020 | 8/2020 | 9/2020 | 10/2020 | 11/2020 | 12/2020 | 1/2021 |
|---|---|---|---|---|---|---|---|---|
| Maturity Request | ||||||||
Security Requirement Update | v. 1.0 | |||||||
Minimum Security Requirement | v. 1.0 | v. 1.0 | v. 1.0 | v. 1.0 | v. 1.0 | v. 1.0 | ||
Maximum Security Requirement | v. 1.0 | v. 1.0 | v. 1.0 | v. 1.0 | v. 1.0 | v. 1.0 | ||
Release 4 Minimum Security Requirement Lock Out Window | ||||||||
Vuls
Vuls will be integrated with Blueprint Validation Framework (Bluval User Guide)
...
- Remarks = #<remark>
- Section = [<section name>]
- Option/value = <option name>=<value of option>
Lynis Incubation: PASS/FAIL Criteria, v1.0
- The Lynis Program Update test MUST pass with no errors.
The following list of tests MUST complete as passing as described below.
In the lynis.log outputfile each test suite has one or more individual tests. The beginning and ending of a test suite is marked with "====". For example, the 'ID BOOT-5122' test suite should display:
020-04-08 15:36:28 ====
2020-04-08 15:36:28 Performing test ID BOOT-5122 (Check for GRUB boot password)
...2020-04-08 15:36:29 Hardening: assigned maximum number of hardening points for this item (3).
2020-04-08 15:36:29 ===If any tests in the test suit failed, there would be the following:
2020-04-08 15:36:29 Suggestion: <Description of failed test>Also, the 'Hardening' line show above would not say 'assigned maximum number of hardening points', instead it would say 'assigned partial number of hardening points'.
| 1 | Performing test ID BOOT-5122 (Check for GRUB boot password) |
| 2 | Test: Checking PASS_MAX_DAYS option in /etc/login.defs |
| 3 | Performing test ID AUTH-9328 (Default umask values) |
| 4 | Performing test ID SSH-7440 (Check OpenSSH option: AllowUsers and AllowGroups) |
| 5 | Test: checking for file /etc/network/if-up.d/ntpdate |
| 6 | Performing test ID KRNL-6000 (Check sysctl key pairs in scan profile) : Following sub-tests required |
| 6a | sysctl key fs.suid_dumpable contains equal expected and current value (0) |
| 6b | sysctl key kernel.dmesg_restrict contains equal expected and current value (1) |
| 6c | sysctl key net.ipv4.conf.default.accept_source_route contains equal expected and current value (0) |
| 7 | Test: Check if one or more compilers can be found on the system |
The lynis.log output file and exception requests for any of the items listed above that cannot be fixed must be sent to the security sub-committee.
| Anchor | ||||
|---|---|---|---|---|
|
...
Maturity: PASS/FAIL Criteria, v1.0
- The Lynis Program Update test MUST pass with no errors.
The following list of tests MUST complete as passing as described below.
In the lynis.log outputfile each test suite has one or more individual tests. The beginning and ending of a test suite is marked with "====". For example, the 'ID BOOT-5122' test suite should display:
020-04-08 15:36:28 ====
2020-04-08 15:36:28 Performing test ID BOOT-5122 (Check for GRUB boot password)
...2020-04-08 15:36:29 Hardening: assigned maximum number of hardening points for this item (3).
2020-04-08 15:36:29 ===If any tests in the test suit failed, there would be the following:
2020-04-08 15:36:29 Suggestion: <Description of failed test>
Also, the 'Hardening' line show above would not say 'assigned maximum number of hardening points', instead it would say 'assigned partial number of hardening points'.
...