Penetration testing in Brisbane: web application testing for Queensland suppliers, done remotely
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.
On this page
Queensland agency and supplier worksheet
Find the row for the question in front of you. Each row names the Queensland source behind it, the question an agency may put to you, what to put in scope, the evidence a web application test can give, what that evidence cannot answer, and who on your side owns the answer.
How to use itHide the instructions
The sources are addressed to Queensland public sector entities, and the rows show how their questions reach a supplier. IP Act sections follow the reprint current as at 29 October 2026, IS18 follows version v10.0.0, and the guideline follows version 1.1. General information, not legal advice.
18 rows
Where the question comes from
What a Queensland agency may ask you
IP Act s 35(1) and (2) and s 36(1): an agency entering into a service arrangement must take all reasonable steps to ensure the contracted service provider is required to comply with chapter 2, parts 1 and 2 and section 41, as if it were the agency, in relation to the discharge of its obligations under the arrangement, but only if the provider will in any way deal with personal information for the agency, or the services involve transferring personal information to the agency or providing services to a third party for it. A bound contracted service provider must comply in relation to the discharge of its obligations under the arrangement, as if it were the contracting agency
- What a Queensland agency may ask you
- "Will you agree to comply with the Queensland Privacy Principles and the rule on disclosure outside Australia as if you were us?"
- What to put in scope
- Nothing. This is a contract decision, made before any test.
- Evidence a web application test can give
- None. A report cannot accept or decline a clause.
- What that evidence cannot answer
- Section 36(2) keeps the duty running for personal information you still hold after your obligations under the arrangement end, so the clause is only half the answer; your exit and deletion plan is the other half.
- Who on your side owns the answer
- Director who signs the contract, advised by your solicitor
IP Act schedule 3, QPP 11.1: reasonable steps to protect personal information from misuse, interference or loss and from unauthorised access, modification or disclosure
- What a Queensland agency may ask you
- "What stops another of your customers, or the wrong person inside our organisation, from seeing our personal information?"
- What to put in scope
- Every role that can see personal information, two test accounts per role, accounts in two customer organisations, and the API called directly as well as through the screens.
- Evidence a web application test can give
- Findings and negative results from tests between roles and between customer organisations, recorded for each account and record tried, with the retest status of each finding.
- What that evidence cannot answer
- Whether the steps taken are reasonable, which a test report cannot decide, and anything outside the application: backups, staff devices, email and support tools.
- Who on your side owns the answer
- Privacy contact, with the technical lead supplying the evidence
IP Act s 47(2)(c) and (d): whether information is protected by security measures, and how likely they are to be overcome, are among the matters to have regard to in deciding whether access, disclosure or loss is likely to result in serious harm
- What a Queensland agency may ask you
- "If files or exports from your application were exposed, what would still protect them?"
- What to put in scope
- Upload and download routes, shared and emailed links, exports, and whether each link expires or needs a session.
- Evidence a web application test can give
- Findings and negative results on whether documents and exports could be fetched without authorisation, from another organisation, or after a link should have stopped working.
- What that evidence cannot answer
- Encryption inside your hosting platform, and the agency's own assessment of harm after a real incident.
- Who on your side owns the answer
- Lead developer
IP Act chapter 3A, ss 48 to 53: the agency's duties to contain and assess a suspected eligible data breach (s 48, within 30 days of forming the suspicion unless extended under s 49) and, once it reasonably believes there has been an eligible data breach, to give a statement to the Information Commissioner and notify individuals or publish a notice (ss 50, 51 and 53), subject to the exemptions in division 3. Read the sections for the full conditions. Local governments from 1 July 2026
- What a Queensland agency may ask you
- "How, and how fast, will you tell us about a suspected data breach involving our information?"
- What to put in scope
- Audit logging of sign-ins, record views and exports, if the agency wants to know what your records could show.
- Evidence a web application test can give
- If logging is in scope, findings on whether the application records who opened or exported a record. Otherwise none.
- What that evidence cannot answer
- Your notification process, who decides and how fast, and whether a weakness in a report was ever used by anyone other than the tester, which only your production logs can show.
- Who on your side owns the answer
- Whoever owns incident response, with the contract owner
IP Act s 33 on disclosure outside Australia, and IS18 reporting requirement 3: the agency reports HIGH or MEDIUM business impact information proposed for storage or processing outside Australia before executing plans
- What a Queensland agency may ask you
- "Is any of our information stored or processed outside Australia, by you or by your providers?"
- What to put in scope
- Nothing for your own providers. For the test itself, ask where the tester keeps evidence.
- Evidence a web application test can give
- For the test only, the tester's data handling terms. Clever Ops stores evidence encrypted in Australia and processes it outside Australia only where your statement of work approves it.
- What that evidence cannot answer
- Where your hosting, database, email delivery, file storage, analytics and support providers keep and reach the data.
- Who on your side owns the answer
- Technical lead, with each provider's contract and list of locations
IS18 Requirement 4: accountable officers obtain security assurance at a level based on the system's criticality, using the QGISCF business impact levels
- What a Queensland agency may ask you
- "What assurance can you give us about the system we are buying?"
- What to put in scope
- The application, environment and build the agency will use, at a depth that fits the highest business impact level the agency assessed.
- Evidence a web application test can give
- The scope as tested (targets, roles, build, environment and dates), the executive summary, each finding with a CVSS v3.1 score beside a separate business-risk rating, and the retest ledger.
- What that evidence cannot answer
- The agency's business impact assessment and its decision on how much assurance is enough. Releases after the tested build sit outside the evidence.
- Who on your side owns the answer
- Account or bid lead, with the technical lead
Procurement guideline, Appendix A: access control and access rights, at all three thresholds
- What a Queensland agency may ask you
- "How do you control who can reach our information in your application, and how are access rights granted, changed and removed?"
- What to put in scope
- Invitations, role changes, account removal and administrator functions, exercised on test accounts.
- Evidence a web application test can give
- Findings and negative results on whether an account kept access after a role change or removal, whether an administrator could act outside their own organisation, and whether hidden functions answered a direct API call.
- What that evidence cannot answer
- Your staff's access to the database, cloud console and support tools, and your joiner and leaver process.
- Who on your side owns the answer
- Technical lead
Procurement guideline, Appendix A: secure authentication, at all three thresholds. IS18 Requirement 3 has the agency comply with the Queensland Government authentication framework
- What a Queensland agency may ask you
- "Do users sign in with multifactor authentication, and can it be bypassed?"
- What to put in scope
- Sign-in, password reset, session handling and the second factor for each role, plus any API tokens.
- Evidence a web application test can give
- Results of the sign-in tests for each role: if a one-time code was required, if a password reset or a direct API call got around it, and if sessions closed on sign-out.
- What that evidence cannot answer
- Whether your design meets the agency's authentication framework, and settings in an identity provider the agency controls.
- Who on your side owns the answer
- Product owner for sign-in
Procurement guideline, Appendix A: management of vulnerabilities, at all three thresholds. Supply chain framework process 10: patching policies and frequencies
- What a Queensland agency may ask you
- "How do you find and fix technical vulnerabilities in your systems?"
- What to put in scope
- The application and API, with read-only code access if the agency also wants dependencies reviewed.
- Evidence a web application test can give
- Findings for outdated or vulnerable components the application exposes, each with a fix and a retest status.
- What that evidence cannot answer
- Patching of servers, operating systems and staff devices, and how often you patch.
- Who on your side owns the answer
- Technical lead, or your hosting provider
Procurement guideline, Appendix A: security testing throughout the software development process and secure coding practices, both at the Comprehensive threshold only
- What a Queensland agency may ask you
- "Do you test security during development, not just before go-live?"
- What to put in scope
- One test covers one build. A code review needs read-only code access in the agreed scope.
- Evidence a web application test can give
- A dated report and retest on identified builds, and a code review where code access was in scope.
- What that evidence cannot answer
- Testing inside your development process: reviews, automated checks and how releases are gated. Your own records answer that.
- Who on your side owns the answer
- Development lead
Supply chain framework process 10: frequency of penetration testing and verification of outcomes. Process 13: agreement to facilitate penetration testing
- What a Queensland agency may ask you
- "How often will the application be tested during the contract, and how will we see the outcomes verified?"
- What to put in scope
- Agree what starts a new test: a major release, a new role, a new integration or a new kind of customer.
- Evidence a web application test can give
- The build identifier in each report and retest, and the retest ledger marking each finding fixed, partially fixed, still reproducible or not retested.
- What that evidence cannot answer
- What frequency the contract should set. That is negotiated between you and the agency.
- Who on your side owns the answer
- Product owner and contract owner
Supply chain framework process 13: agreement on the approach to network, application and equipment testing
- What a Queensland agency may ask you
- "Will you facilitate testing of your network and equipment as well as the application?"
- What to put in scope
- The application and API only.
- Evidence a web application test can give
- Application results only. Clever Ops does not test networks, servers or equipment.
- What that evidence cannot answer
- Network and equipment testing, which needs a network testing specialist.
- Who on your side owns the answer
- Your IT or hosting provider
Procurement policy rule 14: cyber security risks within the supply chain. Guideline section 5.3: whether a control should extend to the supplier's own suppliers
- What a Queensland agency may ask you
- "Which of your own providers handle our information, and what do you check about them?"
- What to put in scope
- How your application connects to each provider, such as payments, email delivery and file storage, tested from your side. Each provider's own systems stay out of scope unless their owner gives written permission.
- Evidence a web application test can give
- Findings on how the application uses each provider, for example whether incoming webhooks are verified and whether keys reach the browser.
- What that evidence cannot answer
- The security of each provider's own systems.
- Who on your side owns the answer
- Technical lead, with your list of providers
Procurement guideline, Appendix A: test information management, separation of environments and protection during audits, at the Comprehensive threshold
- What a Queensland agency may ask you
- "If your live system is tested, how is our information protected during the test?"
- What to put in scope
- A staging copy with seeded data where one exists. If production is the target: agreed windows, and 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 a web application test can give
- The environment named in the scope, evidence with secrets and personal details redacted, the list of test data left behind, and the tester's data handling terms. Clever Ops evidence is stored encrypted in Australia and deleted on the schedule those terms set.
- What that evidence cannot answer
- Whether the agency agrees to its records being used in a test environment at all. Ask before copying production data.
- Who on your side owns the answer
- Technical lead, with the agency's contact
Procurement guideline, Appendix A: information deletion, at all three thresholds, and section 5.4 on secure return or disposal of data when a supplier transitions out. IP Act QPP 11.2
- What a Queensland agency may ask you
- "How do you delete our information when it is no longer needed, and when the contract ends?"
- What to put in scope
- Delete and close-account functions, if the agency wants them checked, run on test records only.
- Evidence a web application test can give
- Whether a deleted test record or document could still be fetched through the API or an old link.
- What that evidence cannot answer
- Retention schedules, backups, logs and the return of data at exit. A web application test observes none of these.
- Who on your side owns the answer
- Operations lead, or whoever owns data retention
Guideline section 5.3: whether the supplier needs to have been independently cyber assessed. Appendix A: independent review of security, at the Comprehensive threshold
- What a Queensland agency may ask you
- "Has your system been assessed independently, and by whom?"
- What to put in scope
- Record who built and who hosts each target before the test starts.
- Evidence a web application test can give
- A report from a provider with no part in building or hosting the system. When Clever Ops built or hosts it, the work is a security review and the report records who built and who hosts it.
- What that evidence cannot answer
- Independence the tester does not have, and a review of your information security practices as a whole, which is wider than an application test.
- Who on your side owns the answer
- Director, who chooses the provider
Guideline section 5.3: what certification meets the agency's benchmark, with ISO/IEC certification, SOC 2 and PCI DSS as examples. Supply chain framework process 12: certifiable cyber security frameworks
- What a Queensland agency may ask you
- "Do you hold a security certification?"
- What to put in scope
- Nothing. A test does not lead to a certificate.
- Evidence a web application test can give
- None. A test report is evidence for the agency's decision, not a certification, and Clever Ops holds no certification and issues none.
- What that evidence cannot answer
- A question about a certification or attestation, which goes to whoever holds it. For PCI DSS, a Qualified Security Assessor validates adherence and an Approved Scanning Vendor runs the external scans.
- Who on your side owns the answer
- Director, or whoever owns compliance
A contract term or invitation that names an accreditation or a standing offer arrangement
- What a Queensland agency may ask you
- "Is your tester CREST accredited, or on a Queensland Government standing offer arrangement?"
- What to put in scope
- Nothing until the wording is settled.
- Evidence a web application test can give
- The provider's name, and any accreditation or arrangement it holds. Clever Ops is not CREST accredited, so we refer that work to a provider that is, and it is not on any standing offer arrangement or government panel.
- What that evidence cannot answer
- Where the wording requires either, a report from a provider without it does not meet that wording.
- Who on your side owns the answer
- Whoever reads the procurement documents, before the test is booked
What a Brisbane penetration test from Clever Ops covers, and what it leaves out
Clever Ops is a small Australian consultancy based in Gippsland, Victoria, serving businesses earning $1M to $50M in annual revenue.
It has no Brisbane office and no staff in Queensland. Penetration testing for a Brisbane business runs over the internet against the targets named in a signed authorisation, and that authorisation lists the source IP addresses test traffic will come from, so your team and your host can pick it out from an attack. Scoping, testing, the report and the retest all happen remotely.
The penetration testing services Brisbane clients can buy are the ones offered everywhere else, aimed at what customers and staff reach through a browser or an API. Pick by what the application holds and who will read the report:
- Website security check, for website security on a Brisbane site with no customer logins. It looks at the site as a stranger on the internet sees it: certificates, headers, cookies, leftover files and exposed admin screens.
- WordPress security audit, covering WooCommerce stores too: customer accounts, orders and the checkout.
- Vulnerability assessment. A broad pass over a website or web application for known kinds of weakness. A tester confirms each one before it is reported, and it arrives ranked, with an owner and a fix.
- Web application and API penetration test. The tester signs in with two test accounts for each role, in two customer organisations where the application serves more than one, and tries to defeat the rules the application enforces, through the screens and by calling the API directly.
- Vibe-coded app security check and AI chatbot and agent security test, for apps made with AI builders and for the chatbots and agents a business deploys.
- A security fix sprint, under its own statement of work, and the one consolidated retest every test includes.
Cyber security work that sits outside this service
Someone searching for cyber security in Brisbane may want help with office computers, email, backups and the network. That is managed IT, and Clever Ops does not provide it, nor monitoring or incident response. It does not test office networks, servers, Wi-Fi, Active Directory or staff devices, which is network testing and needs a network testing specialist, and it does not run phishing or physical tests.
Clever Ops is also on no government panel, standing offer arrangement or other supplier arrangement, and holds no government endorsement and no security accreditation. When a contract requires a CREST-accredited provider, Clever Ops is not CREST accredited, so we refer that work to a provider that is.
A Clever Ops report maps its coverage to the OWASP Web Security Testing Guide v4.2 and ASVS 5.0, which shows a reviewer how the checks were organised. A framework reference is not a finding that the application meets IS18, the Information Privacy Act or any other Queensland requirement.
The Information Privacy Act 2009 (Qld) and contracted service providers
This section and the next cover two documents a Queensland agency may rely on when it sends a web application supplier security questions: the Information Privacy Act 2009 (Qld), the IP Act, and the Queensland Government's Information and cyber security policy, IS18.
The procurement documents follow after them. Section references follow the reprint on the Queensland legislation site marked current as at 29 October 2026. This is general information, not legal advice: whether and how a provision touches your contract is a matter for your solicitor and your customer.
Section 18(1) says an agency means a Minister, a department, a local government or a public authority. Section 26 puts the Queensland Privacy Principles (QPPs) in schedule 3, and section 27(1) says an agency must comply with them.
The QPPs and the data breach scheme came in through the Information Privacy and Other Legislation Amendment Act 2023. The explanatory notes for the proclamation that commenced its remaining provisions say agencies would need to comply with the QPPs from 1 July 2025, and that the mandatory notification of data breach scheme would commence on 1 July 2025, with commencement for local government deferred until 1 July 2026.
A questionnaire written before 1 July 2025 may refer to the principles that applied before the QPPs, so ask which version of the Act it was written against.
Part 3 of chapter 2 deals with contracted service providers. Section 34(1) defines a service arrangement: a contract or other arrangement entered into after the commencement of the section under which an entity other than an agency, the contracted service provider, agrees or otherwise arranges with an agency, the contracting agency, to provide services.
Section 34(2) adds three conditions: the services must be for the purposes of the performance of one or more of the contracting agency's functions, they must be provided directly to the contracting agency or to another entity on its behalf, and the contracted service provider must not be in the capacity of employee of the contracting agency in providing them.
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.
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.
Part 1 of chapter 2 holds the duty to comply with the QPPs, part 2 is section 33 on disclosure outside Australia, and section 41 is the duty not to contravene a QPP code that is in effect and binds the agency.
Section 36(1) says a bound contracted service provider must comply with those provisions in relation to the discharge of its obligations under the arrangement as if it were the contracting agency. Section 36(2) keeps that duty running for personal information the provider still holds after its obligations under the arrangement otherwise end, and section 36(3) says its compliance may be enforced under the Act as if it were an agency.
Section 37 covers the opposite case. If the agency did not take the steps section 35 requires, the obligations that would have attached to the provider attach to the agency instead. So before you answer any security question from an agency, find out whether your contract, or the draft in front of you, contains a clause doing what section 35 describes.
QPP 11.1 says that if an agency holds personal information, it must take reasonable steps to protect it from misuse, interference or loss, and from unauthorised access, modification or disclosure. QPP 11.2 says that once the agency no longer needs the information for a purpose the QPPs allow, and it is not in a public record and no Australian law or court or tribunal order requires it to be kept, the agency must take reasonable steps to destroy it or ensure it is de-identified.
Section 33 says an agency may disclose an individual's personal information to an entity outside Australia only in the cases it lists, among them the individual agreeing, the disclosure being authorised or required under a law, or two or more of the conditions in paragraph (d) applying. Because section 27 sits in part 1 and section 33 is part 2, both QPP 11 and the overseas disclosure rule are among the provisions section 36(1) names for a bound contracted service provider. Whether the steps you take are reasonable is not something a test report can decide.
Chapter 3A sets out the scheme. Section 46 applies it to personal information held by an agency, other than personal information in a document to which the privacy principle requirements do not apply. Section 13 says personal information is held by a relevant entity if it is contained in a document in the possession, or under the control, of that entity, and schedule 5 defines a relevant entity as an agency or bound contracted service provider.
Under section 48, an agency that knows or reasonably suspects that a data breach is an eligible data breach must immediately, and continue to, take all reasonable steps to contain it and mitigate the harm, and, if it does not know whether the breach is eligible, assess whether there are reasonable grounds to believe it is.
Section 48(3) gives 30 days for that assessment from when the suspicion was formed, unless the period is extended under section 49. Once the agency reasonably believes there has been an eligible data breach, sections 51 and 53 have it give a statement to the Information Commissioner and notify individuals, or publish a notice where notifying them is not reasonably practicable, each as soon as practicable, unless an exemption in division 3 applies.
Section 47(2) lists the matters to have regard to in deciding whether access, disclosure or loss is likely to result in serious harm. Two of the matters are whether the information is protected by one or more security measures and, if it is, the likelihood that any of those measures could be overcome.
A web application test records whether the measures in the application held when a tester tried to get past them, for the build and accounts it covered. That is evidence on both points, not the agency's assessment of harm.
These duties are written for agencies. Schedule 5 defines the privacy principle requirements for a bound contracted service provider as those in chapter 2, parts 1 and 2 and section 41, the same provisions section 36 names. Whether information your application holds for an agency is under the agency's control, and so held by it, is a question for the agency and its lawyers.
What an agency can fairly ask you is how fast you would tell it about a suspected breach, and what your records would show.
Section 219 holds chapter 3A back from an agency that is a local government until one year after the commencement, and the explanatory notes put the local government start at 1 July 2026. A council is an agency under section 18(1)(c), so from that date a council customer may ask about breaches in the same terms as a department.
IS18 version 10 and the supply chain framework beside it
The Information and cyber security policy (IS18) is published on the Queensland Government's For government site as version v10.0.0, issued on 17 June 2026, with the status current and mandated.
If a questionnaire refers to an earlier version of IS18, check its questions against the version now published.
IS18 applies to all Queensland Government departments as defined by the Public Sector Act 2022. It also applies to accountable officers not already in scope of that Act, and to statutory bodies under the Financial and Performance Management Standard 2019, in the context of internal controls, financial information management systems and risk management.
Other Queensland government entities, including local governments, are strongly encouraged to apply it as recommended better practice. Its scope includes all areas of the organisation where information, applications and technology could impact service delivery to Queenslanders or the running of the business of Queensland Government, including supply chain management.
Its requirements are addressed to agencies and their accountable officers, and the policy page does not mention suppliers or penetration testing. Four parts of it can reach a supplier as questions:
- Requirement 1: agencies must implement and operate an information security management system based on the current version of ISO 27001, covering all services, information, application and technology assets.
- Requirement 3: agencies must comply with the Queensland Government Information security classification framework (QGISCF), the Data encryption standard and the Queensland Government authentication framework, and must implement the ASD Essential Eight strategies, selecting maturity level targets.
- Requirement 4: accountable officers must obtain security assurance to establish an understanding of information security protections and adherence to the policy, and the level of assurance applied to a system must be based on its criticality or significance, using the business impact levels methodology in the QGISCF. The requirement opens by saying every system is unique and assurance should be applied sensibly and appropriately.
- Reporting requirement 3: agencies must engage with the Cyber Security Unit at the earliest opportunity, and before executing plans, to report any information classified under the QGISCF as having a HIGH or MEDIUM business impact level that is proposed to be stored or processed outside Australia.
Where a test report fits under Requirement 4
Requirement 4 says the accountable officer must obtain security assurance, and that the level applied to a system must be based on its criticality or significance, using the business impact levels methodology in the QGISCF. IS18 does not say what form that assurance takes, and it does not mention test reports.
Our own view, not IS18's, is that a web application test report can be offered as one input to an agency's assurance about one system, for the scope and build it covers, and that it cannot establish that an agency has met IS18.
Ask the agency what business impact level it gave the information your application will hold. That answer is a sound guide to the depth of test worth buying.
The supply chain cyber security risk management framework
Beside IS18, the same site publishes a Supply chain cyber security risk management framework, version v1.0.0, effective from June 2026 and last updated on 24 August 2026. It calls itself a better practice framework that is not mandatory under the current IS18 policy, and it is written mainly for staff in procurement, business planning, ICT planning, cyber project and program management, and ICT architecture. Three of its sixteen processes name kinds of evidence an agency may ask a supplier for.
- Process 10, determining security performance measures, lists requirements to consider, among them agreed recovery time objectives and incident notification timeframes, patching policies and frequencies, acceptable security certification and assurance levels including third-party assurance, the location of data storage, and the frequency of penetration testing and verification of outcomes.
- Process 12 suggests establishing assurance measures early in the procurement selection process, such as demonstration of certifiable cyber security frameworks, software bills of materials, audit reviews, post incident reviews, site visits, configuration architecture, and penetration testing or external attack surface management. For non-compliance it lists responses ranging from remediation plans and dispute resolution to financial penalties subject to contract obligations, temporarily halting contracts where operational impacts are not critical to delivery of services, and terminating contracts.
- Process 13 says monitoring and verification arrangements should be agreed and included in the contract. Its considerations include the approach to network, application and equipment testing, arrangements for code inspection, analysis and testing, and agreement to facilitate, or demonstrate facilitation of, penetration testing, malware scanning or other security logic validation processes.
The application share of process 13
A web application test answers the application part of process 13 and nothing else. Network and equipment testing need a different provider, and Clever Ops makes no site visits in any of its services. If a contract asks you to facilitate testing, agree in writing what you will open to the agency's tester or your own: which hostnames, which environment, which accounts and which hours.
Queensland procurement rules and the Managing Cyber Security in Procurement Guideline
The Queensland Procurement Policy 2026, version 1.1 of 11 November 2025, says it will commence on 1 January 2026, except for the Procurement Assurance Model incentive scheme component, which will commence on 1 January 2027.
It applies to agencies as its glossary defines them: departments and statutory bodies as defined in the Financial Accountability Act 2009, government-owned corporations declared by regulation, and public sector companies. Each rule applies to every agency unless the rule says otherwise.
Rule 14 says agencies must consider requirements for the management of cyber security risks including within the supply chain, and rule 26 says agencies must include appropriate clauses in contracts to manage information and cyber security risks.
For ICT, the For government page on creating an ICT contract says the Queensland Information Technology Contracting (QITC) framework applies to all ICT purchases by budget sector agencies, statutory bodies and public sector companies, and that agencies must use the appropriate template for the procurement category: a General contract for low-risk procurements, or a Comprehensive contract for moderate to high-risk procurements, regardless of value.
Agencies can buy through the Invitation to Offer template or from a Standing Offer Arrangement.
The QITC contract conditions themselves are not summarised here. If your contract is on QITC terms, read its own security and privacy clauses with your solicitor.
The Department of Housing and Public Works publishes the Managing Cyber Security in Procurement Guideline, version 1.1 of May 2026, to support the management of cyber security risks across all types of procurement, not only ICT. It relates to the application of the Queensland Procurement Policy and the requirements of IS18, and applies to all Queensland Government agencies and entities.
It says it is a guide only, for the internal use and benefit of government agencies, that it does not recommend or include specific contract clauses, and that its security criteria are suggestions only.
Read it as a view into how an agency may put its questions together, not as a list of rules addressed to you.
It runs in three stages. In Identify, the agency defines what it is buying and the information that will be shared with, used, acquired or created by the supplier. In Assess, it classifies that information under the QGISCF as Low, Medium or High for each of confidentiality, integrity and availability, records the highest result, and combines it with a value and risk assessment to reach one of three thresholds: Essential, Enhanced or Comprehensive.
In Apply, it chooses the security criteria for that threshold, and the guideline says those principles and controls are intended for the supplier to meet, not the agency.
Each threshold carries the criteria of the ones below it, and the Essential criteria should be considered a minimum whatever is being bought.
Appendix A lists the controls and marks the thresholds each belongs to. These are the ones a web application test has something to say about:
- All three thresholds: access control (rules for who can access information and assets), access rights, secure authentication (strong authentication methods based on access policies, that is, multifactor authentication), management of vulnerabilities (identifying and addressing technical vulnerabilities in the supplier's systems, that is, patching) and information deletion.
- Enhanced and Comprehensive: application security requirements, meaning security needs identified and approved during development or acquisition, and logging.
- Comprehensive only: security testing throughout the software development process, secure coding practices, independent reviews at planned intervals of the supplier's information security practices, separation of development, testing and production environments, protection of information used for testing, and planning for secure audits and other assurance activities involving operational systems.
The guideline does not mention penetration testing. Its closest control, security testing throughout the software development process, is marked for the Comprehensive threshold only. An agency can still ask for a test at any threshold, because the guideline calls its criteria a guide that agencies are encouraged to review against their own needs.
Section 5.3 then lists questions for the agency to settle about what it expects of suppliers. Four of them decide what a test can do for you: whether evidence is required once off or annually, or general acknowledgement is enough; what certification meets the agency's benchmark, with ISO/IEC certification, SOC 2 and PCI DSS given as examples; whether the supplier needs to have been independently cyber assessed; and whether a control should extend to the supplier's own suppliers.
Five answers to get from a Queensland customer before you commission a test
Each answer changes the scope or the evidence you need.
Ask for them in writing.
- What kind of entity the customer is. A department is within IS18's applicability. A statutory body is within it in the context IS18 names. A council is an agency under the IP Act and is strongly encouraged to apply IS18 as better practice.
- Which threshold the procurement reached under the guideline, and the highest business impact level the agency gave the information you will handle. Those two answers tell you which Appendix A controls the agency is working from.
- Whether your contract or draft requires you to comply with chapter 2, parts 1 and 2 and section 41 of the IP Act, and which security clauses the agency has included under rule 26 of the procurement policy.
- Whether any of its information will be stored or processed outside Australia, by you or by your providers. Under IS18, the agency reports HIGH or MEDIUM business impact information proposed for offshore storage or processing to the Cyber Security Unit before executing plans, so it needs your answer early.
- Whether it needs you to have been independently assessed, needs a certification, or names an accreditation or a standing offer arrangement. Settle that before booking any test.
Independent assessment, certification and a builder's own review
Independence turns on who did the testing.
Clever Ops builds and hosts websites and applications as well as testing them. When it tests a system it built or hosts, the work is a security review, never an independent test, and the report records who built and who hosts the system.
A security review is useful before a release, but it does not answer an agency asking whether you have been independently cyber assessed. That needs a provider with no part in building or running the system.
The guideline's Comprehensive control on independent review of security goes wider again: it is about independent reviews of the supplier's information security practices, not of one application. A web application test, however independent, covers the application in its agreed scope.
Certification is a separate question. A test report is evidence for an agency's decision, not a certificate, and Clever Ops holds no certification or accreditation and issues none. A penetration tester cannot answer a question about an ISO/IEC 27001 certificate or a SOC 2 report.
That question goes to whoever holds the certificate or report. For PCI DSS, a Qualified Security Assessor validates adherence and an Approved Scanning Vendor runs the external scans. Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor.
Worked case: an invented Brisbane grants portal with a department and a council as customers
This case is an illustration written for this page.
The company, both customers, their questions and the test are invented, and none of it describes a Clever Ops client or engagement. It shows the worksheet separating what a report can show from what the company has to answer from its own records.
An invented software company in Toowong runs a grants portal at grants.lab.test. Community groups apply for grants and upload supporting documents, including bank statements and incorporation certificates, and customer staff assess applications and approve payments. It has two customers on separate organisations in the portal: a Queensland Government department running a community grants program, and a south-east Queensland council running a smaller one.
Both contracts require the company to comply with chapter 2, parts 1 and 2 and section 41 of the IP Act as if it were the agency.
The department has told the company its procurement reached the Enhanced threshold, with Medium as the highest business impact level of the information.
The evidence on file is one external test of the portal and its API, by a provider with no part in building or hosting it. The scope covered the applicant, assessor and program administrator roles, two accounts each, in both customer organisations, on a staging copy loaded with seeded applications and dummy documents.
Source code, the company's support tools, its email delivery provider and staff laptops were excluded. Three findings came back:
- GR-01, high: an assessor in the council's organisation could list the department's applications by changing the program identifier in an API request. Retest on build 3.8.2: fixed.
- GR-02, medium: links to uploaded documents opened without a session and did not expire. Retest: partially fixed, because links now expire but still open without a session until they do.
- GR-03, low: the password reset form revealed whether an email address had an account. Retest: not retested, because the change had not reached build 3.8.2.
The department's supplier security schedule asked six things. The company matched each to a worksheet row before drafting a word.
- Who can see which applications (the access control row). The answer cites GR-01 as found and fixed, and the negative results for the other record types tried across the two organisations.
- What protects uploaded documents if a link leaks (the section 47(2) row). The answer describes GR-02 as partially fixed, says what still works without a session, and gives the date the session check ships. It does not call the documents protected.
- Where the information is stored and processed (the offshore row). The test has nothing to say here. The answer comes from the hosting contract and lists the email delivery provider, which processes applicant email addresses overseas, so the department can decide whether its offshore reporting step applies.
- When the portal was last tested, by whom and with what result (the Requirement 4 row). The answer gives the test and retest dates, names build 3.8.2, and says the tester had no part in building or hosting the portal.
- Whether security testing happens throughout development (the Comprehensive-only row). The department chose to ask it anyway. The test excluded source code, so the answer comes from the company's pull request reviews and dependency alerts and says the test did not cover them.
- How fast the company would report a suspected breach (the chapter 3A row). The answer comes from the incident response plan, with a named person and a time, and no test evidence.
The document links had behaved the same way in production for months. The report showed the weakness on staging, and could not show whether anyone other than the tester had ever used it. Only production access logs could, so the technical lead pulled them before replying to either customer, and told both what the logs covered and what they did not.
Each customer then decided for itself whether anything in that reply engaged its own duties under chapter 3A.
The council asked four questions, framed around privacy. It is an agency under section 18(1)(c), and chapter 3A has applied to councils since 1 July 2026, so its breach question got the same answer as the department's. Its questionnaire did not mention IS18, which strongly encourages local governments to apply it as better practice, so the company answered in the questionnaire's own terms instead of quoting IS18 requirements back.
For deletion at the end of the contract it answered from its retention settings and section 36(2), because the test said nothing about deletion beyond the test data it left behind.
Service-area notes for Brisbane, Ipswich, Logan and Moreton Bay
Clever Ops has no office, staff, street address or meeting room anywhere in Queensland.
- Brisbane:served remotely from Gippsland, Victoria.
- Ipswich:served remotely.
- Logan:served remotely.
- Moreton Bay:served remotely.
Frequently asked questions
No. Clever Ops is based in Gippsland, Victoria, and has no office, staff or address in Queensland. Brisbane, Ipswich, Logan and Moreton Bay are served remotely, and testing runs over the internet against the targets in a signed authorisation.
No. Clever Ops is not on any standing offer arrangement, panel or other government supplier arrangement, and it holds no government endorsement. If an agency or your contract requires one, that work goes to a provider that is on it. If it requires a CREST-accredited tester, Clever Ops is not CREST accredited, so we refer that work to a provider that is.
IS18 says it applies to Queensland Government departments, and to accountable officers and statutory bodies in the context it names, and it strongly encourages other Queensland government entities, including local governments, to apply it as better practice. Its requirements are addressed to those entities. Where it reaches a supplier, it arrives as an agency's questions and contract terms, so read your contract with your solicitor. This is general information, not legal advice.
No test does that. IS18 Requirement 4 says an accountable officer must obtain security assurance, at a level based on the system's criticality or significance. IS18 does not say what form that assurance takes or mention test reports; our own view is that a report can be offered as one input, for the scope and build it covers. QPP 11.1 says that if an agency holds personal information, the agency must take reasonable steps to protect it, and under section 36(1) a bound contracted service provider must comply with the QPPs in relation to the discharge of its obligations under the arrangement, as if it were the contracting agency. Whether particular steps are reasonable is not something a test report decides.
A local government is an agency under section 18(1)(c) of the IP Act, and section 27(1) says an agency must comply with the QPPs. The explanatory notes for the commencing proclamation give 1 July 2026 as the date the data breach scheme reached local government. IS18 strongly encourages local governments to apply it as recommended better practice. Ask which document each of the council's questions comes from before you match evidence to it.
Yes, remotely. A website security check looks at a site from outside and suits sites without customer logins. A vulnerability assessment goes wider across a website or web application, with each issue confirmed and ranked. Once customers or agency staff log in and see their own records, a web application penetration test is the depth that answers the access questions in the worksheet.
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.