Lunes, Enero 11, 2016

WEBSECURITY

WEBSECURITY



Web application security is a branch of Information Security that deals specifically with security of websites, web applications and web services. At a high level, Web application security draws on the principles of application security but applies them specifically to Internet and Web systems.

Security threats[edit]

With the emergence of Web 2.0, increased information sharing through social networking and increasing business adoption of the Web as a means of doing business and delivering service, websites are often attacked directly. Hackers either seek to compromise the corporate network or the end-users accessing the website by subjecting them to drive-by downloading.[2][3]
As a result, industry[4] is paying increased attention to the security of the web applications[5] themselves in addition to the security of the underlying computer network and operating systems.
The majority of web application attacks occur through cross-site scripting (XSS) and SQL injection attacks[6] which typically result from flawed coding, and failure to sanitize input to and output from the web application. These are ranked in the 2009CWE/SANS Top 25 Most Dangerous Programming Errors.[7]
Phishing is another common threat to the Web application and global losses from this type of attack in 2012 were estimated at $1.5 billion.[8]

According to the security vendor Cenzic, the top vulnerabilities in March 2012 include:[9]
37%Cross-site scripting
16%SQL injection
5%Path disclosure
5%Denial-of-service attack
4%Arbitrary code execution
4%Memory corruption
4%Cross-site request forgery
3%Data breach (information disclosure)
3%Arbitrary file inclusion
2%Local file inclusion
1%Remote file inclusion
1%Buffer overflow
15%Other, including code injection (PHP/JavaScript), etc.

Best Practices Recommendation[edit]

Secure web application development should be enhanced by applying security checkpoints and techniques at early stages of development as well as throughout the software development lifecycle. Special emphasis should be applied to the coding phase of development. Security mechanisms that should be used include, threat modeling, risk analysis, static analysis, digital signature, among others.[10]

Security standards[edit]

OWASP is the emerging standards body for Web application security. In particular they have published the OWASP Top 10 which describes in detail the major threats against web applications. The Web Application Security Consortium(WASC) has created the Web Hacking Incident Database[11] and also produced open source best practice documents on Web application security.

Security technology[edit]

While security is fundamentally based on people and processes, there are a number of technical solutions to consider when designing, building and testing secure web applications. At a high level, these solutions include:

See also[edit]

WEBSECURITY

WEBSECURITY



Web application security is a branch of Information Security that deals specifically with security of websites, web applications and web services. At a high level, Web application security draws on the principles of application security but applies them specifically to Internet and Web systems.

Security threats[edit]

With the emergence of Web 2.0, increased information sharing through social networking and increasing business adoption of the Web as a means of doing business and delivering service, websites are often attacked directly. Hackers either seek to compromise the corporate network or the end-users accessing the website by subjecting them to drive-by downloading.[2][3]
As a result, industry[4] is paying increased attention to the security of the web applications[5] themselves in addition to the security of the underlying computer network and operating systems.
The majority of web application attacks occur through cross-site scripting (XSS) and SQL injection attacks[6] which typically result from flawed coding, and failure to sanitize input to and output from the web application. These are ranked in the 2009CWE/SANS Top 25 Most Dangerous Programming Errors.[7]
Phishing is another common threat to the Web application and global losses from this type of attack in 2012 were estimated at $1.5 billion.[8]

According to the security vendor Cenzic, the top vulnerabilities in March 2012 include:[9]
37%Cross-site scripting
16%SQL injection
5%Path disclosure
5%Denial-of-service attack
4%Arbitrary code execution
4%Memory corruption
4%Cross-site request forgery
3%Data breach (information disclosure)
3%Arbitrary file inclusion
2%Local file inclusion
1%Remote file inclusion
1%Buffer overflow
15%Other, including code injection (PHP/JavaScript), etc.

Best Practices Recommendation[edit]

Secure web application development should be enhanced by applying security checkpoints and techniques at early stages of development as well as throughout the software development lifecycle. Special emphasis should be applied to the coding phase of development. Security mechanisms that should be used include, threat modeling, risk analysis, static analysis, digital signature, among others.[10]

Security standards[edit]

OWASP is the emerging standards body for Web application security. In particular they have published the OWASP Top 10 which describes in detail the major threats against web applications. The Web Application Security Consortium(WASC) has created the Web Hacking Incident Database[11] and also produced open source best practice documents on Web application security.

Security technology[edit]

While security is fundamentally based on people and processes, there are a number of technical solutions to consider when designing, building and testing secure web applications. At a high level, these solutions include:

See also[edit]

WEBSECURITY

WEBSECURITY



Web application security is a branch of Information Security that deals specifically with security of websites, web applications and web services. At a high level, Web application security draws on the principles of application security but applies them specifically to Internet and Web systems.

Security threats[edit]

With the emergence of Web 2.0, increased information sharing through social networking and increasing business adoption of the Web as a means of doing business and delivering service, websites are often attacked directly. Hackers either seek to compromise the corporate network or the end-users accessing the website by subjecting them to drive-by downloading.[2][3]
As a result, industry[4] is paying increased attention to the security of the web applications[5] themselves in addition to the security of the underlying computer network and operating systems.
The majority of web application attacks occur through cross-site scripting (XSS) and SQL injection attacks[6] which typically result from flawed coding, and failure to sanitize input to and output from the web application. These are ranked in the 2009CWE/SANS Top 25 Most Dangerous Programming Errors.[7]
Phishing is another common threat to the Web application and global losses from this type of attack in 2012 were estimated at $1.5 billion.[8]

According to the security vendor Cenzic, the top vulnerabilities in March 2012 include:[9]
37%Cross-site scripting
16%SQL injection
5%Path disclosure
5%Denial-of-service attack
4%Arbitrary code execution
4%Memory corruption
4%Cross-site request forgery
3%Data breach (information disclosure)
3%Arbitrary file inclusion
2%Local file inclusion
1%Remote file inclusion
1%Buffer overflow
15%Other, including code injection (PHP/JavaScript), etc.

Best Practices Recommendation[edit]

Secure web application development should be enhanced by applying security checkpoints and techniques at early stages of development as well as throughout the software development lifecycle. Special emphasis should be applied to the coding phase of development. Security mechanisms that should be used include, threat modeling, risk analysis, static analysis, digital signature, among others.[10]

Security standards[edit]

OWASP is the emerging standards body for Web application security. In particular they have published the OWASP Top 10 which describes in detail the major threats against web applications. The Web Application Security Consortium(WASC) has created the Web Hacking Incident Database[11] and also produced open source best practice documents on Web application security.

Security technology[edit]

While security is fundamentally based on people and processes, there are a number of technical solutions to consider when designing, building and testing secure web applications. At a high level, these solutions include:

See also[edit]

WIRELESS APPLICATION PROTOCOL

WIRELESS APPLICATION PROTOCOL


The WAP Forum dates to 1989. It aimed primarily to bring together the various wireless technologies in a standardised protocol. The first company to launch a WAP site was Dutch mobile phone operator Telfort BV in October 1999. The site was developed as a side project by Christopher Bee and Euan McLeod and launched with the debut of the Nokia 7110.
In 2002 the WAP Forum, founded by Ericsson, Motorola, Nokia and Unwired Planet (later known as Openwave), was consolidated (along with many other forums of the industry) into Open Mobile Alliance (OMA]).
WAP Push

WAP Push Process
WAP Push was incorporated into the specification to allow the WAP content to be pushed to the mobile handset with minimum user intervention. A WAP Push is basically a specially encoded message which includes a link to a WAP address.
WAP Push was specified on top of Wireless Datagram Protocol (WDP); as such, it can be delivered over any WDP-supported bearer, such as GPRS or SMS. Most GSM networks have a wide range of modified processors, but GPRS activation from the network is not generally supported, so WAP Push messages have to be delivered on top of the SMS bearer.
On receiving a WAP Push, a WAP 1.2 (or later) -enabled handset will automatically give the user the option to access the WAP content. This is also known as WAP Push SI (Service Indication). A variant, known as WAP Push SL (Service Loading), directly opens the browser to display the WAP content, without user interaction. Since this behaviour raises security concerns, some handsets handle WAP Push SL messages in the same way as SI, by providing user interaction.
The network entity that processes WAP Pushes and delivers them over an IP or SMS Bearer is known as a Push Proxy Gateway (PPG).