11.07.2015 Views

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

SHOW MORE
SHOW LESS

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

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

782 <strong>Improving</strong> <strong>Web</strong> <strong>Application</strong> <strong>Security</strong>: <strong>Threats</strong> <strong>and</strong> CountermeasuresAfter creating the second rule, the MyPolicy Properties dialog box should look likethe one in Figure 6.Figure 6MyPolicy Properties dialog boxYour IPSec policy is now ready to use. To activate the policy, right-click MyPolicy<strong>and</strong> then click Assign.Summary of What You Just DidIn the previous three procedures, you performed these actions:●●●You started by creating two filter actions: one to allow traffic <strong>and</strong> one to blocktraffic.Next, you created two IP filter lists. The one called MatchAllTraffic matches on alltraffic, regardless of port. The one called MatchHTTPAndHTTPS contains twofilters that match TCP traffic from any source address to TCP ports 80 <strong>and</strong> 443.Then you created an IPSec policy by creating a rule that associated the MyBlockfilter action with the MatchAllTraffic filter list <strong>and</strong> the MyPermit filter action withthe MatchHTTPAndHTTPS filter list. The result of this is that the <strong>Web</strong> server onlyallows TCP traffic destined for port 80 or 443. All other traffic is rejected.

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

Saved successfully!

Ooh no, something went wrong!