Auditing an Oracle database for security issues is very important. PeteFinnigan.com provides all of the information and tools that you will need Click here for details of PeteFinnigan.com Limited's detailed Oracle database security audit service Click here for details of PeteFinnigan.com Limited's Oracle Security Training Courses
There are 41 visitors online    

Pete Finnigan's Oracle security weblog


Home » Archives » July 2005 » Paying a ransom to read your data

[Previous entry: "Is it possible to check whether Oracles CPU update emails are *real*?"] [Next entry: "European software patents have been ditched"]

Paying a ransom to read your data

July 8th, 2005 by Pete

Post to del.icio.us   Post to Furl   Digg!

I saw an interesting short article in the Computer Active magazine today about some research done by a company Websense Security Labs. The article said that a new hacker trend had started where by a hacker gains access to a persons PC via a worm, virus or bug ( in this case it was a bug in IE) and installs some software that encrypts a certain set of files on the unfortunate persons PC, the deletes the originals. Then the hacker leaves a note that says pay a sum of money - a few hundred dollars - and he (the hacker) will send a program that allows the unfortunate persons files to be restored.

The article is a very interesting one. I have no idea how wide spread or not this type of attack is or if it will grow in occurrences. The attack described is aimed at PC's but could move to other areas such as databases, even Oracle databases. What if an attacker, hacker, malicious employee or criminal decided to deprive your company of its data? OK, its not absolutely trivial but he could quite easily encrypt key tables / columns with built in packages such as DBMS_OBFUSCATION or DBMS_CRYPTO and then ask you for money or other goods to be supplied with the key used and also the algorithm used. What can you do to prevent such a situation? A situation like this would never be totally preventable as it could be done by someone with admin access but it is prudent to ban PUBLIC access to these packages and any other encryption routines held in the database. Use audit to know who has done what and when. In 10g Release 2 ensure that no one can add transparent encryption to any critical columns of data. Perform a security audit on your databases or get someone like me in to do it for you and then secure the database.

July 2005
SMTWTFS
     12
3456789
10111213141516
17181920212223
24252627282930
31      

This is the weblog for Pete Finnigan. Pete works in the area of Oracle security and he specialises in auditing Oracle databases for security issues. This weblog is aimed squarely at those interested in the security of their Oracle databases.

Weblog Home
Weblog Archives

Oracle Security Step-by-Step (Version 2.0)

Home
Oracle Security Tools page
Oracle security papers
Oracle Security alerts

Web Development
SQL Server Security

RSS 1.0 FEED
RSS 2.0 FEED
Atom 0.3 FEED
Powered by gm-rss 2.0.0




View Pete Finnigan's profile on LinkedIn

Pete Finnigan

Create Your Badge



Valid XHTML 1.0!