Applying privacy principles to a software development scenario

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. A dev team copies 5,000 real customer records into the testing environment so testers have realistic data. What is the first step in applying a privacy principle?

A Identify the personal information involved (names, emails, addresses in the records)

B Decide the fine the organisation will pay before looking at the data

2. A school app team uses real student records in the test environment, which has weak access controls. Does this practice meet the security principle (APP 11 / IPP 4)?

A Yes. Test environments are not covered by privacy principles, so security does not matter

B No. Personal information must be protected from misuse, loss and unauthorised access, and the test environment is poorly secured

3. Which is the best way to meet privacy requirements when testing a new feature?

A Use fake or de-identified data in the test environment

B Copy the live customer database into testing so the data looks real

4. A company outsources development to an overseas firm and sends it a database of Australian customers' personal details. Which principle must the company consider?

A APP 8 / IPP 9: it must take reasonable steps to make sure the overseas recipient protects the information

B None. Once the data leaves Australia, the company has no privacy responsibilities

5. An outsourced developer is given full access to the live customer database when they only need a few fields. Judge this practice against the security principle.

A It meets the principle because the developer is a trusted external professional

B It does not meet the principle. Access should be limited to what is needed, and the data protected

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left column		Right column
1Step 1: Identify the personal information		AuploadCustomerFile(overseasDeveloper);
2Step 3: Judge whether the practice meets it		BINSERT INTO testDb SELECT * FROM prodCustomers;
3Real customer data copied into a test environment may breach the requirement to protect personal information, so the practice should be judged as not meeting the principle.		CCompare what the organisation actually does with what the principle requires, then conclude that it complies or does not, with evidence from the scenario.
4Sending personal information to an outsourced developer overseas requires the organisation to take reasonable steps to make sure the recipient protects it.		DFind the data in the scenario that identifies a person, such as names, emails, addresses or health records, before any principle is applied.
5Scenario judgement: The app stores names and emails in plain text, so it meets the security principle.		EStoring personal information unencrypted does not take reasonable steps to protect it. The practice fails the principle and the data should be encrypted at rest.
6Scenario judgement: Breaking a privacy principle has no legal consequences if no one complains.		FNon-compliance can bring investigation, penalties, fines and reputational damage, even without a complaint. The organisation must still meet the principle.

Definitions

Apply a privacy principle

Fill in the Blanks

Complete each line of code by filling in the missing parts.

IF testData = "real customer data" THEN meetsPrinciple ← _____ END IF

IF isOverseas ___ noSafeguards THEN meetsPrinciple ← FALSE END IF

IF _________ = TRUE THEN meetsPrinciple ← TRUE END IF

IF meetsPrinciple THEN OUTPUT "Compliant" ____ OUTPUT "Risk of OAIC penalty"

personalInfo ← identify(scenario) requirement ← statePrinciple(principle) result ← _____(practice, requirement)

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A info ← button colours

B principle ← APP 11 security

C IF test uses real data

D verdict ← not met

Question 2

A info ← student health records

B principle ← APP 11 security

C IF stored encrypted

D verdict ← not met

Question 3

A info ← customer phone numbers

B principle ← APP 8 overseas

C IF vendor is in Melbourne

D check recipient protections

Question 4

A info ← patient names and DOB

B principle ← IPP 4 security

C IF no access controls

D verdict ← met

Question 5

A info ← customer addresses

B IF principle not met

C risk ← no consequences

D recommend ← fix practice

Answer Key

Applying privacy principles to a software development scenario

Section A: Quick Questions

A — Identify the personal information involved (names, emails, addresses in the records)

B — No. Personal information must be protected from misuse, loss and unauthorised access, and the test environment is poorly secured

A — Use fake or de-identified data in the test environment

A — APP 8 / IPP 9: it must take reasonable steps to make sure the overseas recipient protects the information

B — It does not meet the principle. Access should be limited to what is needed, and the data protected

Section B: Match the Pairs

Step 1: Identify the personal information → Find the data in the scenario that identifies a person, such as names, emails, addresses or health records, before any principle is applied.

Step 3: Judge whether the practice meets it → Compare what the organisation actually does with what the principle requires, then conclude that it complies or does not, with evidence from the scenario.

Real customer data copied into a test environment may breach the requirement to protect personal information, so the practice should be judged as not meeting the principle. → INSERT INTO testDb SELECT * FROM prodCustomers;

Sending personal information to an outsourced developer overseas requires the organisation to take reasonable steps to make sure the recipient protects it. → uploadCustomerFile(overseasDeveloper);

Scenario judgement: The app stores names and emails in plain text, so it meets the security principle. → Storing personal information unencrypted does not take reasonable steps to protect it. The practice fails the principle and the data should be encrypted at rest.

Scenario judgement: Breaking a privacy principle has no legal consequences if no one complains. → Non-compliance can bring investigation, penalties, fines and reputational damage, even without a complaint. The organisation must still meet the principle.

Section C: Definitions

Apply a privacy principle — Identify the personal information involved, state what the principle requires, then judge whether the organisation's development practice meets it.

Section D: Fill in the Blanks

IF testData = "real customer data" THEN
  meetsPrinciple ← FALSE
END IF

IF isOverseas AND noSafeguards THEN
  meetsPrinciple ← FALSE
END IF

IF encrypted = TRUE THEN
  meetsPrinciple ← TRUE
END IF

IF meetsPrinciple THEN OUTPUT "Compliant"
ELSE OUTPUT "Risk of OAIC penalty"

personalInfo ← identify(scenario)
requirement ← statePrinciple(principle)
result ← judge(practice, requirement)

Section E: Spot the Error

A — The first step is to identify the personal information involved. Button colours are not personal information. It should name the real data, such as 'names and emails'.

C — Stored data is a problem under APP 11 when it is NOT encrypted. Encryption helps meet the principle, so the condition should be 'IF stored unencrypted'.

C — APP 8 applies when personal information is sent to an overseas recipient. A local vendor does not trigger it, so the condition should be 'IF vendor is offshore'.

D — With no access controls, the organisation has not taken reasonable steps to protect the data. The judgement should be 'not met', not 'met'.

C — Failing to comply with a privacy principle can lead to complaints, fines, legal action and reputational damage. 'No consequences' is wrong.