========================
Web Application Security
========================

:category: page
:slug: web-application-security
:sort-order: 13

Website security must be incorporated into building every level of the web 
stack. However, I include a separate section here for topics that deserve 
a comprehensive review such as firewalls, SSL certificates, and public key
authorization.

---------
Key Terms
---------
*Authorization* - specifying access rights and permissions to server and 
application resources. For example, a non-logged in user can view a landing
page but only a logged in user can access an application's "account" screen.


Security Resources
------------------
`When and How to Deploy HTTPS <http://erik.io/blog/2013/06/08/a-basic-guide-to-when-and-how-to-deploy-https/>`_

`Securing a Linux Server <http://spenserj.com/blog/2013/07/15/securing-a-linux-server/>`_ 

`Securing Your Website <http://arstechnica.com/security/2013/02/securing-your-website-a-tough-job-but-someones-got-to-do-it/>`_

`How HTTPS Secures Connections: What Every Web Dev Should Know <http://blog.hartleybrody.com/https-certificates/>`_

Open Web Application Security Project `(OWASP) Cheat Sheets for Security <https://www.owasp.org/index.php/Cheat_Sheets>`_
