In the last lecture, we are an introduction to this vulnerability assessment, in this lecture, we
are going to see different phases of vulnerability assessment.
Vulnerability assessment and scans should be performed on a regular basis, I.T. environments are changing
all the time.
For instance, a software update or a system configuration can change or change in complete new vulnerability.
New threats continue to emerge, so it's essential to identify and address vulnerabilities quickly to
limit cyber security risk when the scanning is only part of a vulnerability assessment of the process.
So that's brain testing can identify different types of threats to I.T. in your organization when testing
complements vulnerability scanning and is useful for determining if they can be acted on and whether
that action will cause damage and data loss or other issues.
So the first phase is initial assessment, phase it, identify the assets and define the risk and critical
value for each device based on the client input, such as security assessment, vulnerability scanning.
It is important to identify at least the importance of the device that you have on your network, or
at least the devices that you will test.
It's also important to understand if the device can be accessed by any member of your company, such
as a public computer, or does administrators and authorized users.
The initial assessment phase is also important to gather information about the systems before the vulnerability
assessment or at least review if the device is open.
Ports, processes and services that shouldn't be open also understand the approved drivers and software
that should be installed on the device and the basic configuration of each new device.
Try to perform a banner grabbing or learn what kind of public information should be accessible based
on the configuration slim like does the device and logs into security information and event management
and same platform are the logs at least stored in a central repository?
Get the public information and vulnerabilities regarding the device platform wasn't vendor and other
relevant details.
Next is to perform vulnerabilities.
Can use the right policy on your scanner to accomplish the desired results prior to starting the vulnerabilities
can look for any compliance requirements based on your company's posture and businesses and then know
the best time and date to perform the scan.
It's important to recognize the climate in this context and determine if the scan can be performed all
at once or if a segmentation is needed.
An important step is to redefine and get the approval of the policy for the vulnerable scan to be performed
for the best results, use related tools and plug ins on the assessment platforms.
In case you need to perform manual scan for critical assets to ensure the best results, be sure to
configure the credentials on the scanner configuration to perform a better and deeper penalty assessment.
The last is the post assessment piece, it includes a risk assessment, a remediation verification and
monitoring and the most important report, creation.
Pay attention to the details and try to add extra value on the recommendations fees to get the real
value from the final report and recommendations based on the initial assessment goals.
Also, add a risk mitigation techniques based on the critical list of the assets and results.
Are findings related to any possible gap between the results and the system baseline definition?
Also at the base, that whole vulnerability can be mitigated.
Findings on the vulnerability assessment are normally very useful and are ordered in a way to ensure
the understanding of the various reports and findings that you have achieved through vulnerability assessment
phase.
The last phase is the post assessment phase will reflect a complete understanding of the security posture
in all the different aspects of the process.
It will also deliver a better outcome for something that in the most cases it does the compliance tool.
There are six types of vulnerability assessment tools.
The first is the host based vulnerability assessment to a host based venerability assessment tool,
finds and identifies the EU's running on a particular host computer and tests it for known deficiencies.
It searches for common applications and services.
The next is the depth assessment tools.
These tools find and identify previously unknown vulnerabilities in the system.
These type of tools include Feather's.
Next is the application that Venerability Assessment Tools Application Larapinta Assessment Tools are
directed towards Web servers or databases.
The scope assessment tools to provide security to the I.T. system by testing for different vulnerabilities
and applications and operating systems.
Active and passive tools, active scanners perform vulnerability checks on the network that consume
resources on the network, passive scanners do not have access to resources considerably.
They only observe the same data and perform data processing on a separate analysis machine, location
and data examine tools.
These are network based scanners Egin with scanners, proxy scanners and plastic scanners.
So characteristics of a good vulnerability assessment tools.
It ensures correct outcomes.
Testing the network, network resources, ports, protocols and operating systems uses well-organized
inference based approach for testing automatically.
Scans against continuously updated databases creates brief, actionable and customizable reports, including
vulnerabilities by severity, level and trend analysis.
Supports various networks how to use the one Raverty assessment tools when their ability assessment
tools are used to test a host application for vulnerabilities.
Tools, the tools that best satisfy the following requirements, like tests from dozens to 3000 different
vulnerabilities, depending on the product, contained several hundred different signatures, match
your involvement and expertise, have a great network application mapping and pen testing, have a number
of regularly updated vulnerably scripts for the platform you're scanning.
It should be able to generate reports and also it should be able to check the different levels of brain
testing to prevent Lokos.
In the next lecture, we will see when rapidly scoring systems.