Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

A test copy of production: masking data, isolating the network and licence questions

Technical article
Hosting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A copy of your live servers is a realistic place to test an upgrade, and also the easiest way to create a second, weaker copy of everything you are responsible for. Before the copy is switched on, write a change list: keep it off the live network and away from the internet, stop it sending email or talking to outside services, decide whether personal data must be masked or the copy secured like the original, and confirm what licences the copy needs.

Why it matters

A clone starts life believing it is the live system. Left unchanged, it can send invoices to real customers, run scheduled jobs against live services, or clash with the original on the network. The data is also a concern: a test copy can end up with fewer protections and more people with access than the live system, yet holds the same records.

How it works

The copy needs the same protection, or less data

The Australian Government's Information Security Manual (ISM) sets two controls that a business can use as a benchmark. Control ISM-0400 says: "Development, testing, staging and production environments are segregated." Control ISM-1420 says: "Data from production environments is not used in non-production environments unless the non-production environment is secured to at least the same level as the production environment."

That leaves two honest choices: protect the test copy as well as the live system, or reduce what it holds by masking or removing personal and sensitive data. The ISM is written for government systems, and these controls sit in its chapter on software development, written for organisations building software; a business applying them to a test copy is using them by analogy, as a useful reference rather than a legal requirement in itself.

For businesses covered by the Privacy Act, the Office of the Australian Information Commissioner's guidance on Australian Privacy Principle 11 says an organisation "must take such steps as are reasonable in the circumstances to protect the personal information it holds from misuse, interference and loss, as well as unauthorised access, modification or disclosure". A test copy is information the business holds, so in our reading it falls under the same duty. Whether the Act covers your business, and what is reasonable for your copy, are questions for your privacy adviser.

Identity on the network

Each Windows installation carries identifying details. Microsoft's Sysprep guidance explains that generalising an image "removes computer-specific information such as installed drivers and the computer security identifier (SID)". A test copy restored from backup is not generalised: unless someone changes them, it keeps the original's computer name, network settings and domain membership, so on the same network as the live servers it can clash with them: two machines answering to one name or address, and the copy using the live server's computer account in the domain. A separate, isolated test network avoids this without altering the copy.

What the copy can reach

Scheduled tasks, mail relays, payment and banking links, cloud services and supplier connections were all set up for the live system. In the copy, each one is a way for a test action to have a real effect.

What to choose and why

The change list, before power-on

Item Change in the test copy
Network Connect only to an isolated test network; no route to live servers
Internet and email Block outbound mail and external services unless a test needs one, then point it at a test endpoint
Scheduled jobs Disable jobs that send, pay, sync or export
Personal data Mask or remove, or secure the copy to the live system's level
Accounts and access Limit who can sign in; record who had access and when
Licences Confirm what the copy needs before it runs
End date Set a date to delete the copy

The table is editorial guidance drawn from the controls above. Settings in the copy that point at real services are application-specific; ask your application vendor which ones to change.

Masking choices

Masking, as used here, means permanently replacing real names, addresses, phone numbers, tax file numbers and bank details in the copy with realistic but fake values, keeping formats so the application still works. Some application vendors provide a script for their own product; ask yours. In our view the masking must happen before testers get access, and the unmasked copy used to produce it must be deleted afterwards.

Not every feature called masking does this. Microsoft's SQL Server dynamic data masking, for example, hides values in query results for users without the right permission, but Microsoft states that "the data in the database isn't changed" and that it "doesn't aim to prevent database users from connecting directly to the database and running exhaustive queries that expose pieces of the sensitive data". A copy protected only that way still holds the real records, so treat it as unmasked and secure it like the live system. Before relying on any masking tool, ask the vendor whether it changes the stored data or only what users see. Replaced values can still identify people when combined, such as a rare job title with a postcode; our companion article on training data without exposing live customer records covers de-identification in more depth.

Licences

Licensing rules for test systems vary by product. One example: Microsoft describes SQL Server Developer edition as including Enterprise features "but is licensed for use as a development and test system, not as a production server". That helps where the test copy can run on Developer edition, but Developer edition's licence terms also limit who may use it and for what, so check them before staff test with it, for example in user acceptance testing. It does not cover Windows Server, remote desktop or the business application itself. Check each product's terms with your licence provider or vendor.

Illustrative example

A 35-person firm wants to test its practice-management upgrade. Its IT provider restores last night's backup into an isolated test network with no internet route, disables the outbound email and bank-feed jobs, runs the vendor's masking script, and gives access to two staff testers for ten days. The vendor confirms the test licence. After sign-off, the copy is deleted and the deletion recorded. The example is illustrative.

Risks and limits

  • Masking can break tests. Some faults appear only with real data; agree in advance how those are investigated, under live-level protection.
  • Isolation can be partial. A shared management network or a forgotten firewall rule can reconnect a test copy; check routes before power-on.
  • Copies outlive their purpose. Without an end date, test copies accumulate, each holding old data.
  • Privacy and licence terms are beyond this article. They differ by organisation and product; take advice for your situation.

Sources

Opened 15 November 2026; the OAIC APP 11 guidance (archive copy of 17 October 2026) and the SQL Server dynamic data masking page opened 16 November 2026.

Related service: Cloud hosting.

Learning notes

  • A test copy is a second copy of everything: secure it like the original or reduce what it holds.
  • ISM-1420: production data stays out of non-production unless secured to the same level.
  • A restored copy keeps the original's name and domain membership; run it on an isolated network.
  • Disable outbound email and jobs that send, pay, sync or export before power-on.
  • Some "masking" only hides values on screen; a copy whose stored data is unchanged must be secured like the live system.
  • Licence terms for test systems vary by product; confirm each before the copy runs.