webapplicationsguide.com

By: MJ

In this advanced era, there are more and more discoveries that allow people from different ends of the Earth to interact. Using the Internet, for example, is one way of being globally updated to other countries. Now, there is a program that we call „Web Applications“ that may further develop a more interactive way of communication.

Web applications are programming languages that interact with the Internet users. Codes and Scripts are used to create web applications. Programming languages should be used such as the JavaScript or HTML. These programs provide a way for the surfer and the web to interact with each other, share information, and of course, have fun at the same time.

Firstly, you should check the security of the servers hosting the e-commerce site. A Web server needs to be hardened and securely maintained. For guidance, I recommend that you download the appropriate Security Configuration Guide from the U.S. National Security Agency Web site. The guides are free and cover most Web servers. You can also use the NIST (National Institute of Standards and Technology) Security Configuration Checklists Repository to find instructions and procedures on how to complete a secure configuration. The free Benchmark and Scoring Tools from the Center for Internet Security (CIS) also provides a quick and easy way to evaluate an e-commerce Web infrastructure and compare its level of security against minimum due-care security benchmarks.

(more…)

CONTENTS OF THE GUIDE, INCLUDE:
* Introduction
o What is Mozilla
o Mozilla Philosophy (standards compliant, etc)
* General Cross Browser Coding Tips
o Browser Detection the Right Way (capabilities VS browser specific checks)
o Abstracting Out Browser Differences
* DHTML
o DOM Differences
+ document.all/global namespace VS document.getElementById
+ Document Fragments
+ Table of mappings from IE -> Standards/Mozilla (innerhtml)
(more…)

Organizations of all sizes use Web applications to deliver services and expand business processes. However, hackers are always searching for weaknesses within these online applications, as they can represent a gateway into valuable back-end databases. With the advent of Web 2.0 features, including blogs, wikis, RSS and other advanced Internet technologies, Web applications are powerful, complex and constantly changing, increasing the likelihood of new vulnerabilities within an application.

To help developers track down and find potential security holes, there are a host of tools available called Web application vulnerability scanners. Their aim is to automate and speed up a process that, when performed manually, is a long and painstaking one. By crawling through a Web site and injecting various attack scenarios, scanners compare an application’s responses against a database of security vulnerability signatures.

Despite their usefulness, Web application vulnerability scanners have not become a must-have for every development team, largely because of cost. Yet there are several good open source scanners available for free. In this tip, we’ll examine a few other reasons for the holdup in Web application vulnerability scanner adoption.

Continue reading here: searchsecurity.techtarget.com

Everyone in IT understands that there are disasters and then there are disasters. Regardless of the scale of any interruption in operations, disaster recovery plans generally comprise details describing how IT will accomplish the two most important tasks they will face in the event of a disaster: business continuity contingencies and the recovery of lost data. While being “down” and “disconnected” from the rest of the world can be financially devastating, losing the data upon which the business relies is equivalent to a monarch losing the crown jewels. Now that’s a disaster, no matter what the underlying cause.

Before Web 2.0 made its way onto the corporate stage, a backup – or two – kept us convinced that, should we lose data for some reason, we could always get it back and, more important, get it back in such a state that we’d have lost nothing more than time. With Web 2.0, however, that task has become a bit trickier. There’s more data, more often, that needs to be backed up and replicated, and only so many hours in the day (the dreaded maintenance window) in which we can accomplish this important task.

Read more here…f5.com

This document examines the architecture behind the early access version of the Adventure Builder Sample Application, which focuses on using the latest Java 2 Platform, Enterprise Edition (J2EE™) 1.4 technologies. For recommendations and guidelines on architecting and designing enterprise applications, see Designing Enterprise Applications With the J2EE Platform, Second Edition. For recommendations and guidelines on architecting and designing Web services, see Designing Web Services with the J2EE Platform.

(more…)

Google’s rate of Web Application development is nothing short of amazing. Not only do they break new ground (just consider the impact that Google Maps has had), but they also redefine and re-energize concepts that have gained very little market traction.

What I’m thinking about here is the concept of using Web applications offline. There have been all sorts of attempts to address this kind of functionality but none of them have had enough market traction to become mainstream. Google Gears is the product from Google Labs that could change that.

(more…)