For this task I will invistage the Check for weak SSL cyhpher. Some older chyspers have a limit to the length of the key making them possible to crack this is likely to be the corse of the error this can be fix by changing the SSL key for a longer one. Some older way of forming cyphers are insecure and can be avoided. The strength of these cythers is mainly judged based on how long it would take to crack any given encription. Any thing which is insecrue will considered weak, anything that will take 10 year to crack is considered median and anything longer is considered strong. It is possible take we could change any SSL we used to be of at least a mediaum level by it is better to keep all sercuirty and the greates level possible so we should aim for strong cyphers.
The CVSS Score is a system for scoring how much of a risk any given vanrability is so people can decide in what order they go about fixing the vanrability. The CVSS database store vanrabilities basied on their score and also explains what percentage of vanrability each score makes up. The database sort infomration such as the complexability of useing an explore, if a explort can be access remotely and what products the vanrability effect. Some of the infomration stored here effects the score that a product gets, for example most 10 scores are low to medium complexity and can be use remotely making them more serious threats. While most 2 to 3 score recquire local access to the device to access and have complexity scores from low to high.
To use a vanrability scanner to find explores a user would need to scan the system a device for vanrability. Once vanrability are found the user need to priorities what order the explorts will be dealt with, in most cases the scaner should be able to help by providing scores for this. Once the order is decided the user would need to research the issue, although some scanner might provide information it is best to do some research if conditions allow. Once the high prioity epoloits are fix it is best to rescan the system to check that the issues were actual resolve, multiple scan are also useful as the scanner can often miss vanrabilities and rescanning allows the users to find any issues which were missed. Once this is completed the user can then repeat this processes until as many of the vanbility as fessible are fixed. It is best to resolve as many issues as possible but due to time constrants it can be not possible to clear all isssue which is why we complete high piroity issues first.