5G MEC/Slice System BP has no new features from Release 4 to Release 6, so please refer to the R3 - Test Documentation to see the following contents.
Besides, based on Release 3 codes, 5G MEC/Slice System integrates with Bluval (Akraino blueprint validation framework) to scan out the system vulnerabilities in the K8s layer and OS layer and fix the vulnerabilities. Bluval introduction and user guide can be found in Bluval Documentation. Bluval test results for 5G MEC/Slice System BP are as follows.
Bluval Tests
1. K8s Layer Mandatory Tests
1.1 Kube-hunter Test Suite
1) Test Execution Step:
Bluval accesses to the 5G MEC/Slice System and executes Kube-hunter test suite on the system.
2) Test Results:
All critical test cases are passed (PASS/FAIL criteria can be found in Kube-Hunter PASS/FAIL Criteria, v1.0).
3) Test logs:
Logs are pushed in nexus repo: https://nexus.akraino.org/content/sites/logs/tencent/bluval/results_upload/k8s/kube-hunter/
2. OS Layer Mandatory Tests
2.1 Lynis Test Suite
1) Test Execution Step:
Bluval accesses to the 5G MEC/Slice System and executes Lynis test suite on the system.
2) Test Results:
29 critical test cases are passed with no errors (PASS/FAIL criteria can be found in Lynis PASS/FAIL Criteria, v1.0).
3) Test logs:
Logs are pushed in nexus repo: https://nexus.akraino.org/content/sites/logs/tencent/bluval/results_upload/os/lynis/
2.2 Vuls Test Suite
1) Test Execution Step:
Bluval accesses to the 5G MEC/Slice System and executes Vuls test suite on the system.
2) Test Results:
Requested 2 exceptions because of the OS version (PASS/FAIL criteria can be found in Vuls PASS/FAIL Criteria, v1.0).
3) Test Logs:
Logs are pushed in nexus repo: https://nexus.akraino.org/content/sites/logs/tencent/bluval/results_upload/os/vuls/