Vulnerability management is the cyclical practice of identifying, classifying, remediating, and mitigating vulnerabilities. In computer security, a vulnerability is a weakness in the system, a threat actor can exploit the weakness, to perform unauthorized actions within organizational applications or network.
To take advantage of a vulnerability, an attacker must have a minimum of one applicable tool or technique to identify and connect with system vulnerability. During this frame, we know the vulnerability because of the attack surface. Vulnerability management is then the cyclical practice of identifying, classifying, remediating, and mitigating vulnerabilities. This practice refers to software vulnerabilities in computing systems.
A security risk is usually incorrectly classified as a vulnerability. Using vulnerability with the identical meaning of risk can result in confusion. The danger is the potential of a major impact as a result of exploiting a vulnerability.
There are vulnerabilities without risk: when the affected asset has no value. We classify a vulnerability with one or more known instances of working and fully implemented attacks as an exploitable vulnerability — a vulnerability that an exploit exists.
(i)The window of vulnerability is the time from when the protection hole was introduced or manifested in deployed software, to when access was removed, a security fix was available/deployed, or is disabled by the attacker — see a zero-day attack.
(ii)A security bug (security defect) could be a narrower concept: there are vulnerabilities that aren’t associated with software: hardware, site, personnel vulnerabilities are samples of vulnerabilities that don’t seem to be software security bugs.
List of Some Common Vulnerabilities:
Categories of Common Vulnerabilities and Exposures (CVE) in the System:
In Fig. 2 Categories of CVE in the system.
In Fig. 3 List of the detailed CVE in the system.
It’s a “cyclical practice of identifying, classifying, prioritizing, remediating and mitigating” software vulnerabilities.
Vulnerability management is an integral part of the computer and network security, and must not be confused with a Vulnerability assessment. We discover vulnerabilities with a vulnerability scanner, which analyzes a system in search of known vulnerabilities, like open/insecure ports, software miss configurations, and susceptibility to malware infections. Unknown vulnerabilities, like a zero-day attack, identified with fuzz testing, which might identify certain types of vulnerabilities, as a buffer overflow with relevant test cases. Test automation can facilitate such analysis.
Antivirus software capable of performing heuristic analysis may discover undocumented malware if it finds software behaving suspiciously (such as attempting to overwrite a system file).
This standardized service offers subsequent pre-vetted support services:
This process typically includes:
In the above section, potential impact, and also the likelihood of occurrence are projected, considerately of existing controls safeguards that would reduce the impact of the likelihood. Use the rating matrix to live the vulnerabilities, to determine a risk rating of Critical, High, Medium or Low to explain the magnitude of risk.
Assessment types Depending on the system a vulnerability assessment can have many sorts and levels.
1. Host Assessment
2. Network Assessment
Host Assessment: A host assessment looks for system-level vulnerabilities like insecure file permissions, application-level bugs, backdoor, and computer virus installations. It requires specialized tools for the software and software packages getting used, besides administrative access to every system that ought to test. Host assessment is commonly very costly within the term of your time and thus barely used in the assessment of critical systems. Tools like COPS and Tiger are popular in host assessment.
Network Assessment: In-network assessment, one accesses the network for known vulnerabilities. It locates all systems on a network, determines what network services are in use, so analyzes those services for potential vulnerabilities. This process doesn’t require any configuration changes on the systems being assessed. Unlike host assessment, network assessment requires little computational cost and energy.
Vulnerability Assessment vs. Penetration Testing
Vulnerability assessment and penetration testing are two unique testing methods. We differentiate them based on certain specific parameters.
Overall likelihood rating shows the probability that they may exercise a potential vulnerability within the construct of the associated threat environment, we must consider the following governing factors:
Note: Please refer to the article The Ultimate Strategy To Identify Threats In A Network And Perform Risk Exposure Matrix, for more information about the likelihood rating.
The next major step in measuring risk level determines the adverse impact resulting from a successful threat exercise of a vulnerability.
We can get this information from existing organizational documentation, such as the mission impact analysis report or asset criticality assessment report. A mission impact analysis (also known as business impact analysis (BIA) for some organizations) prioritizes the impact levels associated with the compromise of an organization’s information assets based on a qualitative or quantitative assessment of the sensitivity and criticality of those assets.
An asset criticality assessment identifies and prioritizes the sensitive and critical organization information assets (e.g., hardware, software, systems, services, and related technology assets) that support the organization’s critical missions.
If this documentation does not exist or such assessments for the organization’s IT assets have not completed, the system and data sensitivity can be measured based on the level of protection required to maintain the system and data’s availability, integrity, and confidentiality (CIA) triad. Regardless of the method used to determine how sensitive an IT system and its data are, the system and information owners are the ones responsible for determining the impact level for their own system and information. In analyzing the impact, the approach is to interview the system and information owners. Therefore, the adverse impact of a security event can be described in terms of loss or degradation of any, or a combination of any, of the following three security goals: integrity, availability, and confidentiality. The following list provides a brief description of each security goal and the consequence (or impact) of it not being met:
We use a risk matrix during risk assessment to define the level of risk by considering the category of probability or likelihood against the category of consequence severity. This is a simple mechanism to increase the visibility of risks and assist management decision making. The determination of risk for a particular threat/vulnerability pair revealed as a function in the following aspects.
To measure risk, a risk scale and a risk-level matrix should be established.
An Evolution of Scoring Security Vulnerabilities:
To categorize CVE using the Security Impact Rating (SIR) criteria. The following are the vulnerability SIR classifications:
Vulnerability management is the cyclical practice of identifying, classifying, remediating, and mitigating vulnerabilities. We studied the simplified way to categorize security vulnerabilities using the standardized system.
Quote of the day:
“Birds of a feather flock together” — English Proverb
Explanation: people of the same sort or with the same tastes and interests will be found together.
Thanks for reading!
Have a pleasant day!