Requires Free Membership to View
When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.
Hannah Smalltree, Editorial Director
The possibilities are endless depending on which perspective you're looking at things from. You might have high utilization on the server's network card or the backend database. You might see numerous locked accounts that occurred as the result of a password cracking attempt. Your Web server and application log files may point to abuse in the form of repeat requests and non-standard requests. Or, you may be notified by a customer, a business partner or a law enforcement that something has gone awry. This is why getting all the right people on board with security and monitoring for the things that matter is so important.
I've written a number of tips on how to prevent software hacker's malicious attempts, here are some that come to mind:
- Identifying whether or not your site or software has been hacked
- Retaking command of your hacked software
- Spotting rich Internet application security flaws with WebGoat
- If all else fails look in the Web 2.0 application security troubleshooting, testing tutorial which should have just about any information pertaining to software and application security you could need.
I have always been of the opinion that "the best offense is a good defense," especially when it comes to computers and software. Retaking control of hacked systems and software is naturally an uphill battle and one that can't always be won. Whereas proper security steps in the beginning can win the war for you before your enemies even strike.
This was first published in October 2009