02.03.2018 Views

Sybex CEH Certified Ethical Hacker Version 8 Study Guide

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

312 Chapter 13 ■ Web Servers and Web Applications<br />

Data Layer Responsible for holding the data and information for the application as<br />

a whole<br />

All of these layers depend on the technology brought to the table in the form of the<br />

World Wide Web, HTML, and HTTP. HTTP is the main protocol used to facilitate<br />

communication between clients and servers, and it operates over port 80. However, other<br />

protocols are sometimes used.<br />

HTTPS (HTTP employing encryption mechanisms) can be used to protect<br />

data in transit. This approach is common in applications such as webmail<br />

and e-commerce.<br />

Web applications make heavy use of an underlying web server technology such as<br />

Microsoft’s Internet Information Services (IIS), Apache Server, and Oracle’s iPlanet Web<br />

Server. Resources such as web pages are requested via the stateless HTTP protocol. The<br />

client provides a uniform resource identifier (URI), which tells the server what information<br />

is being requested and what to return.<br />

Stateless refers to the fact that the protocol does not keep track of session<br />

information from one connection to the next. In fact, each communication<br />

in HTTP is treated as a separate connection.<br />

Another common component of web applications is the feature known as cookies. A<br />

cookie is a file stored on a client system that is used as a token by applications to store<br />

information of some type (depending on the application). As far as applications are<br />

concerned, cookies are a common element, but from a security standpoint they are viewed<br />

as a liability since they can be easily copied.<br />

Cookies emerged as a solution to the problems web developers<br />

experienced with their websites. Cookies allow the owner and developer<br />

of a site to store information on a client system. This information enables<br />

a site to remember the state of the browser as well as store session<br />

information. When a browser is used to visit a site, it will have a cookie<br />

with a unique ID stored on its system. On subsequent visits, this ID will<br />

allow the site to remember the visitor.<br />

Another issue with web applications is vulnerability. No matter how strong the<br />

security policy or standards, every web application is vulnerable to attack and suffers from<br />

flaws. Attacks such as SQL injection, cross-site scripting (XSS), and session hijacking can<br />

take place.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!