Nt1310 Unit 4

1122 Words3 Pages

1. Describe what you did, what you learned, your weekly activities, in what ways are you able to apply the ideas and concepts gained, and finally, describe one important thing that you are thinking about in relation to the activity.
This week we learned about various method to value and rank issues in an application or system using CVSS, CMSS, and CCSS. For that, we looked at how specific metrics were applied for base, temporal, and environmental aspects. Considering the specialization of information that each scoring system provides it made me question why certain aspects would just be considered optional, like the temporal or environmental aspects. If doing the exercise of scoring in the first place, why not obtain as much information as …show more content…

Define CVSS and CCSS with respect to the problem chosen from appendix in Unit 3.
CVSS, or Common Vulnerability Scoring System, provides a method for assessing and prioritizing previously unknown vulnerabilities in an application’s code that have been identified for IT management to address (Scarfone & Mell, 2007). CCSS, or Common Configuration Scoring System, is based off of using similar metrics to CVSS but is focused on known vulnerabilities based upon decisions regarding security configurations of the program.
My chosen unit 3 problem was for a dental practice application for scheduling appointments, maintaining patient records for in-house use and claim generation, printing out reminder letters or postcards, and performing financial transactions (Conger, 2008, p795). Both CVSS and CCSS, from the examples given in our week’s provided text, look at specific vulnerabilities in an application. As the application for the dental practice does not exist, I can only give a generalized idea of the application of each scoring system to that …show more content…

Most vulnerabilities would likely require an active attempt to exploit them but there could be passive ones, such as a configuration allowing higher privilege users to stay logged into the application to stay active for an extended period time allowing access to normally secure features. Temporal metrics would be impossible to judge without the application developed and the ability to gauge exploits in the configurations being taken advantage of. Reasonable conjecture might be able to be made beforehand, but it may end up being inaccurate. For environmental metrics, local vulnerability prevalence would be highly dependent on the specific feature being assessed and would require identification of it to really give an appropriate score. Perceived target value, for most of the system, would likely be high as storing of financial information and personal information about clients is ripe fruit for malicious actors wanting to perform identity theft. Local remediation level would again be dependent on the specific configuration vulnerability being addressed. For instance, if it were the issue of active users not logging out, is there a capability to force a log out after a set amount of time or reentry of authentication to go from screen to screen? Security configuration requirements are not specifically outlined in the application request but some

More about Nt1310 Unit 4

Open Document