Skip to main content
Remote service areaReviewed

Penetration testing for Perth web applications and APIs, with a WA public sector evidence checklist

Clever Ops tests the websites, web applications and APIs that Perth businesses run, working remotely from Gippsland, Victoria.

If a Western Australian department or council buys from you, the checklist on this page lists the questions it may ask under the PRIS Act and the state's cyber security policy, the test evidence that answers each one, and the answers that have to come from somewhere else.

Western Australian supplier evidence checklist

Find the row closest to the question your WA department or council has asked, check the evidence column against what you actually hold, and write a name in the owner column before you answer. Most rows trace the question to a section of the PRIS Act (compilation 00-g0-03), a clause of the 2026 WA Government Cyber Security Policy, a line of the Information Security Risk Self-Assessment Table updated in August 2026, or the OIC's guidance on contracted service providers; the rest point to the customer's own procurement wording or the rules of engagement.

How to use it

The PRIS Act provides a framework for the privacy of personal information handled by public entities, Ministers, Parliamentary Secretaries and contracted service providers to public entities, and section 14(1)(d) names a contracted service provider as an IPP entity; the 2026 policy and the self-assessment table are written for WA Government entities. The rows show how the customer's questions reach a supplier, not that any rule applies to your business. The last three rows cover running the test across the time difference. General information, not legal advice.

20 rows

Western Australian supplier evidence checklist

Question a WA public sector customer may put to youWhere the question comes fromEvidence from a web application testWhat that evidence cannot answerOwner on your side
Will you accept the PRIS compliance clause in our contract?PRIS Act sections 129 and 130; General Conditions of Contract clause 25.2, as the OIC describes it.None. Whether to take on clause 25.2 is a commercial and legal call.Everything here sits outside a test: the clause, your privacy policy, and how your people handle personal information day to day.Whoever signs contracts for the business, with the solicitor's advice in hand.
If that clause is not selected, will you help us meet our PRIS Act obligations and comply with the Australian Privacy Principles?General Conditions clause 25.1, as the OIC describes it; PRIS Act section 140(2), on enforcement against the outsourcing entity.None. The commitment is contractual.Whether your own practices follow the Australian Privacy Principles.The director, with your privacy contact.
What have you done to keep the personal information in your application from misuse, loss and unauthorised access?PRIS Act Schedule 1, IPP 4.1; the OIC's question on each party's responsibilities for the quality and security of personal information (IPP 3 and IPP 4).What happened when one role, or one customer organisation, tried to open another's records, including the attempts that failed; the certificate and transport checks on each public hostname; and where every finding landed at retest.Reasonableness, which the customer weighs, not the tester. Also anything beyond the application in scope, such as backup copies, laptops, mailboxes and building access.The person who answers privacy questions for you, drawing on the technical lead for the test detail.
Once personal information has served its purpose, how is it destroyed or de-identified, and what happens to ours at the end of the contract?IPP 4.2; the OIC's question on destroying or returning personal information at the end of the contract; policy clause 3.4(g).Next to nothing. The report lists the dummy records the tester created and left for removal, and that is all it says about deletion.How long you keep applicant data, how it is purged or de-identified, when backups age out, and how data goes back to the agency at exit.Whoever runs your platform day to day.
Do you have any discretion to disclose our personal information overseas?IPP 9.1; the OIC's question on discretion over use and disclosure, including disclosures overseas (IPP 2 and IPP 9).Nothing about your application. About the test, the tester's data handling terms; Clever Ops keeps its evidence encrypted in Australia and processes it offshore only with the statement of work's approval.Which countries your cloud region, backup copies, mail service and support staff are in, and who can reach the data from there.The technical lead, reading from the hosting and support agreements.
Will you take part in a privacy impact assessment for this service?PRIS Act section 79(2) and (3); section 137(1), for a contracted service provider whose contract includes a section 129 provision.The scope as tested and the access findings, showing which personal information each tested role could reach.The assessment and its report, which weigh likelihood and impact and set out recommendations under section 79(3).Your privacy contact.
How will you tell us about a suspected information breach, and how will we cooperate on notification?The OIC's guidance on notifying the outsourcing entity of a suspected information breach; Part 2 Division 6, which the OIC says will commence from 1 January 2027 and apply under section 134 to a provider with a PRIS compliance clause.Little. If the tester noticed that its own activity went unlogged, the report may say so, but that is the limit.Who spots a suspected breach, who decides it is one, who rings the agency, and the agreed way the two of you handle any notice under the Act.Whoever holds your incident plan.
Can you support our report to DGov within 6 hours of an incident being suspected or confirmed?Policy clauses 3.4(b) and 5.1.None.After-hours cover, alert routing, and the path from your first responder to the agency's contact.Whoever holds your incident plan, together with the contract owner.
What are your cyber security practices and certifications, and have you had a data breach?The OIC's list of due diligence matters for tender documentation; policy clause 3.4(a).A dated report on the application the customer will use, offered as one piece of assurance.A certification, which a test report is not, and anything about past breaches.The director.
Send us current security audit or testing results.The OIC's examples of monitoring, which include a SOC 2 Type II or IRAP assessment report or annual penetration test results.A dated report naming the build it covers and the scope as tested; each finding carrying both a CVSS v3.1 score and a business-risk rating; and the retest ledger, where every finding ends as fixed, partially fixed, still reproducible or not retested.A SOC 2 Type II or IRAP assessment report, which is a different kind of evidence. Clever Ops does not provide either.The technical lead who commissioned the test.
Show evidence of independent assessment of the information security risks of the service we are buying.Self-assessment table, Tier 1 supply chain and third-party risk: evidence of annual or biannual independent assessment, followed in brackets by IRAP, ISO 27001, SOC2 and FedRAMP.A report by an outside tester that neither built nor hosts the application, with a line from that tester confirming it. Where Clever Ops built or hosts a system, its work there is called a security review and the report names the builder and the host.Any of the four assessment types the table names, and any independence the tester lacks.Whoever picks the testing provider.
Is our Tier 1 information hosted in Australia, and what controls cover offshore backups and offshore user access?Policy clause 3.5; self-assessment table, Tier 1 cloud services offshoring.Nothing on location. Access tests show what a support or administrator role can reach once signed in.Data centre locations, backup copies and where support staff sign in from.Your technical lead, with the hosting and support contracts.
Do our staff sign in to your application with phishing-resistant multi-factor authentication?Self-assessment table, Tier 1 identity and access management.Role by role, what the tester met at sign-in: whether a second factor was demanded, and whether a side route such as calling the API directly avoided it.Whether the kind of factor in use counts as phishing-resistant for the agency, and anything configured on the agency's side if its staff sign in through its own directory.Whoever owns sign-in in your product.
Describe your software security practices. Is application security testing, including dynamic testing, part of how you release?Policy clause 3.4(e); clause 3.13(d), which the policy sets for an entity's own in-house development.A dynamic test against the running application on one named build, plus a code review if read-only access to the code was agreed.Whether testing is regular and built into your release process. One report is one point in time.Your development lead.
If you test on staging, does staging hold our real records?Policy clause 3.13(c), on sanitising sensitive production data used in non-production environments, set for an entity's own in-house development.The environment named in the scope as tested, and the list of test data created.How staging is loaded and refreshed.Your technical lead.
Who is responsible for which security layer: you, your host or us?Policy clause 3.4(h), on a shared responsibility model.The report's note of who built the system and who runs its hosting, and the exclusions in the scope as tested, which mark the layers the test did not reach.The responsibility model itself.Your technical lead, with the host's documentation.
Is your tester a supplier under a WA common use arrangement, on a panel, or CREST accredited?The customer's own procurement wording; CUAICTS2021 lists security testing among its Category 2 testing services.The testing provider's name, with any CUA listing, panel place or accreditation it actually holds. Clever Ops is not a supplier under CUAICTS2021 and is on no government panel. Clever Ops is not CREST accredited, so we refer that work to a provider that is.If the tender text demands a listed or accredited tester, a report from anyone else falls short of that text.The person handling the tender, checking the wording before anyone is engaged.
When will test traffic reach our systems, in our time?The rules of engagement both parties sign; section 4 of the Standard Time Act 2005 (WA) puts WA standard time at eight hours ahead of UTC.The window in the authorisation and rules of engagement, written in Perth time with its UTC offset, and the IP addresses the tester's traffic originates from.Traffic from anyone else during the window.Your technical contact for the window.
Who can stop the test during the window, and how is a stop confirmed?The rules of engagement both parties sign.The named stop contact for each hour of the window, in Perth time, and the tester's written confirmation of any pause or stop with the time and the last request sent.Hours the contact roster does not cover.Your technical contact, with a named second contact.
When is the handover, and in which time zone are the report's times?The rules of engagement; section 3(1) of Victoria's Summer Time Act 1972 sets Victorian summer time one hour ahead of standard time for the proclaimed summer period.The handover booked in Perth time on every invitation, and dates and times in the report given with their offset.What the findings mean for your contract with the customer.The person who booked the test.

Question a WA public sector customer may put to you

Where the question comes from

  1. Will you accept the PRIS compliance clause in our contract?
    Where the question comes from
    PRIS Act sections 129 and 130; General Conditions of Contract clause 25.2, as the OIC describes it.
    Evidence from a web application test
    None. Whether to take on clause 25.2 is a commercial and legal call.
    What that evidence cannot answer
    Everything here sits outside a test: the clause, your privacy policy, and how your people handle personal information day to day.
    Owner on your side
    Whoever signs contracts for the business, with the solicitor's advice in hand.
  2. If that clause is not selected, will you help us meet our PRIS Act obligations and comply with the Australian Privacy Principles?
    Where the question comes from
    General Conditions clause 25.1, as the OIC describes it; PRIS Act section 140(2), on enforcement against the outsourcing entity.
    Evidence from a web application test
    None. The commitment is contractual.
    What that evidence cannot answer
    Whether your own practices follow the Australian Privacy Principles.
    Owner on your side
    The director, with your privacy contact.
  3. What have you done to keep the personal information in your application from misuse, loss and unauthorised access?
    Where the question comes from
    PRIS Act Schedule 1, IPP 4.1; the OIC's question on each party's responsibilities for the quality and security of personal information (IPP 3 and IPP 4).
    Evidence from a web application test
    What happened when one role, or one customer organisation, tried to open another's records, including the attempts that failed; the certificate and transport checks on each public hostname; and where every finding landed at retest.
    What that evidence cannot answer
    Reasonableness, which the customer weighs, not the tester. Also anything beyond the application in scope, such as backup copies, laptops, mailboxes and building access.
    Owner on your side
    The person who answers privacy questions for you, drawing on the technical lead for the test detail.
  4. Once personal information has served its purpose, how is it destroyed or de-identified, and what happens to ours at the end of the contract?
    Where the question comes from
    IPP 4.2; the OIC's question on destroying or returning personal information at the end of the contract; policy clause 3.4(g).
    Evidence from a web application test
    Next to nothing. The report lists the dummy records the tester created and left for removal, and that is all it says about deletion.
    What that evidence cannot answer
    How long you keep applicant data, how it is purged or de-identified, when backups age out, and how data goes back to the agency at exit.
    Owner on your side
    Whoever runs your platform day to day.
  5. Do you have any discretion to disclose our personal information overseas?
    Where the question comes from
    IPP 9.1; the OIC's question on discretion over use and disclosure, including disclosures overseas (IPP 2 and IPP 9).
    Evidence from a web application test
    Nothing about your application. About the test, the tester's data handling terms; Clever Ops keeps its evidence encrypted in Australia and processes it offshore only with the statement of work's approval.
    What that evidence cannot answer
    Which countries your cloud region, backup copies, mail service and support staff are in, and who can reach the data from there.
    Owner on your side
    The technical lead, reading from the hosting and support agreements.
  6. Will you take part in a privacy impact assessment for this service?
    Where the question comes from
    PRIS Act section 79(2) and (3); section 137(1), for a contracted service provider whose contract includes a section 129 provision.
    Evidence from a web application test
    The scope as tested and the access findings, showing which personal information each tested role could reach.
    What that evidence cannot answer
    The assessment and its report, which weigh likelihood and impact and set out recommendations under section 79(3).
    Owner on your side
    Your privacy contact.
  7. How will you tell us about a suspected information breach, and how will we cooperate on notification?
    Where the question comes from
    The OIC's guidance on notifying the outsourcing entity of a suspected information breach; Part 2 Division 6, which the OIC says will commence from 1 January 2027 and apply under section 134 to a provider with a PRIS compliance clause.
    Evidence from a web application test
    Little. If the tester noticed that its own activity went unlogged, the report may say so, but that is the limit.
    What that evidence cannot answer
    Who spots a suspected breach, who decides it is one, who rings the agency, and the agreed way the two of you handle any notice under the Act.
    Owner on your side
    Whoever holds your incident plan.
  8. Can you support our report to DGov within 6 hours of an incident being suspected or confirmed?
    Where the question comes from
    Policy clauses 3.4(b) and 5.1.
    Evidence from a web application test
    None.
    What that evidence cannot answer
    After-hours cover, alert routing, and the path from your first responder to the agency's contact.
    Owner on your side
    Whoever holds your incident plan, together with the contract owner.
  9. What are your cyber security practices and certifications, and have you had a data breach?
    Where the question comes from
    The OIC's list of due diligence matters for tender documentation; policy clause 3.4(a).
    Evidence from a web application test
    A dated report on the application the customer will use, offered as one piece of assurance.
    What that evidence cannot answer
    A certification, which a test report is not, and anything about past breaches.
    Owner on your side
    The director.
  10. Send us current security audit or testing results.
    Where the question comes from
    The OIC's examples of monitoring, which include a SOC 2 Type II or IRAP assessment report or annual penetration test results.
    Evidence from a web application test
    A dated report naming the build it covers and the scope as tested; each finding carrying both a CVSS v3.1 score and a business-risk rating; and the retest ledger, where every finding ends as fixed, partially fixed, still reproducible or not retested.
    What that evidence cannot answer
    A SOC 2 Type II or IRAP assessment report, which is a different kind of evidence. Clever Ops does not provide either.
    Owner on your side
    The technical lead who commissioned the test.
  11. Show evidence of independent assessment of the information security risks of the service we are buying.
    Where the question comes from
    Self-assessment table, Tier 1 supply chain and third-party risk: evidence of annual or biannual independent assessment, followed in brackets by IRAP, ISO 27001, SOC2 and FedRAMP.
    Evidence from a web application test
    A report by an outside tester that neither built nor hosts the application, with a line from that tester confirming it. Where Clever Ops built or hosts a system, its work there is called a security review and the report names the builder and the host.
    What that evidence cannot answer
    Any of the four assessment types the table names, and any independence the tester lacks.
    Owner on your side
    Whoever picks the testing provider.
  12. Is our Tier 1 information hosted in Australia, and what controls cover offshore backups and offshore user access?
    Where the question comes from
    Policy clause 3.5; self-assessment table, Tier 1 cloud services offshoring.
    Evidence from a web application test
    Nothing on location. Access tests show what a support or administrator role can reach once signed in.
    What that evidence cannot answer
    Data centre locations, backup copies and where support staff sign in from.
    Owner on your side
    Your technical lead, with the hosting and support contracts.
  13. Do our staff sign in to your application with phishing-resistant multi-factor authentication?
    Where the question comes from
    Self-assessment table, Tier 1 identity and access management.
    Evidence from a web application test
    Role by role, what the tester met at sign-in: whether a second factor was demanded, and whether a side route such as calling the API directly avoided it.
    What that evidence cannot answer
    Whether the kind of factor in use counts as phishing-resistant for the agency, and anything configured on the agency's side if its staff sign in through its own directory.
    Owner on your side
    Whoever owns sign-in in your product.
  14. Describe your software security practices. Is application security testing, including dynamic testing, part of how you release?
    Where the question comes from
    Policy clause 3.4(e); clause 3.13(d), which the policy sets for an entity's own in-house development.
    Evidence from a web application test
    A dynamic test against the running application on one named build, plus a code review if read-only access to the code was agreed.
    What that evidence cannot answer
    Whether testing is regular and built into your release process. One report is one point in time.
    Owner on your side
    Your development lead.
  15. If you test on staging, does staging hold our real records?
    Where the question comes from
    Policy clause 3.13(c), on sanitising sensitive production data used in non-production environments, set for an entity's own in-house development.
    Evidence from a web application test
    The environment named in the scope as tested, and the list of test data created.
    What that evidence cannot answer
    How staging is loaded and refreshed.
    Owner on your side
    Your technical lead.
  16. Who is responsible for which security layer: you, your host or us?
    Where the question comes from
    Policy clause 3.4(h), on a shared responsibility model.
    Evidence from a web application test
    The report's note of who built the system and who runs its hosting, and the exclusions in the scope as tested, which mark the layers the test did not reach.
    What that evidence cannot answer
    The responsibility model itself.
    Owner on your side
    Your technical lead, with the host's documentation.
  17. Is your tester a supplier under a WA common use arrangement, on a panel, or CREST accredited?
    Where the question comes from
    The customer's own procurement wording; CUAICTS2021 lists security testing among its Category 2 testing services.
    Evidence from a web application test
    The testing provider's name, with any CUA listing, panel place or accreditation it actually holds. Clever Ops is not a supplier under CUAICTS2021 and is on no government panel. Clever Ops is not CREST accredited, so we refer that work to a provider that is.
    What that evidence cannot answer
    If the tender text demands a listed or accredited tester, a report from anyone else falls short of that text.
    Owner on your side
    The person handling the tender, checking the wording before anyone is engaged.
  18. When will test traffic reach our systems, in our time?
    Where the question comes from
    The rules of engagement both parties sign; section 4 of the Standard Time Act 2005 (WA) puts WA standard time at eight hours ahead of UTC.
    Evidence from a web application test
    The window in the authorisation and rules of engagement, written in Perth time with its UTC offset, and the IP addresses the tester's traffic originates from.
    What that evidence cannot answer
    Traffic from anyone else during the window.
    Owner on your side
    Your technical contact for the window.
  19. Who can stop the test during the window, and how is a stop confirmed?
    Where the question comes from
    The rules of engagement both parties sign.
    Evidence from a web application test
    The named stop contact for each hour of the window, in Perth time, and the tester's written confirmation of any pause or stop with the time and the last request sent.
    What that evidence cannot answer
    Hours the contact roster does not cover.
    Owner on your side
    Your technical contact, with a named second contact.
  20. When is the handover, and in which time zone are the report's times?
    Where the question comes from
    The rules of engagement; section 3(1) of Victoria's Summer Time Act 1972 sets Victorian summer time one hour ahead of standard time for the proclaimed summer period.
    Evidence from a web application test
    The handover booked in Perth time on every invitation, and dates and times in the report given with their offset.
    What that evidence cannot answer
    What the findings mean for your contract with the customer.
    Owner on your side
    The person who booked the test.

What Clever Ops tests for Perth businesses, and what it leaves to others

Clever Ops is a small Australian consultancy in Gippsland, Victoria, and its clients are businesses earning $1M to $50M in annual revenue.

A Perth engagement runs entirely at a distance: test traffic crosses the internet to the hostnames and API addresses your signed authorisation lists, and nobody from Clever Ops comes to your premises. There is no Perth office and no member of staff in Western Australia.

Anything your customers reach through a browser or an API can be in scope: WordPress sites and WooCommerce stores, marketing websites, custom web applications and the APIs behind them, apps put together with AI builders, and AI chatbots and agents. A security fix sprint and retests are offered alongside.

Cyber security in Perth, as anywhere, takes in managed IT, network and infrastructure testing, monitoring and incident response as well as application testing, and this service is only the last of those. Office computers, email, backups and Wi-Fi are not looked after here; office networks, servers, Active Directory and staff laptops are not tested; phishing simulations, physical intrusion tests and round-the-clock monitoring are not offered. For any of that, look to a managed IT provider or a specialist in network testing.

Inside web applications, the depth follows what the site does and who will read the result.

  • Website security audit, which Clever Ops calls a website security check. The public site is examined from outside, as any visitor could reach it: certificate and transport settings, response headers, cookie flags, exposed files and admin paths, and the software versions the site gives away. It fits sites where nobody signs in.
  • Vulnerability assessment. A broad pass across a website or web application for known kinds of weakness, with each one confirmed and ranked. It does not set out to defeat the rules the application enforces.
  • Web application penetration test. Using an account for every role in scope, the tester works against those rules: which records a user may open, what an administrator at one customer may change, and whether the API applies the same rules when it is called directly. The WA checklist on this page draws mostly on this depth, because public sector questions about personal information turn on who can reach what.

The PRIS Act: who it covers and which parts are in operation

The Privacy and Responsible Information Sharing Act 2024 (WA), the PRIS Act, is quoted here from compilation 00-g0-03 on the Western Australian legislation site.

Its long title describes a framework to protect the privacy of personal information handled by public entities, Ministers, Parliamentary Secretaries and contracted service providers to public entities. What follows reports the text and the bodies it names, and stops there. It is general information rather than legal advice, and how any provision bears on your own contract is for your solicitor to say.

Section 14(1) names four kinds of IPP entity: a Minister, a Parliamentary Secretary, a public entity and a contracted service provider. Section 19 places the information privacy principles in Schedule 1, and section 20(1) says an IPP entity must not do an act, or engage in a practice, that is contrary to, or inconsistent with, one of them.

The public entities listed in section 6(1) include a department of the Public Service and a local government, regional local government or regional subsidiary, so a supplier can find both a state department and a council among the public entities it sells to.

Commencement, as the legislation records it

Section 2(c) leaves most of the Act to start on days fixed by proclamation, and allows different days for different provisions. 1 min read

A supplier is reached through its contract

Section 8 makes a business a contracted service provider when it is a party to a State services contract with a public entity and provides services to or on behalf of that entity under it. 1 min read

IPP 4, IPP 9 and privacy impact assessments

Two principles sit closest to what a web application test observes. 1 min read

What the 2026 WA Government Cyber Security Policy has an agency check in a supplier

The 2026 WA Government Cyber Security Policy says it specifies the measures WA Government entities are required to undertake to manage their cyber security risks, and that it supersedes the 2024 policy.

Its scope makes implementation mandatory for the WA public sector as defined in the Public Sector Management Act 1994 (WA), for entities listed in Schedule 1 of that Act and for Senior Executive Service entities in its Schedule 2.

Local government entities are outside the scope, although the policy encourages them to comply. Its requirements are written for those entities, and a supplier meets them as questions in a tender, a contract schedule or a review.

Set that beside the PRIS Act. A council is a public entity under section 6(1)(d) of the Act but sits outside the policy's scope, so a supplier with a department and a council as customers should not assume both are working from the same documents.

Clause 3.4: secure procurement and supply chain risk

Clause 3.4 says each entity must assess and manage cyber security risk as part of its procurement process for any goods or services that require suppliers or vendors to access the entity's data or systems. It applies to new procurements and where contract extension options allow requirements to be renegotiated or varied. Among the things it says an entity should assess in the supplier:

  • Information security maturity, including relevant security certifications or assurances. For Tier 1 Risk procurements, the policy says preference should be given to suppliers with current certification from an Infosec Registered Assessors Program (IRAP) qualified assessor, or equivalent similar industry certification (3.4(a)).
  • The supplier's ability to let the agency meet its own obligations under the policy, including reporting cyber security incidents to DGov within 6 hours of an incident being suspected or confirmed (3.4(b)).
  • Personnel security controls for access to entity data, including subcontractors, service providers and consultants (3.4(c)), and Artificial Intelligence security (3.4(d)).
  • Software security practices for software that is procured or developed in-house (3.4(e)).

Ownership at exit, shared responsibility and dynamic testing

Clause 3.4 goes on to say entities should ensure their information remains theirs for the duration of the contract and is securely removed, disposed of or transferred back on termination (3.4(g)), and that an adequate shared responsibility model exists between supplier and entity (3.4(h)).

Clause 3.13 covers an entity's own in-house development, which it says should attract the same process as risk assessment as procurement of bespoke software. Its items include sanitising sensitive production data used in non-production environments (3.13(c)) and integrating application security testing, including regular dynamic testing, into the development and deployment process (3.13(d)).

A test of a running application is dynamic testing at one point in time. Whether testing is regular and built into the release process is a fact about your development practice, which a single report cannot show.

Clause 5.1 has each entity report suspected or confirmed cyber security incidents to DGov within 6 hours. The clock is the agency's, and it explains why an agency may press a supplier on how soon it would hear about a suspected incident in the supplier's application.

One more limit applies to every row of the checklist. A report that references the OWASP Web Security Testing Guide and ASVS 5.0 is saying how the testing was organised. It is not a statement that the application meets the policy, the PRIS Act or any other WA instrument.

Data residency: Tier 1 information and access from outside Australia

Clause 3.5 of the policy says entities must not offshore information classified as Tier 1 Risk, and must assess and govern their offshoring arrangements with reference to the Office of Digital Government's Information Security Risk Self-Assessment Table.

The table, updated in August 2026, describes itself as a tool for an initial, high-level information security risk assessment that underpins next steps in contexts including procurement and data offshoring.

Its Tier 1 includes sensitive personal information as the PRIS Act defines it, and any information asset holding two or more of five kinds of personal information that it groups as a "digital identity": name, date of birth, Government ID number, residential address and financial information. A form that collects a name and a residential address reaches that line. For Tier 1, the table's next steps include:

  • Hosting in Australia, preferably in two different locations, with security controls in place for offshore backups or user access from offshore locations, and encryption at rest and in transit.
  • Evidence of annual or biannual independent assessment of the information security risks associated with the service being procured, with IRAP, ISO 27001, SOC2 and FedRAMP named in brackets after it.
  • Phishing-resistant multi-factor authentication, or the strongest form the entity's system supports.

Tier 2, and what a test can and cannot add

For Tier 2, the table says information can be hosted outside Australia, with a risk review if offshoring and, in its words, an assessment against Information Privacy Principle 9 when relevant provisions of the PRIS Act come into force. It strongly recommends limiting arrangements to the Five Eyes countries: Australia, New Zealand, the United States, the United Kingdom and Canada.

A web application test has little to say about residency. It does not show where a database, a backup copy or a support desk sits, and a report with no findings tells an agency nothing about location. Residency is answered from your hosting, backup and support contracts. A test adds two narrower things.

The sign-in tests record, role by role, whether a second factor was requested and whether any route, such as a direct API call, got past it. The access tests show whether a support or administrator role can reach more personal records than its job needs.

How the tester treats its own evidence is a separate question with its own answer. Clever Ops keeps test evidence encrypted in Australia, deletes it on the schedule its data handling terms set, and processes it outside Australia only if your statement of work approves that.

Builder, host or outside tester: whose evidence the agency is reading

The self-assessment table's Tier 1 line speaks of independent assessment, so who produced a report matters as much as what it found.

Some of what Clever Ops tests, it also built or runs. In that case the work is labelled a security review rather than an independent test, and the report names who built the system and who hosts it.

A security review earns its place before a launch or after a large change. Where the evidence has to be independent, get it from an outside provider that neither built nor runs the system.

Credentials and procurement status get read against the exact words the customer used. Clever Ops is not CREST accredited, so we refer that work to a provider that is. Clever Ops is not an IRAP assessor and does not carry out ISO 27001, SOC 2 or FedRAMP assessments.

The WA Government's ICT services common use arrangement, CUAICTS2021, lists testing services, including functional, integration, performance and security testing, in its Category 2, and organisations on its approved register of buyers may procure under it. Clever Ops is not a supplier under that arrangement, is on no government panel or supplier arrangement, and holds no government approval, endorsement or accreditation.

Where a procurement asks for any of those, the wording decides, and we refer the work to a provider that meets it.

Worked case: an invented Osborne Park permit portal with a department and a council as customers

An illustration written for this page.

Everything in it is made up: the company, both customers, the portal, the test and the findings. It is not a Clever Ops client or engagement, and it is here to show the checklist pulling apart what the evidence answers from what has to be answered elsewhere.

The portal, its data and the evidence on hand

An invented software company in Osborne Park runs an online permit application portal and its API at permits.lab.test. 1 min read

The department's five questions

The department's security schedule asks five things, and the company takes each one to its row in the checklist. 1 min read

The council's questionnaire

The council's questionnaire is shorter. 1 min read

A reply to the department that stays inside the evidence

"An outside provider that neither built nor hosts our permit portal tested it and its API on staging in September 2026 and reported three issues. 1 min read

Testing remotely on Perth time: the window, the stop contact and the handover

Section 4 of the Standard Time Act 2005 (WA) says standard time throughout Western Australia is eight hours ahead of Co-ordinated Universal Time.

Victoria's Summer Time Act 1972 defines standard time as ten hours ahead (section 2) and, for a summer period whose start and end are fixed by proclamation, sets summer time throughout the State one hour ahead of standard time (section 3(1)). The NSW Department of Communities and Justice's page on how time is regulated says daylight saving is not observed in Western Australia.

The gap between Gippsland and Perth therefore moves: two hours while both states keep standard time, and three hours while Victoria keeps summer time and Western Australia keeps its standard time.

Nobody needs to hold that in their head if every time is written down with its zone. These are the rules for the two parties to agree in the rules of engagement before the first request:

  • Write the test window in Perth time with its UTC offset, as a start and finish marked UTC+8, together with the dates it covers. The window follows your systems and your users, not where the tester sits.
  • Name a stop contact for every hour of the window, with those hours given in Perth time. If the window runs past that person's working day, name a second contact rather than letting the window outrun the cover.
  • Have the tester send a start message and a finish message, each stamped with the time and offset, and confirm any pause or stop in writing with the time and the last request sent.
  • Agree which time zone the tester's request log uses, so your team can match it line by line against your host's logs.
  • Book the handover, where the findings are walked through, in Perth time on every invitation, and have the report give dates and times with their offset.
  • If a window or the handover falls near the start or end of Victoria's summer period, restate the times in writing rather than relying on the usual gap.
  • Destructive actions are off by default for real people's accounts and records that existed before the test, and reset, lockout and deletion checks run only on test accounts and test records where the rules of engagement allow them.

Perth CBD, Joondalup, Fremantle and Midland

Businesses in the Perth CBD, Joondalup, Fremantle and Midland are served remotely from Gippsland, on the same terms as any other Australian client. In none of the four is there a Clever Ops office, staff member, street address or meeting room.

Frequently asked questions

No. The business is run from Gippsland in Victoria, with no office or staff anywhere in Western Australia. A Perth test reaches only the hostnames and API addresses listed in your signed authorisation, over the internet, and scoping, reporting and the retest follow the process used for clients elsewhere in Australia.

Section 14(1) of the PRIS Act names a contracted service provider as an IPP entity, and section 8(2) defines one by reference to a State services contract with a public entity. Section 130 applies the information privacy principles to the provider only where the contract includes a section 129 provision, and only to that extent. The OIC says that outside a State services contract the Act will not apply, although other laws such as the Privacy Act 1988 (Cth) may. Your solicitor can read your contract against these sections; this answer is general information rather than legal advice.

Compilation 00-g0-03 on the WA legislation site notes that Part 2 Division 6, sections 57 to 75, has not come into operation. The OIC says those provisions will commence from 1 January 2027, and the WA Government gives 1 January 2027 as the date agencies must start reporting all serious data breaches. The information privacy principles in Schedule 1 came into operation on 1 July 2026 under the Commencement Proclamation 2026.

No. Clever Ops is not a supplier under CUAICTS2021 or any other common use arrangement, is on no government panel, and holds no government approval, endorsement or accreditation. Where a procurement requires a CREST-accredited provider, the wording decides. Clever Ops is not CREST accredited, so we refer that work to a provider that is.

No report does that. The policy's requirements are written for WA Government entities. Clause 3.4 has an entity assess a supplier's information security maturity, including certifications or assurances, and for Tier 1 services the self-assessment table lists evidence of annual or biannual independent assessment, with IRAP, ISO 27001, SOC2 and FedRAMP in brackets. A web application test report is evidence about one application on one build, and whether it is enough for a procurement is the agency's decision.

Yes, both are done remotely. The website security audit, which Clever Ops calls a website security check, examines a public site from outside and fits sites where nobody signs in. A vulnerability assessment covers more ground across a website or web application, and each issue it turns up is confirmed and ranked. When people sign in, pay or see their own records, or a WA public sector customer is asking about access to personal information, a web application penetration test is the depth that answers the question.

In writing, in your time. The rules of engagement give the window in Perth time with its UTC offset, name a stop contact for every hour of it, say which zone the request log uses, and book the handover in Perth time. Victoria keeps summer time for part of the year, so the gap between Gippsland and Perth is not the same all year, and written times with offsets matter more than a remembered difference.

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.