Education cyber security: where student and family data moves, and how to test each step
For school business managers, IT leads and the edtech suppliers that serve schools.
This guide follows applications, enrolment, guardian messages, learning portals, student uploads, excursions and the outside services behind them, keeps school-operated sites apart from supplier platforms and guardian access apart from staff access, and comes with a workflow test matrix to run on your own systems with invented students, guardians, teachers, office staff and suppliers.
On this page
Education workflow test matrix for school sites, edtech platforms and ST4S evidence
An illustration, not a school or supplier: every account, student and record below is invented, and so are the access rules the expected results come from. Run it only on systems you own or run, on a staging or test copy where one exists, filled with invented records and never a real student's, with every test account using an email address and phone number you control.
How to use itHide the instructions
Rows S1 to S9 are for a school's own sites and portals and the services it uses. Their test roles: students stu-7a-1 and stu-7a-2 in class 7A and stu-8b-1 in class 8B; guardians gdn-1, gdn-2 and gdn-3, linked to those three students in that order, and gdn-new, an applicant with no enrolled student; teachers tch-7a and tch-8b, who teach 7A and 8B; office staff off-1 and off-2, who handle enrolments and payments; and suppliers sup-exc, an excursion provider's login or shared list where your system gives one, and sup-web, the web agency's account on the school website. The invented school's rules: guardians see linked students only, teachers see the classes they teach, office staff see enrolment and payment records, the web agency edits pages but does not read form entries, and the excursion provider sees its own attendee list until an end date the school sets. Rows E1 to E6 are for an edtech supplier's own platform, on its staging environment, with two invented schools: School A with administrator adm-a, teachers tch-a1 and tch-a2, students stu-a1, stu-a2 and stu-a3 and guardian gdn-a1, linked to stu-a1; and School B with administrator adm-b, teacher tch-b1, student stu-b1 and guardian gdn-b1; plus the supplier's support account sup-1. Rows P1 to P5 are the procurement and evidence lane and send nothing. Test ids in the rows are from OWASP WSTG v4.2 and ASVS 5.0.0. Before running a row, replace the invented rules with your own written rules and write your own expected result. Every row that sends a request carries its limits in the last column.
20 rows
Row and workflow step
Data involved
S1. Applications: the online application form
- Data involved
- Applicant and guardian details, and any documents the form asks families to upload.
- Who should reach it, and who should not
- Should reach it: the guardian who applied, for their own application, and the office staff who process applications. Should not: other applicants, the public, or teachers.
- Test case
- gdn-new submits an application for an invented child with an invented, harmless PDF attached. gdn-1, tch-8b and a visitor with no session each open the confirmation page and the uploaded file's address, and gdn-1 also changes the application number in any address that carries one (WSTG-ATHZ-04; ASVS v5.0.0-8.2.2). The file's address is tried again after gdn-new signs out (WSTG-ATHZ-02).
- Expected result
- gdn-new, off-1 and off-2 see the application and the file. Every other request, including the one after sign-out, gets the same refusal or not-found page, with no applicant details in it.
- Evidence to keep
- For each request: the account, the address with personal details removed (for a link that works for whoever holds it, only which link was tried), the status, a one-line note of what the page showed, the date and the environment.
- Limits of the test
- Sends requests. Run it only on your own system, on a staging copy where one exists, with the invented accounts and records named above and never a real student's, guardian's or staff member's, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, unsubscribe, reset or payment link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. If the form is hosted by a supplier, read its terms and ask it before sending anything, and wait until it agrees.
S2. Enrolment: the student record and the fields behind it (staff access)
- Data involved
- The enrolment record: student and guardian contact details, and any health notes, support plans or contact restrictions your form collects.
- Who should reach it, and who should not
- Should reach it: office staff with an enrolment role, and teachers for the fields the school's field list gives them. Should not: teachers outside the student's classes, or any role for fields the list keeps from it.
- Test case
- off-1 enrols stu-7a-1 from an invented application and fills every field. tch-7a and tch-8b then open stu-7a-1's record by its address. Your developer compares the data each page loads with the school's field list, to check that no field the screen hides is still sent to the browser (ASVS v5.0.0-8.2.3).
- Expected result
- tch-7a receives only the fields the list gives a class teacher. tch-8b is refused, because in this invented school a teacher outside the class sees nothing. No hidden field reaches either browser.
- Evidence to keep
- The field list by role, then for each account the fields shown on screen and the fields in the loaded data, recorded as field names rather than values.
- Limits of the test
- Sends requests. Run it only on your own system, on a staging copy where one exists, with the invented accounts and records named above and never a real student's, guardian's or staff member's, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, unsubscribe, reset or payment link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. If this step runs on a supplier's product, read the supplier's terms and ask the supplier before sending anything; until it agrees, run only the read-only check in row S9.
S3. Guardian portal: reports, attendance and timetables (guardian access)
- Data involved
- Each student's reports, attendance, timetable and any notes the portal shows families.
- Who should reach it, and who should not
- Should reach it: each guardian, for the students linked to them. Should not: other families, a guardian whose link has been removed, or any guardian for staff pages.
- Test case
- gdn-1 opens stu-7a-1's report, then changes the student or report number in the address to stu-7a-2's (WSTG-ATHZ-04; ASVS v5.0.0-8.2.2). gdn-1 opens tch-7a's class list by its address (WSTG-ATHZ-02, vertical; ASVS v5.0.0-8.2.1). Then, with gdn-2 signed in on another browser, off-1 removes gdn-2's link to stu-7a-2, and gdn-2 reloads stu-7a-2's report (ASVS v5.0.0-8.3.2, a Level 3 requirement). If your records can restrict what one guardian receives about a student, add an invented second guardian of stu-7a-1 with that restriction set, and repeat the first check in the portal, notices, reports and exports.
- Expected result
- gdn-1 reaches stu-7a-1 only, and gets the same not-found or refusal for stu-7a-2 as for a report that does not exist. The class list refuses gdn-1. After the link is removed, gdn-2's next request is refused. The restricted guardian receives nothing the restriction covers, in any channel.
- Evidence to keep
- Each address tried, the account, the status and whether any of stu-7a-2's details appeared; the time the link was removed beside the time of gdn-2's next request.
- Limits of the test
- Sends requests. Run it only on your own system, on a staging copy where one exists, with the invented accounts and records named above and never a real student's, guardian's or staff member's, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, unsubscribe, reset or payment link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. If this step runs on a supplier's product, read the supplier's terms and ask the supplier before sending anything; until it agrees, run only the read-only check in row S9.
S4. Guardian communications: notices, messages and alerts
- Data involved
- Guardian names, email addresses and mobile numbers, and what each notice says about classes, events or individual students.
- Who should reach it, and who should not
- Should reach it: the guardians of the students a notice is for, and the staff who send to that group. Should not: other families. No guardian should see another guardian's address or number.
- Test case
- tch-7a sends one invented notice to class 7A. Check that gdn-1 and gdn-2 receive it and gdn-3 does not, and that no copy shows other recipients' addresses or numbers. gdn-1 replies, to see who the reply reaches. gdn-1 then opens the notice preferences or unsubscribe link in their copy and changes any guardian or student number in it.
- Expected result
- Only 7A's guardians receive the notice, no copy lists other recipients, the reply reaches staff only, and the changed link shows nothing about another guardian.
- Evidence to keep
- The notice, which test inboxes and numbers received it, the headers of one copy with addresses masked, where the reply went, and the response to the changed link, without the link itself.
- Limits of the test
- Sends requests. Run it only on your own system, on a staging copy where one exists, with the invented accounts and records named above and never a real student's, guardian's or staff member's, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, unsubscribe, reset or payment link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. Every guardian test account uses an inbox or phone number you control, so no real family receives anything. If this step runs on a supplier's product, read the supplier's terms and ask the supplier before sending anything; until it agrees, run only the read-only check in row S9.
S5. Learning portal: classes, submissions and marks (student and teacher access)
- Data involved
- Course material, and each student's submissions, marks and teacher feedback.
- Who should reach it, and who should not
- Should reach it: each student for their own work, the class teacher, and any role the school's rules add. Should not: other students, or teachers of other classes.
- Test case
- stu-7a-1 opens their own marked submission, then changes the submission or student number to stu-7a-2's (WSTG-ATHZ-02, horizontal; ASVS v5.0.0-8.2.2). stu-7a-1 opens a marking or gradebook page by its address (WSTG-ATHZ-02, vertical; ASVS v5.0.0-8.2.1). tch-8b opens 7A's gradebook and one 7A submission by address.
- Expected result
- stu-7a-1 sees only their own work and is refused the marking page. tch-8b is refused 7A's gradebook and submissions, because the invented school's rules give teachers their own classes only.
- Evidence to keep
- Each address tried, the account and its class, the status, and whether another student's work or marks appeared.
- Limits of the test
- Sends requests. Run it only on your own system, on a staging copy where one exists, with the invented accounts and records named above and never a real student's, guardian's or staff member's, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, unsubscribe, reset or payment link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. If this step runs on a supplier's product, read the supplier's terms and ask the supplier before sending anything; until it agrees, run only the read-only check in row S9.
S6. Student uploads: assignments, images and recordings
- Data involved
- The files students upload, such as written work and any images, audio or video the portal accepts.
- Who should reach it, and who should not
- Should reach it: the student who uploaded the file, the class teacher, and any role the school's rules add. Should not: other students, other families, or anyone holding only the file's address.
- Test case
- stu-7a-1 uploads a harmless text file renamed with an image extension, and an HTML file holding only plain text, a type the portal should not accept (WSTG-BUSL-08; ASVS v5.0.0-5.2.2). stu-7a-2, gdn-2 and a visitor with no session then open the address of an upload the portal accepted from stu-7a-1 (WSTG-BUSL-08; WSTG-ATHZ-02). Your developer confirms that an upload stored in a public folder is not run as server-side code when requested directly (ASVS v5.0.0-5.3.1).
- Expected result
- The renamed file and the HTML file are refused. The accepted upload opens for stu-7a-1 and tch-7a only, and the developer confirms how stored uploads are served.
- Evidence to keep
- The test files used, the response to each upload, each access attempt with its account and status, and the developer's note on where uploads are stored and how they are served.
- Limits of the test
- Sends requests. Run it only on your own system, on a staging copy where one exists, with the invented accounts and records named above and never a real student's, guardian's or staff member's, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, unsubscribe, reset or payment link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. Test files only, none of them harmful; delete them afterwards or list them for removal. If this step runs on a supplier's product, read the supplier's terms and ask the supplier before sending anything; until it agrees, run only the read-only check in row S9.
S7. Excursions: consent, payment and the attendee list
- Data involved
- Consent responses, any medical, dietary or emergency contact details the form asks for, payment status, and the attendee list.
- Who should reach it, and who should not
- Should reach it: each guardian for their own child's form, the staff running the excursion, office staff handling payments, and the excursion provider for only what the school chooses to send. Should not: other families, or the provider once the school's rules say its access ends.
- Test case
- gdn-1 opens stu-7a-1's consent form, then changes the student or form number to stu-7a-2's (WSTG-ATHZ-04; ASVS v5.0.0-8.2.2). Your developer sends gdn-1's payment with the amount or the excursion changed in the request, going around the form straight to the server (WSTG-BUSL-02). If sup-exc has a login or a shared list, sup-exc opens the list for another excursion by its address, then opens its own list after the end date in the school's rules.
- Expected result
- gdn-1 reaches stu-7a-1's form only. The amount charged is the one the server sets. sup-exc sees its own list with only the fields the school chose, and is refused after access ends.
- Evidence to keep
- Each address tried, the account and status, the amount sent beside the amount charged on the test payment account, and the fields in sup-exc's list.
- Limits of the test
- Sends requests. Run it only on your own system, on a staging copy where one exists, with the invented accounts and records named above and never a real student's, guardian's or staff member's, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, unsubscribe, reset or payment link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. Test payments go only through a staging copy connected to a non-live payment account, so no real card is charged. The payment provider's hosted checkout is outside this row. If this step runs on a supplier's product, read the supplier's terms and ask the supplier before sending anything; until it agrees, run only the read-only check in row S9.
S8. School website: staff and supplier accounts (staff access)
- Data involved
- Entries from the website's forms, such as enquiries and applications, and the accounts that can publish pages or change settings.
- Who should reach it, and who should not
- Should reach it: office staff for form entries, named editors for pages, and the web agency for the work it is engaged for. Should not: former staff, a supplier whose engagement has ended, or an account nobody can name.
- Test case
- First, read-only: list every account that can sign in to the website's admin area, with its role and, where the site records it, its last sign-in, and mark each one staff, supplier or unknown. Then sup-web opens the form entries screen by its address (WSTG-ATHZ-02, vertical; ASVS v5.0.0-8.2.1). Finally, with sup-web signed in on another browser, off-2 disables sup-web, and sup-web reloads an admin page (ASVS v5.0.0-7.4.2).
- Expected result
- Every account has a named owner and a role that fits the job. sup-web is refused form entries. Once disabled, sup-web's open session stops working on the next request.
- Evidence to keep
- The account list with roles, owners and last sign-in, then the address, account and status of each request.
- Limits of the test
- The account list is read-only. The two account checks follow these limits. Sends requests. Run it only on your own system, on a staging copy where one exists, with the invented accounts and records named above and never a real student's, guardian's or staff member's, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, unsubscribe, reset or payment link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. If this step runs on a supplier's product, read the supplier's terms and ask the supplier before sending anything; until it agrees, run only the read-only check in row S9.
S9. Third-party learning, payment, messaging and school management services
- Data involved
- Whatever the school sends each service: student and guardian details, marks, payments and messages.
- Who should reach it, and who should not
- Should reach it: the service, for the data and purposes the school's agreement with it sets out, and the school staff who manage it. Should not: anyone the school has not given a role in it.
- Test case
- List each third-party service the rows above rely on: what data the school sends it, how it connects (a sign-in link, a data sync or an embedded form), who at the school can change its settings, and what its terms say about security testing. For each one, compare the roles the school has given guardians, teachers and office staff inside it with the rules used in rows S2 to S7.
- Expected result
- Every service has an owner at the school, a data list and a note of its testing terms, and the roles inside each one match the school's rules. Any test of the service itself waits for the supplier's written agreement.
- Evidence to keep
- The list, the date each set of terms was read, and the supplier's written answer to any request to test.
- Limits of the test
- Read-only: reads lists, settings or documents and sends no test requests. Leave closed any screen or file that shows a password, key or secret. This row makes no statement about what any supplier allows: read its terms and ask it.
E1. Edtech platform: the boundary between schools (every role)
- Data involved
- Each school's classes, staff, students and guardians, held on one platform.
- Who should reach it, and who should not
- Should reach it: each school's own accounts, for that school's records and within their role. Should not: any account at another school, whatever its role.
- Test case
- tch-a1 and adm-a each open a School B class, student record and gradebook by address, and run a list or search with any school, class or filter value changed to School B's (WSTG-ATHZ-04; ASVS v5.0.0-8.4.1, a Level 2 requirement). The same requests are repeated from stu-a1 and gdn-a1.
- Expected result
- Every request for a School B record gets the same not-found response as a record that does not exist, and no list or search returns a School B name.
- Evidence to keep
- For each request: the account and its school, the address with identifiers kept and personal details removed, the status, and whether any School B name appeared.
- Limits of the test
- Sends requests. Run it only on your own platform's staging environment, with the two invented schools and the accounts named above and never a real school's, student's, guardian's or staff member's records, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, export, reset or invitation link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5.
E2. Edtech platform: students and guardians (guardian access)
- Data involved
- Each student's work, results and messages, and the links between guardians and students.
- Who should reach it, and who should not
- Should reach it: a student for their own work, and a guardian for the students linked to them. Should not: other students or families at the same school, anyone at another school, or teacher functions.
- Test case
- gdn-a1, linked to stu-a1, opens stu-a2's results by address, then stu-b1's (WSTG-ATHZ-04; ASVS v5.0.0-8.2.2). stu-a1 opens a teacher function, such as entering a mark, by its address (WSTG-ATHZ-02, vertical; ASVS v5.0.0-8.2.1). Then, with gdn-a1 signed in on another browser, adm-a removes gdn-a1's link to stu-a1, and gdn-a1 reloads stu-a1's results (ASVS v5.0.0-8.3.2, a Level 3 requirement).
- Expected result
- gdn-a1 reaches stu-a1 only, stu-a1 is refused the teacher function, and after the link is removed gdn-a1's next request is refused.
- Evidence to keep
- Each address tried, the account, the status, and the time the link was removed beside the time of the next request.
- Limits of the test
- Sends requests. Run it only on your own platform's staging environment, with the two invented schools and the accounts named above and never a real school's, student's, guardian's or staff member's records, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, export, reset or invitation link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5.
E3. Edtech platform: students and staff who leave
- Data involved
- The accounts a school creates, directly or from a roster it sends, and the sessions those accounts hold open.
- Who should reach it, and who should not
- Should reach it: current students and staff only. Should not: anyone the school has removed, including through a session they still had open.
- Test case
- With stu-a2 and tch-a2 each signed in on another browser, adm-a removes both from School A, or, if that is how your platform works, a test roster for School A sent through the sync leaves them out. Each reloads a page showing school data and then tries to sign in again (ASVS v5.0.0-7.4.2).
- Expected result
- Both open sessions stop working on the next request, and neither account can sign in. If removal waits for a sync, the evidence records how long the old access lasted.
- Evidence to keep
- The time of removal, the time and status of each later request, and the sign-in response.
- Limits of the test
- Sends requests. Run it only on your own platform's staging environment, with the two invented schools and the accounts named above and never a real school's, student's, guardian's or staff member's records, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, export, reset or invitation link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. The roster comes from a test source, never a school's own system. Sign-in through a school's own identity provider adds its own checks and is best treated as separate work.
E4. Edtech platform: the supplier's own support access
- Data involved
- Any school record the supplier's support staff can open while helping a school.
- Who should reach it, and who should not
- Should reach it: support staff, only in the way the supplier's agreement with the school describes. Should not: support staff beyond those terms.
- Test case
- First, read-only: read the support access terms in your agreements with schools and in your own procedures. Then sup-1 opens a School A student record the way support does and, if the support role may change records, changes one invented field. adm-a looks for both actions wherever the platform shows schools an activity record. sup-1 then tries a function the support role should not have, such as exporting a school's data, by its address (WSTG-IDNT-01; ASVS v5.0.0-8.2.1).
- Expected result
- sup-1 reaches only what the terms allow, both actions appear wherever the platform says it records support activity for schools, and the export is refused.
- Evidence to keep
- The terms that set support access, the activity record entries, and the address, account and status of each request.
- Limits of the test
- Reading the terms is read-only. The account checks follow these limits. Sends requests. Run it only on your own platform's staging environment, with the two invented schools and the accounts named above and never a real school's, student's, guardian's or staff member's records, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, export, reset or invitation link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5.
E5. Edtech platform: exports and deletion
- Data involved
- A school's full data as an export, and the records a school asks to have deleted.
- Who should reach it, and who should not
- Should reach it: the school's authorised administrators. Should not: any other school, and, once a record is deleted, nobody beyond what your agreement and documentation say is kept.
- Test case
- adm-a requests School A's full export, and the file is searched for School B names (ASVS v5.0.0-8.4.1). adm-a then deletes invented student stu-a3 through the platform's own deletion feature, and stu-a3 is searched for in search, lists, exports and every address that used to show them.
- Expected result
- The export holds School A records only. After deletion, stu-a3 appears nowhere a school account can reach, or only as your agreement and documentation describe.
- Evidence to keep
- The export's record count by school, the time of deletion, and each place searched afterwards with its result.
- Limits of the test
- Sends requests. Run it only on your own platform's staging environment, with the two invented schools and the accounts named above and never a real school's, student's, guardian's or staff member's records, a small number of requests fixed before you start, and no load. Check your hosting provider's testing policy first, in case it asks for notice or approval. Any email or text message the row sets off goes to an inbox or number you control. Treat a link that works for whoever holds it, such as a file, export, reset or invitation link, as a secret: open it only for the invented records and keep it out of the evidence. If a response shows a real person's details, stop, record what you saw without copying it, and follow row P5. Deletion runs only on invented records created for the test.
E6. Edtech platform: integrations with schools' own systems
- Data involved
- Records that move between a school's own systems and the platform, such as rosters, timetables and marks.
- Who should reach it, and who should not
- Should reach it: the integrations a school has approved, for the data each one needs. Should not: an integration the school has turned off, or data outside what it approved.
- Test case
- List each integration a school can connect: what data it moves, in which direction, who at the school approves it, and how a school turns it off. Compare the list with what your documentation tells schools. The API security guide covers testing each route an integration calls.
- Expected result
- Every integration has a documented data list, an approver and a way to turn it off, and the list matches the documentation.
- Evidence to keep
- The list, dated, with the documentation it was compared against.
- Limits of the test
- Read-only: reads lists, settings or documents and sends no test requests. Leave closed any screen or file that shows a password, key or secret.
P1. An ST4S request from a school or education authority
- Data involved
- The supplier's responses to the ST4S questionnaire, and any supporting documents.
- Who should reach it, and who should not
- ST4S's general information page says final assessment results are made available to ST4S Working Group members, educational jurisdiction Chief Information Officers and the New Zealand Ministry of Education, and that approved ST4S stakeholders may distribute the results to their schools.
- Test case
- Read the request: who sent it, and whether it invites you to the ST4S Readiness Check. The ST4S site says suppliers can take part by self-nomination or by invitation from a school or education authority, that they complete the Readiness Check, and that suppliers invited into the full assessment are sent an online questionnaire with criteria across categories such as data protection, organisational security, software development practices, privacy controls and data breach incident. Its vendor guide page says every assessment is performed against a version of the ST4S assessment framework.
- Expected result
- A named owner for the response, the framework version the request refers to, and a list of the questions whose answers rest on rows E1 to E6.
- Evidence to keep
- Dated results of rows E1 to E6 with the build and accounts used, and any outside test report's scope as tested and retest statuses. The ST4S site says suppliers completing the questionnaire are required to attest that their responses are true, correct, accurate, up-to-date and not misleading, and that depending on responses to some questions, additional supporting documentation may be required.
- Limits of the test
- Read-only: reads the request and the ST4S site and sends no test requests. Nothing here is an ST4S result, and this row describes the questionnaire only as far as the ST4S site's own summary goes. Ask the school or education authority what it needs, and establish with it what applies to your product.
P2. A contract or security schedule from a school, department or sector body
- Data involved
- The contract's terms on privacy, security, testing and notification.
- Who should reach it, and who should not
- The people who manage the contract on each side, and your adviser.
- Test case
- Read the contract for clauses on privacy principles, security, testing and notification, and note which law each clause names. Examples of state provisions about contractors: section 17(2) of Victoria's Privacy and Data Protection Act 2014 says a State contract may provide for the contracted service provider to be bound by the Information Privacy Principles and any applicable code of practice with respect to any act done, or practice engaged in, by the contracted service provider for the purposes of the State contract, in the same way and to the same extent as the outsourcing party would have been bound by them had it done the act or engaged in the practice directly. Section 35(1) of Queensland's Information Privacy Act 2009 says an agency entering into a service arrangement must take all reasonable steps to ensure that the contracted service provider is required to comply with parts 1 and 2 and section 41, as if it were the agency, in relation to the discharge of its obligations under the arrangement, subject to the conditions in section 35(2) and to section 35(3), which sets out when the agency is not required to comply.
- Expected result
- Each clause is listed with the law it names and the matrix rows whose results bear on it, and the adviser has said which laws apply.
- Evidence to keep
- The clause list, the dated matrix results for the rows it names, and the adviser's note.
- Limits of the test
- Read-only: reads the contract and sends no test requests. This row interprets no clause. Whether either Act, or another state or territory's law, applies is for the school or supplier and its adviser.
P3. APP 11: the steps an APP entity takes to protect personal information
- Data involved
- Personal information about students, guardians and staff held in the systems the rows above test.
- Who should reach it, and who should not
- The school or supplier, its adviser, and whoever it reports to on privacy.
- Test case
- Ask your adviser whether your school, the body that runs it or your business is an APP entity. The Privacy Act 1988 says APP entity means an agency or organisation. APP 11.1 says that if an APP entity holds personal information, the entity must take such steps as are reasonable in the circumstances to protect the information from misuse, interference and loss, and from unauthorised access, modification or disclosure, and APP 11.3 says that for the purposes of APP 11.1 and 11.2, and without limiting them or any other provision of the Act, such steps include technical and organisational measures.
- Expected result
- An answer from the adviser on whether APP 11 applies and, if it does, the matrix results filed as one record of the technical measures that were checked.
- Evidence to keep
- The dated matrix results, the fixes made, and the result when each failed row was run again.
- Limits of the test
- Read-only: reads the Act and sends no test requests. A matrix run records what was tested; whether the steps taken are reasonable in the circumstances is for the entity and its adviser to judge.
P4. A privacy impact assessment for a new product or feature
- Data involved
- The personal information a new product, or a new feature of one, will handle in each workflow above.
- Who should reach it, and who should not
- Whoever carries out the assessment, and the people who approve the product or feature.
- Test case
- Section 33D(1) of the Privacy Act 1988 says that if an agency proposes to engage in an activity or function involving the handling of personal information about individuals, and the Commissioner considers that the activity or function might have a significant impact on the privacy of individuals, the Commissioner may, in writing, direct the agency to give the Commissioner, within a specified period, a privacy impact assessment about the activity or function. Section 33D(3) describes a privacy impact assessment as a written assessment of an activity or function that identifies the impact it might have on the privacy of individuals and sets out recommendations for managing, minimising or eliminating that impact, and section 33D(4) says subsection (3) does not limit the matters an assessment may deal with. If a school, department or contract asks for an assessment, hand the matrix rows for the workflows the product touches to whoever carries it out.
- Expected result
- The assessment has dated results for each workflow the product touches, and any failed row has a fix and a date to run it again.
- Evidence to keep
- The rows given to the assessor, their dated results, and where the assessment records them.
- Limits of the test
- Read-only: sends no test requests. A matrix run is one input to an assessment and does not complete or approve one. This row does not say section 33D applies to any school or supplier. Whether an assessment is required, under that section or otherwise, is for the school or supplier and its adviser.
P5. A row that showed a real person's details
- Data involved
- Whatever the response showed: a real student's, guardian's or staff member's details.
- Who should reach it, and who should not
- The person who handles breaches at your school or business, and your adviser. Nobody else receives a copy.
- Test case
- Stop the run. Record the row, account, address and time, and describe what was shown without copying it. Tell the person who handles breaches. The OAIC explains that under the Notifiable Data Breaches scheme, an organisation or agency covered by the Privacy Act 1988 must notify affected individuals and the OAIC when a data breach is likely to result in serious harm to a person whose personal information is involved.
- Expected result
- The exposure is closed, the row is run again after the fix, and the person responsible has decided, with the adviser, what the exposure means under any scheme that applies.
- Evidence to keep
- The record above, kept apart from ordinary test results, the fix, and the result of the row when it was run again.
- Limits of the test
- Read-only from this point: send no further requests to the affected address until the fix is in. Whether the exposure is an eligible data breach is for the person responsible and your adviser.
Education cyber security, followed through the workflows that carry student data
Education cyber security on the web, for a school or for a business that sells software to schools, can be followed through the workflows that put information about students and their families online: applications and enrolment, messages to guardians, learning portals, the files students upload, excursions and their payments, and the outside services each of these relies on.
At each step, some people should reach the data and others should not. This guide follows the workflows one at a time, says where access can go wrong at each, and comes with a matrix of test cases to run on your own systems, or to give your developer or tester, using invented students, guardians and staff.
It is written for two readers whose systems differ. A school, or the body that runs it, operates its own website and forms and perhaps a portal, and uses services that other businesses run. An edtech supplier that runs one platform for many schools has a further boundary to hold: the one between one school's records and another's.
The matrix keeps the two apart: rows S1 to S9 are for a school's own sites and the services it uses, rows E1 to E6 for a supplier's own platform, and rows P1 to P5 are an evidence lane that sends nothing: an ST4S request, a contract, APP 11, a privacy impact assessment, and what to do if a test shows a real person's details.
This is not legal advice. Where a law or the ST4S site is quoted below, the page says what that source says and who it covers, and leaves the question of whether it applies to you for your department, sector body or adviser.
School-operated sites and edtech supplier platforms: who owns which system
A school-operated site is anything the school or its governing body runs or has built for it: the public website and its forms, an enrolment portal, a custom family portal, or a learning site on hosting the school pays for.
A supplier platform is software one business runs for many schools, such as a learning management system, a school management system with a family portal, a messaging app or a payment service. Authorisation to test a school-operated site is signed by a person with authority over each target, and whether that person sits at the school or with the body that runs it is for the school to confirm. A supplier's platform is the supplier's to test, or to agree to have tested.
Take an invented excursion. The notice goes out through a messaging app, consent is collected in a school management system, payment goes through a payment provider, and the attendee list ends up with the excursion company. Four businesses touch one workflow, and the school owns none of the software.
What the school can check from its own records and settings is its side of each: which data it sends, which roles it has given guardians, teachers and office staff, and who at the school can change those settings.
Anything further, such as changing a number in the family portal's address to see whether another child's form opens, waits until the school has read the supplier's terms, asked the supplier and had its agreement.
For a supplier, the position is reversed. The platform is yours to test on your own staging environment with invented schools, but a school's own website and its other suppliers' services are not, even when your product connects to them.
Where each workflow puts student and family data
The workflows below follow the order a family meets them.
Each names the records involved and the checks that matter, and, where a guide in this library explains the underlying mistake in depth, names that guide.
An application form collects whatever the school asks for, from contact details to uploaded documents, from people who are not yet part of the school. The first check is the application itself: an application number in an address, or a document link in a confirmation email, that a second applicant can change or reuse.
WSTG v4.2's test for insecure direct object references starts by mapping every place where user input refers directly to an object such as a database row or a file, then changes that value to see whether objects belonging to other users can be retrieved (WSTG-ATHZ-04). The broken access control and IDOR guide covers the check in depth.
At enrolment the application becomes a student record that office staff and teachers open. If the record carries health notes, support plans or contact restrictions, the question becomes which fields each role receives, including any field a screen hides but the data behind it might still carry.
In ASVS 5.0, requirement 8.2.3 asks that field-level access is restricted to consumers with explicit permissions to specific fields. The sensitive data exposure guide explains how to compare what a screen shows with what the response contains.
Notices, newsletters, alerts and two-way messages carry guardian contact details, and information about students, between staff and families. The checks are about audiences: whether a notice for one class reaches only that class's families, whether a copy shows other recipients' addresses, where a reply goes, and whether a preferences or unsubscribe link can be changed to open another family's settings.
Because these checks send real messages, every guardian test account uses an inbox or phone number you control, so no family receives a test notice.
Where a learning portal holds each student's submissions, marks and feedback, access can fail in two directions. Horizontally, between people in the same role: one student reaches another's work by changing a number in an address, or a teacher reaches a class they do not teach.
Vertically, a student reaches a teacher's marking page. WSTG v4.2 assesses whether either is possible in WSTG-ATHZ-02. For horizontal testing it uses two users with identical privileges and changes the relevant parameters and the session identifier from one user's to the other's on every request, and for vertical testing it establishes sessions for two different roles and changes the session identifier from one role's to the other's on every request.
It also checks, for each role and function, whether a resource can be reached without signing in and after signing out.
Uploads add their own questions. The objectives of WSTG-BUSL-08 in WSTG v4.2 include verifying that unwelcome file types are rejected and handled safely, and its testing steps include checking whether a site checks the file type only by its extension, and whether other uploaded files can be reached directly by a specified URL.
ASVS 5.0 requirement 5.2.2 asks that an accepted file's extension matches an expected extension and that its contents correspond to the type the extension represents. The file upload security guide covers what a server accepts, keeps and hands back.
An excursion can gather consent, a payment and, where the form asks for them, medical, dietary or emergency contact details, and then produce an attendee list for the staff running the day and perhaps for the excursion provider. The checks ask whether one family can open another child's form, whether the amount charged is set by the server rather than by the request, and whether a provider's access to the list matches what the school chose to share and ends when the school says it should.
In WSTG-BUSL-02, WSTG v4.2 calls forging requests a method attackers use to circumvent the front end and submit information directly for back end processing, and says the attacker's goal is to send requests with data values that the application's business logic does not support, guard against or expect. The business logic vulnerabilities guide covers rules like these, including an amount changed in the request.
Each workflow can run partly on a service another business owns. Row S9 is the check a school can make without sending a request: list each service, the data the school sends it, how it connects, who can change its settings, and what its terms say about security testing. That list is also where a supplier's answer to a request to test goes, once you have one.
Student portal security: guardian access and staff access are tested apart
Guardians and staff reach the same records by different routes and for different reasons, so the matrix gives them separate test accounts, and separate rows for what each may reach inside one school: S3 and E2 for guardians, S2 and S8 for staff.
Guardian access
Guardian access is tested horizontally first: one family against another, and one guardian against a student who is not linked to them. The links also change. A guardian can be added to or removed from a student, and if your records can restrict what one guardian receives about a student, that restriction has to hold everywhere the information appears: the portal, notices, reports and exports.
ASVS 5.0 requirement 8.3.2, a Level 3 requirement, asks for changes to the values that authorisation decisions rest on to be applied immediately, and, where that cannot happen, for mitigating controls that alert when someone performs an action they are no longer authorised to do and revert the change, an alternative the standard notes would not mitigate information leakage. That is why rows S3 and E2 remove a link while the guardian is still signed in.
Staff access
Staff access is tested vertically and by scope. A teacher should reach the classes the school's rules give them, office staff the records their role needs, and the web agency or another supplier only the work it is engaged for.
The objectives of WSTG v4.2's role definitions test, WSTG-IDNT-01, are to identify and document the roles the application uses, to attempt to switch, change or access another role, and to review the granularity of the roles and the needs behind the permissions given.
This matrix turns that review into a short written list, made before any testing starts: what a class teacher, a year coordinator, an office administrator and an outside supplier may each open, change and export.
Staff and suppliers who leave need their own check. Requirement 7.4.2 of ASVS 5.0 asks that the application terminates all active sessions when a user account is disabled or deleted, such as an employee leaving the company.
Rows S8 and E3 disable or remove an account while it is still signed in elsewhere and reload a page. How a session ought to end is one of the subjects of the session management guide.
Signing in
However your system creates guardian accounts, whether at enrolment, by invitation or by sign-up, each route needs the checks the broken authentication guide sets out for sign-up, login and password reset. For staff accounts that use a second factor, the MFA security guide covers the paths around it.
Edtech security assessment: the boundary between schools
For a supplier, the first thing to test is the boundary between schools on one platform.
Requirement 8.4.1 of ASVS 5.0, at Level 2, asks that multi-tenant applications use cross-tenant controls so consumer operations do not affect tenants they have no permission to interact with. The matrix treats each school on a platform as a tenant.
Row E1 tests the boundary from every role a school holds, not only from administrators, and checks lists and searches as well as single-record screens. WSTG-ATHZ-04 in WSTG v4.2 says the best way to test for direct object references is with at least two (often more) users who own different objects. Row E1 follows that with two invented schools and accounts in each.
Rows E3 to E5 cover supplier workflows that the school rows do not. Account removal, by an administrator or from a roster the school sends, decides when a student or teacher who has left loses access, including through a sign-in they still had open (row E3). Support access decides what your own staff can open while helping a school, and whether the school can see that it happened (row E4).
Exports and deletion decide what a school takes with it, or leaves behind, when it stops using the product or asks for a student's records to be removed (row E5).
Some work sits beside the matrix rather than in it. Sign-in through a school's own identity provider adds the sign-in exchange, account linking and the provider's settings to what needs testing, and is best treated as separate work. An AI feature, such as an assistant that drafts feedback, needs prompt injection and the actions it can take tested as a surface of its own.
If a school or education authority has asked about ST4S, the next section says what the ST4S site describes, and row P1 lists what to gather.
Privacy and procurement duties: what the sources say, and who decides
This section quotes the Privacy Act 1988, Victorian and Queensland privacy laws, the OAIC and the ST4S site.
It does not say that any of them applies to your school or business. Which privacy laws, contract terms and procurement requests apply is for the school or supplier to establish with its department, sector body or adviser.
Australian Privacy Principle 11.1, in Schedule 1 to the Privacy Act 1988, says that if an APP entity holds personal information, the entity must take such steps as are reasonable in the circumstances to protect the information from misuse, interference and loss, and from unauthorised access, modification or disclosure.
APP 11.3 says that for the purposes of APP 11.1 and 11.2, and without limiting them or any other provision of the Act, such steps include technical and organisational measures. The Act says APP entity means an agency or organisation, and section 6C(1) defines an organisation as an individual, a body corporate, a partnership, any other unincorporated association or a trust that is not a small business operator, a registered political party, an agency, a State or Territory authority or a prescribed instrumentality of a State or Territory.
The OAIC explains that under the Notifiable Data Breaches scheme, an organisation or agency covered by the Privacy Act 1988 must notify affected individuals and the OAIC when a data breach is likely to result in serious harm to a person whose personal information is involved.
Part IIIC of the Act covers notification of eligible data breaches. Row P5 sets out what to record if a test shows a real person's details, so that whoever decides has what they need.
Some state privacy laws have their own provisions about contractors. Section 3 of Victoria's Privacy and Data Protection Act 2014 defines a contracted service provider as a person or body who provides services under a State contract, and a State contract as a contract between an organisation, or a person, agency or body to which Part 4 or 5 of the Act applies, and another person or body (whether or not the Act or a Part of it applies to that person or body) under which services are provided to one party (the outsourcing party) by the other (the contracted service provider) in connection with the performance of the outsourcing party's functions, including services that the outsourcing party provides to other persons or bodies.
Section 17(2) says a State contract may provide for the contracted service provider to be bound by the Information Privacy Principles and any applicable code of practice with respect to any act done, or practice engaged in, by the contracted service provider for the purposes of the State contract, in the same way and to the same extent as the outsourcing party would have been bound by them had it done the act or engaged in the practice directly.
Queensland's Information Privacy Act 2009 says, in section 18(1), that an agency means a Minister, a department, a local government or a public authority, and in section 18(2) that agency does not include an excluded entity, a term section 18(4) defines by reference to schedule 2. Section 35(1) says that an agency entering into a service arrangement must take all reasonable steps to ensure that the contracted service provider is required to comply with parts 1 and 2 and section 41, as if it were the agency, in relation to the discharge of its obligations under the arrangement.
Section 35(2) says the agency must comply with subsection (1) only if the provider will in any way deal with personal information for the contracting agency, or the services will involve transferring personal information to the agency or providing services to a third party for it, and section 35(3) sets out when the agency is not required to comply.
These are examples, not a list.
Whether either Act, or another state or territory's law, bears on a school or supplier is for that school or supplier and its adviser.
Safer Technologies 4 Schools (ST4S) describes itself as a standardised approach to evaluating digital products and services used by schools across Australia and New Zealand against a nationally consistent security and privacy control framework. Its site says ST4S is administered by Education Services Australia (ESA) on behalf of state and territory governments and the Catholic and independent school sectors, and the New Zealand Ministry of Education, and that assessments are co-ordinated by ESA's National Schools Interoperability Program (NSIP) team.
The site says a supplier can take part by self-nomination or by invitation from a school or education authority. The supplier completes the ST4S Readiness Check and, once it has a satisfactory outcome, may formally submit its results for consideration by the ST4S Working Group to undertake the full assessment.
Suppliers invited into the full assessment are sent an online questionnaire with criteria across categories such as data protection, organisational security, software development practices, privacy controls and data breach incident. Suppliers completing it are required to attest that their responses are true, correct, accurate, up-to-date and not misleading in any way, and depending on responses to some questions, additional supporting documentation may be required.
The ST4S vendor guide page says every assessment is performed against a version of the ST4S assessment framework.
Nothing on this page says a product is or will be ST4S assessed, and a test report is not an ST4S result. If a school or education authority raises ST4S, ask it what it needs and which framework version applies, and use row P1 to gather what you hold.
How to use the education website security checklist on your own systems
The matrix is a checklist in table form.
Each row is one workflow step, with the data involved, who should and should not reach it, the test, the result your rules expect, the evidence to keep and the row's own limits. Read across a row before running it, and run rows S9 and E6 first, because they list the services and connected systems that belong to other businesses or to schools.
- Use only systems you own or run, on a staging or test copy where one exists. If a staging copy was made from production, replace its records with invented ones before you start.
- Create the test roles in the matrix description, or your own equivalents, with every test account using an email address and phone number you control. Keep two accounts wherever a row compares people in the same role.
- Write your access rules first: for each workflow, who may open, change and export each kind of record. The expected results in the matrix come from an invented school's rules, so replace them with yours.
- Keep each row small: a number of requests fixed before you start, and no load. Run anything that changes or deletes data only on invented records created for the test, and keep a list of what you created so it can be removed.
- Check your hosting provider's testing policy before the first request, in case it asks for notice or approval. If a row runs on a supplier's product, read the supplier's terms and ask the supplier first; until it agrees, run only the read-only checks.
- If any response shows a real student's, guardian's or staff member's details, stop, record it without copying the details, and follow row P5.
- Keep the evidence each row lists, dated, with personal details removed. A result describes one build on one day.
Who runs which rows
Rows that only read lists and settings suit a business manager or IT lead. Rows that change a number in the browser's address bar can be run by anyone holding the test accounts. Rows that change a request on its way to the server, such as the payment amount in S7, or that compare the data a page loads with what it shows, such as S2, need a developer or tester.
What a review like this cannot show
A matrix run is evidence about the rows you ran.
These are its edges.
- A passing row speaks only for the accounts, records and build it ran on. It does not show that the same mistake is absent elsewhere, or that it stays absent after the next release.
- The matrix tests access through the web. It does not reach staff devices, the school network, email accounts, backups or how long records are kept.
- A school's results on a supplier's product reach only as far as the supplier agreed the tests could go, and say nothing about the parts of the platform a school cannot see.
- It does not decide whether a law applies, whether the steps an entity takes are reasonable, or whether an exposure has to be notified. Those decisions belong to the school or supplier and its adviser.
- It is not an ST4S assessment, a certification or an audit.
Where a Clever Ops test fits
Clever Ops tests the parts of a school's or supplier's systems that families, students and staff reach through a browser or an API.
A school's public website and its enquiry forms suit the website security check: an external review of what anyone on the internet can see without logging in. Where an application or enrolment form takes uploaded documents or payments, or families sign in, the web application and API penetration test is the starting point instead, because the check does not test uploads or anything behind a login.
Where the school's site runs on WordPress, with or without a member area for families, the WordPress security audit is the match, following each role that can log in.
A custom family or student portal built for the school, or an edtech supplier's own platform, fits the web application and API penetration test: a signed-in test with two test accounts in each role in scope, and accounts in two separate customer organisations when an application serves more than one.
On an education platform, that means two schools. For a larger application, or a multi-tenant platform shared by many schools, the scope is set individually after a longer call.
Services run by other businesses, such as a supplier's learning or payment platform that a school uses, stay out of scope unless their owner agrees. An AI feature built into an edtech product, such as an assistant that drafts feedback, belongs to the AI chatbot and agent security test instead.
A school's network, staff devices and phishing tests go to a network or red team specialist. Destructive actions are off by default for real people's accounts and records that existed before the test, reset, lockout and deletion checks run only on test accounts and test records where the rules of engagement allow them, and nothing is sent by email or text message to a real person.
A report is evidence for a decision someone else makes, such as a school, a department or an education authority, and it is not a certificate or an ST4S result. Clever Ops is not CREST accredited, so when an education department, a panel or a contract requires a CREST-accredited provider, that work is referred to an accredited provider.
Where Clever Ops built or hosts a school's site or a supplier's platform, the same work is reported as a security review, not an independent test, and the report names who built it and who hosts it.
Frequently asked questions
Only as far as the supplier's terms allow. Read the terms, ask the supplier in writing, and wait for its answer before sending any test request to its platform. Until then, check the school's own side from its records and settings: which data the school sends, which roles guardians and staff hold, and who at the school can change those settings. Row S9 of the matrix is that check, and it sends nothing.
That is for ST4S and the school or education authority that raised it to say, so ask them what evidence they want. The ST4S site says suppliers completing the questionnaire are required to attest that their responses are true, correct, accurate, up-to-date and not misleading, and that depending on responses to some questions, additional supporting documentation may be required. A test report records what was tested, on which build and when. It is not an ST4S result.
This guide does not answer that; your department, sector body or adviser does. The Privacy Act 1988 says APP entity means an agency or organisation, and its definition of an organisation excludes, among others, a small business operator and a State or Territory authority. Some state laws, such as Victoria's Privacy and Data Protection Act 2014 and Queensland's Information Privacy Act 2009, have their own provisions, including provisions about contractors.
No. Replace the records with invented students, guardians and staff first. A staging copy made from production holds the same people, so a test that opens one student's file from another account has exposed a real student's details, even inside a test. If you cannot replace them yet, run only the read-only rows until you can.
Whatever the school's written rules say, which is why the matrix asks for the rules before any testing. The role definitions test in WSTG v4.2 (WSTG-IDNT-01) sets out to identify and document the roles, and to review the granularity of the roles and the needs behind the permissions given. For each staff role, answer three questions in writing: which classes or year levels it covers, which fields of a student record it receives, and which admin screens it may open, such as form entries. Row S5 tests the first answer and row S2 the second. Row S8 tests the third with the web agency's account; repeat that check from each staff account whose answer keeps it out of a screen.
Stop the run, record the row, account, address and time, describe what was shown without copying it, and tell the person who handles breaches at your school or business. The OAIC explains that under the Notifiable Data Breaches scheme, an organisation or agency covered by the Privacy Act 1988 must notify affected individuals and the OAIC when a data breach is likely to result in serious harm to a person whose personal information is involved. Whether that applies is for the person responsible and your adviser.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.