This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Category:PHP"

From OWASP
Jump to: navigation, search
(css)
m (change)
Line 7: Line 7:
 
== About ==
 
== About ==
  
The OWASP PHP Technology Knowledge Base is the clearing house for all information related to building secure web applications and services based on PHP technologies. The focus of the project is on guidance for developers and application architects on using PHP and PHP frameworks. Moreover, we aim to provide security related guidance for system administrators managing PHP based applications and tools.
+
There are 1.8 billion websites on the internet today [Netcraft]. Nearly 80% are powered by the PHP programming language. Democracy, freedom, and a better world are not possible if PHP is insecure. This project seeks to be the clearing house for the best ways of protecting PHP websites, apps, and the data they have. Thank you for reading.
 +
 +
== What Does PHP Security Mean? ==
 +
* Is my code secure? E.g. am I using the latest version of PHP
 +
* Is my architecture secure? E.g. Have I hardened the web server the application runs on?
 +
* Is my development infrastructure secure? E.g. Do I have 2FA on my Github account along with all other developers?
  
Community content is key to security information. The project depends on content from developers throughout the PHP ecosystem.
 
  
==Purpose==
+
== What Can You Learn Here? ==
 +
* Fastest way to secure a legacy PHP application
 +
* How to secure phpmyadmin, MySQL, and Postgres databases
 +
* What options do I need in my php.ini file for security?
 +
* How to secure the web server running your PHP
 +
* How can I check my dependencies for vulnerabilities?
 +
* How to harden your WordPress or Drupal site
 +
  
* Provide deep, rich guidance for PHP developers in using the security features of PHP and of PHP frameworks.
 
* Address security in relation to PHP and derived technologies.
 
* Guide system administrators in managing PHP related components and applications.
 
* Create guidance for use of OWASP components that are designed for use with PHP.
 
* Focus on information about working with and on OWASP tools built using PHP or other PHP technologies.
 
* Provide a stream of security related information, like vulnerabilities and security patches, related to the PHP universe.
 
* Build an ecosystem allowing to all actors interested to discuss, share and learn.
 
 
== Licensing ==
 
 
OWASP PHP Technology Knowledge Base is free to use. It is licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
 
  
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

Revision as of 22:37, 1 January 2019

About

There are 1.8 billion websites on the internet today [Netcraft]. Nearly 80% are powered by the PHP programming language. Democracy, freedom, and a better world are not possible if PHP is insecure. This project seeks to be the clearing house for the best ways of protecting PHP websites, apps, and the data they have. Thank you for reading. ​

What Does PHP Security Mean?

  • Is my code secure? E.g. am I using the latest version of PHP
  • Is my architecture secure? E.g. Have I hardened the web server the application runs on?
  • Is my development infrastructure secure? E.g. Do I have 2FA on my Github account along with all other developers?


What Can You Learn Here?

  • Fastest way to secure a legacy PHP application
  • How to secure phpmyadmin, MySQL, and Postgres databases
  • What options do I need in my php.ini file for security?
  • How to secure the web server running your PHP
  • How can I check my dependencies for vulnerabilities?
  • How to harden your WordPress or Drupal site


Team

Lead: Dan Ehrlich

Please email dan.ehrlich@owasp.org if you would like to help out.


Meta

Last Update: 12/2018


Other Resources

Mailing List


Related Projects

It is not easy to produce a PHP application without security vulnerabilities. Most application security vulnerabilities apply to PHP applications just like other environments.

The goals of this project are to provide information about building, configuring, deploying, operating, and maintaining secure PHP applications. We cover the following topics or pick a topic from the OWASP PHP Table of Contents

PHP Security for Architects
Provides information about the design and architectural considerations for a PHP web application. Common architectures such as MVC, Ajax, Web Services and PEAR / Zend Frameworks are discussed.
PHP Security for Developers
This section covers dangerous calls and common vulnerabilities associated with them, such as system() exec(), eval() and so on. This section will also cover standard security mechanisms available in the standard language, such as cryptography, logging, encryption, and error handling. Securing elements of an application, such as controllers, business logic, and persistence layers will be covered. We'll discuss handling request parameters, encoding, injection, and more.
PHP Security for Deployers
These articles cover topics specifically related to the PHP hosting environment. We discuss minimizing the attack surface, configuring error handlers, and performing hardening of PHP.

To get involved join the mailing list: OWASP PHP Mailing List

Please visit the Tutorial and remember to add the tag: [[Category:PHP]] at the end of articles so that they're properly categorised.

<TBD>

The previous version of this PHP Project home page is archived here: OWASP_PHP_Project_Archive_(03.2015)