Vulnerability Assessment

Comparing Approaches to Vulnerability Assessment

There are four types of vulnerability assessment solutions: product-based solutions, service-based solutions, tree-based assessment, and inference-based assessment.

Product-based Security solutions

Product-based Security solutions are installed in the organization’s internal network. They are installed either on a private or non-routable space or in the Internet-addressable portion of an organization’s network. If they are installed on a private network (behind the Firewall), they cannot always detect outside attacks.

Service-Based Security Solutions

Service-based solutions are offered by third parties, such as auditing or Security Consulting Firms. Some solutions are hosted inside the network, while others are hosted outside the network. A drawback of this solution is that attackers can perform network vulnerability scans from the Internet/external network.

Tree-based assessment

In a tree-based assessment, the auditor selects different strategies for each machine or component of the information system. For example, the administrator selects a Scanner for servers running Windows, Base, and web services but uses a different scanner for Linux servers. This approach relies on the administrator to provide a starting piece of intelligence, and then to start scanning continuously without incorporating any information found at the time of scanning.

Inference-based assessment

In an inference-based assessment, scanning starts by building an Inventory of the Protocol found on the machine. After finding a protocol, the scanning process starts to detect which Ports are attached to services, such as an email server, Webserver, or database server. After finding services, it selects vulnerabilities on each machine and starts to execute only those relevant tests.

Internet of Things (IoT) Vulnerability Assessment

IoT Vulnerability Assessment Process

Once attackers gather information about a target device, they search for the attack surfaces of a device (identify the vulnerabilities) that they can attack.

Attack Surface Identification

Vulnerability scanning allows an attacker to find the total number of vulnerabilities present in:

Vulnerability Scanning Steps

After identifying the attack surface area, the attacker will:

  1. Scan for vulnerabilities in that area
  2. Identify an attack vector
  3. Perform further exploitation on the device

Common IoT Vulnerabilities

Vulnerability scanning helps identify IoT devices with weak configurations such as:

Dual Purpose of Vulnerability Scanning

For Attackers:

For Security Professionals:

IoT Vulnerability Assessment Tools

Listed below are some of the additional vulnerability scanners for IoT devices:

Cloud Vulnerability Assessment

The vulnerability assessment phase involves identifying and evaluating security weaknesses within the cloud infrastructure. This includes the assessment of misconfigurations, unpatched software, and flaws in cloud-based networks, applications, and services. The primary purpose of this phase is to identify vulnerabilities that can be exploited to gain unauthorized access, escalate privileges, or disrupt cloud services. This phase is crucial for planning further exploitation strategies. Therefore, attackers can use both automated and manual techniques to identify vulnerabilities. Tools such as Tenable Nessus, openvas, and Qualys can be used to perform detailed scans and generate reports on the security posture of a cloud environment. The discovery of vulnerabilities provides attackers with potential entry points into the cloud environment, which can be leveraged to conduct further malicious activities.

Kubernetes Vulnerability Assessment

Container/Kubernetes Vulnerability Scanning

Container images consist of an operating system, application, runtime, etc. packaged together. These containers are reused widely and may contain open source frameworks with vulnerability issues. These vulnerabilities compromise the security not only of each container but of the entire container engine. Attackers use tools, such as Trivy Vulnerability Scanner, Anchore, Clair, Dadga, and synk container, to scan and identify vulnerabilities in the containers.

trivy image ubuntu

Trivy

Source: https://github.com

Trivy is an automated tool used to perform container image vulnerability scanning. One needs to specify the image name to launch an accurate scanning operation. Trivy helps in detecting vulnerabilities of OS packages, such as Alpine, RHEL, and CentOS, and application dependencies, such as Bundler, Composer, npm, and yarn.

trivy <target> [--scanners <scanner1,scanner2>] <subject>

Figure 19.134: Screenshot of Trivy

Sysdig

Source: https://sysdig.com

Sysdig identifies Kubernetes vulnerabilities by integrating continuous integration (CI) or continuous delivery/deployment (CD) pipelines, image registry, and Kubernetes admissions controllers. Sysdig also validates container images at the orchestration level using the Kubernetes admission controller feature. Sysdig automatically generates an inventory of each image content and continuously checks for any new vulnerabilities or common vulnerabilities and exposures (CVEs) associated with containers.

Figure 19.135: Screenshot of Sysdig

Additional Kubernetes Vulnerability Scanning Tools

Additional Kubernetes vulnerability scanning tools include the following: