Identification of Risks, Threats, and Vulnerabilities

 

Question 1

CVE is a list of open source vulnerabilities presented as an identification number with descriptions and public references. The CVE avails an essential list of entries for common vulnerabilities and is usable in numerous capacities by cyber-security agents. The list is available online for free on the Common Vulnerabilities and Exposure website. One of the notable agencies that use data from this source is the U.S. National Vulnerability Database.

Question 2

The CVE program does not explicitly define the term, vulnerability, but relies on standard definitions from other sources. Murshed (2017), thus offers three explanations to this term; one, weakness is inherent if a product owner considers an issue a vulnerability to his or her product. The case implies that if the owner declares that specific entry is a vulnerability on his end, then the entry becomes publicly known for its vulnerability irrespective of other persons’ opinions. Similarly, weakness is an issue that violates the security protocol of a product. As such, whenever the CNA determines that an entry has bypassed security policies, the CAN enlists it as a public threat. Lastly, vulnerabilities also include reports from external sources about vulnerabilities. Ideally, if one reports that an issue is a vulnerability, then the CNA terms it a vulnerability irrespective of everything.

Question 2B

Exposure is the proximity to vulnerability. Once a product has numerous vulnerabilities, then it has exposure to hackers and remote attackers. Therefore, exposure is definable as the presence of loopholes, or weaknesses, in a product that may allow remote attackers to execute unwarranted codes.

Question 3

Having assessed the vulnerabilities of Microsoft XP 2003 Service Pack 1 from the CVE list, I came across 18 vulnerability entries. The following is a description of four of the results;

Question 4

After searching the CVE database by keying in words, Cisco ASA 5505

Security +, only two results of vulnerability emerged. They included;

 

 

 

 

 

 

 

References

Murshed, S. M. (2017). An investigation of software vulnerabilities in open source software

projects using data from publicly-available online sources (Doctoral dissertation, Carleton University).

Perez-Botero, D., Szefer, J., & Lee, R. B. (2013, May). Characterizing hypervisor vulnerabilities

in cloud computing servers. In Proceedings of the 2013 international workshop on Security in cloud computing (pp. 3-10).

Subramanian, P. (2015). Security Content Metadata Model with an Efficient Search

Methodology for Real-Time Monitoring and Threat Intelligence. Retrieved 12(04), 2017.

 

error: Content is protected !!