Securing PHP: Core Concepts cover page

Securing PHP: Core Concepts

Securing PHP: Core Concepts

Security is a big topic. I mean *really* big. If you break it down into little chunks, there's lots of important bits to pay attention to but it all really starts with the application. Without good secure coding practices, your application could be doomed from the start. We as PHP developers have had trouble in the past integrating these practices into our day to day development. This book walks you through some of the most common terms and practices, giving you a better picture of the whole of application…
Securing PHP: Core Concepts Edit
This book is 100% complete


About the Book

Securing PHP: Core Concepts acts as a guide to some of the most common security terms and provides some examples of them in every day PHP. Anything's easier to learn when you're all speaking the same language. This book starts you in the right direction, providing directions on the path to more secure development. Your users deserve a better level of privacy and security in the services they use.

This book looks at topics like:

  • Confidentiality, Integrity and Availability
  • Defense in Depth
  • Failing securely
  • Keeping security simple
  • Threat modeling
  • Attack patterns

...and many more. You'll learn about some of the essential foundations to writing secure software and see how they fit into the over all picture of the Secure Software Development Lifecycle.There's lots of books and articles out there about secure development and secure coding practices, but there's a distinct lack of PHP-targeted resources. The ones that are out there are years old and contain outdated information about things like register_globals or other deprecated features. 

I've been studying secure coding practices and general development for a few years now and I can safely say that this kind of information is in dire need in the PHP community. There's been some efforts in the past to inform developers how to defeat the typical OWASP Top 10 but application securing goes much beyond this. There's a whole ecosystem of terms and techniques around it that PHP developers need to know about.

This book introduces those concepts in an easy and accessible way and provides you with a good jumping off point towards future secure development.

Feedback for Securing PHP: Core Concepts

“I took tremendous value from Securing PHP, rather than a long list of examples of how to implement secure practices; I found this book forced me to really think about some of the decisions I was making in my own code. Writing secure code is more than just taking and implementing specific strategies and more about knowing and understanding all the ways in which your application may be vulnerable and addressing them in a manner that makes the most sense for your application. Even as I was reading, specific examples were coming to mind and giving me a list of things I needed to investigate. Securing PHP did a wonderful job of explaining some common security exploits. This is a must read for any PHP developer.” - Matt Frost

"I finally found the time to read 'Securing PHP: Core Concepts' and it has been a very good reading. I really enjoyed the writing style and the way the CIA approach was presented and the other security concerns. [...] Thanks for writing this book and I look forward to read your next 'Securing PHP: The Usual Suspects'." - Enrico Zimuel

Read more

Table of Contents

  • First, a few thanks
  • Introduction
    • Why should you read this book?
    • The Secure Development Lifecycle
    • Where this book fits
  • The CIA (No, not that CIA)
    • Availability
    • Integrity
    • Confidentiality
    • Is that all?
  • A Few “Quick Hits”
    • Threat
    • Vulnerability
    • Risk
    • Exploit
    • Countermeasure
    • Attack Surface
    • Non-repudiation
    • Attack Pattern
    • Attack Surface
    • Trust
    • And finally…
  • Keeping It Simple
    • Going Agile
    • A quick word on architecture
    • Getting down to it
    • Overkill
  • Defense in Depth
    • Information Assurance
    • When it’s not in depth
  • Fail Securely
    • “Fail Secure” versus “Fail Safe”
    • A code example
    • Architected to fail
    • Failure types
  • Least Privilege
    • But what about attacks?
    • Planning to fail
  • Access Control
    • Authentication versus Authorization
    • Types of Controls
    • Planning for Proxy
  • Threat Modeling
    • Switching Perspectives
    • The Process
    • Using STRIDE
    • Using DREAD
  • Learn, Learn and Learn Some More
    • The Importance of Learning (and Teaching!)
  • Appendix
    • Introduction
    • The CIA (No, not that CIA)
    • A Few “Quick Hits”
    • Fail Securely
    • Access Control
    • Threat Modeling

Read More

About the Author

The Leanpub Unconditional, No Risk, 100% Happiness Guarantee

Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks. We process the refunds manually, so they may take a few days to show up.
See full terms