Penetration testing locations: one remote web application service, compared across eight Australian cities
Clever Ops tests websites, web applications and APIs for businesses across Australia from its base in Gippsland, Victoria, and has no office in any of the cities below.
The selector on this page sets the eight city pages side by side: the clock a test window is written in, the state privacy and procurement documents a public sector customer may work from, what remote testing asks of you, and the invented case each page works through.
On this page
Pages in this section
8 pages
Penetration Testing in Melbourne
Clever Ops tests the websites, web applications and APIs that Victorian businesses run, working remotely from its base in Gippsland for clients in Greater Melbourne, Geelong, Ballarat, Bendigo and beyond. If a Victorian public sector customer has asked you for security evidence, the matrix on this page maps each likely question to the part of a test report that answers it, and to the parts it cannot.
Clever Ops tests the websites, web applications and APIs that Sydney businesses run, remotely from Gippsland, Victoria. If a NSW Government agency is one of your customers, the checklist on this page maps the questions it may put to you to the evidence a web application test can supply, and marks the questions a test cannot answer.
Penetration Testing in Brisbane
Clever Ops tests the websites, web applications and APIs that Brisbane businesses run, working remotely from Gippsland, Victoria. If a Queensland Government department, statutory body or council buys from you, the worksheet on this page takes each question it may send and shows what to put in scope, what a test report can show, where that evidence stops and who on your side has to answer.
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.
Penetration Testing on the Gold Coast
Clever Ops tests websites, booking systems and APIs for Gold Coast businesses remotely, from its base in Gippsland, Victoria. This page takes an invented Gold Coast attraction and turns the rules its ticketing system enforces, from timed entry and weather changes to reseller vouchers, gift cards, waivers and group check-in, into test cases, each with the account that runs it.
Penetration Testing in Adelaide
Clever Ops tests websites, web applications and APIs for Adelaide businesses from its base in Gippsland, Victoria, entirely remotely. If a South Australian public sector customer has sent you security questions, the checklist on this page traces each one to the state instrument behind it, the web application evidence that can answer it, the part no test can answer, and the person in your business who should.
Penetration Testing in Canberra
Clever Ops tests the websites, web applications and APIs that Canberra and Queanbeyan businesses run, working remotely from Gippsland, Victoria. If you supply a Commonwealth entity, the matrix on this page sorts the questions it may ask into those a web application test can answer and those that need an IRAP assessor, a panel supplier or another accredited provider, and names who answers each one in your business and in the agency.
Penetration Testing in Newcastle
Clever Ops tests websites, web applications and APIs for businesses in Newcastle and the Hunter, working remotely from Gippsland, Victoria. The worked case on this page is an invented manufacturing and freight portal used by two companies, with a test matrix that checks whether either company can see or change what belongs to the other.
Service-area selector: the eight city pages side by side
One row per city page, west to east by standard time: Perth, Adelaide, then the cities on Australian Eastern Standard Time, with Queensland first because it does not observe daylight saving, then New South Wales, the ACT and Victoria. Each cell restates what that city page says, no more strongly, and names each Act, policy or scheme as the page names it.
How to use itHide the instructions
"Not covered" means the city page does not deal with the point. The service, the conduct rules and the report are the same in every row, and every city is served remotely from Gippsland, Victoria. The page addresses in the last column are linked under "Pages in this section". General information, not legal advice.
8 rows
City page and the areas it names
State or territory
Perth: Perth CBD, Joondalup, Fremantle and Midland
- State or territory
- Western Australia
- Time zone and daylight saving, as the page states it
- Section 4 of the Standard Time Act 2005 (WA) puts standard time throughout Western Australia eight hours ahead of UTC. The NSW Department of Communities and Justice says daylight saving is not observed in Western Australia. The page puts the gap to Gippsland at two hours while both states keep standard time, and three while Victoria keeps summer time.
- Privacy notes on the page
- Privacy and Responsible Information Sharing Act 2024 (WA), the PRIS Act. Its information privacy principles came into operation on 1 July 2026. Where a State services contract includes a section 129 provision, section 130 applies them to the contracted service provider's acts and practices for the purposes of the contract, and only to that extent. The OIC says the notifiable information breach provisions will commence from 1 January 2027.
- Procurement, panel and accreditation notes
- The 2026 WA Government Cyber Security Policy, with local government outside its scope; the Information Security Risk Self-Assessment Table, whose Tier 1 lists evidence of annual or biannual independent assessment of the information security risks associated with the service being procured (IRAP, ISO 27001, SOC2, FedRAMP); and CUAICTS2021. Clever Ops is not a supplier under CUAICTS2021 and is on no government panel.
- What remote testing asks of you
- The window written in Perth time with its UTC offset, a stop contact for every hour of it, with a second contact where the window outruns the first, an agreed zone for the request log, and the handover booked in Perth time.
- Worked case on the page
- An invented Osborne Park permit portal with a department and a council as customers, backups copied offshore and a support contractor in New Zealand.
- Page address
- /web-security/locations/perth
Adelaide: Adelaide CBD, Norwood, Mawson Lakes and Port Adelaide
- State or territory
- South Australia
- Time zone and daylight saving, as the page states it
- ACST (UTC+9:30), and ACDT (UTC+10:30) from 2 am standard time on the first Sunday in October until 3 am summer time on the first Sunday in the following April. Adelaide clocks read 30 minutes behind Victorian clocks when both states are on standard time or both on summer time.
- Privacy notes on the page
- The Information Privacy Principles Instruction (PC012), headed Cabinet Administrative Instruction 1/89. Clause 5(A) says a contract for service that will necessitate disclosing personal information to a contracted service provider must include conditions so the Principles are complied with as if the provider were part of the agency, and provisions that enable audit and verification of compliance. Special condition S7 in the Special Conditions Clause Bank has a supplier comply with the Information Privacy Principles as if it were an agency, in undertaking its obligations under the agreement. State Records of South Australia says the Instruction does not apply to local governments and universities.
- Procurement, panel and accreditation notes
- The South Australian Cyber Security Framework (SACSF) V2.0, written for agencies; Ruling 6 records that version 2.0 removed the earlier statement that it applied to suppliers. Standard 4.16, addressed to agencies, covers public-facing web services, and at CAT-0 its control 11 says penetration tests must be performed prior to deployment and when any major change is made, through a qualified party. No South Australian Government panel lists Clever Ops.
- What remote testing asks of you
- Every time in the authorisation written with its zone and UTC offset, windows kept clear of the October and April changeovers, a stop contact and a backup, and the window and source IP addresses given to everyone who watches alerts for the service.
- Worked case on the page
- An invented Kent Town home-care scheduling app used by a department and a council, with the retest window restated after the move to summer time.
- Page address
- /web-security/locations/adelaide
Brisbane: Brisbane, Ipswich, Logan and Moreton Bay
- State or territory
- Queensland
- Time zone and daylight saving, as the page states it
- Not covered on the Brisbane page. Queensland time is on the Gold Coast row.
- Privacy notes on the page
- Information Privacy Act 2009 (Qld), the IP Act. Section 27(1) says an agency must comply with the Queensland Privacy Principles. Section 35(1) says an agency entering into a service arrangement must take all reasonable steps to ensure 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, in the cases section 35(2) sets out. The explanatory notes say commencement of the mandatory notification of data breach scheme was deferred for local government until 1 July 2026.
- Procurement, panel and accreditation notes
- IS18 version v10.0.0, which applies to all Queensland Government departments and strongly encourages local governments to apply it as recommended better practice; the Queensland Procurement Policy 2026; the QITC contracting framework; and the Managing Cyber Security in Procurement Guideline, which does not mention penetration testing. Clever Ops is on no standing offer arrangement or panel.
- What remote testing asks of you
- A signed authorisation listing the source IP addresses test traffic comes from, and five answers in writing from your customer: what kind of entity it is, the procurement threshold and impact level, its IP Act clause, any offshore storage, and any independence, certification or accreditation requirement.
- Worked case on the page
- An invented Toowong grants portal with a department and a south-east Queensland council as customers, where links to uploaded documents opened without a session.
- Page address
- /web-security/locations/brisbane
Gold Coast
- State or territory
- Queensland
- Time zone and daylight saving, as the page states it
- AEST (UTC+10), and daylight saving is not observed in Queensland. While New South Wales is on AEDT (UTC+11), from 2 am AEST on Sunday 4 October 2026 to 3 am AEDT on Sunday 4 April 2027, the Gold Coast is an hour behind it, and Victoria also moves to AEDT.
- Privacy notes on the page
- Not covered. The page is built on an industry case rather than state law. Queensland's privacy Act is on the Brisbane row.
- Procurement, panel and accreditation notes
- Not covered. Queensland procurement is on the Brisbane row.
- What remote testing asks of you
- The scope written in Queensland time, with AEST and AEDT side by side while daylight saving is on, blackout times such as gate opening and school holiday peaks, a stop contact on each side, a non-live payment account, and every message routed to a capture inbox.
- Worked case on the page
- An invented attraction whose ticketing rules, from timed entry and weather changes to reseller vouchers, gift cards, waivers and group check-in, become test cases.
- Page address
- /web-security/locations/gold-coast
Sydney: Sydney CBD, Parramatta, North Sydney and Macquarie Park
- State or territory
- New South Wales
- Time zone and daylight saving, as the page states it
- No zone named. The test window is written into the scope with its time zone. New South Wales daylight saving dates are on the Gold Coast row.
- Privacy notes on the page
- Names the Privacy and Personal Information Protection Act 1998 only as the NSW Cyber Security Policy lists it, and does not say what it requires. Clause 9 of the Core& One core terms says a Seller with access to Personal Information under the Agreement must not transfer it outside Australia or access it from outside Australia.
- Procurement, panel and accreditation notes
- The NSW Cyber Security Policy 2026 to 2027, whose requirement 1.10.3 is to have processes to monitor and assess third-party service providers' adherence to cyber security requirements, including using assurance reports, audits, test results or other evaluations, and which section 2.3 says is not mandatory for local government, among others; the ICT Purchasing Framework and the Core& One terms; and the ICT Services Scheme, category K03, security testing. Clever Ops is not a prequalified supplier on the scheme.
- What remote testing asks of you
- The agency's questionnaire word for word, which of your customers sit inside section 2.1 of the policy, your contract terms and any data location restrictions, how agency staff sign in, and whether a staging copy without agency records exists.
- Worked case on the page
- An invented Parramatta shift-rostering company answering an agency questionnaire when its last test predates a new API and one high-risk finding is not retested.
- Page address
- /web-security/locations/sydney
Newcastle: Newcastle and the Hunter
- State or territory
- New South Wales
- Time zone and daylight saving, as the page states it
- No zone named. The window is written down with its time zone. New South Wales daylight saving dates are on the Gold Coast row.
- Privacy notes on the page
- Not covered. The page leaves the New South Wales instruments to the Sydney page.
- Procurement, panel and accreditation notes
- Not covered beyond accreditation: where a contract or tender requires a CREST-accredited tester, Clever Ops is not CREST accredited, so we refer that work to a provider that is. New South Wales procurement is on the Sydney row.
- What remote testing asks of you
- A staging copy seeded with two test companies, production checks only when read-only or on test records and named in the authorisation, portal messages routed to inboxes and numbers the tester controls, and the window written down with its time zone and source IP addresses.
- Worked case on the page
- An invented Hunter supplier and freight portal shared by an engineering supplier and a road freight carrier, tested for separation between the two companies.
- Page address
- /web-security/locations/newcastle
Canberra: Canberra and the rest of the ACT, and Queanbeyan
- State or territory
- Australian Capital Territory, with Queanbeyan in New South Wales
- Time zone and daylight saving, as the page states it
- Not covered on the Canberra page.
- Privacy notes on the page
- Commonwealth law rather than ACT law: section 95B(1) of the Privacy Act 1988, which requires an agency entering into a Commonwealth contract to take contractual measures to ensure that a contracted service provider for the contract does not do an act, or engage in a practice, that would breach an Australian Privacy Principle if done or engaged in by the agency, and the Australian Government Agencies Privacy Code. ACT Government instruments are not covered.
- Procurement, panel and accreditation notes
- The Commonwealth Procurement Rules 17 November 2025, whose conditions for participation may include an accreditation or validation procedure. Clever Ops is not an IRAP assessor and is not on the Digital Marketplace or any other Commonwealth panel, standing offer or coordinated arrangement.
- What remote testing asks of you
- A signed authorisation listing the targets and source IP addresses, any data location clause from your Commonwealth contract, and a name for each role in the page's stakeholder-routing worksheet. Agency premises and networks are outside the service, and Clever Ops advertises no security clearance.
- Worked case on the page
- An invented Queanbeyan grants-portal firm tendering for a department whose conditions for participation require an IRAP assessment.
- Page address
- /web-security/locations/canberra
Melbourne: Greater Melbourne, Geelong, Ballarat and Bendigo
- State or territory
- Victoria
- Time zone and daylight saving, as the page states it
- Not covered on the Melbourne page. Victoria is the state Clever Ops works from.
- Privacy notes on the page
- Privacy and Data Protection Act 2014 (Vic), the PDP Act. Section 13(1)(j) applies Part 3 to a contracted service provider, but only in relation to its provision of services under a State contract which contains a provision of a kind referred to in section 17(2). Part 4, on protective data security, does not apply to a Council (section 84(2)).
- Procurement, panel and accreditation notes
- Buying for Victoria's information security guide, which names evidence from development and assessment activities such as penetration testing among the requirements agencies should include, and ranks a written report from a third party assessor among ways to assess a tenderer. Clever Ops is not on the cyber security contract, DGS-ICT-03-2023, or any other government panel.
- What remote testing asks of you
- A signed authorisation naming the targets and the source IP addresses test traffic will come from, and six questions settled with your Victorian customer before any evidence is collected.
- Worked case on the page
- An invented Ballarat field-inspection app supplier with a Part 4 agency and a regional council as customers.
- Page address
- /web-security/locations/melbourne
About this library
Eight service areas, one remote service
Clever Ops is a small Australian consultancy based in Gippsland, Victoria, working with businesses earning $1M to $50M in annual revenue.
Melbourne, Sydney, Brisbane, Perth, Adelaide, the Gold Coast, Canberra and Newcastle each have a page of their own, and Clever Ops has no office, staff or meeting room in any of them. Each one is served remotely, on the same terms as a client anywhere else in Australia. Scoping, testing, the report and the retest all happen at a distance, and no engagement includes a visit to your premises.
Distance suits this work because of what is being tested. A website, a web application or an API answers over the internet, so a test of it depends on written permission, test accounts for anything behind a login, and a named contact on your side, and none of those needs anyone in your building.
Work that is not reached through a browser or an API, such as office networks or physical security, is outside the service in every city.
The city pages exist because the paperwork around a test changes from state to state even when the test does not. Six of them read the privacy, cyber security and procurement documents a government customer in that state or the Commonwealth may work from, and show how each question reaches a supplier.
The Gold Coast and Newcastle pages take an industry case instead: ticketing rules for an attraction, and a portal two companies share. Three of the pages also plan a test window across a time difference.
What is the same in every city
Scope, conduct and the report do not change with your address.
A test for a business in Canberra and one for a business in Newcastle run on the same terms.
Anything your customers or staff reach through a browser or an API: marketing websites, through the website security check; WordPress sites and WooCommerce stores, through the WordPress security audit; custom web applications and their APIs, through the web application and API penetration test; apps made with AI builders, through the vibe-coded app security check; and AI chatbots and agents, through the AI chatbot and agent security test.
A security fix sprint and retests are offered alongside.
Larger and multi-tenant applications are scoped individually after a longer call, and very logic-heavy products, such as marketplaces, lending platforms and multi-tenant billing, may be referred to a larger firm.
Each exclusion ends in a referral, so you know where that work goes instead.
- Office networks, servers, Wi-Fi, Active Directory, staff devices, red teaming, phishing and physical tests go to a network or red team specialist.
- Managed IT, round-the-clock monitoring, incident response and malware cleanup go to a managed IT provider or an incident response specialist. A post-cleanup audit can follow.
- Denial-of-service, load and volumetric testing go to a load-testing specialist, with your host's written approval.
- Live Shopify storefronts and Laravel applications sit outside this service.
- Work that requires CREST goes elsewhere. Clever Ops is not CREST accredited, so we refer that work to a provider that is.
- PCI DSS scans and assessments go to a provider that holds those roles. Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor.
- An IRAP assessment goes to an IRAP assessor. Clever Ops is not an IRAP assessor.
- A certificate is not something a test produces. A report is evidence for a decision someone else makes.
Testing reaches only the targets named in an authorisation signed by the owner of each target. The authorisation also lists the source IP addresses test traffic will come from, so your team and your host can pick it out from an attack.
A staging copy that matches production is preferred. 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.
Evidence is stored encrypted in Australia, deleted on the schedule set in the data handling terms, and processed outside Australia only where your statement of work approves it.
The scope as tested; each finding with redacted evidence, its business impact and a fix; two ratings for each rated finding, a CVSS v3.1 score from 0.0 to 10.0 and a separate business-risk rating; negative results for the accounts and records tried; and coverage referenced to the OWASP Web Security Testing Guide and ASVS 5.0.
After the one consolidated retest, each finding is marked fixed, partially fixed, still reproducible or not retested.
If Clever Ops built or hosts the system, the work is a security review rather than an independent test, and the report says who built and who hosts it.
The framework references describe how the testing was organised. They do not say that an application meets a state Act, a state policy or a Commonwealth requirement, and no report can. That judgement belongs to the customer reading it.
How to use the service-area selector
The selector on this page is one table with a row for each city page.
Read across a row to see what that page covers, or down a column to compare the eight on one point. Each cell restates the city page at the strength the page states it, and names each Act, policy and scheme the way the page does. The full citations, the sources and the reasoning stay on the city page.
The rows run west to east by standard time: Perth on UTC+8, then Adelaide on UTC+9:30, then the cities on Australian Eastern Standard Time (UTC+10). Inside that last group, the two Queensland cities come first because Queensland does not observe daylight saving, then the two New South Wales cities, then Canberra, and Melbourne last, in the state Clever Ops works from.
Cities in the same state sit next to each other, so Brisbane can be read against the Gold Coast and Sydney against Newcastle.
"Not covered" means the city page does not deal with that point, not that the point never comes up in that state. Where another row covers it, the cell points to that row.
For the documents, read the row for your customer's government, not only your own city. The city pages read their state documents the way a supplier meets them, through its contract and the questions a government customer sends, so a Perth business supplying a Victorian agency gets more from the Melbourne row than the Perth one, and a supplier to a Commonwealth entity starts with Canberra wherever it is based.
The clock works the other way: the test window follows the systems being tested and the people watching them.
The city pages themselves are linked under "Pages in this section", and the last column gives each address.
What changes with the place
Three things differ by location: the clock, the privacy instrument a public sector customer works under, and how that customer buys.
Set side by side, the city pages show patterns in each that no single page can.
Four clocks appear across the pages. Section 4 of the Standard Time Act 2005 (WA) puts standard time throughout Western Australia eight hours ahead of UTC, and the NSW Department of Communities and Justice says daylight saving is not observed in Western Australia. Adelaide moves between ACST (UTC+9:30) and ACDT (UTC+10:30).
Queensland is on AEST (UTC+10), and daylight saving is not observed in Queensland; that covers Brisbane as well as the Gold Coast, though only the Gold Coast page says so. New South Wales, apart from Broken Hill and Lord Howe Island, and Victoria keep AEST and move to AEDT (UTC+11) for daylight saving.
The Gold Coast page gives the New South Wales dates for 2026 to 2027, from 2 am AEST on Sunday 4 October 2026 to 3 am AEDT on Sunday 4 April 2027.
Victoria's summer time runs for a period fixed by proclamation, and none of the eight pages gives its dates. The Gold Coast page lists the ACT on AEST, and no page covers daylight saving in the ACT.
The pages that deal with time each state the gap to the tester's clock in Gippsland. The Perth page puts it at two hours while both states keep standard time, and three while Victoria keeps summer time. The Adelaide page puts Adelaide 30 minutes behind Victorian clocks when both states are on standard time or both on summer time.
The Gold Coast page says the Gold Coast is an hour behind New South Wales during its daylight saving, and that the tester's clock in Victoria differs in the same way while it lasts.
All three ask for the same things: every time written with its zone, a named stop contact with the hours they can be reached written down, and the times restated when a window falls near or across a daylight saving change.
Five of the pages read the provision in a privacy instrument that deals with a government body's contracted service providers. The Sydney page names its state's Act without summarising it.
- Victoria: section 13(1)(j) of the Privacy and Data Protection Act 2014 (Vic) applies Part 3 to a contracted service provider, but only in relation to its provision of services under a State contract which contains a provision of a kind referred to in section 17(2).
- Queensland: section 35(1) of the Information Privacy Act 2009 (Qld) says an agency entering into a service arrangement must take all reasonable steps to ensure 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) limits that duty to arrangements where the provider will in any way deal with personal information for the agency, or where the services involve transferring personal information to the agency or providing services to a third party for it.
- Western Australia: where a State services contract includes a section 129 provision, section 130 of the Privacy and Responsible Information Sharing Act 2024 (WA) applies the information privacy principles to the contracted service provider's acts and practices for the purposes of the contract, and only to that extent.
- South Australia: the Information Privacy Principles Instruction (PC012) is headed Cabinet Administrative Instruction 1/89 and is also known as Premier and Cabinet Circular 12. Clause 5(A) says a contract for service that will necessitate disclosing personal information to a contracted service provider must include conditions so the Principles are complied with as if the provider were part of the agency, and provisions that enable audit and verification of compliance.
- New South Wales: the Sydney page names the Privacy and Personal Information Protection Act 1998 only as the NSW Cyber Security Policy lists it, and does not say what the Act requires. It quotes clause 9 of the Core& One core terms instead.
- Commonwealth: the Canberra page reads section 95B(1) of the Privacy Act 1988, which requires an agency entering into a Commonwealth contract to take contractual measures to ensure that a contracted service provider for the contract does not do an act, or engage in a practice, that would breach an Australian Privacy Principle if done or engaged in by the agency.
Two of the pages touch on how the two meet. The Perth page quotes the WA Office of the Information Commissioner: outside a State services contract the PRIS Act will not apply, but other laws, such as the Privacy Act 1988 (Cth), may. The Sydney page quotes clause 9 of the Core& One core terms, which defines Privacy Laws as the laws governing privacy as applicable in New South Wales and the Commonwealth.
Which laws reach your business is a question for your solicitor, with your contracts in hand. This is general information, not legal advice.
Five of the worked cases give the supplier a council as a customer beside a state agency. What the pages say about councils:
- Victoria: Part 3 of the PDP Act applies to a Council (section 13(1)(d)), but Part 4, on protective data security, does not (section 84(2)).
- Queensland: a local government is an agency under section 18(1) of the IP Act. The explanatory notes for the commencing proclamation say the mandatory notification of data breach scheme would commence on 1 July 2025, with commencement for local government deferred until 1 July 2026. IS18 strongly encourages local governments to apply it as recommended better practice.
- Western Australia: a local government is a public entity under section 6(1)(d) of the PRIS Act, but local government is outside the scope of the 2026 WA Government Cyber Security Policy, which encourages local government entities to comply.
- South Australia: State Records of South Australia says PC012 does not apply to local governments and universities.
- New South Wales: section 2.3 of the NSW Cyber Security Policy says it is not mandatory for local government, which may adopt it as a standard where appropriate.
- In each of the five cases, the supplier does not present the agency's instrument to the council as though it applied.
Each government buys through its own arrangements, and the New South Wales and Western Australian ones list security testing by name:
- Victoria: the Victorian Government's cyber security contract, DGS-ICT-03-2023, a closed panel with non mandatory conditions of use, giving access to suppliers that offer cyber tower products and services, which include endpoint protection, vulnerability management, application control and third party risk management.
- New South Wales: the ICT Services Scheme, whose category K03, security testing, includes penetration testing, web security testing and secure code reviews.
- Queensland: the QITC contracting framework, with buying through an Invitation to Offer or from a Standing Offer Arrangement.
- Western Australia: CUAICTS2021, which lists security testing among the testing services in its Category 2.
- South Australia: the Adelaide page reads GOVSEC 5 and the procurement framework's Records and Information Security Schedule, and names no testing panel.
- Commonwealth: standing offers and panels, with the Digital Marketplace named in the foreword of the Commonwealth Procurement Rules among the panels where the rules prioritise Australian SMEs, and conditions for participation, which may include an accreditation or validation procedure.
Clever Ops is on none of these arrangements. It is not on any government panel, standing offer, scheme or supplier arrangement, and it holds no government endorsement and no security certification or accreditation. Where a tender or contract requires a CREST-accredited tester, Clever Ops is not CREST accredited, so we refer that work to a provider that is.
Clever Ops is not an IRAP assessor either. Where the wording requires a panel supplier, an IRAP assessment or another credential, that wording decides, and the work goes to a provider that meets it.
Where the customer asks for recent test results and evidence that findings were fixed, a web application test can supply that evidence for the scope it covered.
What to settle before a scoping call, from any state
These come from reading the eight pages together.
Each one changes the scope, the evidence or the provider you need, and each is easier to settle in writing before the call than after the report.
- Who the customer is: a state department or agency, a council, a Commonwealth entity or a private business. That decides which row to read and which documents sit behind its questions.
- The exact wording of the questionnaire, tender or contract schedule, including anything that names a panel, a scheme, an accreditation, independence or a certification.
- What your contract or draft says in relation to the privacy provision on contracted service providers: a provision of the kind section 17(2) describes in a Victorian State contract, what section 35 describes for a Queensland service arrangement, a section 129 provision in a Western Australian State services contract, the conditions clause 5(A) of PC012 describes in South Australia, or section 95B contractual measures in a Commonwealth contract. Read it with your solicitor before you book a test.
- The time zone the test window will be written in, a stop contact with the hours they can be reached, and whether the window or the retest falls near a daylight saving change.
- Whether a staging copy holding only seeded test records exists, so no agency or customer records sit in front of the tester.
- Who built and who hosts the system, so the report can say whether the work is an independent test or a security review.
Frequently asked questions
No. Clever Ops is based in Gippsland, Victoria, and has no office, staff or meeting room in Melbourne, Sydney, Brisbane, Perth, Adelaide, the Gold Coast, Canberra or Newcastle. Each city is served remotely on the same terms, and no engagement includes a site visit.
Yes. The service is offered to businesses anywhere in Australia, and scoping, testing, the report and the retest work the same way. The city pages exist for the state documents and the clocks, so if your customer is a public sector body, read the page for its government, or the Canberra page for a Commonwealth entity.
No. Clever Ops is not on the Victorian cyber security contract, the NSW ICT Services Scheme, a Queensland standing offer arrangement, CUAICTS2021 in Western Australia, any South Australian Government panel or the Digital Marketplace, and it holds no government endorsement. Where a procurement requires a panel supplier, that work goes to a provider on the panel.
The page for your customer's government. Each city page reads its state documents the way a supplier meets them, through its contract and its customer's questions, so a Brisbane business supplying a South Australian department reads the Adelaide page, and a supplier to a Commonwealth entity reads the Canberra page. A Queanbeyan business supplying a New South Wales agency reads the Sydney page.
No report does that, and the city pages that read government documents each make the same point in their own terms. A report is evidence about one application, for the build and scope tested, for the customer to weigh in its own assessment, and whether it is enough is the customer's decision. This is general information, not legal advice.
In writing. The Perth, Adelaide and Gold Coast pages each have every time written with its zone, a stop contact named with the hours they can be reached, and the times restated when a window falls near or across a daylight saving change. The Perth and Adelaide pages also give each time its UTC offset.
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.