Web security by industry: pick the guide that follows the work your business does online
Ten guides, each built around one kind of business: healthcare practices, law firms, accounting practices, schools and edtech suppliers, online stores, SaaS products, financial-service businesses, real estate agencies, hospitality businesses and project-based firms.
The workflow selector sets them side by side: the data each guide follows, the portals and sign-ins it covers, where it draws the payment boundary, how documents move, which laws and standards it quotes, its test table counted, and what it says about a Clever Ops service.
On this page
Pages in this section
10 pages
For practice owners, practice managers and technical leads. This guide follows a patient from an online booking to a payment notice, shows where health information is copied along the way and who can reach each copy, and gives you a control matrix of test cases to run on your own systems with invented patients.
A guide for the principal, practice manager or technical lead of an Australian law firm. It follows a matter from the first website enquiry to the trust-payment handoff, shows where client data passes through forms, portals and integrations at each step, and comes with a matter-lifecycle checklist of test cases to run on your own systems, each with the limits it keeps.
Cyber Security for Accountants
An accounting or bookkeeping practice can hold tax file numbers, identity documents, workpapers, payroll files and logins to its clients' ledgers, and its busiest weeks can bring seasonal staff and a stream of shared documents. This guide follows that workflow from first enquiry to former client, sets out the duties that may bear on a practice as their own text states them, and gives a tax-season matrix of access tests and change-freeze evidence to run on systems your practice runs or holds accounts in.
For school business managers, IT leads and the edtech suppliers that serve schools. This guide follows applications, enrolment, guardian messages, learning portals, student uploads, excursions and the outside services behind them, keeps school-operated sites apart from supplier platforms and guardian access apart from staff access, and comes with a workflow test matrix to run on your own systems with invented students, guardians, teachers, office staff and suppliers.
An online store passes personal details, money and stock through a chain of steps: customer accounts, carts, coupons, the handoff to a payment provider, refunds, exports, fulfilment webhooks and loyalty apps. This guide follows that chain across platforms, shows where access breaks at each step and which guide covers each flaw, sets out the payment-page and privacy questions a store settles with others, and gives you an order-path abuse and evidence matrix to run on a staging copy of your own store.
For the founder, CTO or technical lead of a software business that sells subscriptions to other businesses. This guide follows a customer tenant from sign-up to cancellation, shows where one tenant's data can reach another, and gives you a two-tenant evidence grid to run on a staging copy of your own product, with fields for the scope, exceptions, remediation and retest status a buyer or auditor may ask to see.
A lender, mortgage broker, advice practice or fintech product company handles loan and investment enquiries, bank statements, identity records, adviser handoffs and payment authorities, and several of those steps can run through a website, a portal or an integration. This guide follows that workflow, sets out what CPS 234, CPS 230, the Corporations Act, the National Consumer Credit Protection Act and the Privacy Act say and whom each names, and gives a matrix of tests for your own systems, with separate evidence routes for APRA-regulated entities, their suppliers and businesses outside APRA's remit.
A guide for the principal, licensee or property management lead of an Australian real estate agency. It follows a rental through inspection bookings, applications with identity and bank documents, the lease, maintenance requests, contractor work orders, owner portals and changes to payment details, and comes with a rental-to-lease checklist of tests to run on your own systems with invented applicants, property managers, landlords and contractors.
For owners, managers and technical leads of accommodation, restaurant and event businesses. This guide follows a guest through direct bookings, channel-manager handoffs, modification links, group rooming lists, table reservations, event enquiries, gift cards and refunds, shows where each step can put a guest's details within reach of the wrong person, and gives you a guest-journey checklist of test cases to run on your own site with invented guests.
Professional Services Cyber Security
For the principal, operations lead or technical lead of a consultancy, an engineering or architecture practice, an agency or another project-based firm. It traces client documents through enquiry scoping, RFP uploads, proposal exchange, project portals, subcontractor access and handover, sets out what the Privacy Act and government contract rules say and whom they cover, and comes with an engagement-lifecycle matrix to run on your own systems.
Industry workflow selector: ten guides side by side
Find your kind of business in the first column, then read across: the data the guide follows, the portals and sign-ins it covers, where it draws the payment boundary, how documents move, the laws, standards and regulators' pages it quotes, its test table counted, and what its closing section says about a Clever Ops service. The law column only names what each guide quotes; naming a source there says nothing about whether it applies to any business.
How to use itHide the instructions
Rows are numbered 1 to 10 in the library's order, each cell restates its guide no more strongly than the guide does, and all ten guides are linked under Pages in this section.
10 rows
Guide, address and reader
Data the guide follows
1. Healthcare. Cyber Security for Healthcare, at /web-security/industries/healthcare, for the owner, practice manager or technical lead of a medical, dental, allied health or specialist practice.
- Data the guide follows
- A patient from an online booking to a payment notice: booking and intake form answers, referral letters, telehealth links, portal results, letters and invoices, then how long each copy is kept and what the logs would show.
- Portals and sign-ins it covers
- A patient portal, tested between patients, between a patient and a parent, guardian or carer acting for them where the portal offers that, and between staff roles. Vendor booking, video consultation and practice management platforms only as far as their terms allow.
- Payment boundary
- Invoice emails, payment texts and payment links: what each notice shows, and whether a link opens another patient's invoice. The payment provider's hosted checkout stays outside the test.
- How documents move
- Referral letters and reports, where a practice accepts them through an upload form on the website or in a portal, and results, letters and invoices read in the portal.
- Laws, standards and regulators' pages it quotes (named only)
- The Privacy Act 1988 (Cth); the OAIC's page on the Notifiable Data Breaches scheme; the Health Records Act 2001, named only as an Act Victoria's legislation register lists in force. Test ids from OWASP WSTG v4.2 and ASVS 5.0.0.
- Its test table, counted
- 17 rows by 8 columns, numbered 1 to 17. Rows 1, 5, 15, 16 and 17 read and send no test requests; the other twelve carry their own limits. Needs at least two invented patients, a test staff account in each staff role, a carer account if the portal has one, and an inbox and phone the practice controls.
- What the guide says about a Clever Ops service
- Who signs in decides. A site only staff sign in to suits the website security check, and a WordPress site the WordPress security audit. A portal or booking application built for the practice, where patients sign in, upload referrals or pay, takes the web application and API penetration test. Hosted booking, video consultation and practice management platforms stay out of scope unless the business running them agrees.
2. Legal. Legal Cyber Security, at /web-security/industries/legal, for the principal, practice manager or technical lead of an Australian law firm.
- Data the guide follows
- Client data through a matter, from the first website enquiry to the trust-payment handoff: enquiry text, conflict information, identity documents, family-law and conveyancing uploads, matter documents and payment details, then closing the matter.
- Portals and sign-ins it covers
- Matter portals and sharing links for clients, two clients on one matter, and guests such as the other side's lawyer, counsel or experts; staff on and off a matter, and matters restricted to a named team.
- Payment boundary
- Trust-payment handoffs, tested only for who can change payment details and how a change is confirmed. The guide makes no statement about how any trust accounting product works.
- How documents move
- Identity documents, uploads such as financial records in a family-law property matter or a contract in a conveyance, documents released through a portal or a sharing link, and documents held back until they are released.
- Laws, standards and regulators' pages it quotes (named only)
- The Privacy Act 1988; the OAIC's page on the Notifiable Data Breaches scheme; the Anti-Money Laundering and Counter-Terrorism Financing Act 2006, in the compilation showing the law in force on 1 October 2026; the Legal Services Council's pages on the Uniform Law and Uniform Rules, with no conduct rule quoted. WSTG v4.2, ASVS 5.0, and OWASP's Session Management and Authentication Cheat Sheets.
- Its test table, counted
- 21 rows by 7 columns in eight groups (E, C, I, U, P, T, X and V). E1, I3, T1 and V1 only read; every other row gives its number of requests and its conditions in the last column. Needs test matters with invented clients and parties, harmless test documents and two test accounts in each role tested.
- What the guide says about a Clever Ops service
- A brochure site with an enquiry form suits the website security check, and WordPress the WordPress security audit. A custom client portal or intake application takes the web application and API penetration test. A practice management system, document platform or e-signing service its vendor runs stays out of scope unless the owner agrees, and phishing, staff devices and the office network go to a network or red team specialist.
3. Accounting. Cyber Security for Accountants, at /web-security/industries/accounting, for whoever runs an accounting or bookkeeping practice or its systems.
- Data the guide follows
- A practice's year from first enquiry to former client: enquiry and engagement forms, tax file numbers, identity documents, BAS workpapers, payroll files, logins to clients' ledgers and documents sent back at lodgement, with an evidence lane for a tax-season change freeze.
- Portals and sign-ins it covers
- The client portal, for clients and former clients; seasonal staff and outside bookkeepers; and the practice's own logins where it works as an invited user in clients' Xero organisations and MYOB files, as those vendors' help pages describe that access, with the apps connected to each file.
- Payment boundary
- Not covered: the guide follows no payment step. Its payroll row lists the fields an export carries, which may include employees' bank details.
- How documents move
- Tax file numbers and identity documents by portal field or upload (email attachments sit outside the matrix), and returns, statements and signed documents sent back through the portal or as links in an email.
- Laws, standards and regulators' pages it quotes (named only)
- The Privacy Act 1988; the OAIC's page on the Notifiable Data Breaches scheme; the Privacy (Tax File Number) Rule 2015; the Tax Agent Services Act 2009; the Tax Agent Services (Code of Professional Conduct) Determination 2024. ASVS 5.0.0 and WSTG v4.2.
- Its test table, counted
- 18 rows by 7 columns: W1 to W12 follow the workflow, and F1 to F6 are the change-freeze evidence lane. W7 and W8 only read a user or app list, the F rows check a document, list or log, and each other W row states its own limits. Needs invented clients A and B, seasonal staff member S and bookkeeper K, inboxes and phones the practice controls, and a test organisation or company file for the payroll and ledger rows.
- What the guide says about a Clever Ops service
- A site where only editors log in suits the website security check, and a WordPress site the WordPress security audit. A custom client portal takes the web application and API penetration test. A portal, practice system or ledger a vendor runs belongs to that vendor, and Clever Ops does not test it; the read-only rows are how the practice reviews its own accounts inside it.
4. Education. Education Cyber Security, at /web-security/industries/education, for school business managers, IT leads and the edtech suppliers that serve schools.
- Data the guide follows
- Student and family data through applications and enrolment, guardian messages, learning portals, student uploads and excursions, and the outside services behind them, with school-operated sites kept apart from supplier platforms.
- Portals and sign-ins it covers
- Guardian, student, teacher, office staff and supplier accounts on a school's own sites, with guardian and staff access tested apart. On a supplier's platform, two invented schools, their guardians, people who leave, and the supplier's own support access.
- Payment boundary
- Excursion payments: whether the amount charged is the one the server sets. Test payments run only through a staging copy connected to a non-live payment account, and the provider's hosted checkout is outside the row.
- How documents move
- Application documents and links in confirmation emails, student uploads such as assignments, images and recordings, excursion attendee lists, which may also go to the excursion provider, and exports and deletion on a supplier's platform.
- Laws, standards and regulators' pages it quotes (named only)
- The Privacy Act 1988; the OAIC's page on the Notifiable Data Breaches scheme; Victoria's Privacy and Data Protection Act 2014 and Queensland's Information Privacy Act 2009, given as examples; the Safer Technologies 4 Schools (ST4S) site. WSTG v4.2 and ASVS 5.0.0.
- Its test table, counted
- 20 rows by 7 columns: S1 to S9 for a school's own sites and services, E1 to E6 for a supplier's platform, and P1 to P5, an evidence lane that sends nothing. Every row that sends a request carries its limits in the last column. Needs the invented students, guardians, teachers, office staff and suppliers it names, or your own equivalents, with contact details you control.
- What the guide says about a Clever Ops service
- A public website and its enquiry forms suit the website security check. Where a form takes uploads or payments, or families sign in, the web application and API penetration test is the starting point, and it also fits a custom family or student portal or a supplier's own platform, tested across two schools. WordPress takes the WordPress security audit, an AI feature the AI chatbot and agent security test, and a report is not an ST4S result.
5. Ecommerce. Ecommerce Website Security, at /web-security/industries/ecommerce, for a store's owner or ecommerce manager, working alongside whoever builds the store.
- Data the guide follows
- The order path, across platforms: customer accounts, carts, coupons, the payment handoff and its confirmation, the order record and its emails, refunds, exports, fulfilment and loyalty.
- Portals and sign-ins it covers
- Customer accounts, and what stands in for a sign-in at guest checkout, such as an order lookup or an emailed link; the staff roles that refund or export; connected fulfilment, shipping, accounting, loyalty, review and gift card apps.
- Payment boundary
- The handoff to the payment provider and the confirmation that comes back, payment page scripts, refunds and balances. Orders run on a staging copy with each provider in its documented test or sandbox mode, never with a real card, and card payment questions go to the acquirer or payment provider.
- How documents move
- Order and customer export files, and links that open an order, a file or a payment without a sign-in, which are opened only for test records and never copied into the evidence.
- Laws, standards and regulators' pages it quotes (named only)
- The PCI Security Standards Council's post on its payment page security supplement, its Merchant Resources FAQ and its pages on Approved Scanning Vendors and Qualified Security Assessors; the Privacy Act 1988, Compilation No. 104; the OAIC's page on the Notifiable Data Breaches scheme. OWASP WSTG (WSTG-BUSL-10 from the edition the OWASP site labels Latest, read on 15 November 2026, and v4.2), ASVS 5.0, OWASP cheat sheets and MDN on Subresource Integrity.
- Its test table, counted
- 27 rows by 8 columns in eleven groups, with B1 and B2 first. B1, P2, S2 and F1 only read; every row has its own limits, under a run total of 20 checkout submissions. Needs a staging copy, invented customers cust-a and cust-b, staff test accounts and a marker such as ORDERTEST-1115 in every test record.
- What the guide says about a Clever Ops service
- A WooCommerce store falls under the WordPress security audit. A custom-built store that customers sign in to takes the web application and API penetration test, on the store's side of the payment. Live Shopify storefronts are outside Clever Ops services. Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor, so those scans and assessments are referred.
6. SaaS. SaaS Security Checklist, at /web-security/industries/saas, for the founder, CTO or technical lead of a software business that sells subscriptions to other businesses.
- Data the guide follows
- A customer tenant from sign-up to cancellation: provisioning, invitations and roles, billing-only users, support access, exports and file links, API tokens and webhooks, and offboarding, with buyer-audit fields on every row.
- Portals and sign-ins it covers
- The users inside each tenant (owner, staff, someone leaving and, where the role exists, billing), your own support staff and any impersonation they can start, and the API tokens customers connect with.
- Payment boundary
- Billing-only users and billing events received from a payment provider. Where card details stay with the provider, its hosted pages sit outside the grid.
- How documents move
- Export files, stored files served from a link, generated documents, and events sent out to customers by webhook.
- Laws, standards and regulators' pages it quotes (named only)
- The Privacy Act 1988, Compilation No. 104; the OAIC's page on the Notifiable Data Breaches scheme. Published buyer lists and question sets, named as their publishers give them: MVSP, CISA's Secure by Demand Guide, the UK NCSC's supplier assurance questions and the Cloud Security Alliance's CAIQ v4.1. The Cloud Security Alliance's STAR Program page and the AICPA's SOC suite page. OWASP cheat sheets, among them the Multi-Tenant Application Security Cheat Sheet, with ASVS 5.0 and WSTG v4.2.
- Its test table, counted
- 15 rows by 8 columns, G1 to G15. G14 only reads a policy and asks questions; the other rows carry their limits on the row. Needs a staging copy with invented Tenants A and B, their users and records marked with each tenant's letter, and Tenants C and C-West, which G1 creates for the cancellation row.
- What the guide says about a Clever Ops service
- The grid is the business's own to run. For an outside view, the web application and API penetration test, with accounts in two customer organisations; larger and multi-tenant products are scoped individually after a longer call. Clever Ops is not certified to ISO/IEC 27001, holds no SOC 2 report and issues neither.
7. Financial services. Fintech Security, at /web-security/industries/financial-services, for lenders, mortgage brokers, advice practices and fintech product companies, and for companies selling software or services to a bank, insurer or superannuation fund.
- Data the guide follows
- The advice and transaction workflow from first enquiry to audit trail: loan and investment enquiries, bank statements, identity records, adviser and broker handoffs, payment authorities, audit trails, and closed applications and departing advisers.
- Portals and sign-ins it covers
- An applicant portal; advisers, brokers, payment approvers and other staff roles; outside parties sent a link when a file changes hands. In vendor loan origination, customer relationship and identity verification systems, only the business's own accounts and settings.
- Payment boundary
- Payment authorities, such as a direct debit request or the account a loan is paid into: who can read or change one, whether a change asks for more than the open session, and whether one person can approve alone. The application's side only; W6 and W7 run on a staging copy connected to a non-live payment account.
- How documents move
- Bank statements, which can arrive by upload, email attachment or a third-party retrieval service (the matrix tests the upload and reads what a retrieval service sends on), identity document images, and links sent to outside parties at a handoff.
- Laws, standards and regulators' pages it quotes (named only)
- APRA's CPS 234 Information Security and CPS 230 Operational Risk Management (the CPS 230 text made by determination No. 1 of 2026); the Corporations Act 2001; the National Consumer Credit Protection Act 2009; the Privacy Act 1988; the OAIC's page on the Notifiable Data Breaches scheme. ASVS 5.0.0.
- Its test table, counted
- 19 rows by 7 columns. W1 to W9 follow the workflow, and every W row signs in, submits or sends requests with its limits on the row. R1 records which evidence routes apply (A1 to A3, S1 and S2, N1 and N2; a business can sit on more than one), and P1 and P2 sit on every route. R1 and the route rows send no requests. Needs invented applicants, advisers and payment approvers, and statement and identity files marked SAMPLE.
- What the guide says about a Clever Ops service
- A site with no client logins suits the website security check, and WordPress the WordPress security audit. A custom portal or application takes the web application and API penetration test; a partner or mobile-app API is scoped as its own surface, and the mobile app is not part of the service. Loan origination, customer relationship and identity verification services stay out of scope unless their owner agrees.
8. Real estate. Real Estate Cyber Security, at /web-security/industries/real-estate, for the principal, licensee or property management lead of an Australian real estate agency.
- Data the guide follows
- A rental from application to lease and through the tenancy: inspection bookings, applications with identity and bank documents, declined applications, the lease and condition report, maintenance requests and photos, contractor work orders, owner portals and payment details.
- Portals and sign-ins it covers
- Applicants and tenants, property managers, landlords in an owner portal, and contractors through their work orders. In vendor property management software, application platforms and owner portals, the agency's own settings and test accounts, under the vendor's terms.
- Payment boundary
- Changes to payment details: the agency's own account details, landlords' disbursement accounts, and contractors' payee details, with any form a tenant uses to nominate an account listed in P1. The change rows check who can change them, confirmation or a second sign-off, authenticating again, who is told and logging, each row saying which.
- How documents move
- Identity documents and bank statements uploaded with applications, the lease and condition report where they go out as links in an email, signing that may run on an e-signing service, and maintenance photos, which can be taken inside a home.
- Laws, standards and regulators' pages it quotes (named only)
- The Privacy Act 1988; the OAIC's page on the Notifiable Data Breaches scheme; two Consumer Affairs Victoria pages, credited to it and speaking for Victoria only; the Anti-Money Laundering and Counter-Terrorism Financing Act 2006, in the compilation showing the law in force on 1 October 2026. WSTG v4.2, ASVS 5.0 and OWASP cheat sheets.
- Its test table, counted
- 25 rows by 7 columns in nine groups (I, R, D, L, M, C, O, P and V). I2, R1, D1, P1 and V1 only read; the other twenty start their last cell with the conditions they run under and the number of requests they send. Needs invented applicants, property managers, landlords and contractors for test properties X and Y, and documents made for the test and marked as specimens.
- What the guide says about a Clever Ops service
- Listings and enquiry forms suit the website security check, and WordPress the WordPress security audit. An application of the agency's own that applicants, tenants, landlords or contractors sign in to takes the web application and API penetration test, and a chatbot answering rental enquiries the AI chatbot and agent security test. Licensed property management software, application platforms, owner portals and e-signing services stay with their vendors.
9. Hospitality. Hospitality Cyber Security, at /web-security/industries/hospitality, for owners, managers and technical leads of accommodation, restaurant and event businesses.
- Data the guide follows
- A guest's details from booking to refund: direct bookings and channel-manager handoffs, modification links, group rooming lists, dietary, allergy and accessibility notes, table reservations, event enquiries, gift cards and refunds.
- Portals and sign-ins it covers
- Guests through confirmation pages, booking lookups and modification links; event organisers through shared documents and invoices; staff accounts, which can span a booking engine, a channel manager, a reservation platform, a payment dashboard and the website itself.
- Payment boundary
- Deposits and card holds, event invoices paid by link, gift card balances, refunds and payment page scripts. A vendor's system is touched only in its documented test mode and within the vendor's written answer, never with a real card, and card payment questions go to the acquirer or the payment brand.
- How documents move
- Rooming lists, which can arrive by upload, email attachment or shared spreadsheet; event enquiry attachments where the form allows them; proposals, function sheets and guest lists, each of which can be sent as a link; and, where the names and notes guests or organisers type are exported for staff, the spreadsheet itself.
- Laws, standards and regulators' pages it quotes (named only)
- The Privacy Act 1988, Compilation No. 104; the OAIC's page on the Notifiable Data Breaches scheme; the PCI Security Standards Council's post of 10 March 2025 and its Merchant Resources FAQ. OWASP WSTG v4.2 and WSTG-BUSL-10 from the edition the OWASP site labels Latest, read on 15 November 2026, ASVS 5.0, OWASP cheat sheets and automated threat entries, and MDN on Subresource Integrity.
- Its test table, counted
- 26 rows by 8 columns in eight groups, with B1 and B2 first. B1, A3, S2, Z1 and Z3 are read only; every row that signs in, submits a form or changes a request carries its limits in the seventh column. Needs invented guests guest-a and guest-b, organisers org-a and org-b, staff test accounts and a marker such as STAYTEST-1115 in every test record.
- What the guide says about a Clever Ops service
- A brochure site that links to or embeds a vendor's booking engine suits the website security check, and WordPress the WordPress security audit. A booking, reservation or event application built for the business takes the web application and API penetration test, on the application's part of the payment. Booking engines, channel managers, reservation platforms and the payment provider's platform stay out of scope unless their owner agrees.
10. Professional services. Professional Services Cyber Security, at /web-security/industries/professional-services, for the principal, operations lead or technical lead of a consultancy, engineering or architecture practice, agency or other project-based firm.
- Data the guide follows
- Client documents through an engagement: enquiry scoping, RFP uploads, proposal exchange, project portals and client folders, subcontractor access, handover and the archive.
- Portals and sign-ins it covers
- Project portals and client folders for clients, staff on and off the project, and subcontractors; the firm's own accounts in the tender portals that clients or government buyers run.
- Payment boundary
- Not covered: no row takes or changes a payment. Row P3 checks that the fee and scope a client accepts online are the ones the server holds.
- How documents move
- Enquiry attachments, RFP packs uploaded to the firm's own site, proposals where they go out as web links, project folders with their downloads and previews, and handover packages sent by link, transferred or kept in a portal folder.
- Laws, standards and regulators' pages it quotes (named only)
- The Privacy Act 1988; the OAIC's page on the Notifiable Data Breaches scheme; Victoria's Privacy and Data Protection Act 2014; Queensland's Information Privacy Act 2009; the NSW Cyber Security Policy 2026 to 2027 from Cyber Security NSW; the UK NCSC's supplier assurance questions. WSTG v4.2, ASVS 5.0 and OWASP cheat sheets.
- Its test table, counted
- 24 rows by 8 columns: Q, R, P, J, C and H rows follow six stages, E1 to E6 are the evidence lane and V1 covers third-party systems. Nine rows only read; fifteen sign in, submit or send requests within the limits in their last column. Needs invented clients A and B on test projects, staff test accounts S1 and S2, subcontractor K and harmless test files.
- What the guide says about a Clever Ops service
- A brochure site whose enquiry form takes no attachments suits the website security check; where a form takes attachments, the check is a starting point and the penetration test the right depth. WordPress takes the WordPress security audit, and a custom client, project or RFP intake portal the web application and API penetration test. Licensed file-sharing, collaboration and proposal tools stay with their vendors, and a client's tender portal with the client.
About this library
Web security by industry: ten guides that follow how a business works
The same weakness can sit behind very different screens.
One customer reaching another customer's records looks like a patient opening the wrong letter in a practice portal, a landlord opening another owner's statement, or one school's administrator seeing another school's students. What changes from one kind of business to the next is the work around the weakness: what people send in, who signs in to read it, where money moves and which documents travel.
So this part of the web security library is arranged by industry. Ten guides each take one kind of business, follow its work online a step at a time, name the data at each step and who should and should not reach it, and come with a table of test cases to run on the business's own systems with invented records.
The workflow selector on this page gives each guide one row, read across eight columns: the guide and the reader it is written for, the data it follows, the portals and sign-ins it covers, where it draws the payment boundary, how documents move, the laws, standards and regulators' pages it quotes, its table counted, and what its closing section says about a Clever Ops service.
Read as a set of industry data security workflows, the rows let you compare application security by sector before you open a guide, and they show which guide carries the industry website security checklist for your kind of business.
Each cell says what its guide says and no more. Where a guide does not cover a step, such as a payment, the cell says so rather than filling the gap. A guide written for a sector is information for the people who run that sector's systems, and it implies no specialist accreditation in that sector.
How the workflow selector is laid out
The ten rows follow the library's own order and are numbered 1 to 10, from healthcare to professional services, and this page refers to them by number.
There is no filter on the table. To narrow it, read down a single column for the question in front of you: down the payment column to see which guides follow money at all, or down the documents column to see which ones deal with uploads, links or exports.
- Guide, address and reader: the guide's title, its address and who it is written for, in the guide's own words.
- Data the guide follows: the workflow from the guide's opening and step-by-step sections, in the order the guide takes it.
- Portals and sign-ins: who the guide tests as a signed-in user or as the holder of a link, and how far it goes inside a system that a vendor runs.
- Payment boundary: the payment steps the guide tests and where it stops. The accounting and professional services guides follow no payment step, and their cells say so.
- How documents move: the uploads, links, exports and handovers the guide follows, and any route it leaves outside its table.
- Laws, standards and regulators' pages: each named as its guide names it, with an edition or compilation where the guide gives one.
- Its test table, counted: rows and columns counted from the guide as published, its row groups, which rows only read, and what you need in place before you open it.
- What the guide says about Clever Ops: only what that guide's closing section says about which service fits and where it stops.
The law column names sources and decides nothing
Naming an Act, an instrument, a standard or a regulator's page in this table is not a statement that it applies to any business, to any kind of business or to you. Each guide quotes particular provisions for what their text says, and each leaves the question of whether any of them applies to the reader, and with what effect, to the reader and their own adviser, regulator or professional body.
This page does not summarise or restate any of those provisions.
A shortened version here would be a second and weaker copy of the law, so the definitions, tests and duties stay in the guides, quoted in the source's own words.
Standards are named the same way. Test ids in the guides come from OWASP's Web Security Testing Guide and Application Security Verification Standard, in the editions each guide names. The ecommerce and hospitality guides also take one payment test, WSTG-BUSL-10, from the edition that the OWASP site labels Latest, as read on 15 November 2026.
When a business sits across two industries
A business can fit more than one row.
Start with the guide whose workflow matches the system your customers sign in to or send records through, run its table, and take rows from a second guide only for steps the first has no row for. Mark a step your business does not run as not applicable rather than leaving it blank, as the ecommerce and hospitality guides ask, and keep each borrowed row to its own limits. Four combinations show how the guides divide the work.
A practice that also sells online: rows 1 and 5
A dental or allied health practice with an online shop runs two workflows on one website. The healthcare guide follows the patient: bookings, intake answers, referral uploads, telehealth links, the portal and payment notices. The ecommerce guide follows the order: accounts, carts, coupons, the payment handoff and its confirmation, refunds, exports and fulfilment.
Their payment rows cover different things. Healthcare row 14 deals with invoice emails, texts and payment links, while the ecommerce matrix runs the shop's checkout on a staging copy with each payment provider in its test mode.
If the site runs on WordPress, both guides' closing sections point to the WordPress security audit, which takes in a WooCommerce store's customer accounts, orders and checkout pages.
A software company selling to schools: rows 4 and 6
An edtech supplier sells software to many schools from one platform. The education guide's rows E1 to E6 are written for that platform, on the supplier's staging environment with two invented schools: the boundary between schools, guardians and students, people who leave, the supplier's own support access, exports and deletion, and integrations with schools' own systems.
The SaaS grid follows a customer tenant from sign-up to cancellation and has rows the E rows do not, such as self-serve provisioning, invitations, billing-only users, API tokens and webhooks.
Where both cover the same step, as with support access and exports, one workable approach is to run it with the education guide's roles and record the outcome in the SaaS grid's buyer-audit fields. The ST4S request in education row P1 is particular to the education guide.
Software sold to lenders, brokers or advisers: rows 6 and 7
The financial services guide is also written for the technical lead of a company selling software or services to a bank, insurer or superannuation fund. For a software company that sells to brokers or advisers, holds neither kind of licence and is not APRA-regulated, the guide gives its route through the matrix as the Privacy Act rows plus the supplier rows that match its contracts.
The boundary between one customer firm and another is the SaaS grid's subject. A product of that kind can therefore take the SaaS grid for isolation between customers and the financial services route rows for what a client's agreement, questionnaire and due diligence requests ask to see.
Which route a business is on is something the guide leaves to APRA, the client or the business's adviser.
A venue with an online shop: rows 9 and 5
A hotel, restaurant or events venue that also sells gift cards or packages online meets both guides at the checkout. The hospitality guide follows the booking side: reservations, deposits, event invoices, gift cards, and refunds against a cancellation policy.
The ecommerce guide follows a store's order path, including coupons, exports, fulfilment and loyalty balances. Both tables have payment-page rows labelled S1 and S2 that record which scripts load on each payment page and who would hear of a change, so a business running both can keep one record per payment page.
In each, row B1 puts card payment questions in writing to the acquirer or another party the guide names, before anything is sent.
What a review like these cannot show
A completed table records what was tried, on which copy and accounts, on which day.
Each guide sets out its own edges, and read together they mark the same boundaries.
- A result is narrow. Each guide treats a passing row as a result for what it ran against on the day it ran, and nothing wider.
- Inside a vendor's platform. The guides test the business's own instance and settings, and leave the vendor's platform to the vendor.
- Email and staff devices. The healthcare, legal, accounting, education, ecommerce, real estate and professional services guides each put email and staff devices outside their tables, and the hospitality guide leaves out the office network, staff devices, guest Wi-Fi and in-venue card terminals.
- People with valid access. A seasonal staff member, an adviser, a subcontractor or anyone else with a valid login who copies data out passes every access row, as the accounting, financial services, real estate and professional services guides each point out.
- Process steps. A call to a number already on record before money moves is a process; the legal and real estate guides say a table can record that the step exists but cannot test that people follow it.
- Volume and timing. None of the tables is a load test, and the SaaS and financial services guides say a handful of records or requests cannot show problems that need volume. The ecommerce and hospitality guides add that a burst of three requests behaving as expected is a result for that burst, not proof that no timing gap exists.
- Staging and live. The ecommerce, SaaS and hospitality guides note that a staging copy can carry different settings, scripts or connections from the live system, so a clean result covers what the copy carried.
- An intrusion already under way. The ecommerce and hospitality guides treat finding out whether a site has already been compromised as incident response work.
- The law. No table settles whether a duty applies to the business or whether it is met. Each guide leaves that with the business and its adviser.
Where the guides stop and a Clever Ops service takes over
The tables are written for the business to run, or to hand to its own developer or tester.
A Clever Ops test is a separate piece of work with a scope of its own, and it covers the parts of a business that customers, and attackers, reach through a browser or an API. Each guide's closing section says which service fits that kind of business and where it stops, and the last column of the selector draws only on that section.
- The web application and API penetration test appears in all ten closing sections, for a portal or application built for the business that customers or staff sign in to. It signs in as each role and covers authentication and sessions, what each role can see and change, whether one customer can reach another customer's records, the API called directly rather than only through the screens, payment and billing flows, file uploads and business rules. Its scope asks for two test accounts in each role, and accounts in two customer organisations when an application serves more than one.
- The WordPress security audit appears in nine, every guide except SaaS. It follows each role that can log in and checks the login and password-reset flows, the installed plugin and theme versions and how the admin area is exposed, and a WooCommerce store adds customer accounts, orders and checkout pages.
- The website security check appears in eight, all but the ecommerce and SaaS guides, for a brochure or enquiry site without customer logins. It is an external review of what anyone on the internet can see without logging in, and it does not look behind a login, read source code or test business logic.
- The AI chatbot and agent security test appears in three, education, SaaS and real estate, for an AI feature or a chatbot that answers enquiries, and it tests the chatbot or agent rather than the AI model behind it. The SaaS guide also names the vibe-coded app security check for a product made with an AI app builder.
What the guides send elsewhere
Software another business runs stays with that business. The methodology keeps services run by other businesses, such as a hosted payment page or a booking platform on one of the business's subdomains, out of scope unless their owner agrees, and the web application penetration test covers an application's side of a payment, not the payment provider's platform.
Some work needs a different kind of provider. Clever Ops holds no security certification or accreditation and is not CREST accredited, so where a contract, panel or tender requires a CREST-accredited provider, we refer that work to a provider that is.
Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor, so a PCI DSS scan or assessment goes to a provider that holds that role, as the ecommerce, financial services and hospitality guides say. Internal networks, staff devices and phishing go to a network or red team specialist, load or denial-of-service testing is not part of any Clever Ops service, and a business dealing with an incident now should call an incident response specialist first.
Two points hold whichever row you start from. If Clever Ops built or hosts the system, the work is a security review rather than an independent test, and the report names who built it and who hosts it.
And a 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. The financial services guide carries its CREST and independence statements in its section on independent testers rather than in its closing section, so row 7's last cell gives only what the closing section says.
A filled-in table is useful on a scoping call. The ecommerce and hospitality guides ask you to bring theirs, because it shows which steps the business has or runs itself, which systems it connects to or hands customer details to, and which terms are already answered.
Frequently asked questions
The row whose first cell describes your business and whose data column matches what your customers send you. If two rows fit, start with the guide for the system customers sign in to or send records through, then take rows from the second guide only for steps the first has no row for. The section on businesses that sit across two industries works through four combinations, from a practice with an online shop to a venue with one.
This page does not say, and neither do the guides. Each guide quotes particular provisions for what their text says and leaves the question to you and your own adviser, regulator or professional body. The law column lists what each guide quotes so you know which guide to open before that conversation. Naming a source there is not a statement that it applies to any business.
Each guide's table works as one. Read down its first column for the steps, and across a row for the test case, the expected result, the evidence to keep and the row's limits. Before you run it, write your own access rules into the expected results, create the invented accounts and records the table names, and read the terms of any vendor whose system a row touches. The healthcare and hospitality guides say the rows that only read suit a manager and the rows that send requests suit a developer or tester. The education guide gives its read-only rows to a business manager or IT lead, rows that change a number in the address bar to anyone holding the test accounts, and rows that change a request on its way to the server to a developer or tester.
Only where the guide says so. All ten use a staging copy where one exists, and invented records in every row that sends a request. The SaaS grid runs only on a staging copy, and the ecommerce matrix puts every order, form submission and changed request on one, with each payment provider in its documented test mode. A system a vendor runs is touched only after you have read its terms and, where the guide asks, had the vendor's answer. Every row that acts carries its own limits, and none of the tables is a load test.
No. A guide written for a sector is information for the people who run that sector's systems and implies no specialist accreditation, and Clever Ops holds none, for any industry. What Clever Ops tests is the same in every row: the parts of a business that customers, and attackers, reach through a browser or an API. Where a contract, panel or tender sets a condition that Clever Ops cannot meet, the section on where a Clever Ops service takes over says which kind of provider the work goes to.
Because the accounting and professional services guides follow none. The accounting guide's payroll row lists the fields an export carries, which may include employees' bank details, and the professional services guide checks that the fee and scope a client accepts online are the ones the server holds, but neither has a row that takes or changes a payment. A practice or firm that takes payments online can borrow the payment rows of another guide, such as the healthcare guide's payment notices or the real estate guide's changes to payment details, keeping each row's limits.
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.