Web security compliance guides: find the one that matches the request in front of you
Guides for the point where someone asks your business for security evidence: a customer's questionnaire or contract, an insurer's proposal form, a question under a privacy law, prudential standard or other Act, an auditor or assessor, or a project about to go live.
Each sets out what its documents say in their own words, leaves whether they apply to you with your adviser or the party it names, and comes with a table you work through for your own business. The buyer-evidence finder sets them side by side.
On this page
Pages in this section
17 pages
For owners, managers and technical leads who have met Australian Privacy Principle 8 in a privacy policy review, a customer questionnaire, a contract or a question from their adviser. This guide sets out APP 8 and section 16C of the Privacy Act 1988 from the Act's text and the OAIC's guidelines, then gives you a register that records which outside services receive personal information through your website, in which country and on what terms, with the data flows observed on your own systems.
Prudential Standard CPS 230 Operational Risk Management asks an APRA-regulated entity to manage its operational risks, maintain its critical operations through disruptions, and manage the risks arising from service providers. This guide reads the 2026 instrument on the Federal Register of Legislation paragraph by paragraph, sets out what it says about material service providers and their agreements, marks where APRA's guidance in CPG 230 fits, and draws the line between what a website or web application test can evidence and the operational controls that sit elsewhere. A fillable dependency map and evidence register comes with the guide.
Paragraph 27 of Prudential Standard CPS 234 says an APRA-regulated entity must test the effectiveness of its information security controls through a systematic testing program. This guide reads paragraphs 27 to 31 from the instrument on the Federal Register of Legislation, shows how the standard reaches information assets that suppliers manage, marks where APRA's guidance in CPG 234 fits, and sets out what a website or web application test can and cannot add to an entity's testing record. It comes with a control-testing calendar you can fill in.
For owners, managers and technical leads whose business has met the Privacy Act 1988 in a contract, a customer questionnaire or a complaint. This guide sets out the thirteen principles from the Act's own text, shows where each one meets a website's forms, analytics, chatbots, customer accounts and portals, and gives you a touchpoint map of what a targeted test can and cannot evidence.
CREST Penetration Testing Explained
CREST International says CREST ANZ is a separate organisation. Each body uses its own names for what it accredits, approves and certifies. This guide reads each body's own pages, decodes the wording a tender or contract uses, lists the questions an issuer answers before deciding on any equivalent, and comes with a scope sheet for briefing the provider you engage. Clever Ops is not CREST accredited, and where your documents require CREST, we refer you to an accredited provider.
Chubb's Cyber ERM Short MarketPlace, Standard and Extensive forms and DUAL's 08.26 cyber form, read on 15 November 2026 and compared topic by topic: which of them ask about penetration testing and scanning, in their own words, and which of your records relate to each question. Not insurance advice: your broker advises on cover.
The Cyber Security Act 2024 provides for security standards for smart devices, a 72-hour report after a ransomware payment, voluntary information sharing with the National Cyber Security Coordinator and a Cyber Incident Review Board. This guide reads the Act and the ransomware and smart device rules made under it, section by section, places the ransomware payment clock beside the Privacy Act and SOCI Act clocks, and is plain that the Act does not ask for a website test. It comes with a reporting timeline and evidence pack you can fill in.
ISO/IEC 27001:2022 sets requirements for an information security management system (ISMS), and its text is sold under licence. If a contract, tender, questionnaire or board decision has put the standard in front of your business, this guide sets out what IEC's catalogue page shows openly, where a website or web application turns up in an ISMS, the questions to put to your own copy when a contract, questionnaire or auditor cites Annex A 8.8 or 8.29, and what a security test of the application can and cannot add to your records. It comes with an evidence matrix to complete from your copy.
The NIST Cybersecurity Framework (CSF) 2.0 is a set of cybersecurity outcomes published by the US National Institute of Standards and Technology. If it has reached your business through a contract, a customer questionnaire or a board paper, this guide explains what the Framework is and how it is organised in NIST's own words, which of its outcomes a website or web application takes part in, and a crosswalk that shows, Subcategory by Subcategory, where a security test can add evidence and where only your own records, monitoring and response plans can.
For owners, managers and technical leads whose website or web application may have exposed personal information. This guide sets out Part IIIC of the Privacy Act 1988 from its own text: who it covers, what an eligible data breach is, the assessment of a suspected breach under section 26WH, when notification is required and what the statement contains. It then gives you a worksheet for the assessment period, with separate handoffs for a forensic responder and a post-remediation tester. Whether an incident must be notified is a decision for your business and its own adviser.
PCI DSS is the PCI Security Standards Council's standard for protecting payment account data. This guide sets out what the Council's own open pages say about who the standard covers, who decides how a merchant validates, what a self-assessment questionnaire is, and what an ASV scan report does and does not show. It then sets out, in this library's own terms, how such a scan differs from a penetration test, marks where a website or web application test can contribute evidence and where that evidence stops, and comes with a responsibility matrix for the records the merchant, the scanning vendor, the assessor and whoever fixes the findings each hold.
The PCI Security Standards Council says Requirements 6.4.3 and 11.6.1 of PCI DSS focus on the scripts on a payment page. This guide reads them only from the Council's open web pages, its FAQs, glossary and blog. It did not open the standard, which the Council publishes in its Document Library, or any self-assessment questionnaire. It sets out what those pages say the requirements are for, when they took effect, how SAQ A changed and who decides, then gives you a script ledger and change-detection evidence sheet for your own payment page.
Written for whoever runs or builds the website or web application of a business that has been asked about APP 11, whether in a customer questionnaire, a contract, an insurer's form or a letter from the regulator. It quotes the eleventh Australian Privacy Principle from the Act, sets out how the OAIC describes reasonable steps and technical and organisational measures, explains why the principle names no test, and gives you an evidence canvas that lines up kinds of measure with the test and retest records that can feed your own assessment.
For owners, managers and technical leads planning a new form, client portal, chatbot or hosting move, or asked for a PIA by a customer or an agency. This guide sets out the OAIC's method step by step, who has to carry out an assessment and who is encouraged to, and a worked data-flow canvas that traces an invented enquiry and client account record to show where a targeted test can inform a step.
SOC 2 is an examination of controls at a service organisation, performed by a licensed, independent CPA under the AICPA's attestation standards. If a customer has asked your business for a SOC 2 report, this guide sets out what the AICPA publishes openly about the examination, its report types and its criteria, where a website or web application test fits, and an evidence timeline with a sample packet for test records you may be asked to put before your service auditor.
The SOCI Act ties its duties to defined classes of critical infrastructure asset and to the entities that hold set roles for them. Among those duties are giving ownership and operational information for a register the Secretary keeps, a written risk management program, cyber security incident reports under sections 30BC and 30BD, each with its own trigger and time limit, and further obligations for Systems of National Significance. This guide reads the Act and its rules from the Federal Register of Legislation, shows where a website, portal or app can fall inside them, sets out the evidence that testing a web application can supply, and its limits, and comes with a decision tree for a responsible entity and the businesses that supply one.
For owners and technical leads of edtech businesses whose product has been asked to go through Safer Technologies 4 Schools (ST4S). This guide sets out the process, the outcomes and the framework versions from the ST4S site and its Supplier Guide, read on 15 November 2026, shows which criteria a web application touches, and comes with a worksheet that labels every piece of evidence as a supplier record, a school decision or an independent test artefact.
Buyer-evidence finder: the compliance guides side by side
Find the request in front of you in the second column, then read across: the document the guide explains and what it quotes, what it says a test's records can add, what it says they cannot show and who decides, where it says an independent, accredited or licensed party comes in, its table counted, and what its closing section says about a Clever Ops service. Naming a document in the third column says nothing about whether it applies to any business.
How to use itHide the instructions
Each cell restates its guide no more strongly than the guide does, rows follow the library's order, and the guides are linked under Pages in this section.
17 rows
Guide and address
Who is asking, in the guide's terms
Australian Privacy Principles, at /web-security/australian-privacy-principles.
- Who is asking, in the guide's terms
- A contract, a customer questionnaire or a complaint: written for owners, managers and technical leads whose business has met the Privacy Act 1988 in one of those.
- Document explained and what it quotes (named only)
- The thirteen principles in Schedule 1 to the Privacy Act 1988 (Cth), from Compilation No. 104 (compilation date 4 June 2026), with APP 1.7 to 1.9 noted from the Privacy and Other Legislation Amendment Act 2024. The OAIC's APP guidelines, its quick reference, small business and rights pages, and its history of the Act.
- What it says a test's records can add
- How a control behaved on the build, accounts and records tested, such as whether one customer's session could open another customer's record. A check that found nothing is a negative result for what was tried, and after fixes a retest records whether each finding was fixed.
- What it says they cannot show, and who decides
- Whether the business is an APP entity, whether a field is reasonably necessary, whether a use or disclosure is permitted or an exception applies, and nothing of training or procedures. The business decides with its adviser, and the regulator can form its own view.
- Independent, accredited or licensed parties, as the guide puts it
- Not covered: the guide names no assessor, auditor or accredited tester for the principles.
- Its table, counted
- Touchpoint map: 13 rows, one per principle, by 7 columns. Rows 1, 5, 8 and 9 read pages, documents and settings and send no test requests; the other nine send requests, submit forms or sign in, each with its own limits.
- What the guide says about a Clever Ops service
- The website security check for a site with no customer logins, the WordPress security audit, the web application and API penetration test (the ground of rows 11 to 13), and the AI chatbot and agent security test. The report is evidence for the business and its adviser, not a compliance opinion or a certificate.
Privacy Act APP 11, at /web-security/privacy-act-app-11.
- Who is asking, in the guide's terms
- A customer questionnaire, a contract, an insurer's form or a letter from the regulator asking a business about APP 11.
- Document explained and what it quotes (named only)
- APP 11.1 to 11.3 from the Privacy Act 1988, Compilation No. 104. The OAIC's chapter on APP 11 and its key concepts chapter, and its Guide to securing personal information (publication date 5 June 2018). Test ids from OWASP WSTG v4.2 and ASVS 5.0.0.
- What it says a test's records can add
- For each access, sign-in, transport, upload, logging and deletion check: what was sent, from which account, against which build, on which day, and what came back. After fixes, each finding's status on an identified later build: fixed, partially fixed, still reproducible or not retested.
- What it says they cannot show, and who decides
- Whether the business is an APP entity, whether a record is held, whether a step is reasonable, or whether information is still needed; training, policies, physical security and staff devices, except as documents someone hands over. The business decides first, with its adviser; the Commissioner can reach a view in an investigation, and a court in civil penalty proceedings.
- Independent, accredited or licensed parties, as the guide puts it
- The guide quotes the OAIC's Guide to securing personal information, whose testing questions include who is responsible for conducting testing, with internal or independent as its examples.
- Its table, counted
- Evidence canvas: 13 rows by 7 columns in three groups (rows 1 to 3, 4 to 11, and 12 and 13). Rows 4 to 8 and 10 send requests or create and delete test records, each stating its limits on the row; the other seven read or record.
- What the guide says about a Clever Ops service
- The website security check reaches the transport checks in row 7 and nothing behind a login. The web application and API penetration test covers the ground of rows 4, 5, 6 and 8, and its retest gives the canvas's retest column its four statuses. Clever Ops certifies no one and makes no decision on whether a business's steps were reasonable.
Notifiable Data Breaches, at /web-security/notifiable-data-breaches.
- Who is asking, in the guide's terms
- No outside request: the business's website or web application may have exposed personal information, and the guide follows the assessment of a suspected breach.
- Document explained and what it quotes (named only)
- Part IIIC of the Privacy Act 1988 (Cth), from Compilation No. 104, including the section 26WH assessment. The OAIC's pages on the scheme, on when to report and on reporting, its quick reference guide and its Data breach preparation and response guide. ASD's ACSC page on reporting.
- What it says a test's records can add
- After the fix, on a staging copy or the fixed build: whether the route, file or access rule that exposed the information still does so, and whether similar routes share the weakness. After a consolidated retest, which findings are fixed, partially fixed, still reproducible or not retested.
- What it says they cannot show, and who decides
- Who reached information in the past, how many records left the system, or whether someone still holds a copy; whether serious harm is likely, whether remedial action prevented it or whether an exception applies. The entity decides, with its own legal adviser.
- Independent, accredited or licensed parties, as the guide puts it
- The guide names no accreditation for the assessment, the forensic work or the test after the fix. Working out what happened goes to a forensic or incident response provider the entity chooses, or one its insurer's process names where the policy sets one, and row 16's tester is one the entity authorises in writing.
- Its table, counted
- Suspected breach worksheet: 17 rows by 6 columns. Rows 4 and 16 send requests, each with its own limits; every other row makes a record, reads documents or reads a preserved copy. Rows 15 and 16 are the handoffs to a forensic responder and to a tester after the fix.
- What the guide says about a Clever Ops service
- Clever Ops comes in once a specialist has cleaned the site and the fix is in, as the post-remediation tester in row 16. Forensics, incident response, malware cleanup and round-the-clock monitoring are not Clever Ops services, and whether an incident is notifiable stays with the entity and its adviser.
Cyber Insurance, at /web-security/cyber-insurance.
- Who is asking, in the guide's terms
- An insurer's proposal form, with the business's broker advising on cover.
- Document explained and what it quotes (named only)
- Four proposal forms as read on 15 November 2026: Chubb's Cyber ERM Short MarketPlace (published 11/2023), Standard (published 06/2023) and Extensive (footer reads "Published 06/0623") forms, and DUAL Australia's form 08.26. The Insurance Contracts Act 1984 (Cth), Compilation No. 33. The CVSS v3.1 specification.
- What it says a test's records can add
- Testing dates, the report date and version, the scope as tested, CVSS v3.1 scores to set against the remediation targets the Standard and Extensive forms ask about, and each finding's retest status. Only a finding the retest recorded as fixed is closed on the records.
- What it says they cannot show, and who decides
- Internal testing, the scanning questions and any system outside the scope are left for other records, and a website security check report is not a record of a penetration test. How an answer is read is the insurer's decision, and the broker advises on cover.
- Independent, accredited or licensed parties, as the guide puts it
- As read, neither the Standard form's tick boxes nor the Extensive form's questions 5 and 6 ask who performed the testing. If a broker or insurer asks for an independent tester, the guide says to pick a provider with no part in building or hosting the application.
- Its table, counted
- Comparison table: 11 rows, one per topic, by 8 columns, four of them one for each form. Every row reads only the forms and your own records and sends no request to any system.
- What the guide says about a Clever Ops service
- For an application in its scope, the web application and API penetration test's records relate to the external testing items and remediation questions on the Chubb Standard and Extensive forms. A website security check is not a penetration test. Answering the form stays with the business and its broker.
APRA CPS 234, at /web-security/cps-234.
- Who is asking, in the guide's terms
- The technology or risk lead at an APRA-regulated entity who has to show what was tested, and a supplier asked about CPS 234 in a questionnaire, a due diligence request or a contract.
- Document explained and what it quotes (named only)
- Prudential Standard CPS 234 Information Security as made (determination No. 1 of 2018, F2018L01745), read by paragraph number. APRA's page for the standard, CPG 234 as guidance, and paragraph 24 of CPS 230 on APRA's page.
- What it says a test's records can add
- A dated record about one information asset: the scope and depth tested, each finding's ratings, the remediation plan and retest status, and the tester's own statement of who did the work and whether it built, hosts or runs the system.
- What it says they cannot show, and who decides
- How the entity classifies its assets, its response plans, internal audit work and controls outside the scope; whether anything is material. A test is not a notification to APRA. The entity, its Board, internal audit and APRA judge the testing; for a supplier, the regulated customer.
- Independent, accredited or licensed parties, as the guide puts it
- The guide quotes paragraph 30 on testing by appropriately skilled and functionally independent specialists, and says whether a tester is both is the regulated entity's judgement.
- Its table, counted
- Control-testing calendar: 12 rows by 7 columns, C1 to C12, with C12 for a supplier. C6 and C9 send requests, each with its limits in the last column; every other row reads or writes records.
- What the guide says about a Clever Ops service
- One test can supply dated evidence about one web-facing asset for rows C7 to C10, and nothing in the guide is regulatory assurance. Where a policy, agreement or tender requires a CREST-accredited provider, the work is referred, because Clever Ops is not CREST accredited.
APRA CPS 230, at /web-security/cps-230.
- Who is asking, in the guide's terms
- The risk or technology lead at an APRA-regulated entity mapping what its online channels depend on, and a business that builds, hosts or runs something for one and has been sent a CPS 230 questionnaire, due diligence request or contract clause.
- Document explained and what it quotes (named only)
- Prudential Standard CPS 230 Operational Risk Management as made by determination No. 1 of 2026 (F2026L00475), with its explanatory statement. APRA's page for the standard, CPG 230 as guidance, and the text of CPS 234.
- What it says a test's records can add
- The scope as tested and an external hostname inventory for the dependency rows; a dated record of how one application's controls behaved; each finding's ratings and status after the retest; a supplier's report for the entity's assessment of controls; and the facts a tabletop exercise needs.
- What it says they cannot show, and who decides
- Whether an operation stays within tolerance, recovery times, backups and restores, the business continuity plan, whether a provider is material, and behaviour under load. The Board, senior management, internal audit and APRA decide for the entity; for a supplier, the regulated customer decides.
- Independent, accredited or licensed parties, as the guide puts it
- The guide quotes CPG 230, as guidance, that testing would be conducted by staff and teams independent of those with operational responsibility for controls.
- Its table, counted
- Dependency map and evidence register: 19 rows by 6 columns in three parts (M1 to M8, T1 to T5, E1 to E6). Only M8 sends requests, with its limits printed on the row; T1 to T5 are paper exercises, and the rest read or write records.
- What the guide says about a Clever Ops service
- The website security check and the web application and API penetration test feed named rows, and the WordPress security audit fits a public site built on WordPress. None of the three is an operational resilience assessment, and a report is not a certificate, a CPS 230 assessment or a compliance opinion.
SOCI Act, at /web-security/soci-act.
- Who is asking, in the guide's terms
- A business that may hold a role under the Act for an asset, and a supplier that has met the Act in a contract clause, a due diligence questionnaire or a request about incident reporting.
- Document explained and what it quotes (named only)
- The Security of Critical Infrastructure Act 2018, Compilation No. 9 (compilation date 4 June 2026). The CIRMP Rules (Compilation No. 2), the Application Rules (Compilation No. 1) and the Definitions Rules (Compilation No. 2). The Cyber and Infrastructure Security Centre's pages on the Act.
- What it says a test's records can add
- Findings and negative results on access, sessions and the API for the build tested, as input on hazards for one system; what the tested sign-in asked of test accounts; and a supplier's own report for the entity to weigh. Nothing towards incident reporting.
- What it says they cannot show, and who decides
- Whether an asset is a critical infrastructure asset or who its responsible entity is, operational technology and internal networks, whether a program meets Part 2A or whether an incident has to be reported. The entity, its governing body, its adviser and the officials the Act names decide; for a supplier, its customer and its own adviser.
- Independent, accredited or licensed parties, as the guide puts it
- The guide sets out sections 30CU and 30CW on vulnerability assessments and designated officers, and says a test run for another reason is not an assessment under the Act.
- Its table, counted
- Responsible-entity decision tree: 15 rows by 7 columns, T1 to T15, with T13 to T15 for a supplier. Every row works from documents, and none sends anything to any system.
- What the guide says about a Clever Ops service
- Awareness and referral material. A supplier can commission a Clever Ops test of its own website or application, after settling with its adviser whether that system is part of a critical infrastructure asset. Clever Ops offers no incident response.
ISO/IEC 27001, at /web-security/iso-27001.
- Who is asking, in the guide's terms
- A contract, tender, questionnaire or board decision that has put the standard in front of the business, or an auditor who cites it. The guide also names a parent company's policy.
- Document explained and what it quotes (named only)
- ISO/IEC 27001:2022 and its 2024 amendment, from IEC's open catalogue pages only. The guide was prepared with no access to the standard's text, and gives questions to put to your own licensed copy instead. It also quotes Queensland's IS18 policy and the CSA STAR Program page.
- What it says a test's records can add
- Route lists, roles and accounts for the inventory; findings with evidence, CVSS v3.1 scores and business-risk ratings for the risk record; findings mapped to OWASP Top 10:2025 and the checks that came back clean; each finding's retest status; and the scope, dates and exclusions for the review after a cycle.
- What it says they cannot show, and who decides
- How the ISMS is run, whether its scope and risk method are sound, whether reviews and audits take place, and networks, devices, backups and suppliers' platforms. It finds no conformity. The organisation decides on its ISMS, and an auditor decides what evidence they need.
- Independent, accredited or licensed parties, as the guide puts it
- The guide does not set out who may certify an organisation or who accredits certifiers. It suggests asking a provider that offers certification which body will issue the certificate, and whether that body is accredited and by whom.
- Its table, counted
- Evidence matrix: 13 rows by 7 columns, M1 to M13, completed from your own licensed copy. Only M7, a check before a release goes live, and M9 send requests, each with its limits and request count in the last column; the other eleven read or update records.
- What the guide says about a Clever Ops service
- A report is a dated record of what was tested and certifies nothing. Clever Ops holds no ISO/IEC 27001 certificate and is not a certification body, and none of its tests is an ISMS audit or a certification audit.
SOC 2 Compliance, at /web-security/soc-2.
- Who is asking, in the guide's terms
- A customer asking for a SOC 2 report in a security questionnaire, a tender or a contract clause. The guide also covers meeting SOC 2 from the buyer's side, when a supplier shows a logo.
- Document explained and what it quotes (named only)
- The AICPA's open pages: its SOC suite page, the product page for its SOC 2 guide, the download page for the Trust Services Criteria, its announcement of 28 October 2026 on proposed criteria, its logo pages and its illustrative SOC 2 type 2 report. Written without the text of the criteria, as the guide says.
- What it says a test's records can add
- The scope as tested, the dates and build, findings with redacted evidence and a fix, negative results, remediation and each finding's retest status, and the tester's relationship to the system, for a service auditor to weigh.
- What it says they cannot show, and who decides
- The examination's own testing, controls outside the system tested, vendors' platforms and anything released after the test; a test report is not an opinion. The service auditor judges whether a record bears on any criterion, and the customer whether what you send meets its request.
- Independent, accredited or licensed parties, as the guide puts it
- The guide quotes the AICPA describing SOC 2 as an examination performed by a licensed, independent CPA under the AICPA Attestation Standards.
- Its table, counted
- Evidence timeline and sample packet: 17 rows by 7 columns, T1 to T8 and P1 to P9, with sample entries for an invented business on invented dates. Only T6 sends requests, three in total, with its limits on the row.
- What the guide says about a Clever Ops service
- The web application and API penetration test's report holds parts the sample packet draws on. It is not the examination, a SOC 2 report, a certificate or a compliance opinion. When a service auditor or customer asks for independence, choose a tester that neither built nor runs the system.
PCI DSS, at /web-security/pci-dss.
- Who is asking, in the guide's terms
- A business that takes card payments through a website or web application and has met PCI DSS through a merchant agreement, a payment provider's request, a customer's questionnaire or an insurer's form.
- Document explained and what it quotes (named only)
- The PCI Security Standards Council's open pages: its PCI DSS page, glossary, Merchant Resources page, dated FAQs and blog posts, and its pages on Approved Scanning Vendors and Qualified Security Assessors. Written without the text of the standard, which the guide asks you to read in your own copy.
- What it says a test's records can add
- For the scope rows, the targets, routes, roles and accounts tested. For the testing rows, the scope as tested, findings with CVSS v3.1 scores and business-risk ratings, checks that found nothing, the test cases a web application test could not run, and retest statuses. A dated record of a test after a change, where one followed.
- What it says they cannot show, and who decides
- It is not an ASV scan, a self-assessment questionnaire, a Report on Compliance or an attestation, and it covers nothing of the payment provider's platform or the merchant's internal networks. In the Council's FAQs, the compliance-accepting entity, typically an acquirer or payment brand, determines how compliance is evidenced.
- Independent, accredited or licensed parties, as the guide puts it
- The guide quotes the Council describing QSAs as independent security organisations qualified and trained by it to perform assessments, and ASVs as qualified and trained to scan. Whether PCI DSS says who may carry out penetration testing is, it says, a question for the standard's text.
- Its table, counted
- Responsibility matrix: 14 rows by 7 columns, R1 to R14. R12, an access check after a change to the store, is the only row that sends anything, with its limits written into the row.
- What the guide says about a Clever Ops service
- Clever Ops is not an Approved Scanning Vendor or a Qualified Security Assessor, and refers a merchant that needs either to a company the Council lists. A report is not an Attestation of Compliance or a certificate, and the payment work stays on the merchant's side of the payment.
PCI DSS 6.4.3 and 11.6.1, at /web-security/pci-payment-script-controls.
- Who is asking, in the guide's terms
- No outside request in the opening: the guide starts from the merchant's own payment page and sends the questions of what applies to the acquirer or payment brand, and to an assessor where one is engaged.
- Document explained and what it quotes (named only)
- The Council's open FAQs, glossary, Merchant Resources and assessor pages, blog posts and a podcast transcript, with MDN and OWASP pages. The guide did not open the standard or any self-assessment questionnaire; its subheadline says the Council describes the two requirements as focusing on the scripts on a payment page.
- What it says a test's records can add
- What a review of your own payment page can record, for the loads a row names, on a stated build and day: which scripts the browser fetched and from where, which external scripts carried an integrity check, which security headers came with the page, and what changed since the last recorded load.
- What it says they cannot show, and who decides
- What other visitors received, what happens on another company's server or inside the payment provider's frame, and whether a script is harmful. Whether the requirements are met or SAQ A applies is for the merchant with its acquirer or payment brand, and its assessor where one is engaged.
- Independent, accredited or licensed parties, as the guide puts it
- The guide quotes the Council describing Qualified Security Assessor companies as independent security organisations it qualifies, and leaves scans and tester independence to the PCI DSS guide.
- Its table, counted
- Payment page script ledger: 17 rows by 6 columns (L1 to L8, C1 to C4, A1 to A5). L1, L2, L7, L8, C1 and C2 look at your own payment page and carry their limits on the row. Only L1, C1 and C2 load pages, with at most one submission of invented checkout details and one test-account sign-in, no card details entered and no payment submitted, and L8 sends a request only through the security headers checker's site check. The others work from records, from L1's load or from written questions.
- What the guide says about a Clever Ops service
- The WordPress security audit lists each script a WooCommerce checkout loads, a starting point for row L2, and the penetration test takes in payment flows on the application's side. A report is not a PCI DSS assessment or an ASV scan and confirms the SAQ A criterion for no one.
ST4S Assessment, at /web-security/st4s.
- Who is asking, in the guide's terms
- An edtech supplier whose product has been asked to go through Safer Technologies 4 Schools, after nominating itself or being invited by a school or education authority.
- Document explained and what it quotes (named only)
- The ST4S site and the ST4S Supplier Guide, release 2026.1, read on 15 November 2026, with criteria named by identifier and described in short form because the Supplier Guide reserves its wording.
- What it says a test's records can add
- For the penetration testing element of criterion T1, one report on one build: the build, dates, roles, accounts and exclusions, with each finding's status after the retest. Whether to lodge it, and in what redacted form, is the supplier's decision.
- What it says they cannot show, and who decides
- A monitoring plan, a scan schedule, a patching record, a development process, testing of later releases, and criteria that rest on the supplier's own records. The ST4S Team analyses and validates responses, and the school or education authority decides what to accept.
- Independent, accredited or licensed parties, as the guide puts it
- T1's response options distinguish an answer that also uses outside, independent testers, and section 6.8 lets the ST4S Team ask a tester for proof of certification. The guide says to ask the Team what it expects of the tester before any test is booked.
- Its table, counted
- Question-to-evidence worksheet: 15 rows by 7 columns, built on two invented schools on a staging copy. Rows 3, 5, 11, 12, 14 and 15 are read-only; the other nine send requests or sign in, each with its limits in its fifth column.
- What the guide says about a Clever Ops service
- The web application and API penetration test, with two test accounts for each role and accounts in two schools, sits on rows 6 to 10. A report is not an ST4S assessment, an outcome or a badge. When an authority or contract requires a CREST-accredited provider, Clever Ops passes the work to one.
Cyber Security Act 2024, at /web-security/cyber-security-act-2024.
- Who is asking, in the guide's terms
- A board paper, an insurer's proposal form, a customer's questionnaire or an incident response plan in which the business has met the Act; the guide concentrates on the report after a ransomware payment.
- Document explained and what it quotes (named only)
- The Cyber Security Act 2024 as made (C2024A00098), the Cyber Security (Ransomware Payment Reporting) Rules 2025 and the Cyber Security (Security Standards for Smart Devices) Rules 2025. The Department of Home Affairs' pages and factsheet, and ASD's ACSC page on reporting. It sets the Privacy Act and SOCI Act clocks, from their compilations of 4 June 2026, beside the ransomware payment clock.
- What it says a test's records can add
- Before an incident, a dated report on one website or application, with its scope as tested, findings, negative results and retest statuses (row R4); after the cleanup, a test record (row R13). The guide is plain that the Act does not ask for a website test.
- What it says they cannot show, and who decides
- Whether the business is a reporting business entity, what was exploited in an incident, the content of a ransomware payment report, a view on any payment, a Privacy Act assessment or a SOCI Act report. The business decides with its lawyer or privacy adviser, and the Department of Home Affairs administers the Act.
- Independent, accredited or licensed parties, as the guide puts it
- Not covered for a website test. The guide notes that where the Act speaks of testing, in section 23, it is about the examination of a relevant connectable product.
- Its table, counted
- Reporting timeline and evidence pack: 16 rows by 7 columns, R1 to R16. No row sends test requests, and twelve begin their test column with Nothing. R13 records a test that runs under its own written scope and authorisation, with that test's limits on the row.
- What the guide says about a Clever Ops service
- Two rows of the pack: R4 before an incident, and R13 once an incident response specialist has finished the cleanup. Incident response, forensics, malware cleanup and round-the-clock monitoring sit outside what Clever Ops sells, and how the Act applies is for the business and its lawyer.
NIST CSF 2.0, at /web-security/nist-csf.
- Who is asking, in the guide's terms
- A contract, a customer questionnaire or a board paper that has brought the Framework to the business. The guide also names a parent company that set it as policy.
- Document explained and what it quotes (named only)
- NIST CSWP 29, the CSF 2.0 publication dated 26 February 2024, with Subcategory wording from its Appendix A. NIST's CSF FAQs and About page, its Implementation Examples workbook and its Informative References page. OWASP WSTG v4.2 and ASVS 5.0.0.
- What it says a test's records can add
- Findings with evidence (ID.RA-01), the remediation plan and retest statuses (ID.RA-06 and ID.IM-02), negative results for the sign-in and access checks run (PR.AA-03 and PR.AA-05), external check results, and the scope with its exclusions, for the system and dates tested. An input to those Subcategories and proof of none of them.
- What it says they cannot show, and who decides
- Govern outcomes, awareness and training, physical access, backups, capacity, continuous monitoring, response and recovery, and everything outside the scope. Whoever asked decides whether the evidence is enough, and may use its own auditor or assessor.
- Independent, accredited or licensed parties, as the guide puts it
- The guide quotes NIST's FAQ: NIST does not offer certifications or endorsements of CSF-related products, implementations or services, and has no plans to develop a conformity assessment program.
- Its table, counted
- Evidence crosswalk: 26 rows by 7 columns, one per Subcategory. Four rows (ID.AM-03, PR.AA-03, PR.AA-05 and PR.DS-02) send requests, with their limits in the last column; in every other row you read, ask or write a record.
- What the guide says about a Clever Ops service
- The evidence lands chiefly in ID.RA-01, ID.RA-06, ID.IM-02 and the Protect rows for the system tested. A Clever Ops test is not a CSF assessment and produces no Organizational Profile, Tier, maturity rating or certification.
Privacy Impact Assessment, at /web-security/privacy-impact-assessment.
- Who is asking, in the guide's terms
- A project before it goes live, such as a new form, client portal, chatbot or hosting move, or a request for a PIA from a customer or an agency.
- Document explained and what it quotes (named only)
- The OAIC's Guide to undertaking privacy impact assessments (publication date 2 September 2021) and its ten-step page (29 April 2021). Section 33D of the Privacy Act 1988, Compilation No. 104. The Australian Government Agencies Privacy Code. Chapter 1 of the OAIC's APP guidelines.
- What it says a test's records can add
- Inputs at steps 5, 6, 7 and 10: whether one invented client could open another's record or file, whether a signed-out browser could, whether a typed value reached an analytics or advertising host, how many copies an enquiry left, and whether a staff action was logged.
- What it says they cannot show, and who decides
- Whether a field is necessary, whether a use is one people would expect, whether consultation was enough, community expectations, exceptions, and whether an outcome is acceptable. The entity running the project decides; the OAIC has no role in approving a private sector organisation's PIA.
- Independent, accredited or licensed parties, as the guide puts it
- The guide quotes the OAIC that a robust and independent PIA conducted by external assessors may be preferable where a project will have substantially more privacy impact than others, and notes that privacy consultancies and law firms offer PIAs as a service.
- Its table, counted
- Worked data-flow canvas: 14 rows by 7 columns, for an invented business. Rows P0, E2, E3, A5 and R1 send no test requests; the other nine send requests, sign in or change test records, each stating its own limits.
- What the guide says about a Clever Ops service
- The penetration test overlaps rows A1 and A2 and the role questions in A3, and row R1 carries the retest status into step 10. None of the services is a PIA, a report neither completes nor approves one, and the PIA stays with the business and the adviser it chooses.
APP 8 Cross-Border Disclosure, at /web-security/app-8-cross-border-disclosure.
- Who is asking, in the guide's terms
- A privacy policy review, a customer questionnaire, a contract's data-location clause or a question from the business's adviser.
- Document explained and what it quotes (named only)
- APP 8 and section 16C of the Privacy Act 1988 (Cth), Compilation No. 104. Chapter 8 of the OAIC's APP guidelines (updated 3 October 2025) and its quick reference. The Privacy Regulations 2025. OWASP ASVS 5.0.0.
- What it says a test's records can add
- Which hosts received requests from the pages, forms and widgets tested, which fields each request carried, what the logs recorded for a test request, and where the hosting settings say data sits, each on a stated build and date.
- What it says they cannot show, and who decides
- Where a recipient keeps information after it arrives, whether an arrangement is a use or a disclosure, whether steps are reasonable or an exception applies, and whether a recipient keeps to its contract. The business decides with its adviser.
- Independent, accredited or licensed parties, as the guide puts it
- The guide names no assessor or accredited tester; its three rows that send requests are for a developer or tester the business has authorised in writing. On a belief under APP 8.2(a), the guide quotes the OAIC that a reasonable basis might, for example, be independent legal advice.
- Its table, counted
- Cross-border data-flow register: 14 rows by 8 columns, R1 to R14. R2, R4 and R5 send requests, each with its own limits; the other eleven read lists, settings, logs, contracts or notices.
- What the guide says about a Clever Ops service
- The website security check, the penetration test and the AI chatbot test each stop at a defined edge, and none builds the register or decides an APP 8 question. A report is a record of what was checked, not a certificate or a compliance opinion.
CREST Penetration Testing Explained, at /web-security/crest-penetration-testing.
- Who is asking, in the guide's terms
- A request for tender, a panel application or a customer contract saying penetration testing has to be done by a CREST member company, by CREST-certified testers, or by an equivalent.
- Document explained and what it quotes (named only)
- CREST International's and CREST ANZ's own pages, as read on 15 November 2026, on membership, accreditation, the Pathway stages, certifications held by people, approved companies and ABPT accreditation. The guide keeps the two bodies apart.
- What it says a test's records can add
- Not a test guide. It reads the wording of a CREST clause, and says the wording CREST International recommends is about who does the work; what one test covers comes from your scope, and its scope sheet is the brief for a provider.
- What it says they cannot show, and who decides
- Whether a provider meets the clause, whether an equivalent is acceptable and whether a submission complies. The issuer of the document decides, and so does any party whose contract the clause came from.
- Independent, accredited or licensed parties, as the guide puts it
- The subject of the guide: CREST International accredits organisations and examines people, and CREST ANZ approves companies and accredits individual testers. Each body publishes its own list, which is where a check of a provider's status ends.
- Its table, counted
- Decoder, equivalence questions and scope sheet: 27 rows by 6 columns (D1 to D10, E1 to E8, S1 to S9). Every row reads documents or records decisions; none sends a test request, signs in or submits a form.
- What the guide says about a Clever Ops service
- Clever Ops is not CREST accredited and refers work that requires a CREST-accredited provider. A document that requires a CREST ANZ approved company or ABPT-accredited testers gets the same referral, and an "or equivalent" does not change it. Where a document names no scheme, its exact words are where the scoping call starts.
About this library
Web security compliance guides, arranged by who is asking for evidence
This part of the library is for the moment another party asks your business to show its security.
A customer sends a questionnaire or a contract clause. An insurer sends a proposal form. A supplier agreement or a regulator's standard puts a question to your technology lead. An auditor or examiner asks for records, or a form, portal or release is about to go live.
Each guide here takes the documents behind one such request or duty, sets out what they say in their own words, and says where the evidence it describes can help and where it stops.
The buyer-evidence finder on this page gives each guide one row, read across eight columns: the guide and its address, who is asking in the guide's own terms, the document it explains and what it quotes, what it says a test's records can add, what it says they cannot show and who decides, where it says an independent, accredited or licensed party comes in, its table counted, and what it says about a Clever Ops service.
Read as a set, the rows show which guide holds the website compliance security checklist for your request, and which records can serve as customer security evidence or application security audit evidence in that guide's terms.
Every cell restates its own guide and adds nothing to it. This index says nothing about what any law, standard or scheme requires and nothing about whether one applies to your business: each guide leaves that question with you and the party it names, such as your adviser, your broker, your acquirer or your CPA firm.
The index offers no certification or legal sign-off, and a Clever Ops report is evidence for a decision someone else makes. It is not a certificate or a compliance opinion.
How the buyer-evidence finder is laid out
The rows follow the library's own order, from the Australian Privacy Principles to CREST penetration testing, and this page refers to each by its guide's name.
There is no filter on the table. To narrow it, read down a single column: down the second for the kind of request you have received, down the sixth for where an independent or accredited party comes in, or down the seventh to see which tables send requests and which only read.
- Guide and address: the guide's title and where it sits in the library.
- Who is asking: the requests the guide's opening sections describe, in its own words. Where an opening names no outside request, the cell says so.
- Document explained and what it quotes: each Act, instrument, standard, form or publisher's page named as the guide names it, with the edition, compilation or reading date the guide gives.
- What a test's records can add: the report and retest records the guide says can feed its table. Where a guide is not about testing, the cell says so.
- What they cannot show, and who decides: the guide's own limits on a test, and the party it says makes the decision.
- Independent, accredited or licensed parties: what the guide says about who may assess, certify, audit, scan or test, with "not covered" where it names no one.
- Its table, counted: rows and columns counted from the guide as published, its row groups, and which rows send requests.
- What the guide says about Clever Ops: only what its closing section says about which service fits and where it stops.
The third column names documents and decides nothing
Naming an Act, an instrument, a standard or a form in the finder is not a statement that it applies to any business, to any kind of business or to you. Each guide quotes particular passages for what their text says and leaves the rest to the reader and the party it names.
A shortened version of a provision here would be a second and weaker copy of it, so the provisions stay in the guides.
Four guides were written without the text of the standard they explain, and each says so: ISO/IEC 27001, read from IEC's open catalogue pages; SOC 2, read from the AICPA's open pages without the Trust Services Criteria; and PCI DSS and the payment script guide, read from the PCI Security Standards Council's open pages.
Their rows describe each guide as it describes itself and give no clause, control, criterion or requirement number beyond the script guide's own title.
Start from the request in front of you
Pick a guide from the words of the request rather than from its subject.
Each route below names the guides whose opening sections describe that kind of request. Several guides name more than one route, and the finder's second column shows which.
The Australian Privacy Principles, APP 11, APP 8, ISO/IEC 27001, SOC 2, PCI DSS, NIST CSF 2.0 and Cyber Security Act 2024 guides each name a customer's questionnaire, a contract or both among the ways their document reaches a business, and the privacy impact assessment guide names a customer asking for a PIA.
The CPS 234, CPS 230 and SOCI Act guides are also written for a supplier asked about the standard or Act in a questionnaire, a due diligence request or a contract clause.
The CREST guide starts from a tender, panel application or contract that names CREST, and the ST4S guide from a request to put an edtech product through Safer Technologies 4 Schools.
For the rest of a questionnaire, the Australian Privacy Principles guide points to the security questionnaires guide for which questions a test can evidence and how to word an honest answer.
The cyber insurance guide sets four proposal forms side by side, Chubb's three Cyber ERM forms and DUAL Australia's form 08.26, as read on 15 November 2026, and ties each testing question to the records behind an answer. As read that day, two of the four ask about penetration testing and two do not, and the guide is clear that this is a reading of four documents, not a statement about cyber insurance in general.
The APP 11, PCI DSS and Cyber Security Act 2024 guides also name an insurer's form among the ways their document reaches a business, and the notifiable data breaches guide asks you to check what any cyber insurance policy asks of the business before it engages an incident response provider.
These guides read an Act or a prudential standard from its text for a business working out where it stands, and each leaves that to the business and its adviser. The Australian Privacy Principles guide names a complaint, and the APP 11 guide a letter from the regulator.
The notifiable data breaches guide follows the assessment of a suspected breach of a website or web application, from the day the business became aware to the review afterwards. The CPS 234 and CPS 230 guides are written for the technology or risk lead at an APRA-regulated entity as well as for its suppliers, and the SOCI Act guide for a business that may hold a role under that Act for an asset.
The Cyber Security Act 2024 guide concentrates on the report after a ransomware payment, and the privacy impact assessment guide reads the Australian Government Agencies Privacy Code for agencies beside the OAIC's encouragement to other organisations.
The ISO/IEC 27001, SOC 2 and PCI DSS guides prepare records for someone else's audit, examination or assessment. The ISO/IEC 27001 matrix ends in a pack for an external audit, and the guide asks you to put that row's questions to your auditor before a test is scoped.
The SOC 2 timeline places test records against the dates your CPA firm sets for the report. The PCI DSS matrix sets out the records the merchant, the scanning vendor, the assessor and whoever fixes the findings each hold.
The CPS 234 and CPS 230 guides also name the regulated entity's internal audit function among those who weigh testing evidence.
The privacy impact assessment guide is written for a project before it goes live, such as a new form, client portal, chatbot or hosting move. One way it suggests bridging the gap between a design and a build is to complete the PIA on the design, carry each security question forward as an open item with an owner, and test a staging build before launch.
Other tables carry a row for a release or a change. ISO/IEC 27001 row M7 is a security check before a release goes live, SOC 2 row T6 a narrow check after a significant release, CPS 234 row C6 a check after a material change, PCI DSS row R12 an access check after a change to the store, and the payment script ledger's rows C1 to C4 the change records for the payment page, from a baseline to a sign-off.
The CREST guide decodes tender and contract wording against CREST International's and CREST ANZ's own pages, lists the questions an issuer answers before deciding on any equivalent, and comes with a scope sheet for briefing the provider you engage. Where a request asks for independence rather than a named scheme, the finder's sixth column shows what each guide says about it.
Where the parts of a test report land in the guides' tables
The web security hub lists what a Clever Ops report holds: the scope as tested, each finding with its evidence redacted and a fix, a CVSS v3.1 score and a business-risk rating for each rated finding, checks that found nothing recorded as negative results for the build and accounts tested, and a remediation plan in priority order.
Every test includes one consolidated retest, after which each finding is fixed, partially fixed, still reproducible or not retested.
The guides file those parts in different places, and each item below gives what that guide's closing section names: rows, a column, a packet or form questions.
- Australian Privacy Principles: rows 11 to 13 of the touchpoint map, for a custom application.
- APP 11: rows 4, 5, 6 and 8 for a custom application, row 7 for the website security check's transport checks, and the canvas's retest column.
- Notifiable Data Breaches: row 16, the handoff to a tester after the fix.
- Cyber insurance: testing dates, the scope as tested, CVSS scores against remediation targets and retest statuses, for the external testing and remediation questions on the Chubb Standard and Extensive forms.
- CPS 234: rows C7 to C10 of the calendar, for one web-facing asset.
- CPS 230: the website security check's hostname inventory and certificate and DNS results in rows M3, M7 and T1, and the penetration test's results in rows M4 to M6, T2 to T4, E1, E2, E5 and E6.
- ISO/IEC 27001: the matrix's fourth column, which shows which parts, if any, each row can use.
- SOC 2: the sample packet, which draws on parts the penetration test report holds.
- PCI DSS: the website security check's hostname inventory in row R3, and an audit or penetration test report and retest in rows R8, R10 and R13.
- PCI DSS 6.4.3 and 11.6.1: the WordPress security audit's list of checkout scripts, as a starting point for row L2.
- ST4S: rows 6 to 10 of the worksheet, and EV10 if the supplier decides to lodge the report.
- Cyber Security Act 2024: row R4 before an incident and row R13 after the cleanup.
- NIST CSF 2.0: chiefly ID.RA-01, ID.RA-06, ID.IM-02 and the Protect rows for the system tested.
- Privacy impact assessment: rows A1 and A2 and the role questions in row A3, with row R1 carrying the retest status into step 10.
Closing sections that name no row
The closing sections of the SOCI Act, APP 8 and CREST guides name no part of their tables for a report. The SOCI Act guide calls itself awareness and referral material, the APP 8 guide says none of the services builds its register or decides an APP 8 question, and the CREST guide's scope sheet is a brief for whichever provider you engage.
In each guide listed above, the row a part lands in has a column for what it cannot show or where it stops, and the decision stays with the party the guide names.
What these guides say a test cannot show
A test record speaks for what was tried, on which build and accounts, on which day.
Each guide draws its own edges, and each point below names the guides that make it.
- Whether the document applies, or is met. No guide lets a test report settle whether a law, standard or scheme reaches the business, or whether the business meets it.
- Judgement calls. Whether a step is reasonable, a field necessary or an exception available is for the business and its adviser in the Australian Privacy Principles, APP 11, APP 8 and privacy impact assessment guides.
- What happened before. The notifiable data breaches guide says a test cannot say who reached information in the past or whether someone still holds a copy, and the Cyber Security Act 2024 guide that it cannot say what was exploited in an incident.
- Outside the scope. Office networks and the platforms vendors run sit outside a web application test in the CPS 234, CPS 230, ISO/IEC 27001, SOC 2 and NIST CSF guides, and the two PCI guides leave the payment provider's own platform, hosted pages or frame untested.
- Organisational measures. Staff training is out of a test's sight in the Australian Privacy Principles, APP 11, SOC 2, NIST CSF and privacy impact assessment guides.
- Load and capacity. The CPS 230 guide says a web application test does not test behaviour under load, and the NIST CSF crosswalk answers its capacity row from the hosting plan and the provider's availability terms.
- Later builds. A result speaks for the build and accounts tested, and the SOC 2 and PCI DSS guides add that it covers nothing released after the test.
Where an independent, accredited or licensed party comes in
The finder's sixth column keeps each guide's own terms.
Grouped by kind, they fall as follows.
- A licensed professional. The SOC 2 guide quotes the AICPA describing SOC 2 as an examination performed by a licensed, independent CPA under the AICPA Attestation Standards.
- Roles a standards body qualifies. The PCI DSS guide quotes the PCI Security Standards Council on Qualified Security Assessors and Approved Scanning Vendors, and says none of the open pages it read covers who may carry out penetration testing. The payment script guide quotes the Council on Qualified Security Assessor companies and leaves tester independence to the PCI DSS guide.
- Schemes for testing providers. The CREST guide sets out what CREST International and CREST ANZ each accredit, approve or certify, and leaves whether a provider meets a clause to the document's issuer.
- Independence weighed by the regulated entity. The CPS 234 guide quotes paragraph 30 on appropriately skilled and functionally independent specialists, and the CPS 230 guide quotes CPG 230, as guidance, on testing by staff and teams independent of those with operational responsibility for controls.
- Certification and its absence. The ISO/IEC 27001 guide does not set out who may certify or who accredits certifiers, and suggests asking. The NIST CSF guide quotes NIST that it offers no certifications or endorsements of CSF implementations.
- What a buyer or regulator may look for. The ST4S guide notes T1's option for outside, independent testers, and that section 6.8 lets the ST4S Team ask a tester for proof of certification. The privacy impact assessment guide quotes the OAIC that an independent PIA by external assessors may be preferable for a project with substantially more privacy impact. The APP 11 guide quotes the OAIC's testing questions, which give internal or independent as examples of who conducts testing. The cyber insurance guide finds that, as read, neither form that asks about penetration testing asks who performed it, and says that if a broker or insurer asks for an independent tester, to pick a provider with no part in building or hosting the application.
- Not covered. The Australian Privacy Principles and APP 8 guides name no assessor or accredited tester for the principles they explain. The notifiable data breaches, SOCI Act and Cyber Security Act 2024 guides name roles rather than an accreditation: a forensic responder, a designated officer, and an expert examining a connectable product.
Where Clever Ops stands
Clever Ops holds no security certification or accreditation. It is not CREST accredited, so where a tender, panel or contract requires a CREST-accredited provider, we refer that work to a provider that is. It is not a PCI Approved Scanning Vendor or a Qualified Security Assessor, so an ASV scan or a QSA assessment goes to a provider that holds that role.
When Clever Ops built or runs the system, the work is a security review, not an independent penetration test, and the report states who built and who hosts it. Where a request asks for a tester with no hand in building or running the system, several guides, among them CPS 234, CPS 230, SOC 2, PCI DSS, NIST CSF and CREST, say to engage a provider that did neither.
Where a Clever Ops service fits beside these guides
Clever Ops tests the parts of a business that customers, and attackers, reach through a browser or an API: a website security check from outside without logging in, a WordPress security audit, a web application and API penetration test of a custom application that customers or staff sign in to, a vibe-coded app security check, and an AI chatbot and agent security test.
The finder's last column gives only what each guide's closing section says about which of those fits and where it stops.
A test report is evidence for a decision someone else makes, such as a customer, an auditor or an insurer. It is not a certificate or a compliance opinion, and the decision on whether a law, standard or scheme applies, and whether it is met, stays with your business and the parties each guide names.
If your request asks for a penetration test and names no scheme, bring its exact words to a scoping call, as the CREST and cyber insurance guides both say.
- Internal networks, servers, Active Directory, staff devices, red teaming, phishing or physical testing need a network or red team specialist.
- Denial-of-service, load or volumetric testing is not part of any Clever Ops service.
- A site that is hacked now, malware cleanup, forensics, incident response or round-the-clock monitoring: call an incident response specialist first. Once the site is clean, an audit can check the web application before you rely on it again.
- Services run by other businesses, such as a hosted payment page or a booking platform on one of your subdomains, stay out of scope unless their owner agrees.
- Live Shopify storefronts and Laravel applications sit outside these services.
Frequently asked questions
The one whose document is named in the request in front of you: the Act, standard, scheme, form or clause the customer, insurer, regulator or auditor cites. If the request names none, start from the section on the request in front of you, which sorts the guides by who is asking, and read the finder's second column. Where a request names two documents, open both guides: each table covers its own document.
This page does not say, and neither do the guides. Each one quotes particular passages for what their text says and leaves the question to you and the party it names, such as your own adviser, your broker, your acquirer or your CPA firm. The third column lists what each guide quotes so you know which guide to open before that conversation. Naming a document there is not a statement that it applies to any business.
Each guide's table works as one for its own document. Read down its first column to find the row you need, and across that row for what to record and what it cannot settle. Before you run any row that sends a request, signs in or submits a form, read the limits printed on that row and keep to them, starting with the systems it allows. Rows that only read can be worked from your own records, settings and documents.
In these guides' terms, a dated record of one system: the scope as tested, findings with redacted evidence and their ratings, checks that found nothing as negative results for the build and accounts tested, and each finding's status after the retest. Whether that answers a particular question is for whoever asked it, and the section on where the parts of a report land shows where each guide files them.
That turns on the document in front of you. The sixth column of the finder gives what each guide says, in its own terms. Where a tender, panel or contract requires a CREST-accredited provider, Clever Ops refers the work, because it is not CREST accredited. Where a request asks for a tester independent of the build and hosting, and Clever Ops built or hosts the system, its work there is a security review rather than an independent test, so engage a provider that did neither.
No. Each guide treats a report as evidence for someone else's decision, and none lets it settle whether a law, standard or scheme applies or is met. A Clever Ops report is not a certificate or a compliance opinion, and Clever Ops holds no security certification or accreditation. The finder's sixth column shows what each guide says about who examines, assesses or certifies.
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.