Test data | 31
on production performance. and are not subject to testing by the
The main secure methods of test department.
scrambling are: Database structures tend to
•
Extract the data through scrambling change regularly and the scrambling
functions either on a live copy functionality needs to be upgraded
of production or preferably a with each release. After a while
reporting copy. the scrambling routines tend to
•
Build a set of views that use be forgotten. In an attempt to be
scrambling functions to mask the more systematic, the use of tools
data. Data will be extracted through can be helpful as well as turning
these views. The access to these the scrambling task into a normal
views can be granted using normal IT project. The scrambling project
database security. As an indicator would be subject to the infrastructure,
the initial data retrieval through the testing and control used in your
views is usually 5 to 10 times slower normal development lifecycle. The
than against a native table. benefits of this are:
•
Create a secure environment
•
Traceability – extremely important
and take a copy of production if data loss occurs.
data, update the data in situ
•
The scrambling tends to be more
and when complete copy this to thorough and more useful to testing
development. The same functions teams.
outlined in this paper can be used in
•
Scrambling for new releases of
update scripts to scramble the data software is automatically upgraded
in situ. as part of the normal life cycle.
The first consideration
Ad hoc or systematic? Know your data
It is very easy to write a few scripts, Before beginning a scrambling project
when designing a
change a few customer names or alter you will need to understand your data.
scrambling architecture
a few characters of an account ID, but A request from management may is where you want to
there are problems with this approach. be as simple as “make sure no one
physically scramble the
The scripts tend to fall outside normal can recognise a customer”; however,
data. Is it good enough to
programming control and are written understanding what a customer
in SQL and non standard languages consists of is the first task before you
copy production, move it
such as PERL. They may well be perfect can begin scrambling. To begin building into development, run a
but tend not to be documented, not up a picture, you will need to gather
few scripts and off you go?
incorporated in source control systems all of the available ‘free’ information
T.E.S.T | March 09 March 09 | T.E.S.T
Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52