Penetration testing in Canberra: web application evidence for Commonwealth suppliers
Clever Ops tests the websites, web applications and APIs that Canberra and Queanbeyan businesses run, working remotely from Gippsland, Victoria.
If you supply a Commonwealth entity, the matrix on this page sorts the questions it may ask into those a web application test can answer and those that need an IRAP assessor, a panel supplier or another accredited provider, and names who answers each one in your business and in the agency.
On this page
Commonwealth supplier evidence matrix
Find the row for the question in front of you. Each row gives the question a Commonwealth agency may put to a supplier, the instrument or document it comes from, the web application evidence that answers it, and what that evidence cannot answer.
How to use itHide the instructions
The last three columns say whether Clever Ops can meet the requirement or it goes to another provider, who owns the answer in your business, and where the question goes in the agency. Paragraph numbers follow the Commonwealth Procurement Rules 17 November 2025, and section numbers follow the Privacy Act 1988, Compilation No. 104, and the Australian Government Agencies Privacy Code. The Procurement Rules are addressed to officials of non-corporate and prescribed corporate Commonwealth entities (paragraph 2.2), and the Agencies Privacy Code binds agencies (section 7). In the Privacy Act, the APPs quoted here set duties for an APP entity, which section 6(1) defines as an agency or organisation, and section 95B sets requirements for an agency entering into a Commonwealth contract. The rows show how each question reaches a supplier. General information, not legal advice.
17 rows
Question an agency may put to you
Where the question comes from
"Show that you meet the conditions for participation, including any accreditation they list."
- Where the question comes from
- CPRs paragraph 10.14 and the definition of conditions for participation, which may include an accreditation or validation procedure. Paragraph 10.6(b) puts them in the request documentation.
- Web application evidence that answers it
- Only the accreditation or validation itself. A test report counts here only if the condition asks for test evidence.
- What that evidence cannot answer
- Any accreditation your business or its tester does not hold.
- Clever Ops or another provider
- Depends on the wording. Where it requires an accreditation Clever Ops does not hold, another provider meets it.
- Owner in your business
- Bid lead, then the director
- Where it goes in the agency
- The contact the approach to market names
"Has the solution been assessed by an IRAP assessor?"
- Where the question comes from
- The request documentation or contract. ASD describes IRAP Assessors as ASD-endorsed ICT professionals with a detailed knowledge of its ISM.
- Web application evidence that answers it
- None. A web application test report is not an IRAP assessment.
- What that evidence cannot answer
- The assessment, and anything it concludes.
- Clever Ops or another provider
- Another provider. Clever Ops is not an IRAP assessor, so we refer that work to one.
- Owner in your business
- Director, with the bid lead
- Where it goes in the agency
- Whoever owns the requirement, through the procurement contact or the contract manager
"How does your system measure up against the ISM?"
- Where the question comes from
- The agency's own requirements. ASD describes the ISM as a cyber security framework an organisation can use to protect its information technology and operational technology systems.
- Web application evidence that answers it
- None by ISM reference. Findings describe one application and are not mapped to the ISM.
- What that evidence cannot answer
- Which parts of the ISM the system meets, and the systems around the application.
- Clever Ops or another provider
- Another provider. Clever Ops does not assess systems against the ISM.
- Owner in your business
- Security lead or director
- Where it goes in the agency
- Whoever owns the requirement, named in writing
"Is your tester CREST accredited?"
- Where the question comes from
- The agency's procurement wording. CREST lists penetration testing and vulnerability assessment among its accreditation disciplines.
- Web application evidence that answers it
- The provider's name and any accreditation it holds, checked with CREST.
- What that evidence cannot answer
- A CREST requirement, unless the provider holds that accreditation.
- Clever Ops or another provider
- Another provider where CREST is required. Clever Ops is not CREST accredited, so we refer that work to a provider that is.
- Owner in your business
- Bid lead, before the test is booked
- Where it goes in the agency
- The contact the approach to market names
"Is your provider on the panel this work is bought through?"
- Where the question comes from
- CPRs definition of a standing offer, paragraphs 9.12 to 9.14, paragraph 5.5 on DTA standing offers, and paragraphs 4.11 and 4.12 on coordinated arrangements.
- Web application evidence that answers it
- None. Panel membership is a listing, not a test result.
- What that evidence cannot answer
- Membership of any panel, standing offer or coordinated arrangement.
- Clever Ops or another provider
- Another provider. Clever Ops is not on the Digital Marketplace or any other Commonwealth panel, standing offer or coordinated arrangement.
- Owner in your business
- Bid lead
- Where it goes in the agency
- The official responsible for the procurement
"When was the solution last penetration tested, what was found and what was fixed?"
- Where the question comes from
- Evaluation criteria in the request documentation (CPRs paragraph 7.12), or a supplier questionnaire.
- Web application evidence that answers it
- Dated report pages naming the build, environment, roles and targets tested; every finding rated twice, by CVSS v3.1 score (0.0 to 10.0) and by business risk; and the retest status of each.
- What that evidence cannot answer
- Code shipped since the tested build, and anything left out of scope.
- Clever Ops or another provider
- Clever Ops, for websites, web applications and APIs it did not build or host.
- Owner in your business
- Technical lead
- Where it goes in the agency
- Procurement contact during the tender, contract manager after award
"Did the tester have any part in building, hosting or maintaining the solution?"
- Where the question comes from
- The agency's own wording. In the CPRs, an independent assessor appears in paragraph 7.28, on auditing compliance with an applied standard.
- Web application evidence that answers it
- A signed statement from the provider saying whether it developed, hosts or maintains the system. Where Clever Ops did any of that, its report says so and names the work a security review.
- What that evidence cannot answer
- An independent view, if the tester developed or runs the system.
- Clever Ops or another provider
- Clever Ops when it had no part in the system. When it built or hosts the system, the work is a security review and an independent test goes to another provider.
- Owner in your business
- Director, who chooses the provider
- Where it goes in the agency
- Procurement contact or contract manager
"What steps protect the personal information in your application, and how do you keep one organisation's users out of another's records?"
- Where the question comes from
- APP 11.1 and 11.3 in Schedule 1 of the Privacy Act, and any clauses an agency includes in the contract under section 95B.
- Web application evidence that answers it
- What the cross-organisation and cross-role tests found or ruled out on the records tried, the certificate and transport checks for each public hostname, and where each finding stood at retest.
- What that evidence cannot answer
- Organisational measures such as staff access, training and backups, and the judgement of what is reasonable, which belongs to the agency.
- Clever Ops or another provider
- Clever Ops, for the technical measures in the application tested.
- Owner in your business
- Privacy contact, with the technical lead supplying evidence
- Where it goes in the agency
- Contract manager, who can bring in the Privacy Officer
"Will you agree not to do anything with personal information that would breach an APP if we did it, and carry that into subcontracts?"
- Where the question comes from
- Privacy Act section 95B(1) to (3).
- Web application evidence that answers it
- None; this is a contract term.
- What that evidence cannot answer
- Whether to agree to the term.
- Clever Ops or another provider
- Not a testing question.
- Owner in your business
- Director, advised by your solicitor
- Where it goes in the agency
- Contract manager, or the agency's legal area through them
"Will any personal information we provide be disclosed to, or reached from, anyone outside Australia?"
- Where the question comes from
- APP 8.1 on disclosure to an overseas recipient, and any data location clause in the contract.
- Web application evidence that answers it
- For your application, none. For the test itself, the tester's data handling terms.
- What that evidence cannot answer
- Which providers hold or can open the data, and from which countries: hosting, database, support, backups and email.
- Clever Ops or another provider
- Not a testing question. On Clever Ops work, test evidence is stored encrypted in Australia and processed outside Australia only where your statement of work approves it.
- Owner in your business
- Technical lead and privacy contact, with the hosting and support contracts in hand
- Where it goes in the agency
- Contract manager and Privacy Officer
"Name your subcontractors."
- Where the question comes from
- CPRs paragraph 7.21, under which relevant entities must make subcontractor names available on request. Privacy Act section 95B(3) and (4) on subcontracts, and the section 6(1) definition of a contracted service provider, which includes a subcontractor.
- Web application evidence that answers it
- None in the report beyond the name of the provider that tested.
- What that evidence cannot answer
- Whether a test provider counts as a subcontractor under your contract. That depends on what the contract covers.
- Clever Ops or another provider
- Not a testing question.
- Owner in your business
- Contract owner, advised by your solicitor
- Where it goes in the agency
- Contract manager
"Give us what we need for our privacy impact assessment."
- Where the question comes from
- Australian Government Agencies Privacy Code section 12, a privacy impact assessment for all high privacy risk projects, with the Privacy Officer assisting under section 10(5)(c).
- Web application evidence that answers it
- The scope as tested and the role list, showing which roles could reach which records in the tested build.
- What that evidence cannot answer
- The information flows and privacy impacts the assessment describes, which are the agency's to assess.
- Clever Ops or another provider
- Clever Ops, for the application evidence only.
- Owner in your business
- Privacy contact
- Where it goes in the agency
- Privacy Officer, through the contract manager
"Help us assess the cyber security risk of this procurement."
- Where the question comes from
- CPRs paragraphs 8.2 and 8.3, which point relevant entities to the Protective Security Policy Framework.
- Web application evidence that answers it
- A summary of the report, its scope page and its findings list with retest status, released under a confidentiality agreement.
- What that evidence cannot answer
- The agency's own risk assessment, and any PSPF requirement it passes on. Ask for those in writing.
- Clever Ops or another provider
- Clever Ops, for evidence about the application tested.
- Owner in your business
- Bid lead, with the technical lead
- Where it goes in the agency
- Procurement contact, then whoever owns the requirement
"Show us during the contract that you still meet the standard it names."
- Where the question comes from
- CPRs paragraphs 7.27 and 7.28: evidence of relevant certifications, and periodic auditing of compliance by an independent assessor.
- Web application evidence that answers it
- Dated reports and retest ledgers, offered as input for the scope each one covered.
- What that evidence cannot answer
- A certification, or an audit of compliance with the standard.
- Clever Ops or another provider
- Another provider: the certifying body or an assessor the standard recognises. A test report is evidence for their decision, not a certificate.
- Owner in your business
- Director, with the technical lead
- Where it goes in the agency
- Contract manager
"What is your Essential Eight maturity?"
- Where the question comes from
- The agency's questionnaire. ASD says assessments against the Essential Eight should be conducted using the Essential Eight assessment process guide.
- Web application evidence that answers it
- None. A web application test does not assess Essential Eight maturity. What it records about sign-in on the application, such as whether a second factor was asked for, describes that application only and is not an Essential Eight assessment.
- What that evidence cannot answer
- All of it.
- Clever Ops or another provider
- Another provider. Clever Ops does not assess Essential Eight maturity.
- Owner in your business
- Your IT provider
- Where it goes in the agency
- Whoever sent the questionnaire
"Do your testers hold a security clearance, and can they work on our premises?"
- Where the question comes from
- The request documentation or contract.
- Web application evidence that answers it
- None.
- What that evidence cannot answer
- Clearances and on-site work.
- Clever Ops or another provider
- Another provider. Clever Ops advertises no security clearance, and its testing is remote.
- Owner in your business
- Bid lead
- Where it goes in the agency
- Procurement contact
"Are you an Australian business as the CPRs define it?"
- Where the question comes from
- CPRs paragraph 5.4 and the definition of an Australian business: Australian ownership or listing, Australian tax residency, and a principal place of business in Australia. For paragraph 5.4 only, it also includes a New Zealand business.
- Web application evidence that answers it
- None. This is about your business, not your application.
- What that evidence cannot answer
- All of it.
- Clever Ops or another provider
- Not a testing question.
- Owner in your business
- Director, with your accountant
- Where it goes in the agency
- Procurement contact
Web application penetration testing for Canberra and Queanbeyan businesses
Clever Ops is a small Australian consultancy based in Gippsland, Victoria.
It offers penetration testing services to businesses in Canberra and Queanbeyan from there, remotely, on the same footing as clients in any other part of Australia. It has no office, staff or street address in the Australian Capital Territory or in Queanbeyan, and none of its work involves a visit to your premises.
Nobody needs to be in your building for a web application test. Requests travel across the internet to the targets your signed authorisation names, from source IP addresses that the authorisation also lists, which lets your staff and your hosting provider separate test traffic from hostile traffic. Scoping, testing, reporting and the retest all happen this way.
In scope can be anything your customers or staff use in a browser or call as an API: custom web applications and their APIs, websites, WordPress sites and WooCommerce stores, apps made with AI builders, and AI chatbots and agents. Clever Ops also runs security fix sprints and retests. The work comes in these depths:
- Website security audit, which Clever Ops sells as a website security check. It examines the public face of a site without signing in: certificates and transport settings, security headers, cookie flags, stray files and admin paths that answer from the internet, and version numbers the site gives away. It fits a site that has no user accounts.
- Web application and API penetration test. Using test accounts in each role in scope, the tester attempts to cross each boundary the application is meant to hold: one organisation reaching another organisation's grants, cases or bookings, a junior role performing a senior role's actions, and API calls made directly to skip what the screens prevent. The matrix on this page draws on the evidence this test produces.
- Security review. When Clever Ops built or hosts the system, the same work goes by that name instead of an independent test, and the report states who built the system and who hosts it.
What cyber security in Canberra means here, and what it does not
A search for cyber security in Canberra can come from someone who wants office IT, email and backups looked after, systems watched around the clock, or the internal network tested.
Clever Ops does none of those. Managed IT, monitoring, internal network and Active Directory testing, staff device testing, phishing, physical tests and denial-of-service or load testing all sit outside its service. Take that work to a managed IT provider, a network testing specialist or an incident response specialist.
This page is written for a business that supplies, or wants to supply, a Commonwealth entity, and needs to know what evidence about its own application will answer the entity's questions. It calls that customer the agency. It is general information about the instruments it quotes, not legal advice.
Can a web application test meet your requirement?
Settle this before you book anyone, from the exact words of the request documentation, draft contract or questionnaire.
Sort each requirement into one of the three groups below. The matrix on this page works through each question in detail.
A web application test can supply the evidence
For the application, build and scope that were tested, a report can answer requests like these.
- Evidence of recent penetration testing of the application or API the agency will use, with what was found and how serious each finding is.
- Proof that findings were fixed, from a retest on an identified build.
- Whether staff of one applicant or client organisation can reach a different organisation's records, and whether each role is limited to its own functions.
- How sign-in, sessions and password reset behaved under test, for each role.
- Certificate and transport settings for each public hostname in scope.
This goes to an accredited, endorsed or listed provider
A test report cannot stand in for any of these, whatever it finds. Where the wording requires one of them, the wording decides.
- An IRAP assessment. Clever Ops is not an IRAP assessor, so we refer that work to one.
- A statement of how a system measures up against ASD's Information Security Manual (ISM). Clever Ops does not assess systems against the ISM.
- A CREST-accredited tester. Clever Ops is not CREST accredited, so we refer that work to a provider that is.
- A supplier on a Commonwealth panel or standing offer, such as the Digital Marketplace. Clever Ops is not on any Commonwealth panel, standing offer or marketplace.
- An Essential Eight maturity assessment. Clever Ops does not assess Essential Eight maturity; your IT provider or a specialist does.
- People with a security clearance, or work on agency premises or agency networks. Clever Ops advertises no security clearance and works remotely, testing only what is reached through a browser or an API.
- A certificate, or an audit of compliance with a standard. A test report is evidence for someone else's decision, not a certification.
This is not a testing question
These are answered from your own records and contracts, by the owners the matrix names.
- Whether your business is an Australian business as the Commonwealth Procurement Rules define it.
- The privacy clauses in the contract, and whether you accept them.
- The names of your subcontractors, and which terms your contracts with them pass down.
- Where your hosting, database, support and backup providers keep the data and where they reach it from.
- Your incident notification process, and who in your business makes the call to the agency.
The Commonwealth Procurement Rules, read from the supplier's side
The Commonwealth Procurement Rules (CPRs) are made by the Minister for Finance under section 105B(1) of the Public Governance, Performance and Accountability Act 2013.
The version quoted here is the Commonwealth Procurement Rules 17 November 2025, registered as F2025L01263 on the Federal Register of Legislation. Its foreword says the 1 July 2024 rules are repealed when it commences on 17 November 2025. Paragraph 2.2 says officials from non-corporate Commonwealth entities, and from the prescribed corporate Commonwealth entities listed in section 30 of the PGPA Rule, must comply with the CPRs when performing duties related to procurement. The CPRs call these relevant entities.
The rules are addressed to officials, not to suppliers. A supplier encounters them through the documents officials produce: the approach to market, the request documentation and the contract. Paragraph 3.8 says officials of non-corporate Commonwealth entities must comply with Division 1 for every procurement, whatever its value, and with the additional rules in Division 2 when the estimated value is at or above the relevant procurement threshold and no Appendix A exemption applies.
Paragraph 10.14 lets a relevant entity specify conditions for participation that potential suppliers must be able to demonstrate compliance with in order to participate, limited to those that ensure a supplier has the legal, commercial, technical and financial abilities to fulfil the requirements of the procurement.
The CPRs' definitions describe conditions for participation as minimum conditions a potential supplier must demonstrate compliance with to participate in a procurement process or for its submission to be considered, and say they may include a requirement to undertake an accreditation or validation procedure. Paragraph 10.6 says request documentation must include a complete description of any conditions for participation.
So the first place to look for an IRAP assessment, a CREST accreditation, a clearance or any other credential is the conditions for participation. If one is listed and your business cannot show it, a test report does not change that.
If none is listed, read the evaluation criteria next. Paragraph 7.12 says relevant entities should include relevant evaluation criteria in request documentation, and a request for test evidence may sit there instead.
Two rules in Division 2, which paragraph 10.1 applies to procurements at or above the relevant procurement threshold that Appendix A does not exempt, concern where a supplier is based. Paragraph 10.15 says conditions for participation must not specify, as a requirement, previous experience with the relevant entity, with the Australian Government or in a particular location.
Paragraph 10.2 says potential suppliers must not be discriminated against due to their size, degree of foreign affiliation or ownership, location, or the origin of their goods and services.
For a band of procurements below the relevant procurement threshold, excluding procurements from a standing offer, paragraph 5.4 has non-corporate Commonwealth entities invite only Australian businesses to make submissions. The CPRs define an Australian business as one, including any parent business, that has 50% or more Australian ownership or is principally traded on an Australian equities market, is an Australian resident for tax purposes, and has its principal place of business in Australia.
For the purpose of paragraph 5.4 only, the definition says an Australian business also includes a New Zealand business, and the CPRs direct relevant entities to Finance's guidance when applying it.
The definition names no state or territory. Whether your business meets it is a question for you and your accountant, not for a test report.
The CPRs define a standing offer as a Commonwealth arrangement setting out the terms and conditions, including a basis for pricing, under which a supplier agrees to supply specified goods and services to a relevant entity or entities for a specified period, and their definition of a contract notes that it includes standing offers and panels.
Paragraph 9.12 says procurements from an existing standing offer are not subject to Division 2 but must comply with Division 1, and paragraph 9.14 says officials should approach multiple potential suppliers when a standing offer includes them.
Paragraph 5.5 names the Management Advisory Services Panel, the People Panel and any standing offer managed by the Digital Transformation Agency (DTA). Below a value it sets, it has non-corporate Commonwealth entities invite only SMEs on the relevant standing offer, and the CPRs define an SME as an Australian or New Zealand business with fewer than 200 full-time equivalent employees.
Its footnote points to the DTA's BuyICT page for DTA standing offers, and the foreword names the Digital Marketplace among the panels where the rules prioritise Australian SMEs.
Separately, paragraph 4.12 says non-corporate Commonwealth entities must use coordinated arrangements, the whole-of-Australian-Government arrangements described in paragraph 4.11. Exemptions are granted jointly by the entity's portfolio minister and the Finance Minister on a demonstrated special need, unless the arrangement itself specifies another approach.
If an agency tells you it buys security testing through a panel or a coordinated arrangement, ask which one, and whether the provider who tests your application needs to be on it. Clever Ops is not on the Digital Marketplace or on any other Commonwealth panel, standing offer or coordinated arrangement.
Where the agency's wording asks for a supplier from one of them, we refer you to a supplier that is on it.
Paragraph 7.21 says relevant entities must make available on request the names of any subcontractors engaged by a contractor in respect of a contract. Keep your own list current, so the agency can answer when someone asks it.
Paragraph 7.27 covers procurements at or above the relevant procurement threshold where a standard is determined to be applicable: tender responses must demonstrate the capability to meet the standard, and contracts must contain evidence of the applicable standards.
Paragraph 7.28 says that where it applies a standard, a relevant entity must make reasonable enquiries to determine compliance during the contract period, including gathering evidence of relevant certifications and periodic auditing of compliance by an independent assessor.
A web application test report is neither a certification nor an audit of compliance with a standard. Where a contract names a standard, a report can be one input to those enquiries, for the scope it tested.
Paragraph 8.2 says relevant entities must establish processes to identify, analyse, allocate and treat risk when conducting a procurement, and paragraph 8.3 says they should consider and manage their procurement security risk, including cyber security risk, in accordance with the Australian Government Protective Security Policy Framework (PSPF).
What the PSPF itself contains is outside this page. Ask the agency, in writing, which of its requirements it is passing on to you.
The Privacy Act 1988 when your customer is a Commonwealth agency
The Privacy Act 1988 is quoted here from Compilation No. 104 on the Federal Register of Legislation, which shows the law as amended and in force on 4 June 2026.
Section 6(1) of the Act defines "agency" by a list that begins with a Minister and a Department. How any of these provisions bears on your own contract is for your solicitor to advise on, with your customer's documents in hand.
Section 95B(1) requires an agency entering into a Commonwealth contract to take contractual measures to ensure that a contracted service provider for the contract does not do an act, or engage in a practice, that would breach an Australian Privacy Principle (APP) if done or engaged in by the agency.
Under section 95B(2) the agency must ensure that the Commonwealth contract does not authorise a contracted service provider for the contract to do or engage in such an act or practice, and under section 95B(3) it must also ensure that the contract contains provisions to ensure that such an act or practice is not authorised by a subcontract.
Section 6(1) defines a Commonwealth contract as a contract to which the Commonwealth or an agency is or was a party, under which services are to be, or were to be, provided to an agency. A contracted service provider for a government contract is an organisation that is or was a party to it and responsible for providing services under it, or a subcontractor for the contract.
Section 6D(4)(e) says an entity that is a contracted service provider for a Commonwealth contract, whether or not a party to the contract, is not a small business operator. If your business has treated itself as a small business operator under the Act, take that section to your solicitor.
APP 11.1, in Schedule 1, says that if an APP entity holds personal information, the entity must take such steps as are reasonable in the circumstances to protect the information from misuse, interference and loss, and from unauthorised access, modification or disclosure. APP 11.3 says that, for the purposes of APP 11.1 and 11.2 and without limiting them or any other provision of the Act, such steps include technical and organisational measures.
A web application test speaks to some of the technical measures, for the application tested, and to none of the organisational ones.
APP 8.1 says that before an APP entity discloses personal information about an individual to a person (the overseas recipient) who is not in Australia or an external Territory and who is not the entity or the individual, the entity must take such steps as are reasonable in the circumstances to ensure that the overseas recipient does not breach the APPs (other than APP 1) in relation to the information.
APP 8.2 sets out cases where APP 8.1 does not apply. Section 6(1) says an APP entity means an agency or organisation.
When an agency asks where its data is hosted, supported and backed up, the answer comes from your hosting and support arrangements and your contract, not from a test report.
The Australian Government Agencies Privacy Code was developed under section 26G of the Privacy Act and binds all agencies as section 5 of the code defines them, a definition that leaves out Ministers. Section 10 says an agency must at all times have a designated Privacy Officer, the primary point of contact for advice on privacy matters in the agency, and the Privacy Officer functions it lists include assisting with the preparation of privacy impact assessments.
Section 12 says an agency must conduct a privacy impact assessment for all high privacy risk projects, and that a project may be one if the agency reasonably considers it involves new or changed ways of handling personal information that are likely to have a significant impact on the privacy of individuals.
For a supplier, that makes the Privacy Officer the person to ask your contract contact to involve when a privacy question arrives, and a privacy impact assessment one document your evidence may feed.
IRAP, the ISM, CREST and the Essential Eight: where a test report stops
An agency may name any of these four.
Three of them describe things a web application test report is not: an IRAP assessment, a statement against the ISM, or an Essential Eight assessment. CREST concerns who does the testing, and only an accredited provider meets a requirement for it. In every case a report can still sit beside the requirement as evidence about one application.
IRAP and the ISM
ASD calls the program the Infosec Registered Assessors Program (IRAP). It describes IRAP Assessors as ASD-endorsed ICT professionals from across Australia who have the necessary experience and qualifications in ICT security assessment and risk management, and a detailed knowledge of ASD's ISM.
ASD's page for the Information Security Manual (ISM) shows September 2026 in its heading, and describes the ISM as a cyber security framework that an organisation can use to protect their information technology and operational technology systems from cyber threats.
This page does not describe what the ISM contains, what an IRAP assessment involves or which systems need one. Ask the agency which requirement it is applying, and which edition of the ISM it means.
Clever Ops is not an IRAP assessor, holds no ASD endorsement or approval, and does not assess systems against the ISM. Where an agency requires an IRAP assessment, that work goes to an IRAP assessor. A Clever Ops test report can sit beside it only as evidence about the application tested.
CREST accreditation
CREST says its accreditation goes to organisations that evidence compliance with CREST Accreditation Standards through an application, evidence submission and review, followed by periodic reassessment, and it lists penetration testing and vulnerability assessment among its disciplines. Clever Ops is not CREST accredited, so we refer that work to a provider that is.
The Essential Eight
ASD calls the Essential Eight the most effective of its Strategies to mitigate cyber security incidents, designed to protect organisations' internet-connected information technology networks. The eight are patch applications, patch operating systems, multi-factor authentication, restrict administrative privileges, application control, restrict Microsoft Office macros, user application hardening and regular backups.
ASD says assessments against the Essential Eight should be conducted using the Essential Eight assessment process guide. A web application test does not assess Essential Eight maturity, and Clever Ops does not assess it.
Anything a test records about sign-in on the application, such as whether a second factor was asked for, is an observation about that application, not an Essential Eight assessment.
Security clearances
If a requirement names a security clearance for the people doing the work, it goes to a provider that can meet it. Clever Ops advertises no security clearance.
Who did the testing, and whether they had a stake in it
An agency weighing your evidence can fairly ask whether the tester had any part in building, hosting or maintaining the application.
The CPR paragraph that mentions an independent assessor, paragraph 7.28, is about auditing compliance with an applied standard rather than penetration testing, so for a test the agency's own wording sets the independence it expects.
This matters for Clever Ops too, because it develops and hosts software for clients as well as testing it. Where Clever Ops wrote or runs the system, its work carries the name security review, never independent test, and its report says who developed the system and who hosts it.
That kind of review earns its place ahead of a go-live, but where an agency has asked for an independent tester, the supplier needs one: a provider that took no part in developing or operating the application.
Before any test is booked, ask the provider, Clever Ops included, for a written statement of its part in the system, if it has one, and put that statement in your answer pack beside the report.
Worked case: an invented Queanbeyan grants-portal supplier bidding for a department
Everything in this case is made up for the page: the business, the department, the tender, its questions and the test results.
It is not drawn from any Clever Ops client or job. What it demonstrates is the split the matrix makes between questions a report can carry and requirements it cannot.
The made-up business is a Queanbeyan software firm with a grants portal at funding.lab.test. Community groups log in to prepare and lodge funding applications; department staff log in to assess them. Its servers sit in an Australian cloud region, but a support contractor in the Philippines can view live records when it handles a ticket.
A made-up non-corporate Commonwealth entity, called the department here, has put an open approach to market on AusTender for a replacement grants portal. The firm plans to tender.
The firm holds a single external penetration test, carried out by a provider that neither developed nor operates the portal. That provider tested the portal and its API in a staging environment filled with invented applications, using applicant, assessor and administrator accounts across two applicant organisations. Source code, office IT and the support contractor's systems were left out. The report lists three findings.
- FA-01, high: an applicant could read another organisation's draft application by changing its identifier in an API request. Retest on build 2.6.1: fixed.
- FA-02, medium: an assessor could export applications from grant rounds they were not assigned to. Retest: still reproducible, with a fix scheduled for the next release.
- FA-03, low: signing out did not end the session on the server. Retest: fixed.
The firm matches each item to a matrix row, then hands it to the owner that row names.
- A condition for participation: the solution must have been assessed by an IRAP assessor. This is the IRAP row, and the test report does not meet it. The director and the bid lead decide whether to commission an IRAP assessment or not to bid.
- An evaluation criterion asking for evidence of recent penetration testing of the offered solution, and the outcome of any retest. This is the testing evidence row. The bid lead attaches the report's summary pages and its list of findings with their retest status, and says plainly that FA-02 still reproduces and when the fix is due.
- A clause in the draft contract that the supplier must not do anything with personal information that would breach an APP if the department did it, with the same term carried into any subcontract. This is the section 95B row. It goes to the director and the firm's solicitor; the test has nothing to add.
- A question asking for the names of subcontractors and whether any personal information can be reached from outside Australia. These are the subcontractor and APP 8 rows. The answer names the support contractor in the Philippines and describes what it can open. Before the bid goes in, the privacy contact and the solicitor decide whether to restrict that access or to ask the department to agree to it.
- A question about Essential Eight maturity for the firm's own IT. The firm's IT provider answers it, because the web application test did not assess it.
Every clarification question goes in writing through the channel the approach to market names, and nowhere else. Paragraph 10.8 of the CPRs says relevant entities must promptly reply to any reasonable request from a potential supplier for relevant information about a procurement and, when responding, must avoid any supplier gaining an advantage in a competitive procurement process. The firm's office is close to the department's, and that changes nothing about the channel.
Before deciding to bid, the firm asks one question through that channel: does the IRAP condition apply to the whole solution, or only to its hosting? The department's written answer is the whole solution, so the decision turns on the IRAP assessment, not on the test.
"In September 2026 a provider independent of our development and hosting tested our grants portal and API in a staging environment, and reported three issues. Its retest of build 2.6.1 found the high-risk and low-risk issues fixed; the medium-risk issue still reproduces, and its fix is due in our next release.
Source code, office IT and our support contractor's systems were outside that test, and the test is not an IRAP assessment."
Canberra and Queanbeyan stakeholder-routing worksheet
Fill this in once, before the next questionnaire arrives, and keep it with your bid templates.
Write a person's name beside each role, not a job title. The last two columns of the matrix use these roles.
In your business
One name per line. A small business may give several lines to the same person.
- Director: decides whether to bid, signs the contract, and accepts or declines privacy and security clauses.
- Bid lead: reads the request documentation, finds the conditions for participation and the evaluation criteria, and sends every clarification question through the named channel.
- Technical lead: holds the test report and retest ledger, and answers questions about the application, its hosting and access between organisations.
- Product owner: decides which build ships, so the evidence matches the release the agency will use.
- Privacy contact: answers APP questions and keeps the record of where personal information goes, including to support contractors.
- Contract owner and solicitor: read section 95B clauses, subcontract terms and data location clauses.
- IT provider: answers Essential Eight and office IT questions.
- Test provider: states in writing its part in the system, if any, and supplies its data handling terms.
In the agency
Ask for each name in writing, and record where it came from.
- Before the contract: the contact the approach to market names. Every question goes there, in writing.
- After the contract: the contract manager the contract names. Security, privacy and subcontractor questions go there first; ask the contract manager to bring in anyone else.
- Privacy: the agency's Privacy Officer, whom the Australian Government Agencies Privacy Code makes the primary point of contact for advice on privacy matters in the agency.
- Security requirements: whoever the agency names as the owner of the requirement it is passing on.
- Procurement decisions: the official responsible for the procurement, a role paragraph 5.4 of the CPRs refers to.
Three habits for a supplier near the agency
Being close by changes the conversations you can have, not the rules that apply to them.
- Keep questions in the channel. Paragraph 10.8 says that when a relevant entity responds to a supplier's enquiry, it must avoid any supplier gaining an advantage in a competitive procurement process, so a question asked in a corridor or at an industry event does not replace a written one.
- Do not count on being local. Paragraph 10.15 says conditions for participation must not require previous experience in a particular location, and paragraph 10.2 says potential suppliers must not be discriminated against due to their location.
- Check which government is asking. An ACT Government directorate, a NSW public sector body or a council works from its own instruments, which this page does not cover. Ask which document each question comes from before you answer it.
How remote delivery works for the ACT and Queanbeyan
Work for clients in the ACT and Queanbeyan is run from Gippsland in exactly the way it is for clients elsewhere in the country.
In practice:
- Canberra and the rest of the ACT: served remotely. Clever Ops has no premises or people anywhere in the territory.
- Queanbeyan: served remotely, on the same terms. Clever Ops has no presence in New South Wales either.
- Every engagement: scoping, testing, reporting and the retest are remote, and requests go only to the targets the signed authorisation lists.
- Destructive actions are off by default for real people's accounts and records that existed before the test, and reset, lockout and deletion checks run only on test accounts and test records where the rules of engagement allow them.
- Evidence is stored encrypted in Australia, deleted on the schedule set in the data handling terms, and processed outside Australia only where your statement of work approves it. Bring any data location clause from your Commonwealth contract to the scoping call so those terms can match it.
- Agency premises, agency networks and your own office network are outside the service, so a requirement for on-site or internal testing goes to another provider.
- Test coverage is mapped to OWASP's Web Security Testing Guide and to ASVS 5.0, which shows the method a tester followed. Neither reference claims that the application meets the ISM or another standard.
Frequently asked questions
No. The business operates from Gippsland in Victoria and has no premises, people or street address in either place. Canberra and Queanbeyan clients get the same remote process as every other client in Australia.
No to both. Clever Ops is not an IRAP assessor, holds no ASD endorsement or approval, and is not on the Digital Marketplace or any other Commonwealth panel, standing offer or coordinated arrangement. Where a requirement names any of these, we refer the work to a provider that meets it.
No. A test report records what was tested and found in one application, for one build and scope. It is not an IRAP assessment, and it does not say which parts of the ISM a system meets. It can still answer a separate request for recent test evidence, and the matrix on this page shows which requests those are.
Paragraph 2.2 says officials from non-corporate Commonwealth entities and prescribed corporate Commonwealth entities must comply with the CPRs when performing duties related to procurement. They are rules for those officials, and a supplier meets them through the approach to market, the request documentation and the contract. Read those documents with your solicitor. This is general information, not legal advice.
Section 95B(1) requires an agency entering into a Commonwealth contract to take contractual measures to ensure that a contracted service provider for the contract does not do an act, or engage in a practice, that would breach an Australian Privacy Principle if done or engaged in by the agency. Section 95B(3) says the agency must also ensure that the contract contains provisions to ensure that such an act or practice is not authorised by a subcontract. A supplier meets the section as clauses in the contract. Read them with your solicitor. This is general information, not legal advice.
Yes, delivered remotely. For a public site with no logins, the website security check reviews what an outsider can see and reach. For an application with users, the web application and API penetration test works through the roles and organisation boundaries in scope, and that is the evidence the matrix on this page relies on.
Only if the agency's wording does not ask for independence. A builder testing its own work has a stake in the result. Clever Ops applies the same rule to itself: a system it built or hosts gets a security review, and the report names the builder and the host. Where independence is asked for, use a tester that had no hand in the build or the hosting.
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.