Abstract
The discussion of security usually involves latest threats, the technology for safeguarding against those threats, and the best practices that influence current thinking in regards to people, process and technology. While such discussion is important, it should not ignore legacy applications, proprietary solutions, and mainframes. These three areas are commonly overlooked. Perhaps this is because of their perceived separation from mainstream threats. However, because the insider does not view these devices separate from the mainstream computing environment, the threat is real. There are many legacy applications running on mainframes but there are few individuals able to provide support These types of legacy applications suffer from: having no access control, passwords that are embedded in the code, poor auditing capabilities, poor logging, poor documentation, being written in a legacy programming language, being designed to work in an environment far different than today's, and not having the functionality to conform to regulatory compliance. This chapter provides an example of an insider with a conscience and the threat posed by the scenario.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
