Scan 1According to this scan,the host for the security system was running on Linux and thus it was prone toservice denial, remotely. As a result, the system became vulnerable.
Theidentified nodes that contributed to the system vulnerability were 188.8.131.52(1-1-1-167.tvc-ip.com).
The vulnerability of this system was identified through the vulnerabilitydetection method that is inherent in the security system. The vulnerability ofthis system implies that security is prone to any attack, thus any remoteattack is likely to lead to kernel crash, if it is exploited by illegitimateintruders. The obvious implication of these illegitimate users may deny accessto legitimate users of this security and thus bring about insecurity concerns. Thebest way to overcome or fight such types of system vulnerabilities is by upgradingthe system’s Linux kernel version from the version you are using now to 3.0.
17,3.1.9 or 3.2.1.Scan 2In this scan, the webserver used was susceptible to any access had a long basic authenticationfield. This vulnerability was to the extent of causing continual web servercrashes, or in some cases a cracker or hacker of your security system can executearbitrary codes on your security system.
The affected nodes revealed in thisscan were 184.108.40.206(1-1-1-169.tvc-ip.
com). The best solution for this type of servervulnerability is upgrading the security system software or protecting thesecurity with a filtering reverse proxy.Scan 3 Inthis scan, it was revealed that the security system used was running on aserver with SSL/TTL, and as such the system is liable to information disclosuresusceptibility. The fault detected in this system showed that vulnerabilityarose due to a cookie that did not use ‘secure’ attribute and as such hackersfind it easy to access this system. The affected nodes in this scan were 1.1.1.
169(1-1-1-169.tvc-ip.com).The best solution for this security system is to ensure that the ‘secure’attribute is set hence ensuring all the cookies are sent over a SSL/TTLconnection. Scan 4In this scan, it wasrevealed that the routine reports for all the SSL/TTL cipher suites areaccepted by a service that makes attack vectors exist only on HTTPS services.
The64-bit blocker 3DES was made susceptible to SWEET32 hijacking attacks. Theaffected nodes revealed in this scan were 220.127.116.11(mail.hrfmlaw.
com) and18.104.22.168(1-1-1-169.tvc-ip.com). To overcome this challenge, there needs to bechanges made on configurations made in the aforementioned services, to ensureall the listed cipher suites do not appear at all.