International Developer Logo Last Updated 25.07.08 at 11.48
On Sale
This months front cover, click to see the table of contents.
Subscribe
Powered by SEEK
Keywords (optional)
 
RESOURCES

Database Security Best Practices: Implementing the Missing Piece


  03.10.06

Management and practitioners are consistently caught off guard with ever increasing security infringements. The fact that data privacy violations are increasing is due to three primary reasons. First, hackers are becoming more sophisticated and more resourceful. Second, management is not always aware of the factors that will govern and establish viable security policies ensuring data security. Third, practitioners lack knowledge on a variety of security mechanisms available to them, this is necessary to protect data, apply best practices and implement security solutions.

Whether it is the apparent increase in data theft incidents or the stricter regulatory environment, companies are worried about how they house their data. On the regulatory side, congress began passing acts that had significant information impact with the Health Insurance Portability and Accountability Act (HIPPA) in 1996 followed by the Gramm-Leach-Bliley Act (GLBA) in 1999 and the Sarbanes-Oxley Act (SOX) in November 2002. These acts were in response to the rise data privacy violations, malicious code, identity theft. But the events that flamed these provisions were the financial fraudulent acts of WorldCom, Enron, and Tyco top executives. Prior to SOX, data privacy or data security wasn’t the highest priority or concern for database managers, administrators and developers.

 

Download PDF Article





HAVE YOUR SAY
This article is rated  Rate this article 
 
Editors Letter
Picture of the Editor  
Alphabet Street 

Each month we try our hardest to cover every angle and aspect of software engineering. Indeed, we pride ourselves on our platform-agnostic wide ranging view of the development landscape. How then could we push ourselves even further and really broaden the spectrum of our editorial coverage? The answer had to be – the complete A to Z of software. Well, not complete, but a rip roaring twenty-six letter technology tour to provoke some interest and thoughts in areas you might not normally think about.

But first, a personal confession so that you know how all this started. I actually got the idea from reading a cookery magazine that had done something similar. You know the kind of thing – A for apples, B for bread, C for custard and so on. But those pesky food journalists have it easy don’t they? When they get to X, Y and Z they can just use X for Xérès Sherry, Y for Yeast and even Z for Zabaglione.

Now, X is simple enough with plenty of XMLs out there, Z for zero tolerance we reckoned, but Y, wow - now that is a hard one.

So, please dive in and jump to your favourite letter. It was always going to be the case that we would miss out on a few key areas, but we think it’s pretty cool to be able to work your way through the whole alphabet and just stay within the world of software development. Next month, 1001 aspects of application development and how you can implement them in your daily working schedule. Joke – ok?

Happy coding!

Adrian Bridgwater

Editor

Write to the Editor