Skip to content
Browse files

Merge pull request #12815 from Adam89/patch-1

Update security.md [ci skip]
  • Loading branch information...
2 parents 0bb6b43 + 336caf9 commit b31b6e669935cfa7e88e75c02dbd0892d1b9853e @fxn fxn committed
Showing with 1 addition and 1 deletion.
  1. +1 −1 guides/source/security.md
View
2 guides/source/security.md
@@ -17,7 +17,7 @@ After reading this guide, you will know:
Introduction
------------
-Web application frameworks are made to help developers building web applications. Some of them also help you with securing the web application. In fact one framework is not more secure than another: If you use it correctly, you will be able to build secure apps with many frameworks. Ruby on Rails has some clever helper methods, for example against SQL injection, so that this is hardly a problem. It's nice to see that all of the Rails applications I audited had a good level of security.
+Web application frameworks are made to help developers build web applications. Some of them also help you with securing the web application. In fact one framework is not more secure than another: If you use it correctly, you will be able to build secure apps with many frameworks. Ruby on Rails has some clever helper methods, for example against SQL injection, so that this is hardly a problem. It's nice to see that all of the Rails applications I audited had a good level of security.
In general there is no such thing as plug-n-play security. Security depends on the people using the framework, and sometimes on the development method. And it depends on all layers of a web application environment: The back-end storage, the web server and the web application itself (and possibly other layers or applications).

0 comments on commit b31b6e6

Please sign in to comment.
Something went wrong with that request. Please try again.