Book Image

Hands-On Cybersecurity for Finance

By : Dr. Erdal Ozkaya, Milad Aslaner
Book Image

Hands-On Cybersecurity for Finance

By: Dr. Erdal Ozkaya, Milad Aslaner

Overview of this book

Organizations have always been a target of cybercrime. Hands-On Cybersecurity for Finance teaches you how to successfully defend your system against common cyber threats, making sure your financial services are a step ahead in terms of security. The book begins by providing an overall description of cybersecurity, guiding you through some of the most important services and technologies currently at risk from cyber threats. Once you have familiarized yourself with the topic, you will explore specific technologies and threats based on case studies and real-life scenarios. As you progress through the chapters, you will discover vulnerabilities and bugs (including the human risk factor), gaining an expert-level view of the most recent threats. You'll then explore information on how you can achieve data and infrastructure protection. In the concluding chapters, you will cover recent and significant updates to procedures and configurations, accompanied by important details related to cybersecurity research and development in IT-based financial services. By the end of the book, you will have gained a basic understanding of the future of information security and will be able to protect financial services and their related infrastructures.
Table of Contents (20 chapters)

Vulnerabilities and Exploits

In almost all engineering fields, it is very common to analyze past failures so that we can learn and improve on the current situation. According to the US Department of Homeland Security, 90% of security incidents are the result of exploiting software defects. Many developers are therefore testing their software before releasing it. These tests happen either on-premise or in the cloud. However, they often focus on user ability, performance, and somewhat synthetic security testing. Therefore, many developers are often unaware of security vulnerabilities in their software. There is no mandate or regulation on adapting a secure development life cycle or having a responsible vulnerability disclosure. It is therefore the responsibility of the individual and the broader security community to build more secure software and inform independent software vendors...