Versions Compared

Old Version 6

changes.mady.by.user Todd Malsbary

Saved on

compared with

New Version Current

changes.mady.by.user Kuralamudhan Ramakrishnan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Nodus provide Provider networks using VLAN networking and Service Function Chaining.
  • After the pod is up and running we will be able to attach to the pod and check for multiple interfaces created inside the container. 
  • Nodus networking is setup and created
Nodus Validation and test case results
ToolsLogs
Synk

synk logs data

BDBA

BDBA log data

CheckMarx

Nodus Checkmarx data

Fuzzing tool(Radamsa) 

Fuzzing testing shell script

Fuzzing test with 100 iterations

Kube-hunterKube hunter logs
kube-benchKube bench logs
Node Feature Discovery
  • Node Feature Discovery for Kubernetes detects hardware features available on each node in a Kubernetes cluster and advertises those features using node labels.
  • Create a pod with specific label information in the case the pods are scheduled only on nodes whose major kernel version is 3 and above. Since the NFD master and worker daemonset is already running, the master has all the label information about the nodes which is collected by the worker.
  • If the OS version matches, the Pod will be scheduled and up. Otherwise, the Pod will be in a pending state in case there are no nodes with matching labels that are requested by the Pod

...

  • Use KUD to setup 3 clusters (sdewan-hub, edge-a, edge-b)
  • Run the SDEWAN CRD Controller in each clusters.
  • Create SDEWAN CNF instance and dummy pod (using httpbin instead) in edge-a, SDEWAN CNF instance and httpbin pod in edge-b
  • Create IPSec CR to configure sdewan-hub as responder to provide virtual IP addresses to any authenticated party requesting for IP addresses through SDEWAN CRD Controller.
  • Create IPSec CR to configure edge-a and edge-b IPSec configuration to get the IP addresses through SDEWAN CRD Controller.
  • Establish edge-a tunnel to sdewan-hub, edge-b tunnel to sdewan-hub, and hub XFRM policies will automatically route traffic between edge-a and edge-b
  • Create SNAT CR to establish SNAT rule in edge-a and DNAT CR to establish DNAT rule in edge-b which will enable TCP connection from edge-a to edge-b's httpbin service.
  • Verify curl command is successful from edge-a dummy pod (using httpbin instead) to edge-b's httpbin service. The function of the curl command is to return back the ip address of the requester.

BluVal Testing

Status as of March 14th 2022:

Release 6 Blueprint Scanning Status

OS Vuls Scan

  • Pass/Fail
  • Exceptions

OS Lynis Scan

  • Pass/Fail
  • Exceptions

Kube-Hunter Scan

  • Pass/Fail
  • Exceptions

See results here

Exceptions requested for the following

Layer

Result

Comments

Nexus

os/vuls

PASS with exceptions

Exceptions

:

  • CVE-2021-33574
  • CVE-2019-19814
  • CVE-2021-35942
Logs

os/lynis

PASS with exceptions

Exception requests


See results here

Exceptions requested for the following

Exceptions

:

  • BOOT-5122: GRUB boot password interferes with the unattended reboot during OS provisioning.
  • USB-2000: USB hubs and HID device must be enabled for BMC Console Redirection.
  • SSH-7408:
Checking MaxSessions, Checking Port
  • MaxSessions of 2 prevents lynis from running under Bluval.  Lynis, etc. robot files need to be updated to handle a different port.
  • KRNL-6000:
 kernel.modules_disabled, net.ipv4.conf.all.forwardingLogs

k8s/kube-hunter

PASS

With aquasec/kube-hunter:edge image

Logs

Release 6 Blueprint Scanning Status

  • Kernel module loading required by accelerator drivers.  Forwarding required by k8s.

See results here

Pass

Akraino CVE Vulnerability Exception Request

Akraino BluVal Exception Request

CD logs

...

ICN Master Bare Metal Deployment Verifier

ICN Master Virtual Deployment Verifier

ICN SDEWAN Master End2End Testing

...