Network World
Friday, May 25, 2012
DNSstuff.com
Get information about your IP
IP Information
50+ On-demand DNS and network tools
Error 404--Not Found

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

Not protecting Web appliances

Hackers are gravitating toward Web app exploits, so be prepared.

Click to see:

Ensuring that mobile applications are truly secure
05/25/12
Mobile devices are the next big platform for serious business and consumer applications. Smartphones and tablets are now home to apps for mobile payments, banking, healthcare, customer service, product inventory, law enforcement and so much more. But they may be putting sensitive data at risk. viaForensics offers a unique service to uncover vulnerabilities.

Cisco all but kills Cius tablet computer
05/25/12
Cisco is slowly killing off its Cius business tablet less than a year after it started shipping.

Untethered jailbreak for iOS 5.1.1 available for download
05/25/12
Absinthe 2.0, the jailbreak for iOS 5.1.1, is ready and available for download, the Jailbreak Dream Team announced at the Hack in the Box conference in Amsterdam on Friday.

One of the most common and biggest mistakes that companies make is not taking the steps necessary to properly protect their Web site and Web applications.

While exploits through mail, virus, malware, Trojan horses and distributed denial-of-service programs are unfortunately going to be with us for a long time, the fastest-growing area for new exploits is through Web interfaces.

Almost every company has some type of Web presence — ranging from simple brochure sites to sophisticated transaction-oriented applications — and therefore has some type of conduit from the general Internet to company resources and or company data.

Everybody allows a variety of Web protocols and programs directly through their firewalls and routers. Because you cannot stop this traffic from coming through your barrier systems, you have to do an outstanding job of creating an environment that detects malicious attempts that you cannot prevent and prevents as many different types of exploits as possible. To do this, several areas need to be addressed, each in its own way.

A Web environment consists of three main parts:


Not having a security architecture
Not investing in training
Neglecting identity management
Ignoring the insider threat
Buying products with the most bells and whistles


  • The host that the Web services run on.
  • The supporting Web server infrastructure.
  • The Web application itself.

It is important to understand that these components are independent of each other and that effective Web security depends on getting each of them right. Failure of one part could may mean failure of the system as a whole.

For example, a company may have done a good job deploying a minimally configured and well-hardened host and have a well-configured Web server, but if it has a Web application designed using poor assumptions about authentication, authorization or session management, the system as a whole is vulnerable.

To achieve a robust Web presence, you need to look at each of these three areas and perform the testing and remediation measures each requires.