ISO 27001 requirements and your web application: when a questionnaire or auditor cites Annex A 8.8 or 8.29, what a security test can add to your records
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.
In this guide
Evidence matrix for a web application in an ISO/IEC 27001 ISMS
Use it on your own systems only, with your own licensed copy of ISO/IEC 27001 open beside it. Set the table up in a spreadsheet and give each website, portal or web application its own copy.
How to use itHide the instructions
Rows M1 to M13 follow one test cycle: the inventory and ISMS scope, the risk record, any statement of applicability lines for 8.8 and 8.29, as confirmed in your copy, the test scope, the vulnerabilities found, each finding's owner and decision, a security check before each release, the report, a developer check of fixes, the retest, the parts a supplier runs, the review after the cycle and the pack for an external audit. Where a row asks a question of the standard, write the answer from your copy with the clause or control number and the edition. The matrix does not quote or paraphrase the standard, and its placement of rows against 8.8 and 8.29 is an assumption made without the text of either control: confirm in your copy that both are controls, then move any row to wherever your copy and your auditor put it. Only M7 and M9 send requests, and each gives its limits and its request count in its last column: your own application only, a staging copy where one exists, test accounts holding invented records, and no password, token, key or link that works for whoever holds it kept in the record. The remaining eleven rows read or update records and send nothing. The sixth column gives examples of what an auditor may still request; they are examples written for this page, not a list from the standard. The matrix records evidence and no row says a control is met. Whether your ISMS conforms to the standard is for your organisation's own audit and for the auditor you engage.
13 rows
Row and record
Where it sits in your ISMS, and the question to put to your own copy or your auditor
M1. Web application inventory and the ISMS scope
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- Your ISMS scope statement. Question for your copy: does it say anything about setting the scope, and if so what? Then check that your scope statement names each website, portal and API, or records why one sits outside it.
- What to keep
- A line per website, portal, API and integration giving its name and address, its purpose, the information it holds, whether it is run in-house or by a named supplier, whether the ISMS scope includes it, and when it last changed materially.
- What a test of the website or application can contribute
- From a website security check, a hostname inventory that can turn up names you did not know about, showing where each points and who seems to run it. From a web application test, the build, dates, route list, roles and accounts used. Both are snapshots on a given date, to hold up against this list.
- Where it stops, and whose decision it is
- Whether the scope is right. Setting it is your organisation's decision; a test shows only what answered on the dates it ran.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the scope statement, and the reason a public website or API sits outside it.
- Limits of this row
- No requests: this row is compiled from your own records.
M2. Risk record entries for the application
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- Your information security risk assessment and risk treatment records. Question for your copy: does it say what a risk assessment has to produce, and if so what? Then check that your risk record has entries for this application's threats, such as one customer reaching another customer's records.
- What to keep
- For each application: the risks recorded against it, the risk owner, the rating under your own method, the treatment chosen and the controls it points to, including any entries for 8.8 and 8.29, with the date each entry was last reviewed.
- What a test of the website or application can contribute
- Concrete inputs. Each finding in a Clever Ops report has a description, evidence with secrets redacted and the business impact, and each rated finding carries a CVSS v3.1 score and a business-risk rating. Negative results record which checks found nothing on the build and accounts tested.
- Where it stops, and whose decision it is
- Your risk rating. A CVSS score and a tester's business-risk rating are inputs to your method, not a replacement for it, and the decision to accept a risk belongs to whoever your ISMS names as that risk's owner.
- What an auditor may still request (examples only, not a list from the standard)
- Example: how the last test's findings changed the risk record, and the record of who accepted any risk left open.
- Limits of this row
- No requests: this row updates your risk record.
M3. Statement of applicability lines for 8.8 and 8.29, if your ISMS keeps one
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- Any statement of applicability your ISMS keeps. Question for your copy: does it call for one, and if so, does it say what one contains? If it does, check your lines for 8.8 and 8.29 against that text, word for word.
- What to keep
- The version and date of the statement, the exact wording of your lines for 8.8 and 8.29, and, for each line, the records it points to as evidence.
- What a test of the website or application can contribute
- A dated report gives those lines a record to point to for the application tested: the scope, the build and dates tested, and what turned up.
- Where it stops, and whose decision it is
- Whether a control is included, why, or how it is implemented across the ISMS. Those entries are your organisation's, and an auditor forms their own view of them.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the evidence behind the status your statement gives 8.8 for every application in scope, not only the one that was tested.
- Limits of this row
- No requests: this row reads and updates one document.
M4. Test scope, authorisation and test window
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- 8.8 and 8.29, once your copy confirms both as controls, as your organisation applies them. Question for your copy: does the text of each control name any activities, and if so which? Then mark which of them this test's scope covers for this application.
- What to keep
- The signed scope, naming the targets, the testing window, the environment, the depth, each role with its test accounts, and the exclusions; written authorisation from whoever owns each target; your host's testing policy as you found it; the terms you read for anything a vendor runs; and the result you expect from each check.
- What a test of the website or application can contribute
- The report's record of what actually ran: build, dates, routes, roles and accounts, each exclusion, and any test case that did not run and why, so the plan can be set beside what ran.
- Where it stops, and whose decision it is
- Whatever sat outside the scope. Nothing excluded was tested, so M12 should log each exclusion either as a gap or as a decision someone recorded.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the signed authorisation, and the reason an application listed in M1 was not tested this cycle.
- Limits of this row
- No requests: this row collects paperwork before any testing.
M5. Vulnerabilities identified in the application (filed under 8.8 by assumption)
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- 8.8, if your copy confirms it as a control. Question for your copy: what does the control's text say, word for word? Copy it into this row, then mark which part of it a test of this application gives evidence for and which parts need other records.
- What to keep
- The report date and version; every finding, its ratings and the build it was found on; and, for the same application, the other sources of vulnerability information your process uses, such as dependency alerts and supplier security advisories, with the date each was reviewed.
- What a test of the website or application can contribute
- A dated record of the vulnerabilities a test found in one application, on the build, dates and accounts tested, each with evidence that reproduces it, plus the checks that found nothing. Each finding is mapped to its OWASP Top 10:2025 category.
- Where it stops, and whose decision it is
- Vulnerabilities in other systems or introduced after the test, and anything about how your organisation tracks vulnerabilities between tests. A clean check covers the thing it looked at and nothing more.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the record of supplier advisories received between tests for the components this application uses, and what was done about each.
- Limits of this row
- No requests: this row files results.
M6. Each finding's owner, decision and target date
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- Your risk treatment records and 8.8, if your copy confirms it as a control. Question for your copy: does the text of 8.8, or of any clause on risk treatment, say anything about deciding what to do with a known vulnerability and by when? Check your procedure against it.
- What to keep
- For each finding: the owner, the target fix date, the decision (fix, accept, or treat another way) with its maker and date, and the link to its entry in M2.
- What a test of the website or application can contribute
- A fix for each finding written for your stack, the criteria the retest will apply, and a remediation plan that ranks the fixes by priority.
- Where it stops, and whose decision it is
- Whether a delay is acceptable, or whether a risk is accepted. Those are your organisation's decisions.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the approval for a finding left open past its target date.
- Limits of this row
- No requests: this row holds owners, dates and decisions.
M7. Security check before a release goes live (filed under 8.29 by assumption)
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- 8.29, if your copy confirms it as a control. Question for your copy: what does the control's text say, word for word, and does it bear on particular stages of your development and release process? If so, which? Then list the security checks your release process runs and where each run is recorded.
- What to keep
- The release identifier and date, who approved it, any release held back by a failed check, and the outcome of three requests sent to the staging build before it goes live, each with its date and time. First, signed in as test customer B, ask for one of test customer A's records by its id. Second, signed in as test customer A, ask for one page or API route meant only for staff. Third, signed in as no one, ask for that record of A's again. Note whether each request was refused.
- What a test of the website or application can contribute
- No tester takes part. Your own team runs this short check on each release, and the test accounts kept from an earlier test can serve for it.
- Where it stops, and whose decision it is
- Anything past those three requests. A release that changes sign-in, roles or customer records may call for a scoped test of its own. Whether your release process meets what your copy says under 8.29 is for your organisation and its auditor to judge.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the security acceptance criteria a release has to meet, and the record of a release they stopped.
- Limits of this row
- This row sends requests. Point them at your own organisation's application and nothing else, using staging if a copy exists. Sign in only with test accounts whose records are invented; no real customer's, client's or staff member's account or record takes part. Send the counted requests below one after another and nothing more, so there is no load. An email or text that a request sets off has to arrive at an address or number you control. The record holds the address, the time, the status code and whether access was refused, and never a password, session cookie, token or key. A link that works for whoever holds it (a password reset link, for one) is opened only for a test account's own invented record and is not copied into the record. If a vendor runs any part of what the requests reach, go through the vendor's terms beforehand, ask the vendor about any gap in them, and stop where the terms or the answer stop. A response carrying a real person's data ends the row: record only where it appeared and when, go no deeper into it, and report it to your organisation's privacy or incident contact. Count for this row: one sign-in as test customer B, a sign-out, one sign-in as test customer A, a sign-out, and the three requests listed, each sent once, seven in all.
M8. Test report filed
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- The records your ISMS points to as evidence, such as any statement of applicability. Question for your auditor: which parts of the report do you need to see, and may a summary stand in for the full report?
- What to keep
- Report date and version; build and test dates; scope as tested; findings and their ratings; checks that found nothing; test cases that did not run; the report's storage location and the people allowed to read it.
- What a test of the website or application can contribute
- The report, as a dated account of how one application's controls behaved on the build that was tested, along with its findings and where the test stopped.
- Where it stops, and whose decision it is
- Whether the ISMS exists or runs, and any control beyond the scope, office networks, staff devices, backups and incident response among them.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the full report rather than its summary, read under your confidentiality terms.
- Limits of this row
- No requests: this row files a document. Because the full report explains how to reproduce open findings, limit it to the people your process names.
M9. Developer check of fixes before the retest
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- 8.8 and 8.29, once your copy confirms both as controls, as your process applies them. Question for your process: does a fix have to pass its own checks on an identified build before the retest is requested?
- What to keep
- Which build was checked, and for every finding, what happened when its retest criteria were run once against that build, timestamped.
- What a test of the website or application can contribute
- The retest criteria a Clever Ops report writes into each finding, setting out in advance what the retest will look at.
- Where it stops, and whose decision it is
- Independence. Developers checking their own fixes are getting ready for the retest; the record M10 keeps is the tester's retest.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the change record that links each fix to its finding.
- Limits of this row
- This row sends requests. Point them at your own organisation's application and nothing else, using staging if a copy exists. Sign in only with test accounts whose records are invented; no real customer's, client's or staff member's account or record takes part. Send the counted requests below one after another and nothing more, so there is no load. An email or text that a request sets off has to arrive at an address or number you control. The record holds the address, the time, the status code and whether access was refused, and never a password, session cookie, token or key. A link that works for whoever holds it (a password reset link, for one) is opened only for a test account's own invented record and is not copied into the record. If a vendor runs any part of what the requests reach, go through the vendor's terms beforehand, ask the vendor about any gap in them, and stop where the terms or the answer stop. A response carrying a real person's data ends the row: record only where it appeared and when, go no deeper into it, and report it to your organisation's privacy or incident contact. Count for this row: for each test account the retest criteria use, a single sign-in and a single sign-out, plus each request those criteria list, sent once from the accounts the original test used, and nothing beyond that.
M10. Retest status for each finding
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- 8.8, if your copy confirms it as a control, and your risk record. Question for your process: does the risk record carry every finding's post-retest status, and does every finding not marked fixed go back to M6?
- What to keep
- Date of the retest, the build it covered, and every finding's status in the retest report.
- What a test of the website or application can contribute
- After a Clever Ops retest every finding stands as fixed, partially fixed, still reproducible or not retested; a finding the retest skipped shows as not retested, not as passed.
- Where it stops, and whose decision it is
- Findings that were never reported, and anything released once the retest was over.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the plan and owner for each finding still marked partially fixed or still reproducible.
- Limits of this row
- No requests: this row writes down the retest outcome.
M11. Parts of the application a supplier runs
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- Your supplier records and risk record. Question for your agreement: what does it say about security testing and reporting for the parts the supplier runs?
- What to keep
- The supplier's name and what it runs; its published security and testing terms as read, with the date; what you asked it and its answer; and any report or certificate it supplied, with who issued it, the period it covers and the service it names.
- What a test of the website or application can contribute
- A test of your own side of the connection, such as what your application sends to the supplier and what it accepts back, where the supplier's terms allow it or the supplier agrees.
- Where it stops, and whose decision it is
- How the supplier's platform treats its other customers. A test of your application is not an assessment of the supplier.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the scope of the supplier's own certificate, to show whether it covers the service you use.
- Limits of this row
- No requests: this row reads agreements and terms, and it runs no test of any kind, the supplier's own system included.
M12. Review after the test cycle
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- Any internal audit or management review records your ISMS keeps, and any statement of applicability. Question for your copy: does it call for reviews of this kind, and if so, does it say what they must consider? Then note where test results enter them.
- What to keep
- Who reviewed and when; applications listed in M1 that went untested this period; M4's exclusions; findings still open in M10; supplier answers still outstanding in M11; any statement of applicability lines changed in M3; and the decisions taken.
- What a test of the website or application can contribute
- For every test in the period, its scope, dates, exclusions and retest statuses, which together separate the tested from the untested.
- Where it stops, and whose decision it is
- Whether the ISMS conforms to the standard. That is a judgement for the people your ISMS names and for the auditor you engage, not for a tester.
- What an auditor may still request (examples only, not a list from the standard)
- Example: the record showing that test results were considered at whatever review your ISMS holds, and the actions it set.
- Limits of this row
- No requests: this row compares your own records.
M13. Pack for an external audit
- Where it sits in your ISMS, and the question to put to your own copy or your auditor
- The audit itself. Question for your auditor, before any test is scoped: which applications do you expect evidence for, what age of report will you accept, and do you expect the tester to have had no role in building or running the system?
- What to keep
- For each application: its M1 line, its risk record entries from M2, any statement of applicability lines from M3, the scope and authorisation from M4, the report from M8, the decisions from M6 and the retest from M10, with an index of where each sits.
- What a test of the website or application can contribute
- Dated, scoped evidence about the applications tested, with a status for each finding after the retest.
- Where it stops, and whose decision it is
- Certification. The auditor weighs a test report as evidence; it is no certificate, and which controls it supports, if any, is the auditor's call.
- What an auditor may still request (examples only, not a list from the standard)
- Examples: records of the same process for applications not tested this cycle, evidence that the people running the process were trained for it, and how your organisation checked the tester's independence. These are examples, not a list from the standard.
- Limits of this row
- No requests: this row assembles records.
ISO 27001 requirements at a glance: the standard, its edition and where to read it
ISO/IEC 27001:2022 is an International Standard titled Information security, cybersecurity and privacy protection, Information security management systems, Requirements.
Its designation carries the names of both ISO and IEC, and IEC's catalogue page for it, as read on 15 November 2026, lists it as edition 3.0, published on 25 October 2022, and names its technical committee as ISO/IEC JTC 1/SC 27.
The page's Lifecycle tab lists an amendment, ISO/IEC 27001:2022/AMD1:2024, dated 23 February 2024, under the same edition, and shows both it and the 2022 standard with the status Valid.
IEC's own page for that amendment gives it a title ending in Amendment 1: Climate action changes. The earlier editions it lists, from 2005 and 2013, carry the status Revised.
The same page carries a short abstract which, in brief, describes the document as specifying requirements for an information security management system. It does not mention penetration testing, an annex or any individual control.
That is as far as the open catalogue page goes. The standard itself is licensed text: IEC's page offers it for sale, and its clauses are read in a copy obtained under licence, not in a summary. This guide was prepared with no access to the standard's own text.
It does not say what any clause or control contains, and the IEC catalogue pages it cites print no annex, no control number and no control title. So before you use the matrix, confirm in your own copy that each number your documents cite, such as 8.8 or 8.29, is a control there, and read what it says.
A paraphrase of a requirement, from memory or from a secondary website, can lead you to file the wrong evidence against it. Wherever the guide needs to know what the standard says, it gives you a question to put to your own copy instead, and the evidence matrix at the end puts that question in its second column, for you to answer in the same row.
Write the edition, and the amendment if your copy includes it, beside every clause or control number you file, so the record still makes sense when someone reads it against a different copy. A contract, tender or auditor may name an edition of its own; where one does, use theirs.
How the standard reaches a business
ISO/IEC 27001 can reach a business through its own choice or through someone else's documents: a customer contract, a tender, a supplier questionnaire, a parent company's policy or a board paper. Government policy shows one way it gets named. Queensland's Information and cyber security policy (IS18), in its Requirement 1, says agencies "must implement and operate an ISMS based on the current version of ISO 27001", and that "the scope of the ISMS will include the protection of all services, information, application, and technology assets".
Under its applicability heading, IS18 says it applies to "all Queensland Government departments (as defined by the Public Sector Act 2022)", and also "to accountable officers (not already in scope of the Public Sector Act 2022) and to statutory bodies under the Financial and Performance Management Standard 2019 in the context of internal controls, financial information management systems and risk management".
Whether IS18, or a contract or tender that names ISO/IEC 27001, applies to your organisation is for your own adviser, or the agency or customer that set the requirement, to confirm with you.
The reader in mind owns, manages or leads the technical side of a business that has run into the standard and has a website, customer portal or web application. Read it as background, not as legal advice or an audit; nothing in it says that a business conforms to the standard or holds a certificate.
When your documents cite Annex A 8.8 or A.8.29: checking the numbers in your own copy
This guide is built around two numbers, 8.8 and 8.29, which a questionnaire, contract, tender or auditor may put to you as Annex A 8.8 and A.8.29, or without the A.
Whatever your own copy says under those numbers is what you file evidence against, not this page or any summary of it.
NIST's Informative Reference catalogue for its Cybersecurity Framework (CSF) 2.0 hosts mappings to ISO/IEC 27001:2022 that other parties submitted, and NIST says it does not test non-NIST mappings for correctness and that listing them does not imply its endorsement. As the catalogue showed them on 16 November 2026, the mapping whose developer it gives as Razilio lists "ISO/IEC 27001:2022: Annex A Controls: 8.8" against ID.RA-01 ("Vulnerabilities in assets are identified, validated, and recorded"), against PR.DS-01 ("The confidentiality, integrity, and availability of data-at-rest are protected") and against the Platform Security (PR.PS) category, and it lists nothing numbered 8.29.
The mapping whose developer it gives as "Independent" lists "ISO/IEC 27001:2022: Control 8.8" against PR.PS-01 ("Configuration management practices are established and applied") and "ISO/IEC 27001:2022: Control 8.29" against PR.PS-06 ("Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle").
Neither mapping prints a title or text for any entry, so they show where their developers placed the numbers, not what your copy says under them.
Why these two numbers? They are the ones this guide is built around. As an assumption made without the text of either control, the matrix files its vulnerability rows (M5, M6 and M10) against 8.8, its pre-release check (M7) against 8.29, and the test scope (M4) and the developer check of fixes (M9) against both.
Once you have read your copy, move any row to wherever your copy and your auditor put it. Other controls may bear on the same application too; if your ISMS keeps a statement of applicability, check which ones it links to the application.
A separate standard sits beside this one. IEC's catalogue page for ISO/IEC 27002:2022, edition 3.0, published on 15 February 2022, says it provides a reference set of generic information security controls "including implementation guidance", designed to be used in the ways its abstract lists, the first of them within the context of an ISMS based on ISO/IEC 27001.
It is its own publication, sold on its own. Neither catalogue page says how the numbering of ISO/IEC 27002 relates to ISO/IEC 27001, so check that in your own copies before you rely on one to read the other.
Questions to put to your copy about 8.8
These questions follow this guide's assumption about the number. Drop any that do not fit what your copy says, and write each answer, with the number and edition, into the matrix.
- Is 8.8 a control in your copy, and if it is, what does it say, word for word? Copy it into row M5.
- Does it say where information about weaknesses should come from? List the sources your process uses: test reports, supplier advisories, dependency alerts and reports from people outside the business.
- Does it say anything about evaluating a weakness, or about how quickly one is dealt with? Compare that with the target dates in row M6.
- If your ISMS keeps a statement of applicability, which systems does it apply 8.8 to, and is this application one of them?
Questions to put to your copy about 8.29
The same discipline applies to 8.29.
- Is 8.29 a control in your copy, and if it is, what does it say, word for word? Copy it into row M7.
- Does it name stages of building and releasing software? If it does, mark which of them your own release process covers.
- Does it say anything about planning tests or about criteria a change must meet before it is accepted? Compare that with what your release checklist records.
- Does a test by an outside tester count towards it in your ISMS, or is that evidence for 8.8 instead? Ask your auditor, and record the answer in row M13.
Where a website or web application sits in an ISMS
This guide reads a website, a customer portal or a web application, together with its API and the records it keeps, as something an ISMS accounts for once it falls inside the scope.
On that reading it turns up in five kinds of record, and the matrix gives each one rows of its own.
- The scope statement, which says whether each website, portal and API is inside the ISMS, and why any of them sits outside it (row M1).
- The risk record, where threats to the application and its data are recorded, rated, owned and treated (rows M2 and M6).
- A statement of applicability, if your copy calls for one and your ISMS keeps one, where your lines for 8.8 and 8.29, once you have confirmed them in your copy, point to the records that evidence them (row M3).
- The evidence the matrix files against 8.8 and 8.29 for this application, as an assumption made without the text of either control and to be moved once you have read your copy: the test's scope, its findings, the decisions on them, the checks run on each release, and the retest (rows M4 to M10).
- The reviews and audits that look back over a cycle, and the pack you give an external auditor (rows M12 and M13).
Parts a supplier runs
A booking engine, a payment page or a hosted platform behind your portal is part of how the application works, but its owner runs it. Row M11 keeps what you know about those parts: the supplier's terms, what you asked and the answer, and any certificate or report it gave you, with the issuer, dates and service covered.
A test of your application can cover your side of the connection where the supplier's terms allow it or the supplier agrees. It is not an assessment of the supplier.
ISO 27001 penetration testing: what a test report can add to your records
Read narrowly, a test report describes one application on particular dates.
It names the build, the roles and accounts used, the routes tried and what was left out, and for each weakness it found, the evidence that reproduces it. That narrowness is what makes it useful inside an ISMS.
A dated record can be filed against one scope line, one risk entry or, if your ISMS keeps a statement of applicability, one line of it, and anyone reading it later can see exactly how far it reaches.
Mapped onto the evidence matrix on this page, a web application and API penetration test report can supply the following records, and no more:
- For the inventory and scope (M1): the route list, roles and accounts the test covered, to compare with your own list. A website security check adds a hostname inventory that includes names you may not know about.
- For the risk record (M2 and M6): each finding's description, evidence and business impact, and for each rated finding its CVSS v3.1 score and its business-risk rating, as inputs that your own risk method then rates.
- For a statement of applicability, where your ISMS keeps one (M3): a dated record its lines can point to, for the application tested and nothing else.
- For the vulnerability record (M5): the weaknesses the test found, each mapped to its OWASP Top 10:2025 category, and the checks that came back clean on the build and accounts tested.
- For the fixes and the retest (M9 and M10): a fix and retest criteria for each finding, then, once the single consolidated retest is done, one of four statuses for each: fixed, partially fixed, still reproducible or not retested.
- For the review at the end of the cycle (M12): the scope, dates and exclusions, which show what the period's testing covered and what it did not.
What a test cannot show an auditor
A test of one application says nothing about how an ISMS is run. It does not show that the scope was set well, that risks were assessed by a consistent method, that the people running the system know what to do, or that reviews and audits take place.
Office networks, staff devices, email, backups, cloud consoles and suppliers' platforms sit outside its scope, and it says nothing about them.
It does not decide whether a risk is acceptable or a delay reasonable. Nor does it find that an organisation conforms to ISO/IEC 27001, and it is no certificate of any kind.
The matrix marks each row's boundary in its fifth column, so that a test result is not filed against a record it does not support. The security questionnaires guide covers the related problem of answering a customer who asks about several frameworks at once.
How to use the evidence matrix for 8.8 and 8.29
The matrix turns one web application's test cycle into the records an ISMS keeps about it.
Paste it into a spreadsheet, start a fresh copy for each application, and work through the rows in order.
- Open your own copy of the standard beside the matrix, and confirm there that 8.8 and 8.29 are controls before you file anything under them. Where a row asks a question of your copy, write the answer with its clause or control number, so the row records what your edition says rather than what someone remembers it saying.
- Fill in M1 for each website, portal and API ahead of planning any test. An application missing from the inventory has no row to evidence anything.
- Rows M2 to M4 come before the test, M5 to M10 follow it, M7 runs on every release, M11 covers the parts a supplier runs, and M12 and M13 close the cycle.
- Only M7 and M9 send requests to a running copy of your application, staging where one exists, and the last column of each carries its own limits and request count. The other eleven rows work from documents and records.
- If M7 or M9 would touch something a vendor operates, the vendor's terms set the boundary. Read them, ask the vendor about any gap, and do no more than those terms, or the vendor's answer, permit. Nothing here states what a vendor permits.
- Keep the evidence for checks that passed as well as those that failed, because the review in M12 needs a dated pass to show that an application was tested.
- The sixth column gives examples of what an auditor may still ask for after reading a test report. They are examples written for this page, not a list from the standard, and your auditor decides what they need.
- A real person's record turning up where an invented one should be is the signal to stop. Record where it appeared and when, open nothing else, and pass it to your organisation's privacy or incident contact.
Certification, audit and who decides
An organisation that runs an ISMS makes its own decisions about it: the scope, the risks and how each is treated, any statement of applicability, and the evidence behind each line.
A test report feeds those decisions without making any of them. Whether a finding is acceptable, whether a delay is reasonable and whether a control is included all stay with the people your ISMS names.
Certification is a separate step from testing. The Cloud Security Alliance's STAR Program, as one published scheme, describes its Level 2 as a "Third-party audit" and lists its forms as "Certification (ISO/IEC 27001), Attestation (SOC 2), or C-STAR for the Greater China market, each combined with a CAIQ submission".
This guide does not set out who may certify an organisation or who accredits the bodies that do. Ask any provider that offers certification which body will issue the certificate, and whether that body is accredited and by whom. When a supplier shows you a certificate, check that its scope covers the service you are buying.
If you are being audited, your auditor decides what evidence they need. Put the questions in row M13 to them before a test is scoped and bring their answers to the scoping call, so the test covers what they expect to see. A SOC 2 report is a different kind of audit report, and the SOC 2 guide deals with it.
What Clever Ops can add to an ISMS, and what it leaves to others
Clever Ops tests what a business exposes to its customers and staff in a browser or through an API.
A website gets the website security check, from outside, or on WordPress the WordPress security audit, which covers each role able to log in. Custom applications with customer or staff sign-in get the web application and API penetration test. The vibe-coded app security check is for apps produced with an AI builder, and the AI chatbot and agent security test is for chatbots and agents.
Inside an ISMS, the report from any of them is a dated record of what was tested, and the fourth column of the matrix shows which parts of it, if any, each row can use; M7 is a check your own team runs on every release.
In it you get the scope as tested; findings whose evidence has secrets redacted; a CVSS v3.1 score beside a business-risk rating on every finding that is rated; a priority-ranked remediation plan; and the checks that came back clean, recorded against the build and accounts tested.
Coverage is described against ASVS 5.0 (OWASP's Application Security Verification Standard) and WSTG v4.2 (its Web Security Testing Guide), as a statement of what was checked, which does not make the report a certificate.
A single consolidated retest is part of every test, and afterwards each finding is fixed, partially fixed, still reproducible or not retested.
Clever Ops itself is neither certified nor accredited in security. It holds no ISO/IEC 27001 certificate, it is not a certification body and it certifies no one, and none of its tests is an ISMS audit or a certification audit. A Clever Ops report is material for your auditor's judgement; it certifies nothing and gives no view on compliance.
For an application that Clever Ops built or hosts, the work is a security review; we do not offer it as an independent test, and its report identifies the builder and the host. If an auditor or customer wants that application tested by someone who neither built nor runs it, we refer that work to another provider, one uninvolved in either.
Clever Ops is not CREST accredited, so if a contract or tender specifies a CREST-accredited provider, we refer the work on to a provider that is.
Other testing an ISMS might draw on is not something Clever Ops offers. Testing of internal networks, Active Directory, servers or staff devices, along with phishing, red teaming and physical testing, needs a network or red team specialist. No Clever Ops service covers denial-of-service, load or volumetric testing.
Clever Ops does not test a vendor's own product or platform; the system a supplier runs behind your portal is one example. The methodology guide follows a test from scope and authorisation through to the retest.
Frequently asked questions
The abstract on IEC's catalogue page for ISO/IEC 27001:2022 does not mention penetration testing. Beyond that, the answer is in the licensed text: read any part of your copy on assessing and treating risk, and whatever it says under any number your auditor cites, such as 8.8 or 8.29, and look for anything it says about testing. Whether a penetration test is the evidence your ISMS relies on for a control is your organisation's decision, and what evidence an audit needs is your auditor's. Ask them before you scope a test, using the questions in row M13 of the matrix.
They are numbers a questionnaire, contract or auditor may cite, with or without the A. This guide was written without the standard's text, and IEC's catalogue page prints no control title or text, so the page uses them as numbers only: check in your own copy, against your edition, that each is a control and what it says. In NIST's Informative Reference catalogue, the mapping whose developer is given as Razilio lists "Annex A Controls: 8.8" against ID.RA-01 and other CSF 2.0 entries, and the one whose developer is given as "Independent" lists "Control 8.29" against PR.PS-06; NIST says it does not test mappings that others submit for correctness. As an assumption made without the text of either control, the matrix files its vulnerability rows against 8.8 and its pre-release check against 8.29, a placement to check against your copy.
The one your contract, tender or auditor names, and otherwise the one your ISMS is built on. IEC's catalogue page lists ISO/IEC 27001:2022, edition 3.0, and its Amendment 1 of 2024 with the status Valid, and the 2005 and 2013 editions with the status Revised. The designation on your copy, such as ISO/IEC 27001:2022, carries its year, and IEC's catalogue gives the amendment a page of its own. Write the edition beside every clause or control number in the matrix, so the record still reads correctly against another copy, and ask your auditor which edition the audit will use before you relabel anything.
First check whether your copy calls for one and whether your ISMS keeps one. If it does, this guide's matrix treats it as the place where your lines for 8.8 and 8.29, once confirmed in your copy, point to their evidence: use row M3 to record which test reports, risk entries and release records each line relies on. A test report gives a line something dated to point to for the application tested. It does not decide whether a control is included or how it is implemented.
A test does not certify anyone. Its report covers the application, build and scope tested on the dates it gives, and it is for your auditor to judge whether it supports any control, and which. Clever Ops holds no ISO/IEC 27001 certificate and is not a certification body, so it issues no certificates. Its report gives your auditor the scope, the findings and the retest result to weigh.
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.