Penetration testing in Adelaide: remote web application testing and a South Australian supplier checklist
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.
On this page
South Australian supplier checklist and test-window planner
Find the row for the question in front of you. Each row names the topic and the South Australian instrument, clause or requirement it comes from, the question a South Australian public sector customer may put to a supplier, the web application evidence that answers it, what that evidence cannot answer, and who in your business owns the answer.
How to use itHide the instructions
The last rows plan a remote test window across ACST, ACDT and Victorian time, and the final row is the service-area guide. Instruments are cited in the versions current on 14 November 2026: PC012 effective May 2020, SACSF V2.0, Standard 4.16 V2.0 and the Records and Information Security Schedule version 1.0. They are addressed to the public sector; the rows show how their questions reach a supplier. General information, not legal advice.
21 rows
Topic and source
What the customer may ask you
Privacy instruction. PC012 clause 5(A), carried into a contract by a clause such as special condition S7
- What the customer may ask you
- "Will you handle personal information under the Information Privacy Principles as if you were part of our agency, and allow audit and verification?"
- Web application evidence that answers it
- None. The answer is the contract clause.
- What that evidence cannot answer
- A test report cannot accept a contract term, and says nothing about your privacy policy, staff training or how you collect personal information.
- Who in your business owns the answer
- Director who signs the contract, advised by your solicitor
Privacy instruction. PC012 clause 4(4): reasonable steps so personal information is securely stored and not misused
- What the customer may ask you
- "How do you stop people opening personal information in your application that they should not see?"
- Web application evidence that answers it
- Access tests between roles and between customer organisations: each finding with its evidence, the negative results for the accounts and records tried, and the retest outcome of every finding.
- What that evidence cannot answer
- Whether the steps are reasonable, which the agency judges. Backups, staff devices, email and hosting accounts sit outside an application test.
- Who in your business owns the answer
- Privacy contact, with the technical lead supplying the evidence
Privacy instruction. Special condition S7.2, or model clause 1.14: notice of unauthorised access or disclosure
- What the customer may ask you
- "How will you tell us if personal information is accessed or disclosed without authority?"
- Web application evidence that answers it
- None. A report can note logging gaps the tester observed, nothing more.
- What that evidence cannot answer
- Your notification process, who decides and how quickly it runs.
- Who in your business owns the answer
- Owner of your incident response plan
Procurement. SACSF policy statement 1.5 at Tier One: assurance from suppliers upon contract award. GOVSEC 5: identifying and mitigating the security risks a procurement creates, and security terms in contracts
- What the customer may ask you
- "Before we sign, give us what we need for our supplier risk assessment."
- Web application evidence that answers it
- The executive summary, the scope as tested and the findings table with retest outcomes, for the application and environment the agency will use, shared under a confidentiality agreement.
- What that evidence cannot answer
- A report on another product, an earlier build or another environment. The risk assessment itself is the agency's document.
- Who in your business owns the answer
- Bid lead, with the technical lead
Procurement. Policy statement 1.5 at Tier One: assurance periodically after award, including at expiry or termination
- What the customer may ask you
- "Show us during the contract that the controls are still in place."
- Web application evidence that answers it
- The retest ledger, marking each finding fixed, partially fixed, still reproducible or not retested on an identified build, with your dated plan to test again after a significant change.
- What that evidence cannot answer
- Releases after the retested build, and controls outside the application.
- Who in your business owns the answer
- Product owner
Procurement. Questionnaire template question 8.2
- What the customer may ask you
- "Is regular security testing, such as penetration testing, carried out on your IT environment? How often?"
- Web application evidence that answers it
- The test and retest dates, the scope as tested and the build named in each. Answer with what was tested and name what was not.
- What that evidence cannot answer
- The rest of your IT environment: office network, staff devices, email and cloud administration accounts. How often you test is a plan you set, not something a report shows.
- Who in your business owns the answer
- Technical lead
Procurement. Questionnaire question 5.2, and Guideline 3.0 data security controls
- What the customer may ask you
- "Are your systems patched, and do you run regular vulnerability scans?"
- Web application evidence that answers it
- The software versions the test observed, and any finding about outdated components, on the dates tested.
- What that evidence cannot answer
- Your patching process and scan schedule, which come from your own records.
- Who in your business owns the answer
- IT or hosting lead
Procurement. Standard 4.16 control 11, and policy statement 2.9 at Tier One
- What the customer may ask you
- "Was the release we will use penetration tested before deployment, and will it be tested after a major change?"
- Web application evidence that answers it
- The report and retest for the named build, with the scope as tested.
- What that evidence cannot answer
- The category the agency gives the web service, its testing program schedule, and whether it accepts your tester as a qualified party, a term the standard's text does not define. Those are the agency's decisions.
- Who in your business owns the answer
- Product owner, who controls which build ships
Procurement. Policy statement 1.5 at Tier Three; questionnaire question 8.1; Standard 4.16 control 14 at CAT-2
- What the customer may ask you
- "Provide independent assurance of your controls." or "Are your controls independently reviewed?"
- Web application evidence that answers it
- A report whose author neither wrote nor runs the application, with that fact stated in it. If Clever Ops is the builder or host, its work is labelled a security review and the report names the builder and host.
- What that evidence cannot answer
- Independence, when the builder or host did the testing. Assurance about controls beyond the application is also out of reach.
- Who in your business owns the answer
- Director, who chooses the provider
Procurement. A contract or tender term naming a credential or a panel. Questionnaire question 1.4 is a different question: it asks about the supplier's own security certification and its scope
- What the customer may ask you
- "Does your tester hold a recognised certification, accreditation or panel listing?"
- Web application evidence that answers it
- The provider's name and any accreditation or panel listing it holds. Clever Ops is not CREST accredited, so we refer that work to a provider that is, and it is on no government panel.
- What that evidence cannot answer
- A credential the provider lacks. If the customer's wording demands one, choose a provider that holds it before the test, not after.
- Who in your business owns the answer
- Procurement contact, reading the customer's exact wording
Evidence ownership. Records and Information Security Schedule, and model clause 1.1: official records stay with the public authority
- What the customer may ask you
- "Will any of our records end up with your tester, and who owns what the test produces?"
- Web application evidence that answers it
- The environment named in the scope. When the target is a staging copy holding seeded records only, the tester never sees agency records.
- What that evidence cannot answer
- Who receives your report and what the agency may do with it. Your contract with the agency and your agreement with the tester set that.
- Who in your business owns the answer
- Contract owner, advised by your solicitor
Evidence ownership. Guideline 2.0 on third parties; Standard Goods and Services Agreement clauses 16.1 and 21.1
- What the customer may ask you
- "Will our information go to anyone else, including a subcontractor?"
- Web application evidence that answers it
- The tester's data handling terms: what evidence is kept, with secrets and personal details redacted, and the list of test data left behind.
- What that evidence cannot answer
- Whether testing production needs the agency's written approval under your contract. Read those clauses before choosing production.
- Who in your business owns the answer
- Contract owner
Data handling. Guideline 3.0 data location, and Ruling 2.1 offshore storage and processing
- What the customer may ask you
- "Where is our data stored, backed up, logged and supported, and does any of it leave Australia?"
- Web application evidence that answers it
- For the test itself, the tester's data handling terms. Clever Ops evidence is stored encrypted in Australia, deleted on the schedule in those terms, and processed outside Australia only where your statement of work approves it.
- What that evidence cannot answer
- Where your hosting, backups, logs, monitoring and support staff hold or reach the data. Those come from your providers' contracts, and the offshore decision is the agency's.
- Who in your business owns the answer
- Technical lead, with each provider contract in hand
Data handling. Standard 4.16 API control 18: production data in non-production deployments
- What the customer may ask you
- "Will real agency data be used in testing?"
- Web application evidence that answers it
- The environment named in the scope, the seeded test accounts and the list of test data left behind.
- What that evidence cannot answer
- How your own developers use production data outside production.
- Who in your business owns the answer
- Development lead
Data handling. Guideline 3.0 exit obligations; Records and Information Security Schedule on contract end
- What the customer may ask you
- "What happens to our information when the contract ends?"
- Web application evidence that answers it
- None for your service. For the test, the deletion schedule in the data handling terms.
- What that evidence cannot answer
- Return, deletion and sanitisation of the agency's information, which belong in your exit plan.
- Who in your business owns the answer
- Operations lead
Incidents. Guideline 3.0 incident notice within 24 hours; PC042 directions to suppliers
- What the customer may ask you
- "Will you advise us of an incident within 24 hours, and follow directions during a cyber incident?"
- Web application evidence that answers it
- None. A report does not show how you detect, notify or respond.
- What that evidence cannot answer
- Your incident plan, and what your contract says you supply. PC042 says suppliers won't be directed outside what they are contracted to supply.
- Who in your business owns the answer
- Owner of your incident response plan, with the contract owner
Test window. Standard Time Act 2009 (SA) s 3; Daylight Saving Act 1971 (SA) s 3(1); Summer Time Act 1972 (Vic) ss 2 and 3(1)
- What the customer may ask you
- "When will test traffic reach our service, in our time?"
- Web application evidence that answers it
- The window in the authorisation, written in ACST (UTC+9:30) or ACDT (UTC+10:30), whichever applies on each date, with the tester's local time beside it. When both states are in the same season, Victorian time is 30 minutes ahead.
- What that evidence cannot answer
- Alerts from anyone not told about the window. Give the window, its zone and the source IP addresses to each party that monitors the service.
- Who in your business owns the answer
- Technical lead
Test window. Daylight Saving Regulations 2024 (SA) reg 4
- What the customer may ask you
- "What if testing falls on the weekend the clocks change?"
- Web application evidence that answers it
- A window kept clear of 2 am on the first Sunday in October and 3 am on the first Sunday in April, or written in UTC if it must cross one. Victoria's period is fixed by proclamation, so each side checks its own government's notice.
- What that evidence cannot answer
- Nothing about the application. This row exists so that nobody misreads the window.
- Who in your business owns the answer
- Technical lead, with the tester
Test window. Rules of engagement: pause, stop and restart
- What the customer may ask you
- "Who can stop testing, and when can we reach them?"
- Web application evidence that answers it
- The named stop contact and backup, the hours each can be reached written in their own local time, the stop phrase and its valid channels, and the person who approves a restart.
- What that evidence cannot answer
- How long anything takes. Dates and durations are set in your statement of work.
- Who in your business owns the answer
- Technical lead, with a business backup
Test window. Report handover and retest
- What the customer may ask you
- "When do we walk through the report, and does the retest window still apply after the clocks change?"
- Web application evidence that answers it
- A walkthrough time written in both zones, and a retest window restated in the variation when it falls in a different season from the test.
- What that evidence cannot answer
- Fixes shipped after the retested build.
- Who in your business owns the answer
- Product owner
Service area. Adelaide CBD, Norwood, Mawson Lakes and Port Adelaide
- What the customer may ask you
- "Where is your tester based, and will anyone come to our site?"
- Web application evidence that answers it
- Clever Ops is based in Gippsland, Victoria, and serves these areas remotely. The signed authorisation lists the source IP addresses test traffic comes from.
- What that evidence cannot answer
- Anything that needs a site visit or physical access, which is outside the service.
- Who in your business owns the answer
- Whoever reads the procurement documents
What Clever Ops tests for Adelaide businesses, and how
Clever Ops is a small Australian consultancy in Gippsland, Victoria, for businesses with $1M to $50M in annual revenue.
Its testing covers what customers reach through a browser or an API: marketing websites, WordPress sites and WooCommerce stores, custom web applications and their APIs, apps made with AI builders, and AI chatbots and agents. For a business in Adelaide, scoping, testing, reporting and the retest all happen remotely. Clever Ops has no office or premises in South Australia and nobody on its staff is based there.
Cyber security covers far more ground than this service does. Managed IT, monitoring around the clock, incident response, phishing simulations and tests of office networks, servers, Active Directory or staff laptops are all outside this service. The web application is where the work ends. For the rest, start with a managed IT provider, or with a specialist in network testing.
Inside that boundary there are four depths, and the right one depends on what your application does and who will read the result.
- Website security audit. On this site it is called a website security check: the public face of a site, examined without signing in. Certificates and transport settings, response headers, cookie flags, reachable admin paths and files, and software versions the site gives away. It fits sites where nobody but staff logs in.
- Vulnerability assessment. A broad sweep across a site or application for recognised classes of weakness, each one confirmed, then ranked so somebody owns the fix. It stops short of trying to defeat the application's rules.
- Web application penetration test. The tester signs in as every role in scope and tries to make the application break its own rules: opening another customer's records, changing what a role should only read, or calling the API directly to skip a check the screens enforce. The access row in the South Australian checklist on this page relies on evidence at this depth.
- Secure code review. Read-only access to the code, added when the riskiest logic sits in files that can be read directly.
South Australia's privacy instruction, cyber framework and procurement rules, read as a supplier
The documents below are circulars, frameworks, standards, guidelines and procurement policies, and none of them is an Act of Parliament.
PC012, the Cyber Security Framework with its rulings, Standard 4.16, Guideline 3.0 and the questionnaire template, GOVSEC 5 and the procurement schedule are addressed to the state's public sector, and the clause bank, model terms and standard agreement supply contract wording. A supplier meets that first group through contract clauses and supplier questionnaires.
Two documents also speak to suppliers directly: SACSF Guideline 2.0 says it will support suppliers who access, process, store or otherwise handle digital information on behalf of an agency, and PC042 applies to organisations or individuals providing services to government agencies as well as to public sector employees.
This section reads all of them from the supplier's side. Every document was opened on 14 November 2026 and is quoted from the version current on that day.
This is general information, not legal advice. Whether a clause reaches your business, and what it means for you, are questions for your solicitor and your customer.
South Australia's public sector privacy rules are an administrative instruction, not an Act. The document is headed Cabinet Administrative Instruction 1/89, also known as the Information Privacy Principles Instruction and as Premier and Cabinet Circular 12, and the version on the Department of the Premier and Cabinet (DPC) site is effective from May 2020, with its latest amendment dated 4 May 2020.
DPC says Premier and Cabinet circulars are used to establish whole of government policies, and that once a circular has been approved by Cabinet it must be followed by all government departments.
Clause 2(2) applies the Instruction, subject to any contrary determination by Cabinet, to the public sector agencies defined in section 3(1) of the Public Sector Act 2009, and clause 2(3) excludes the agencies in its schedule, among them the Independent Commissioner Against Corruption and Return to Work South Australia. State Records of South Australia adds that the Instruction does not apply to local governments and universities.
For security, the principle to read is clause 4(4): an agency should take such steps as are, in the circumstances, reasonable to ensure that personal information in its possession or under its control is securely stored and is not misused. Clause 4 makes each agency's principal officer responsible for seeing the Principles implemented, maintained and observed.
Two clauses reach a contractor. Subject to clause 5(A), clause 5(c) deems an act done or a practice engaged in by a person employed by, or in the service of, a contractor, in the course of a contract for services with an agency, to have been done or engaged in by the agency, and personal information disclosed to that person to have been disclosed to the agency.
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.
A contracted service provider, in clause 3(1), is a third party that contracts with an agency to provide goods or services the agency needs for its operations.
Clause 5(A) explains why a supplier meets the Instruction through paperwork. The Special Conditions Clause Bank published on Buying4SA includes clause S7, Privacy, for use where the supplier will have access to the personal information of any person. S7.1.1 has the supplier comply with the Information Privacy Principles as if it were an agency, S7.1.2 has it allow and cooperate with any audit or investigation the government party deems necessary to verify that, and S7.2 has it promptly notify the government party of any actual or threatened disclosure of, or unauthorised access to, personal information.
The same clause bank says that for a procurement of ICT products or services the agency should contact the Crown Solicitor's Office, so an ICT contract may carry wording of its own.
The Crown Solicitor's Office has also developed model terms for the Instruction and records management, which State Records of South Australia publishes. In the long version, clause 1.1 has the supplier agree that the customer keeps ownership of all official records arising from the services, clause 1.14 has it notify unauthorised disclosure of official records or personal information as soon as practicable, and clause 3 lets the customer appoint someone, at its own cost, to audit compliance at any time.
The South Australian Cyber Security Framework (SACSF) V2.0 was approved by Cabinet on 23 June 2025 and is maintained by the Cyber Security Directorate of the Office of the Chief Information Officer, in the Department of Treasury and Finance. Section 2.4 applies it to public sector agencies as defined in section 3(1) of the Public Sector Act 2009, and to any other person or organisation generally subject to the direction of a Minister of the Crown.
Ruling 6 records that version 2.0 removed the earlier statement that the framework applied to suppliers and to non-government personnel providing services to agencies, and the procurement framework's Records and Information Security Schedule tells public authorities that the SAPSF and SACSF apply to government only and not to external entities such as suppliers.
The framework still shapes what an agency asks you. Policy statement 1.5 says cyber security requirements must be included in all agreements with all suppliers handling government data throughout the procurement lifecycle. At Tier One, the baseline every agency implements, agencies obtain assurance from suppliers that they have implemented controls to meet their cyber security obligations upon contract award and periodically thereafter, including at contract expiry or termination.
At Tier Three that becomes independent assurance, at contract award and annually, for critical services, services with high availability or integrity requirements, services storing sensitive information or higher, or services with a moderate or higher risk profile.
Two statements cover testing inside agencies. Policy statement 2.9, at Tier One, has vulnerability assessments and penetration tests conducted by suitably skilled personnel before systems are deployed, after significant changes, and at least annually or as specified by the system owner, and has outsourced software development supervised. Policy statement 2.7, at Tier Two, includes vulnerability assessments and penetration tests throughout a system's lifecycle in the agency's vulnerability management strategy.
The framework's standard written for web services is SACSF Standard 4.16, the Secure Web Service Standard, version 2.0, approved by the CIO Steering Committee on 5 August 2025. It is addressed to agencies and covers public-facing web services, including those hosted by third parties or cloud providers, and including web applications developed or modified by agencies or third parties.
Web services reachable only from government networks and accounts are excluded. Each agency must determine and document a category for each web service: CAT-0, CAT-1 or CAT-2.
Processing, storing or transmitting personal information or OFFICIAL: Sensitive information is one of the CAT-2 criteria, and meeting any one criterion is enough.
Control 11 deals with penetration testing. At CAT-0, penetration tests must be performed on the web service prior to deployment and when any major change is made, to detect exploitable vulnerabilities, through a qualified party, and findings are remediated under the agency's policy. CAT-1 adds periodic tests on the agency's testing program schedule, and CAT-2 periodic internal or external tests no less than annually.
The standard's text does not define a qualified party, so what the agency accepts is the agency's call. Control 14 at CAT-2 says code reviews should be performed by an independent third party before implementation.
In the API section, control 18 says production data should not be used with non-production API deployments, and control 20 says to avoid disclosing software package version numbers in API responses.
SACSF Guideline 2.0 is written for suppliers who handle digital information for an agency. It says suppliers should provide information that lets the agency complete a risk assessment, and are expected to provide evidence that the controls documented in the contract or service level agreement are implemented and effective, before the engagement starts and periodically after it, as the contract sets out.
It also says agency information must not go to any third party, sub-contractors included, without the agency's express written approval. Guideline 3.0, written for agencies, lists the contract terms they consider: where every copy of agency data is held, including backups and the support staff who can reach it, a right to audit, notice of incidents within 24 hours, encryption, vulnerability management and patching, multi-factor authentication, and return and sanitisation of data at exit.
The Office of the Chief Information Officer publishes a Third Party Security Questionnaire template, provided for agencies to customise to their needs. Its response column asks for a description of each control and any evidence. Question 8.1 asks about formal and independent reviews of cyber security controls, and question 8.2 asks whether regular security testing, such as penetration testing, is carried out on your IT environment, and how often.
SACSF Ruling 2.1 governs offshore data. Information classified OFFICIAL: Sensitive or PROTECTED, or with an integrity or availability classification of ABSOLUTE, may be stored or processed offshore only after a risk assessment that the agency's Accountable Authority documents its acceptance of. The ruling's definition of an ICT arrangement includes back-up or log storage, system monitoring, and remote support that accesses data.
GOVSEC 5, a policy in the South Australian Protective Security Framework (SAPSF), seeks to make security risk a considered element in all procurement. Its supporting requirements have agencies identify and mitigate the security risks a procurement creates, put security terms in contracts, monitor the contractor and its subcontractors through the contract, and manage security when the contract ends. Its page gives a review date of 30 November 2022.
The Records and Information Security Schedule, version 1.0, effective 1 September 2026, is part of the state's procurement framework. It says outsourcing does not transfer operational risk from the State, and that accountability for the security of records and information stays with the public authority.
It has public authorities document arrangements for ownership and custody, noting that ownership of official records remains with the public authority, for disposal and return at contract end, for monitoring and auditing the supplier's information management, and for the supplier to notify any actual or suspected security incident affecting government information or the systems used to deliver the contract.
Premier and Cabinet Circular PC042, Cyber Security Incident Management, effective from September 2024, applies to public sector employees and to organisations or individuals providing services to government agencies. During an incident managed under its framework, the State Controller and the government's Chief Information Security Officer, or their deputies, can direct workers of a supplier to act in certain ways, and the actions listed include stopping any work or operation.
A footnote says suppliers won't be directed to undertake action outside of what they are contracted to supply.
Sorting a South Australian request before you gather evidence
A questionnaire from a South Australian customer can mix privacy, procurement and cyber framework questions on one page.
Work out where each one comes from before deciding what evidence it needs.
- Who is the customer? A public sector agency under the Public Sector Act 2009, one of the agencies PC012's schedule excludes, a council or a university. State Records says the privacy instruction does not apply to the last two, so their questions come from somewhere else.
- Which document is in front of you? The agency's copy of the Third Party Security Questionnaire, a contract security schedule, special condition S7, or wording drafted with the Crown Solicitor's Office. Answer in that document's own terms.
- Which category has the agency given the web service under Standard 4.16, and what classification has it given the information you will hold? The agency decides both, and they set how often it will ask for a test and what Ruling 2.1 says about offshore storage.
- Will personal information be disclosed to you? If so, clause 5(A) of PC012 points to privacy conditions and audit rights in the contract, and those need your solicitor before they need a tester.
- Does the wording ask for independent assurance, a qualified party or a named credential or panel? Settle what the agency will accept in writing before you book anyone.
- Which application, build and environment will hold the agency's data? A report speaks for that system and nothing else.
Which parts of a test report a South Australian reviewer can use
Any web application report speaks for a single application, environment and build, inside the scope both parties signed.
Six of its parts carry weight with a South Australian reviewer.
- The scope as tested, naming the hostnames, roles, environment, build and testing dates, and listing what was excluded. It answers "which system does this evidence cover?"
- Each finding with its evidence, its effect on the business and the fix, and each rated finding scored twice: CVSS v3.1 for technical severity, on its 0.0 to 10.0 scale, and a business-risk rating kept apart from it.
- Negative results, recorded for the accounts and records tried. They support "tests between two customer organisations found no way across on the records tried", not "our customers' data is separated".
- The retest ledger, marking each finding fixed, partially fixed, still reproducible or not retested on an identified build after the one consolidated retest.
- Redacted evidence, with secrets and personal details removed, and a list of any test records the testing created that your team should delete.
- Where Clever Ops built the system or hosts it, a line in the report saying so.
Where a report stops
Question 8.2 of the questionnaire template asks about testing of your IT environment. A web application test covers the application and its API, so answer with what was tested and name what was not: the office network, staff devices, email and cloud administration accounts.
Questions about patching cadence, vulnerability scanning, multi-factor authentication for your own staff, incident response and data retention are answered from your own records. A test report can mention what it observed on those topics on the day, and that is all.
The report's coverage is mapped to the OWASP Web Security Testing Guide and the Application Security Verification Standard 5.0. Those references describe the method. Whether the application satisfies Standard 4.16, the SACSF or any other South Australian instrument is a judgement the agency makes, and no tester's report can make it for them.
Evidence ownership and data handling when agency information is involved
Two sets of records meet in a supplier's test.
One is the agency's information inside your application. The Records and Information Security Schedule has agencies document that ownership of official records stays with them, and the model terms say the same in clause 1.1. The other is the test evidence about your application: requests, responses, screenshots and the report.
Who receives the report, and what the agency may do with it, are set by your contract with the agency and your agreement with the tester, so agree both in writing before the test starts.
The cleanest way to keep the first set away from the second is to test a staging copy that holds nothing but seeded records. Standard 4.16's API section says production data should not be used with non-production API deployments, and seeded data means no agency records are in front of the tester at all.
If production is the only target, read special condition S7, Guideline 2.0's line on third parties and your contract's confidentiality and subcontracting clauses with your solicitor first.
In the Standard Goods and Services Agreement, version 2.2, clause 16.1 says that, subject to the rest of clause 16, neither party may disclose the other's Confidential Information except as genuinely and necessarily required for the purpose of the agreement, and clause 21.1 requires the government party's written permission before any subcontractor other than an approved one is engaged. Whether a tester counts as either is a question for that solicitor.
Agencies following Guideline 3.0 ask where data is held, and Ruling 2.1 adds the question of whether any of it goes offshore. For the test itself, Clever Ops 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.
For your own service, list the primary store, backups, logs, monitoring and support access, including any that sit overseas, and let the agency make the call the ruling gives it.
Independence, panels and accreditation in a South Australian bid
Several South Australian documents turn on who did the checking.
Policy statement 1.5 at Tier Three speaks of independent assurance from suppliers, question 8.1 of the questionnaire template asks about formal and independent reviews, and Standard 4.16 asks for penetration tests through a qualified party and, at CAT-2, code reviews by an independent third party.
Clever Ops also designs, builds and hosts sites and applications for clients. Where it is asked to test one of those, it calls the work a security review, never an independent test, and the report names the builder and the host.
That review can be the quickest way to fixes before a release. An agency asking for independent assurance needs something else: a tester who neither wrote the application nor runs its servers.
Read every credential or panel question against the customer's exact words. Clever Ops is not CREST accredited, so we refer that work to a provider that is. It holds no security certification or accreditation. No South Australian Government panel lists it, it belongs to no other government panel either, and the state has not endorsed it.
Planning a remote test window across Central and Eastern time
Remote testing for an Adelaide business means two clocks.
South Australia's Standard Time Act 2009, section 3, sets standard time at 9 hours and 30 minutes ahead of Co-ordinated Universal Time (UTC). Section 3(1) of the Daylight Saving Act 1971 sets summer time one hour ahead of that, and regulation 4 of the Daylight Saving Regulations 2024 sets the summer period from 2 am standard time on the first Sunday in October until 3 am summer time on the first Sunday in the following April.
The NSW Department of Communities and Justice names the two: Australian Central Standard Time (ACST), UTC + 9.5 hours, and Australian Central Daylight Time (ACDT), UTC + 10.5.
Victoria's Summer Time Act 1972 defines standard time as 10 hours ahead of UTC (section 2), with summer time one hour ahead during a period fixed by proclamation (section 3(1)). The same NSW page lists Victoria on Australian Eastern Standard Time (AEST), UTC + 10, moving to Australian Eastern Daylight Time (AEDT), UTC + 11.
On those offsets, Adelaide clocks read 30 minutes behind Victorian clocks whenever both states are on standard time, or both are on summer time: 19:00 ACST is 19:30 AEST, and 19:00 ACDT is 19:30 AEDT.
This page does not quote Victoria's proclamation, so check each state's changeover against its own government's notice when a window falls near the first Sunday in October or April.
Both states' Acts also say which time a reference to time in a contract or other instrument is taken to mean, unless a contrary intention is expressed (section 4 of each South Australian Act, and section 4 of Victoria's). A test window should not depend on that. These are the rules the two parties set, and the planner rows in the checklist turn them into questions and answers.
- Write every time in the authorisation and the rules of engagement with its zone and UTC offset, such as "19:00 to 22:00 ACST (UTC+9:30)", and give the tester's local equivalent beside it.
- Keep a window clear of 2 am on the first Sunday in October and 3 am on the first Sunday in April, when South Australian clock time changes. If it has to cross one, write it in UTC.
- Restate the retest window if it falls in a different season from the test. A window agreed in ACST does not carry over unchanged into ACDT.
- Name the stop contact and a backup, and write the hours each can be reached in their own local time. The stop phrase, the channels it is valid on and the person who approves a restart go in the rules of engagement.
- Give the window, its zone and the tester's source IP addresses to everyone in South Australia who watches alerts for the system: your team, the host's support desk and any agency with monitoring on the service.
- Set the report walkthrough and any handover call in both zones. Dates and durations are set in your statement of work.
Worked case: an invented home-care scheduling company in Kent Town
Everything in this case is made up to illustrate the checklist: the company, both customers, the questionnaire and the test report.
None of it describes a Clever Ops client or engagement.
An invented software company in Kent Town runs a web application and API, at visits.lab.test, that schedules home-care visits and stores the notes carers write after each one. A South Australian Government department uses it for its case workers, and a metropolitan council's community services team uses it for its own clients.
Both hold personal information in it. The company hosts the application in an Australian region of its cloud provider, and its error-tracking service stores application logs in the United States.
Its evidence is one external test, run by a provider that neither built nor hosts the application. Three roles were in scope (case worker, coordinator and administrator), each with accounts in both customer organisations, against the application and API on a staging copy filled with seeded records. Source code, the marketing site, the office network, staff laptops and email were left out.
The test ran on weekday evenings in August 2026, written in the authorisation as 19:00 to 22:00 ACST (UTC+9:30). The company's on-call developer was the stop contact, with her hours written in the same zone.
- HV-01, high: a case worker could open visit notes for clients outside her caseload by changing a client number in an API request. Retest on build 5.8.2: fixed.
- HV-02, medium: a council coordinator could add a user to the department's workspace through an invitation endpoint that no screen exposed. Retest: partially fixed; the endpoint now checks the workspace for new invitations, and the change for pending ones is booked into the next release.
- HV-03, low: API error responses named the web framework and its version, the disclosure Standard 4.16's API control 20 says to avoid. Retest: fixed.
- Negative result: exporting visit notes was tried from every role in both organisations, and no export returned another organisation's notes.
The department's questionnaire was its own customised copy of the Third Party Security Questionnaire, and its contract renewal included special condition S7. The company sorted each item to a checklist row before writing anything.
- Special condition S7 (the clause 5(A) row). The director accepted it after advice from the company's solicitor, and noted the audit right in S7.1.2. No test evidence was involved.
- Question 8.2 on testing of the IT environment (the questionnaire row). The answer gave the test and retest dates, the build retested and the scope, and said plainly that the office network, laptops and email were not tested.
- Question 8.1 on independent review (the independence row). The answer said the tester did not build or host the application.
- The web service category (the Standard 4.16 row). The company asked the department which category it had assigned. The department said CAT-2, because the service holds personal information, so the company put its next test date in the answer and committed to a test after the next major release.
- Data location (the Guideline 3.0 and Ruling 2.1 row). The answer listed the hosting region, backups, support access and the error logs held in the United States, and asked the department to confirm whether it accepted that arrangement or wanted the logs moved. The decision is the department's to make.
- Patching and scanning (question 5.2). Answered from the hosting provider's update records and the company's scan reports, not from the test.
State Records says the privacy instruction does not apply to local governments, so the company answered the council's shorter questionnaire in its own terms and did not cite PC012 back to it. It used the same evidence: the scope, all three outcomes including HV-02 as partially fixed, the export negative result, and the list of what the test did not cover.
The retest fell in October 2026, after the first Sunday of the month, when South Australia had moved to summer time. The company restated the window in the variation as 19:00 to 22:00 ACDT (UTC+10:30) instead of reusing the August wording, gave the new window and the source IP addresses to its host's support desk and to the department's monitoring contact, and asked the tester to repeat each time in UTC in its confirmation.
"An external provider that did not build or host our visit scheduling application tested it and its API in August 2026, on a staging copy holding seeded records only. The provider reported one high, one medium and one low-risk issue. When build 5.8.2 was retested in October 2026, the high and low-risk issues were confirmed fixed; the medium-risk issue was confirmed partly fixed, and the remaining change is booked into our next release. Source code, our office network, staff devices and email were outside the test."
Service-area guide: Adelaide CBD, Norwood, Mawson Lakes and Port Adelaide
Each entry says how the area is served, and that is all it says.
None of the four has a Clever Ops office, address or staff member, and site visits are not part of any engagement.
- Adelaide CBD: served remotely from Gippsland, Victoria.
- Norwood: served remotely from Gippsland, Victoria.
- Mawson Lakes: served remotely from Gippsland, Victoria.
- Port Adelaide: served remotely from Gippsland, Victoria.
Frequently asked questions
No. Clever Ops is based in Gippsland, Victoria, and has no office, premises or staff in South Australia. Adelaide businesses are served remotely, and the signed authorisation records each test window with its time zone.
No. No South Australian Government panel lists Clever Ops, nor does any other government panel, and the state has not endorsed it. It holds no security certification or accreditation. Clever Ops is not CREST accredited, so we refer that work to a provider that is.
Clause 2(2) of PC012 applies the Instruction to the public sector agencies defined in section 3(1) of the Public Sector Act 2009. For contractors, 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, with audit and verification provisions. What reaches a supplier is therefore in its contract, such as special condition S7. Read it with your solicitor. This is general information, not legal advice.
Section 2.4 of SACSF V2.0 applies it to public sector agencies and to persons or organisations generally subject to the direction of a Minister of the Crown. Ruling 6 records that version 2.0 removed the earlier statement that it applied to suppliers, and the Records and Information Security Schedule says the SAPSF and SACSF apply to government only and not to external entities such as suppliers. Agencies carry requirements into supplier contracts under policy statement 1.5, so read your contract for what applies to you.
No test report can say that. Standard 4.16 is addressed to agencies and spans controls from backups and logging to supplier management and cryptography, as well as API security. Its control 11 calls for penetration tests before deployment and after any major change, through a qualified party, and the agency decides the category of the web service and what evidence it accepts. A report is evidence about one application and build for the agency to weigh.
Write every time in the authorisation with its zone and UTC offset, such as 19:00 ACST (UTC+9:30), and the tester's local time beside it. Adelaide clocks read 30 minutes behind Victorian clocks whenever both states are on standard time or both on summer time. Keep windows clear of South Australia's changeovers on the first Sunday in October and April, and restate a retest window that falls in a new season.
Both are offered, delivered remotely. The website security audit, which this site calls a website security check, examines the public side of a site without an account, so it fits sites where only staff sign in. A vulnerability assessment covers a whole site or application, confirming and ranking each weakness it finds. Once customers or agency staff sign in to see records that are theirs alone, choose a web application penetration test, because only that depth tests who can open what.
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.