Cbyber

Abuse cases are the adaptation of use cases which anticipate the abnormal behavior of the software that is being developed. Uses cases modeled to display the positive features of the software to users. Software vendors talk about how the software changes the business world and the positives outcomes overall. On the other hand, we have to think about the abnormal behavior of the software and prepare for it ahead. This scenario is called abuse cases (Hope, Mcgraw, & Anton, 2004).

What is the Importance of Abuse Cases?

Abuse cases give a chance to think from the attackers perspective and be ready to secure the software from the beginning. By thinking beyond normative features, while simultaneously contemplating negative or unexpected events, software security professionals can better understand how to create secure and reliable software. Besides, by doing so, we assure the confidentiality, integrity and availability of the system. Security architecture must be built in from the ground up, as a critical part of the design from the very beginning and included in every subsequent development phase all the way through in a complete system (Hope, Mcgraw, & Anton, 2004). Last but not the least is that, abuse cases present information about security risks in a format that may already be familiar to the vendors of the software development process. This should make it easier for people with little or no security background to start thinking about securing their systems and how to trade off security and functionality (Sinnema, 2012).

Hope, p., Mcgraw, G., & Anton, A. I. (2004, June 21). Misuse and abuse cases: getting past the positive. IEEE Security and Privacy, 2(3), 90-92. DOI:10.1109/MSP.2004.17

Sinnema, R. (2012, August 13). Abuses cases. Retrieved from https://remonsinnema.com/2012/08/13/abuse-cases/