Information Commissioners View on using Personal data for system testing
by Dale on Feb.05, 2010, under InfoSec
Following on from my recent post on “Doing the right thing when testing with production data“, I was discussing my frustation with a colleage at work and they told me to take a look at a copy of the the “Data Protection: Guidelines for the Use of Personal Data in System Testing” document. We had an old copy, and this is a statement from the ICO, in 2003 I believe. There is an updated 2009 version, but I dont have access to this, so I am unable to comment. Either way its a useful snip it to share with everyone.
The Information Commissioner’s view
The ICO advises that the use of personal data for system testing should be avoided. Where there is no practical alternative to using ‘live’ data for this purpose,
systems administrators should develop alternative methods of carrying out system testing. Should the Information Commissioner receive a complaint about
the use of personal data for system testing, his first question to the data controller would be to ask why no alternative to the use of ‘live’ data had been found.
Key risks in system testing There are a number of general risks that exist whenever system testing is undertaken using live data and/or a live environment.
These are as follows:
• unauthorized access to data;
• unauthorized disclosure of data;
• intentional corruption of data;
• unintentional corruption of data;
• compromise of source system data where appropriate;
• loss of data;
• inadequacy of data;
• objections from customers.
There will of course also be sector-specific risks peculiar to each individual business, each type of business and each particular system.
Before commencing any system testing, it is advisable for the data controller to undertake a risk assessment identifying the nature of the risks that apply, their
possible impact and planned handling strategies.
A cautionary tale
The view is sometimes expressed that system testing poses no real data protection problem, as it takes place all the time with little apparent detriment
to individuals. The following case study, which is based on a true complaint received by the Information Commissioner’s Office, shows that the use of ‘live’
data to test systems can indeed cause very real problems for individuals. A pupil was away from home at boarding school. The pupil’s parents received a
letter from the local hospital informing them that their daughter had been involved in a road accident. In fact, there had been no accident, but the hospital
had been using live patient data to test a system for sending out letters to patients.
UK Organisations still struggling with PCI:DSS Compliance… Time for fines?
by Dale on Feb.02, 2010, under InfoSec
Apparently only 9% of the UK’s level 1 retailers are confirmed as being PCI:DSS compliant, and most of these are virtual retailers, who most likely have a slightly easier task at becoming and demonstrating compliance.
So with the fact that organisations still seem to be lacking, VISA and MasterCard are apparently taking steps to up their game and apply some more pressure / persuasion. I know what your thinking, most likely the same as me. We have heard it all before, and with disclosure being the way it is we dont get to hear about it anyway.
So what does this mean. Well the fines are starting to flow, many organisations are being fined (apparently a little under half a million a month), as well as taking steps to prevent acquirer hopping which is common if an organisation is getting to much hassle, they simply jump ship to another. Now if organisations are suspected of doing this to dodge regulation they are effectively black listed.
Of course I cant prove this is happening, same as no one else can because disclosure laws dont allow for it, and companies are not going to be actively publishing this on their sites, and customers I have worked with obviously share information under NDA.
All you can be sure of is the fact that companies are making progress, but its slow and non impressive, and obviously isnt a big enough priority. To provide encouragement fines are and will continue to be handed out, and they will be increasing. It can sometimes be hard to find out about the fines, so here is the current schedule of fines, correct on 2nd Feb 2010.
Fines are represented in US Dollar and Euro respectively
MasterCard fines for non compliance are:
Level 1 & 2 Merchants
- First Violation – Assessment Amount: Up to 25,000
- Second Violation – Assessment Amount: Up to 50,000
- Third Violation – Assessment Amount: Up to 100,000
- Fourth Violation – Assessment Amount: Up to 200,000
Level 3 Merchants
- First Violation – Assessment Amount: Up to 10,000
- Second Violation – Assessment Amount: Up to 20,000
- Third Violation – Assessment Amount: Up to 40,000
- Fourth Violation – Assessment Amount: Up to 80,000
Visa expects level 1, 2 and 3 merchants to demonstrate that they are actively engaged in the programme to become compliant. A merchant will not be at risk from Visa fines for non-compliance if they are compliant with milestones 1-4 of the Prioritised Approach
Do the right thing when testing with production data
by Dale on Feb.01, 2010, under InfoSec
I thought I would write a post about organisations not doing the right thing (in my opinion) when they are using production data for carrying out testing. Perhaps I am alone on this one, and I would appreciate any feedback and opinions in the forms of comment.
Now when I talk about production data, I am talking about data that could be considered personal or sensitive data. This could be credit card information, bank details, national insurance number, address, date of birth, medical records, sexual preference, etc. All of this data would be considered highly valuable to a criminal / fraudster, and as a result should be considered a significant business risk, not to mention the compliance implications regardless of the industry the organisations operate in.
So with this in mind, why is it that so many organisations seem to think that serious consideration doesn’t need to given when it comes to the protection of data when its comes to using production data in a testing environment. Now I fully understand the value of using production data, and the possibly improved quality of testing that can be achieved, however this data shouldn’t be used as is. This data should be removed and sanitised to make it anonymous / de-personalised. This ensures that should the data be compromised, or not cleaned down appropriately or migrated into production this is no real world impact. Also I think we all know that test environments are not often a full representation of a production environment, especially when it comes to security controls.
I have seen this happen in organisations and it can have a real impact on an individual. Put yourself in this situation. Perhaps an organisation who offers health insurance is testing a new premiums engine. They use production data, and kick off testing, changing various parameters, including illness information, and decide to test the impact of having a sexually transmitted disease. Testing then completes, and by some error information is migrated back into production. Next thing the customers knows is they receive a letter saying they can no longer be offered insurance due to being a sufferer of HIV. This information will have been linked with other databases of other organisations, and the domino’s begin to topple.
When we think how something might impact us as an individual we tend to take a little more ownership and care, and I think this is something lacking in alot of organisations. I am not saying creating test data or converting production data for testing purposes is a trivial process, but that doesn’t mean its something that shouldn’t be done. There are various tools and scripts available to do the necessary to production data, and some companies also offer off the shelf test data that may be appropriate.
So next time your involved in testing, make sure you do the right thing. Understand what the goal of testing is, and what the results might look like. Review the data sets that are relevant and the risks and exposures may bring. Then as appropriate do what is needed to mask, scramble, randomise and de-personalise the data. During testing ensure access levels are appropriate, and the necessary logging is in place. Then when all the testing is completed, follow the appropriate steps to clear down the environment ready for next time.
Ideally all this would be clearly defined in security and testing policies and processes, but regardless you will know you are doing the right thing, and this will also help greatly with meeting compliance and regulatory controls. Its probably not considered that this occurs from a consumer level, but doing the right thing could also be considered a marketing benefit.
So rant over, maybe you agree, maybe you don’t, but I would be interested in your comments.
Internet Explorer Zero Day Patch
by Dale on Jan.21, 2010, under InfoSec
Microsoft has announced that today (21-01-2010) at approximately 6pm (UK time), it will release an emergency out-of band patch to fix the Internet Explorer zero day security vulnerability that has been used by attackers in various high-profile targeted attacks, specifically the recent Trojan.Hydraq attacks waged against Google and a number of other companies. The vulnerability affects Internet Explorer 6, 7 and 8, which make up the bulk of the versions used today. However, the only in-the-wild exploit code for this vulnerability detected thus far is confirmed to affect just Internet Explorer 6.
Keep an eye on the Microsoft Security Site for more information.
Also check out the Mircrosoft Advisory on this matter (979352).
Here is the patch MS10-002
Secure USB Devices Vulnerable – Lists here…
by Dale on Jan.19, 2010, under Encryption, InfoSec
This information might be about a week old now, but seeing as I have been going over the Enterprise and Personal offerings from Ironkey, I thought I would briefly touch on this newly found vulnerability, and what devices are currently known to be vulnerable.
So late Dec 2009 SySS produced a couple of papers detailing how they have managed to bypass the security on Sandisk and Kingston Secure USB storage devices. Basically they have designed a tool that produces a static unlock code to always unlock the affected devices. Its my understanding that this is possible due to a flaw in how the users passcode is verified on the PC and signaled to the device.
This is obviously a significant issue, and I know personally of many organisations that have deployed these devices in their organisations, and this will also include Government organisations as most of the devices are classified as FIPS 140-2 compliant.
So should you be worried, well yes if your using one of the following devices:
- SanDisk Cruzer Enterprise FIPS Edition USB flash drive, CZ32 – 1GB, 2GB, 4GB, 8GB
- Verbatim Corporate Secure FIPS Edition USB Flash Drives 1GB, 2GB, 4GB, 8GB
- SanDisk Cruzer Enterprise with McAfee USB flash drive, CZ38 – 1GB, 2GB, 4GB, 8GB
- SanDisk Cruzer Enterprise USB flash drive, CZ22 – 1GB, 2GB, 4GB, 8GB
- SanDisk Cruzer Enterprise FIPS Edition with McAfee USB flash drive, CZ46 – 1GB
- Kingston DataTraveler BlackBox (DTBB)
- Kingston DataTraveler Secure – Privacy Edition (DTSP)
- Verbatim Corporate Secure USB Flash Drive 1GB, 2GB, 4GB, 8GB
- Kingston DataTraveler Elite – Privacy Edition (DTEP)
As I was looking at Ironkey devices at the time of all these, I have had confirmation from Ironkey that as far as they are aware they are not susceptible to this type of vulnerability due to the architecture used in their devices, and the fact that all verification occurs at the onboard hardware level.
Ironkey S200 Personal Review
by Dale on Jan.18, 2010, under Encryption, InfoSec, Reviews, Security Active
I don’t wont to go over to much of what has already been covered by the Enterprise Review from last week. The main focus of this review is to demonstrate that you don’t have to be part of a large organisation to benefit from what the Ironkey has to offer, as the personal versions are great to. As I previously said I have been using Ironkeys for a while myself and these are personal devices.
Below will be a brief recap of what the Ironkey Personal is all about and how you go from opening the box, to secure storage and browsing.
Personal Version Specs:
Rugged Metal Casing
Waterproof
Tamper-Resistant
AES 256BIT Hardware Encryption
FIPS Validated 140-2 Level 3
Strong Authentication
Secure Browser / Portable Apps
Secure Password Management
Self Service Password Recovery
So you have just got your hands on your nice new shiny S200 Ironkey personal, you have popped open the nicely designed black box and popped it into your USB slot. The first step is to initialise your key.
Its important to give your Ironkey an appropriate name, so that you can easily identify it in your personal online console, because your going to want more than one at some point. The next one is to obviously select a strong passphrase. It might be AES256 bit encrypted, but using the password “password” isnt going to be that secure.
The part it to read through and accept or reject the T’s and C’s.
Once thats all out of the way the Ironkey will start doing its thing, encryption, configuring and installing.
As with the enterprise version, you need somewhere to keep track of your keys, backup your password for recovery, etc etc. So now you need to create online account, or if like me add your Ironkey to your existing account.

Now your account is setup, Ironkey will send you an email with an activation code. You will need to enter this into your online account, to setup and confirm association with your account and your Ironkey.
Now your good to go. You should find that the Ironkey control panel has also launched, and this gives you access to the various pre-installed application and services. Secure Firefox browser, password managers, update manager and more.
You will also notice there is an option to fill in some Lost and Found information. This is then displayed to anyone who inserts and attempts to activate the Ironkey. They can then contact you to make you aware of how foolish you were to lose your precious key
So thats pretty much you good to go. However I will add one thing, that seems to be very unclear when your looking around online. People seem to think for some reason you are unable to install new applications onto your Personal Ironkey. Well of course you can. I will quickly go through how to install Pidgin, and other applications should be the same.
First off head along to Portable Apps, and get yourself a copy of Pidgin.
You then simply install this to the secure files location on your Ironkey. Then from your Ironkey control panel right click on the applications screen and select add application.
Now select the Pidgin Executable in your secure storage location. Then Bob’s your uncle you have Pidgin good to go.
I hope this review was information and helpful to a few of you. For more information on Ironkey and where to buy one check out their website.
The Real Hustler Blogging – Paul Wilson
by Dale on Jan.18, 2010, under Blogging, InfoSec
I first found out about Paul’s work on the TV show in the UK “The Real Hustle”. They carry out some excellent cons on this show and explain how this goes down. Paul does some awesome slight of hand work, and I really admire his knowledge. Its great to see Paul has decided to set up a blog, and hopefully share some of his insight further with the rest of us.
- Paul Wilson
- A world renowned expert on cheating and con games, Paul is writer/presenter of hit BBC show The Real Hustle. He is also the co-creator, producer and star of Court TV’s “The Takedown” and has pulled more cons than anyone in history.
Ironkey S200 Enterprise Review
by Dale on Jan.14, 2010, under Encryption, InfoSec, Reviews, Security Active
I am a probably a little biased, as I have been using a personal Ironkey 1GB S100 for some time now, and have recently got myself an 8GB S200 thanks to Don at The Ethical Hacker Network, so its clear I think they rock, and in my opinion I really do think they are the best secure USB Pen Drive on the market.
However I have never had any exposure to their enterprise offering, and with lots of companies now looking to adopt secure portable / removable media I think if Ironkey could be a good solution from a device perspective to help with data loss prevention. Ironkey have been kind enough to set me up with a temporary enterprise account, and sent me a couple of enterprise S200 1GB sticks to have a look how it all hangs together.
Before I get started, if you have never heard of Ironkey, let me just give you a little bit of info on what they are all about, and why in my opinion they are the 007 secure usb stick of choice, did I mention they look the business to
Enterprise Version Specs:
Rugged Metal Casing
Waterproof
Tamper-Resistant
AES 256BIT Hardware Encryption
FIPS Validated 140-2 Level 3
Strong Authentication
RSA SecureID / Verisign ID Protection
Secure Browser / Portable Apps
Self Destruction
Anti-Malware Protection
So on with the review. First we need an Ironkey Enterprise Account, and an Enterprise Ironkey, I was provided with both of these. When you get an Ironkey it comes in a little black box, once you have opened it up and plugged in the Enterprise Ironkey and the launcher is run, you are informed that you need to activate your Ironkey. (*Setup on a Mac)
To progress past this stage you will need an activation code that your Ironkey Enterprise would have setup for you through the console. This will result in you having received an email with your activation code.
So with that in mind we will go to the Enterprise Web Interface and get things setup (policies, preferences and accounts).
First we log in with our Enterprise Account number.
Now as its our first login we need to go through the 10 steps of getting our configuration setup that we are going to apply to all the Ironkeys in our enterprise.
Step 1 – Make sure we are the right man for the job…. Check ![]()

Step 2 – Now we need to define how many failed password attempts before the Ironkey self destructs. (Default is 10)
Its important to remember once destruction occurs, thats it. No undo or try again.

Step 3 – Now we define our password settings, complexity, and recovery settings.

Step 4 – Now we setup the default applications available from the Ironkeys, Firefox, RSA, etc

Step 5 – Its all about the Lost & Found. We can configure a message that will seen by anyone who inserts the Ironkey

Step 6 – Now we setup the Enterprise Administrator Account, with a strong password.

Step 7 – Time for some challenge response info, for when we forget ourselves.

Step 8 – Now to create your secret identification image to ensure your at the REAL Ironkey admin page.

Step 9 – Creating your backup sys admin account.

Step 10 – Confirming everything is just how you wanted it.

So now we have our admin account setup and our admin Ironkey associated. So lets take a look at what we can do at the web interface. Its important to understand that logging into your management interface requires two factor authentication, so not only your username and password, but your Ironkey also. If you dont have your Ironkey you just get into the Safe Mode option.
So when we login with the Ironkey we get all the good stuff, user management, policy creation alteration, alerts, log information and more. Things are pretty self explanatory, so here is a screen shot montage.
Now we can continue to activate our Ironkey, as we have created an account, and associate policy.
Now we setup a name for our Ironkey and a strong passphrase.

The key is then initialised and encrypted.

Then then if the user doesnt already have an online account, they are prompted to create one.

Now the user is good to go, the policy will have been applied, applications made available and secure storage created.
If the user is also an administrator they get access to admin tools from their Ironkey also, allowing them to recover data from other Ironkey, reauthorise, etc.

Below are also some screen shots of an Ironkey that has been assigned a Silver Bullet Policy meaning it cannot be used unless it is connected to the Internet for authentication, and a device that has been disabled.


Here is the control panel a user see’s on a Mac and PC, do control panel is currently available to Linux users.


Its pretty clear that PC users currently get better percs from the Ironkey, but regardless of the plaform your getting some awesome secure storage. I am really impressed with the simple yet appropriate level of control the Ironkey Enterprise solution gives, and I dont think I would hesitate to recommend this to a customer. I will say that I had one device get stuck in some sort of authentication loop, but Ironkey support where extremely helpful, and the few things we tried didn’t work so they sent out a replacement by Fedex.
Ironkey also offer pretty much the same offering but for personal users, and I will be putting up a similar mini review of this offering later in the month.
For more information on the Ironkey offerings, and to locate your local reseller visit the Ironkey website.
I will leave you with a short video clip I made, testing the waterproof theory of the Ironkey S200.
Waterproof Testing
Data Protection Act related breach… £500,000 fine!!
by Dale on Jan.12, 2010, under InfoSec
I have spoken before about the Information Commissioners Office getting new powers from April 2010. Well now it has been confirmed that they will now have the power to issue fines upto £500,000 to organisations suffering a security breach in relation to the Data Protection Act 1998.
Personally I think its good they are getting some more teeth that they can use to hopefully get organisations to start taking the DPA a little more seriously. I wonder how soon we will here about this happening with current disclosure laws.
I think we will see similar trends coming in relation to regulation and compliance in 2010, this could be an interesting year.
BackTrack 4 Final Released … woop woop
by Dale on Jan.12, 2010, under InfoSec
Its official, on the 9th Jan 2010 BackTrack 4 Final has been released, which is excellent news for everyone who knows just how good the BackTrack distro’s are.
With this release includes a new kernel, a larger and expanded toolset repository, custom tools that you can only find on BackTrack, and more importantly, fixes to all (well, most..) major bugs that we knew of. This release we received an overwhelming support from the community and we are grateful to everyone that has contributed to the success of this release.
So what are you waiting for, download it now.

Looking for something?
Use the form below to search the site:
Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!
Visit our friends!
A few highly recommended friends...
Archives
All entries, chronologically...



























