C. Steward, Luay A. Wahsheh, Aftab Ahmad, J. Graham, Cheryl V. Hinds, Aurelia T. Williams, S. J. DeLoatch
{"title":"软件安全:危险的事后考虑","authors":"C. Steward, Luay A. Wahsheh, Aftab Ahmad, J. Graham, Cheryl V. Hinds, Aurelia T. Williams, S. J. DeLoatch","doi":"10.1109/ITNG.2012.60","DOIUrl":null,"url":null,"abstract":"As users of many different types of software, one of the last things we think about when deciding which is best for the task at hand is the security of the software. This of course depends on the type of software as well. If it is banking or tax software then, security is of concern. However, in most cases the thought rarely crosses the average users mind. That is until something happens to the system or information the system may hold. This way of thinking is very similar to the way some software is created. The software's features, usability, and interface are normally at the forefront. On the other hand the software's security is just an afterthought for many developers. While software is developed in a very intricate process, it does not currently stress security. In this paper, we will describe different approaches that have been recently researched to help create more secure software. Although these approaches will be introduced separately, using a combination of two or all three together would be the most secure combination.","PeriodicalId":117236,"journal":{"name":"2012 Ninth International Conference on Information Technology - New Generations","volume":"137 2 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2012-04-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"7","resultStr":"{\"title\":\"Software Security: The Dangerous Afterthought\",\"authors\":\"C. Steward, Luay A. Wahsheh, Aftab Ahmad, J. Graham, Cheryl V. Hinds, Aurelia T. Williams, S. J. DeLoatch\",\"doi\":\"10.1109/ITNG.2012.60\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"As users of many different types of software, one of the last things we think about when deciding which is best for the task at hand is the security of the software. This of course depends on the type of software as well. If it is banking or tax software then, security is of concern. However, in most cases the thought rarely crosses the average users mind. That is until something happens to the system or information the system may hold. This way of thinking is very similar to the way some software is created. The software's features, usability, and interface are normally at the forefront. On the other hand the software's security is just an afterthought for many developers. While software is developed in a very intricate process, it does not currently stress security. In this paper, we will describe different approaches that have been recently researched to help create more secure software. Although these approaches will be introduced separately, using a combination of two or all three together would be the most secure combination.\",\"PeriodicalId\":117236,\"journal\":{\"name\":\"2012 Ninth International Conference on Information Technology - New Generations\",\"volume\":\"137 2 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2012-04-16\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"7\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2012 Ninth International Conference on Information Technology - New Generations\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ITNG.2012.60\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2012 Ninth International Conference on Information Technology - New Generations","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ITNG.2012.60","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
As users of many different types of software, one of the last things we think about when deciding which is best for the task at hand is the security of the software. This of course depends on the type of software as well. If it is banking or tax software then, security is of concern. However, in most cases the thought rarely crosses the average users mind. That is until something happens to the system or information the system may hold. This way of thinking is very similar to the way some software is created. The software's features, usability, and interface are normally at the forefront. On the other hand the software's security is just an afterthought for many developers. While software is developed in a very intricate process, it does not currently stress security. In this paper, we will describe different approaches that have been recently researched to help create more secure software. Although these approaches will be introduced separately, using a combination of two or all three together would be the most secure combination.