What do you think?
Rate this book
Secure Coding in PL/SQL
Secure Coding in PL/SQL is a thought-provoking book laying out the core issues that you may come across that can make your PL/SQL be the cause of a security breach or loss of data for your organization. Data theft is becoming so common that even the BBC evening news talks about data breaches, hackers, identity theft, and much more on a seemingly regular basis with no consideration now for what was a technical subject just a short time ago. The public is aware of data theft and loss, so you as a PL/SQL developer must also be aware of the key threats and causes.
Secure Coding in PL/SQL starts with the why data is insecure, what makes it insecure, why the way Oracle Database works causes concern over securing of data, and what we as practitioners of Oracle Database and PL/SQL inadvertently do to make matters worse. Focus is on issues and their underlying causes, helping you to first understand why an issue even exists, and then laying out a solution. The author is an expert in the subject of PL/SQL security and data security in general, and is well-known for his expertise in design, good coding practice, and ideas and methods for security.
Secure Coding in PL/SQL starts with why data can be insecure in your database, investigating poor design choices and advising best practice. The book also covers all common insecure coding techniques that allow data loss or your code to be an attack vector for hackers. The author then looks at best practice with realistic techniques and tips that can be used to ensure securely coded PL/SQL. The book also investigates why your PL/SQL itself can be the target of attack. Some attackers may simply steal your code and use it as a black box, or they may be more interested in learning the algorithms that you have used in order to exploit holes in those algorithms in an attack. We explore techniques to prevent such things. The book completes with a discussion on next steps such as creating policies, and testing and scanning of existing or new PL/SQL code.
What you'll learnLearn why data can be insecure in an Oracle databaseGrasp the ground rules for good code and data designAvoid insecure coding style and detect insecure codeFollow ground rules and practices for writing code to withstand attackSecure your PL/SQL source code itself, from theft and from loss of intellectual property rightsImplement automated testing of new and existing code to ensure compliance with policies and best practice
Who this book is for
Secure Coding in PL/SQL is aimed squarely at programmers responsible for writing PL/SQL that runs inside an Oracle Database Instance. The book is also helpful to database administrators tasked with ensuring the security of their databases against malicious attack and data theft. "
Secure Coding in PL/SQL starts with the why data is insecure, what makes it insecure, why the way Oracle Database works causes concern over securing of data, and what we as practitioners of Oracle Database and PL/SQL inadvertently do to make matters worse. Focus is on issues and their underlying causes, helping you to first understand why an issue even exists, and then laying out a solution. The author is an expert in the subject of PL/SQL security and data security in general, and is well-known for his expertise in design, good coding practice, and ideas and methods for security.
Secure Coding in PL/SQL starts with why data can be insecure in your database, investigating poor design choices and advising best practice. The book also covers all common insecure coding techniques that allow data loss or your code to be an attack vector for hackers. The author then looks at best practice with realistic techniques and tips that can be used to ensure securely coded PL/SQL. The book also investigates why your PL/SQL itself can be the target of attack. Some attackers may simply steal your code and use it as a black box, or they may be more interested in learning the algorithms that you have used in order to exploit holes in those algorithms in an attack. We explore techniques to prevent such things. The book completes with a discussion on next steps such as creating policies, and testing and scanning of existing or new PL/SQL code.
What you'll learnLearn why data can be insecure in an Oracle databaseGrasp the ground rules for good code and data designAvoid insecure coding style and detect insecure codeFollow ground rules and practices for writing code to withstand attackSecure your PL/SQL source code itself, from theft and from loss of intellectual property rightsImplement automated testing of new and existing code to ensure compliance with policies and best practice
Who this book is for
Secure Coding in PL/SQL is aimed squarely at programmers responsible for writing PL/SQL that runs inside an Oracle Database Instance. The book is also helpful to database administrators tasked with ensuring the security of their databases against malicious attack and data theft. "
100 pages, Paperback
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
No one has reviewed this book yet.