Skip to main content
Security guideReviewed

CREST penetration testing: what your tender's CREST wording asks for, and how to brief a provider that holds it

CREST International says CREST ANZ is a separate organisation.

Each body uses its own names for what it accredits, approves and certifies. This guide reads each body's own pages, decodes the wording a tender or contract uses, lists the questions an issuer answers before deciding on any equivalent, and comes with a scope sheet for briefing the provider you engage. Clever Ops is not CREST accredited, and where your documents require CREST, we refer you to an accredited provider.

CREST tender-wording decoder, equivalence questions and scope sheet

One table in three parts for a buyer whose tender, contract or customer policy names CREST. Rows D1 to D10 decode the wording, each against what CREST International or CREST ANZ says on its own pages.

How to use it

Rows E1 to E8 are equivalence questions for the issuer to answer and for you to record; they never decide that anything is equivalent. Rows S1 to S9 are the scope sheet, your own record of what you want tested on systems you own or hold written permission to test, ready to send to a provider that holds what your document names. Copy the table into a spreadsheet, paste your exact clause beside the matching D row, fill in the record column with the names and dates it asks for, and keep the finished sheet with the report. Every row reads documents or records decisions, and no row tests anything: none sends a test request to a website or application, signs in to one or submits a form in one. Whether a provider meets your document is decided by its issuer, and by any party whose contract the clause came from.

27 rows

CREST tender-wording decoder, equivalence questions and scope sheet

Part and rowWording, question or fieldWhere the answer comes fromWhat to check, answer or recordWhat it does not settle, and who decidesLimits of this row
D1. A CREST-accredited providerA provider "CREST accredited for penetration testing", a "CREST-accredited provider", or "CREST accreditation" with no discipline named.CREST International's Accreditation page: CREST Accreditation is awarded to organisations that evidence compliance with CREST Accreditation Standards through an application, evidence submission and review; CREST-accredited companies must undergo periodic reassessment to ensure continued compliance with best practices and CREST's Accreditation Standards; the disciplines include Penetration Testing and Vulnerability Assessment.The discipline the document names, and whether the provider is accredited in it, checked on CREST International's Marketplace, which its procurement guide says lets buyers search for accredited Member companies by service, capability and region. Record the provider, the discipline shown and the date checked.Whether the people who will test hold CREST certifications: CREST International's standards page says there is no mandatory requirement for individuals to be CREST qualified for a company to achieve accreditation. Which discipline the document means, where it names none, is for the issuer to say.Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
D2. A current CREST Member company for the relevant servicesA "CREST member", a "CREST Member company", or "a current CREST (International) Member company for the relevant services", the wording CREST International's procurement guide recommends.CREST International's Accreditation Pathway page: the Member stage represents the formal application and awarding of CREST Accreditation and Membership. Its membership FAQs: membership lasts for 12 months and is renewed annually; companies can hold multiple CREST accreditations under a single membership, and each accreditation remains subject to its own application and assessment process.That the provider is a Member rather than a Pathway or Pathway+ organisation, that its accreditation covers the services in your scope, and that its status is current on the date your document sets. Record all three with the date checked.What "relevant services" covers where the document does not list them, and which date "current" refers to. The issuer decides both.Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
D3. CREST Pathway or Pathway+A proposal, website or logo that shows CREST Pathway or Pathway+ status.CREST International's Accreditation Pathway page: Pathway involves registration and sign-up to the CREST Code of Conduct, and it is important that the organisation presents itself only as Pathway and not as a CREST-accredited Member. Pathway+ adds a self-assessment that CREST will not independently review at that stage, and it remains important that the organisation presents itself only as Pathway+ and not as a CREST Accredited Member.Which status your document asks for, and which CREST list the provider appears on. Record the status shown and the date.Whether your document accepts a Pathway or Pathway+ status. CREST International's page tells those organisations not to present themselves as accredited Members; whether the document accepts either status is for the issuer.Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
D4. CREST-certified testers"CREST certified testers", "personnel with CREST certifications", or "All personnel engaged in delivering the services should hold appropriate CREST professional certifications or equivalent."CREST International's exams page: professional examinations are broken down into three levels, Practitioner, Registered and Certified. Its certifications page lists under Penetration Testing the CPSA, CRT, CCT INF, CCT APP, CCRTS and CCRTM examinations, named in full on that page.The names of the testers, the certification each holds and the evidence the provider supplies, as your document asks. Note whether the document says must or should, and whether it names a level or an examination.What "appropriate" means, whether "certified" means any CREST certification or the Certified level, and what an equivalent may be. The issuer decides.Read-only row: it reads your document and the provider's evidence, and no test request goes to any system. Keep testers' personal details to the people who need them for the decision.
D5. "Or equivalent""Or equivalent" attached to a CREST clause, for the company, the people or both.CREST International's recommended RFT or RFP wording puts "or equivalent" in the sentence about personnel certifications, not in the sentence about the company. Its Certification Equivalency Recognition Programme page says CREST, in partnership with OffSec, recognises the OSCP and OSCP+ certification as meeting key requirements toward the CREST Registered Tester (CRT) qualification, under certain conditions. Its Australasia page says CREST ANZ membership alone is not recognised by CREST International as being equivalent.Which clause the "or equivalent" attaches to. Then take rows E1 to E8 to the issuer.Whether anything is equivalent. The issuer decides under its own procurement rules, and neither CREST body's statement makes that decision.Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
D6. CREST Australia, CREST Australasia or CREST ANZA document that names "CREST Australia", "CREST Australasia", "CREST ANZ" or "CREST Australia New Zealand".CREST ANZ's history page calls the organisation established in 2012 CREST Australia, and says that on 18 January 2016 CREST (Aust) Limited changed its registered company name to CREST Australia New Zealand Ltd. CREST International's Australasia page says CREST Australasia is represented and managed by the Australasia Council, and that the formal relationship between CREST International and CREST ANZ ended at the end of April 2019.Ask the issuer in writing which body it means, and keep the dated answer.Which body the document means. Only the issuer can say.Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
D7. CREST approved, or a CREST ANZ Approved CompanyA "CREST approved" provider, a "CREST ANZ Approved Company" or a "CREST ANZ Approved Member Company".CREST ANZ's Approved Companies page lists organisations who have satisfied the CREST Australia New Zealand requirements to become CREST Approved, and says CREST ANZ Approved Member Companies have subjected themselves to audit and scrutiny by CREST ANZ and have signed up to the CREST ANZ Code of Conduct. Its membership application page lists the criteria, which include a regular audit of policies and procedures relating to security testing. CREST International's web address is crest-approved.org, and its Accreditation Pathway page calls its company status CREST Accreditation and a CREST-accredited Member.Which body the document means, using row D6. For CREST ANZ, check the provider on its Approved Companies page and record the date.Whether a CREST ANZ approval answers a document that names CREST without saying which body. The issuer decides.Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
D8. ABPT, or Accredited Best of Breed Penetration TesterA CV, bid or clause that lists ABPT or Accredited Best of Breed Penetration Tester.CREST ANZ's home page: the ABPT program accredits individual penetration testers (employees and contractors) against Technical Competency, Professional Competency and Trust Standards developed and defined by CREST ANZ members, and is open to testers from member and non-member companies. Its accreditation process page: ABPT accreditations remain valid for 18 months from the date of completion.The tester's name and the completion date of the accreditation, so you can see whether it falls within 18 months of the date your document sets.Whether an ABPT accreditation answers a clause about CREST certifications. CREST International's Australasia page says CREST ANZ have no rights to the CREST International suite of company accreditations or individual certifications; what your document accepts is for the issuer.Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
D9. Evidence with the submission"Evidence of company accreditation and individual certifications must be provided with the tender submission", or any clause on when and how status is shown.CREST International's procurement guide, in its recommended RFT or RFP wording. Among the questions its checklist says organisations should ask are whether the organisation is a current CREST (International) Member for the relevant service(s), and whether it can demonstrate that personnel hold current CREST (International) certifications or equivalent.What evidence is due, in what form and by when. When you are the one requesting quotes, ask each provider for that evidence with its quote.Whether the evidence supplied is enough. The issuer's evaluation decides; the recommended wording says submissions that do not meet the requirements "may be deemed noncompliant".Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
D10. CREST attached to the test or the reportWording that attaches CREST to a test or a report, such as "a CREST penetration test", rather than to the provider or the people.The CREST International and CREST ANZ pages cited in this guide describe the accreditation, approval or membership of companies and the certification or accreditation of individuals. None of them describes a CREST status for a single test or report.Ask the issuer whether it means the provider's accreditation, the testers' certifications or both, and record the answer.What the wording means. The issuer decides.Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
E1. Is an equivalent allowed, and for which clause?Does the document allow an equivalent at all, and does it attach to the company clause, the people clause or both?Your document. In CREST International's recommended wording, "or equivalent" appears only in the sentence about personnel certifications.The exact words, the clause number, and which clause the equivalent attaches to.If the answer is no, rows E2 to E8 do not apply, and the work goes to whichever provider holds what the document names. The issuer decides what the document allows.Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
E2. Who decides, under which rule, and how is it recorded?Who decides equivalence, under which procurement rule or policy, and is the decision made before submissions are read?Your procurement policy, panel rules or contract.The person or panel that decides, the rule they apply, when the decision is made, where it is filed, and whether your policy says it is shared with every respondent.What your rules require. Whoever oversees your procurement interprets them.Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
E3. What do you rely on the clause for?What does your organisation rely on the CREST clause for?Your own reasons, in your own words. A clause carried down from a customer contract or a panel brings that party's reasons with it.A short statement of what the clause is meant to give you, such as an assessed provider for a named discipline, or assessed people on the engagement team.Whether anything else gives you the same. That is the decision the issuer reaches through rows E4 to E8.Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
E4. Which discipline and which level?Which discipline does the company clause name, and which certification or level does the people clause name?Your document. CREST International's accreditation disciplines include Penetration Testing and Vulnerability Assessment, and its professional examinations are broken down into three levels: Practitioner, Registered and Certified.The discipline and the certification or level as written, or the issuer's answer where the document names none.Which disciplines or levels an alternative has to match. The issuer decides.Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
E5. What would an alternative company status have to show?What evidence about a company would the issuer accept in place of the status the clause names, and who must have assessed it?Your procurement rules. For reference, CREST International's Accreditation page describes its process as an application, evidence submission and review with periodic reassessment, and CREST ANZ's membership application page lists criteria that include a regular audit of policies and procedures relating to security testing.Who assessed the company, against what, for which services, on what date, and whether it is reassessed.Whether a given status qualifies. The issuer decides; this guide does not.Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
E6. What would an alternative qualification for people have to show?Which qualifications would the issuer accept for each role in place of the certification the clause names?Your procurement rules. CREST International's own equivalency programme recognises OSCP or OSCP+ as meeting key requirements toward its CRT qualification only under the conditions its page sets, which include a valid CPSA pass.The qualifications accepted for each role, who issues them, and how currency is shown.Whether a named qualification is accepted. CREST's recognition inside its own framework does not decide your document; the issuer does.Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
E7. On what date must status be current?On which date must the company's status and each person's certification be current?Your document. CREST International's membership FAQs say membership lasts for 12 months and is renewed annually; CREST ANZ says ABPT accreditations remain valid for 18 months from the date of completion.The date the issuer names (closing date, contract date or each day of the testing window), and the date you checked each status.Status after the day you checked. Check again close to the date that matters.Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
E8. Did the clause come from someone else?Was the clause set by another party, such as a customer, a head contractor or a panel, and has that party been asked about equivalence?The contract, policy or panel rule the clause came from.Who set the clause, whether they were asked, their answer in writing and its date.What your contract requires of you. Ask your own adviser.Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
S1. The requirement, who asked and by whenThe CREST clause copied exactly, and the people and dates around it.Your tender, contract or customer policy, read with rows D1 to D10, and any answers from E1 to E8.Document name and clause number; the exact words; the body named; the discipline; the people clause; the evidence due and when; the issuer or customer and their contact; the date the report or evidence is due; and any equivalence answers with their dates.Whether a provider meets the clause. The issuer decides, from the provider's evidence.Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
S2. What is to be tested, and whereTargets and environment.Your own list of systems and your hosting setup.Every domain, subdomain and API address that is in scope; what the application does and who signs in to it; the build or version; anything at those addresses that must be left alone; and whether a staging copy that matches production exists, with its address. If production is the target, the agreed testing windows and how test data is removed afterwards.Systems not listed here. They are out of scope, and the report should say so.Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
S3. Ownership and written permissionWho owns each target, and the permission you hold to have it tested.Your contracts, and your hosting provider's testing policy.The owner of each target and who will sign the authorisation; for any target you do not own, the written permission you hold; and the hosting provider's testing policy as you read it, with the date.Permission you do not hold. A target without it stays out of scope until the permission is in writing.Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
S4. Services another business runsPayment pages, booking engines, hosted forms, learning or practice management platforms and similar services the application uses.Each vendor's own terms, and its written reply where they are silent.For each service: what its terms say about testing, the question you sent the vendor where the terms are silent, the vendor's reply and its date, and anything listed as excluded.What a vendor permits. Its own terms and its written reply decide; anything not permitted stays excluded.Record-only row: it reads vendor terms and replies, and no test request goes to the vendor's systems or yours.
S5. Roles, test accounts and test recordsThe roles in scope and the accounts created for the test.Your application's roles, and the number of accounts the provider asks for.Each role in scope; the test accounts for each, with accounts in two customer organisations if the application serves more than one; the invented records each account holds; and the address or number any email or text from those accounts goes to, which your business controls. Keep passwords out of this sheet and send them to the provider separately.Accounts the provider needs beyond these. It asks, and you add them here.Record-only row: it lists the accounts your business sets up for the test on your own application, on the staging copy in S2 where one exists. They hold invented records only, never a real customer's, patient's, client's, student's, tenant's or guest's. Passwords, keys, tokens and shareable links that open an account or a file for anyone who has them stay out of this sheet.
S6. Depth and disciplineHow far the test goes, and the discipline your document names.Your document and your own decision. The methodology guide in this library explains unauthenticated, authenticated and code-assisted testing.The depth (unauthenticated, authenticated or code-assisted), the roles each depth covers, and the CREST discipline the document names, such as Penetration Testing or Vulnerability Assessment.Whether that depth is enough for whoever will rely on the report. They decide.Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
S7. Conduct limits and exclusionsThe rules the provider works to, written into your request.Your own rules for testing, agreed in writing before testing starts.Testing only against the targets in S2, on the staging copy listed there where one exists, with the permission in S3. No load testing, volumetric testing or denial-of-service attempts. Destructive actions off by default for real people's accounts and records that existed before the test; reset, lockout and deletion checks only on test accounts and test records where the rules of engagement allow them. Evidence and the report leave out passwords, keys, tokens and shareable links that open an account or a file for anyone who has them. If testing shows a real person's data, the provider stops, records the address and the time, opens nothing further and tells the contact in S8.Anything the rules of engagement leave unstated. Settle it in writing before testing starts.Record-only row: it states limits for the provider, and no test request goes to any system.
S8. Contacts, evidence handling and what comes backWho the provider talks to, where evidence goes, and what you need at the end.Your own people, and your document's evidence clause. Under Penetration Testing and / or Red Teaming, CREST International's procurement guide says to request evidence of methodologies, reporting standards and retesting processes.The technical contact during testing who can pause it; the person responsible for privacy questions and incidents; where test evidence may be stored and who may read the report; and what you need back: the report, the retest result, the provider's accreditation evidence and its testers' certification evidence as your document asks, and a statement of whether the provider built, hosts or maintains the system.Whether the report satisfies the issuer. The issuer decides.Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
S9. Provider status checkThe provider's status, checked with the body your document names.CREST International's Marketplace or CREST ANZ's Approved Companies page, as row D6 decides.The provider's name, the body, the status and discipline shown, the date checked and who checked it; the evidence received for each tester; and, if you are a supplier rather than the issuer, the date you sent this record to the issuer.Status after the day you checked. Each body keeps its own list.Read-only row: it reads a body's public list, and no test request goes to any system.

Part and row

Wording, question or field

  1. D1. A CREST-accredited provider
    Wording, question or field
    A provider "CREST accredited for penetration testing", a "CREST-accredited provider", or "CREST accreditation" with no discipline named.
    Where the answer comes from
    CREST International's Accreditation page: CREST Accreditation is awarded to organisations that evidence compliance with CREST Accreditation Standards through an application, evidence submission and review; CREST-accredited companies must undergo periodic reassessment to ensure continued compliance with best practices and CREST's Accreditation Standards; the disciplines include Penetration Testing and Vulnerability Assessment.
    What to check, answer or record
    The discipline the document names, and whether the provider is accredited in it, checked on CREST International's Marketplace, which its procurement guide says lets buyers search for accredited Member companies by service, capability and region. Record the provider, the discipline shown and the date checked.
    What it does not settle, and who decides
    Whether the people who will test hold CREST certifications: CREST International's standards page says there is no mandatory requirement for individuals to be CREST qualified for a company to achieve accreditation. Which discipline the document means, where it names none, is for the issuer to say.
    Limits of this row
    Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
  2. D2. A current CREST Member company for the relevant services
    Wording, question or field
    A "CREST member", a "CREST Member company", or "a current CREST (International) Member company for the relevant services", the wording CREST International's procurement guide recommends.
    Where the answer comes from
    CREST International's Accreditation Pathway page: the Member stage represents the formal application and awarding of CREST Accreditation and Membership. Its membership FAQs: membership lasts for 12 months and is renewed annually; companies can hold multiple CREST accreditations under a single membership, and each accreditation remains subject to its own application and assessment process.
    What to check, answer or record
    That the provider is a Member rather than a Pathway or Pathway+ organisation, that its accreditation covers the services in your scope, and that its status is current on the date your document sets. Record all three with the date checked.
    What it does not settle, and who decides
    What "relevant services" covers where the document does not list them, and which date "current" refers to. The issuer decides both.
    Limits of this row
    Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
  3. D3. CREST Pathway or Pathway+
    Wording, question or field
    A proposal, website or logo that shows CREST Pathway or Pathway+ status.
    Where the answer comes from
    CREST International's Accreditation Pathway page: Pathway involves registration and sign-up to the CREST Code of Conduct, and it is important that the organisation presents itself only as Pathway and not as a CREST-accredited Member. Pathway+ adds a self-assessment that CREST will not independently review at that stage, and it remains important that the organisation presents itself only as Pathway+ and not as a CREST Accredited Member.
    What to check, answer or record
    Which status your document asks for, and which CREST list the provider appears on. Record the status shown and the date.
    What it does not settle, and who decides
    Whether your document accepts a Pathway or Pathway+ status. CREST International's page tells those organisations not to present themselves as accredited Members; whether the document accepts either status is for the issuer.
    Limits of this row
    Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
  4. D4. CREST-certified testers
    Wording, question or field
    "CREST certified testers", "personnel with CREST certifications", or "All personnel engaged in delivering the services should hold appropriate CREST professional certifications or equivalent."
    Where the answer comes from
    CREST International's exams page: professional examinations are broken down into three levels, Practitioner, Registered and Certified. Its certifications page lists under Penetration Testing the CPSA, CRT, CCT INF, CCT APP, CCRTS and CCRTM examinations, named in full on that page.
    What to check, answer or record
    The names of the testers, the certification each holds and the evidence the provider supplies, as your document asks. Note whether the document says must or should, and whether it names a level or an examination.
    What it does not settle, and who decides
    What "appropriate" means, whether "certified" means any CREST certification or the Certified level, and what an equivalent may be. The issuer decides.
    Limits of this row
    Read-only row: it reads your document and the provider's evidence, and no test request goes to any system. Keep testers' personal details to the people who need them for the decision.
  5. D5. "Or equivalent"
    Wording, question or field
    "Or equivalent" attached to a CREST clause, for the company, the people or both.
    Where the answer comes from
    CREST International's recommended RFT or RFP wording puts "or equivalent" in the sentence about personnel certifications, not in the sentence about the company. Its Certification Equivalency Recognition Programme page says CREST, in partnership with OffSec, recognises the OSCP and OSCP+ certification as meeting key requirements toward the CREST Registered Tester (CRT) qualification, under certain conditions. Its Australasia page says CREST ANZ membership alone is not recognised by CREST International as being equivalent.
    What to check, answer or record
    Which clause the "or equivalent" attaches to. Then take rows E1 to E8 to the issuer.
    What it does not settle, and who decides
    Whether anything is equivalent. The issuer decides under its own procurement rules, and neither CREST body's statement makes that decision.
    Limits of this row
    Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
  6. D6. CREST Australia, CREST Australasia or CREST ANZ
    Wording, question or field
    A document that names "CREST Australia", "CREST Australasia", "CREST ANZ" or "CREST Australia New Zealand".
    Where the answer comes from
    CREST ANZ's history page calls the organisation established in 2012 CREST Australia, and says that on 18 January 2016 CREST (Aust) Limited changed its registered company name to CREST Australia New Zealand Ltd. CREST International's Australasia page says CREST Australasia is represented and managed by the Australasia Council, and that the formal relationship between CREST International and CREST ANZ ended at the end of April 2019.
    What to check, answer or record
    Ask the issuer in writing which body it means, and keep the dated answer.
    What it does not settle, and who decides
    Which body the document means. Only the issuer can say.
    Limits of this row
    Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
  7. D7. CREST approved, or a CREST ANZ Approved Company
    Wording, question or field
    A "CREST approved" provider, a "CREST ANZ Approved Company" or a "CREST ANZ Approved Member Company".
    Where the answer comes from
    CREST ANZ's Approved Companies page lists organisations who have satisfied the CREST Australia New Zealand requirements to become CREST Approved, and says CREST ANZ Approved Member Companies have subjected themselves to audit and scrutiny by CREST ANZ and have signed up to the CREST ANZ Code of Conduct. Its membership application page lists the criteria, which include a regular audit of policies and procedures relating to security testing. CREST International's web address is crest-approved.org, and its Accreditation Pathway page calls its company status CREST Accreditation and a CREST-accredited Member.
    What to check, answer or record
    Which body the document means, using row D6. For CREST ANZ, check the provider on its Approved Companies page and record the date.
    What it does not settle, and who decides
    Whether a CREST ANZ approval answers a document that names CREST without saying which body. The issuer decides.
    Limits of this row
    Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
  8. D8. ABPT, or Accredited Best of Breed Penetration Tester
    Wording, question or field
    A CV, bid or clause that lists ABPT or Accredited Best of Breed Penetration Tester.
    Where the answer comes from
    CREST ANZ's home page: the ABPT program accredits individual penetration testers (employees and contractors) against Technical Competency, Professional Competency and Trust Standards developed and defined by CREST ANZ members, and is open to testers from member and non-member companies. Its accreditation process page: ABPT accreditations remain valid for 18 months from the date of completion.
    What to check, answer or record
    The tester's name and the completion date of the accreditation, so you can see whether it falls within 18 months of the date your document sets.
    What it does not settle, and who decides
    Whether an ABPT accreditation answers a clause about CREST certifications. CREST International's Australasia page says CREST ANZ have no rights to the CREST International suite of company accreditations or individual certifications; what your document accepts is for the issuer.
    Limits of this row
    Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
  9. D9. Evidence with the submission
    Wording, question or field
    "Evidence of company accreditation and individual certifications must be provided with the tender submission", or any clause on when and how status is shown.
    Where the answer comes from
    CREST International's procurement guide, in its recommended RFT or RFP wording. Among the questions its checklist says organisations should ask are whether the organisation is a current CREST (International) Member for the relevant service(s), and whether it can demonstrate that personnel hold current CREST (International) certifications or equivalent.
    What to check, answer or record
    What evidence is due, in what form and by when. When you are the one requesting quotes, ask each provider for that evidence with its quote.
    What it does not settle, and who decides
    Whether the evidence supplied is enough. The issuer's evaluation decides; the recommended wording says submissions that do not meet the requirements "may be deemed noncompliant".
    Limits of this row
    Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
  10. D10. CREST attached to the test or the report
    Wording, question or field
    Wording that attaches CREST to a test or a report, such as "a CREST penetration test", rather than to the provider or the people.
    Where the answer comes from
    The CREST International and CREST ANZ pages cited in this guide describe the accreditation, approval or membership of companies and the certification or accreditation of individuals. None of them describes a CREST status for a single test or report.
    What to check, answer or record
    Ask the issuer whether it means the provider's accreditation, the testers' certifications or both, and record the answer.
    What it does not settle, and who decides
    What the wording means. The issuer decides.
    Limits of this row
    Read-only row: it reads your document and the bodies' public pages, and no test request goes to any system.
  11. E1. Is an equivalent allowed, and for which clause?
    Wording, question or field
    Does the document allow an equivalent at all, and does it attach to the company clause, the people clause or both?
    Where the answer comes from
    Your document. In CREST International's recommended wording, "or equivalent" appears only in the sentence about personnel certifications.
    What to check, answer or record
    The exact words, the clause number, and which clause the equivalent attaches to.
    What it does not settle, and who decides
    If the answer is no, rows E2 to E8 do not apply, and the work goes to whichever provider holds what the document names. The issuer decides what the document allows.
    Limits of this row
    Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
  12. E2. Who decides, under which rule, and how is it recorded?
    Wording, question or field
    Who decides equivalence, under which procurement rule or policy, and is the decision made before submissions are read?
    Where the answer comes from
    Your procurement policy, panel rules or contract.
    What to check, answer or record
    The person or panel that decides, the rule they apply, when the decision is made, where it is filed, and whether your policy says it is shared with every respondent.
    What it does not settle, and who decides
    What your rules require. Whoever oversees your procurement interprets them.
    Limits of this row
    Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
  13. E3. What do you rely on the clause for?
    Wording, question or field
    What does your organisation rely on the CREST clause for?
    Where the answer comes from
    Your own reasons, in your own words. A clause carried down from a customer contract or a panel brings that party's reasons with it.
    What to check, answer or record
    A short statement of what the clause is meant to give you, such as an assessed provider for a named discipline, or assessed people on the engagement team.
    What it does not settle, and who decides
    Whether anything else gives you the same. That is the decision the issuer reaches through rows E4 to E8.
    Limits of this row
    Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
  14. E4. Which discipline and which level?
    Wording, question or field
    Which discipline does the company clause name, and which certification or level does the people clause name?
    Where the answer comes from
    Your document. CREST International's accreditation disciplines include Penetration Testing and Vulnerability Assessment, and its professional examinations are broken down into three levels: Practitioner, Registered and Certified.
    What to check, answer or record
    The discipline and the certification or level as written, or the issuer's answer where the document names none.
    What it does not settle, and who decides
    Which disciplines or levels an alternative has to match. The issuer decides.
    Limits of this row
    Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
  15. E5. What would an alternative company status have to show?
    Wording, question or field
    What evidence about a company would the issuer accept in place of the status the clause names, and who must have assessed it?
    Where the answer comes from
    Your procurement rules. For reference, CREST International's Accreditation page describes its process as an application, evidence submission and review with periodic reassessment, and CREST ANZ's membership application page lists criteria that include a regular audit of policies and procedures relating to security testing.
    What to check, answer or record
    Who assessed the company, against what, for which services, on what date, and whether it is reassessed.
    What it does not settle, and who decides
    Whether a given status qualifies. The issuer decides; this guide does not.
    Limits of this row
    Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
  16. E6. What would an alternative qualification for people have to show?
    Wording, question or field
    Which qualifications would the issuer accept for each role in place of the certification the clause names?
    Where the answer comes from
    Your procurement rules. CREST International's own equivalency programme recognises OSCP or OSCP+ as meeting key requirements toward its CRT qualification only under the conditions its page sets, which include a valid CPSA pass.
    What to check, answer or record
    The qualifications accepted for each role, who issues them, and how currency is shown.
    What it does not settle, and who decides
    Whether a named qualification is accepted. CREST's recognition inside its own framework does not decide your document; the issuer does.
    Limits of this row
    Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
  17. E7. On what date must status be current?
    Wording, question or field
    On which date must the company's status and each person's certification be current?
    Where the answer comes from
    Your document. CREST International's membership FAQs say membership lasts for 12 months and is renewed annually; CREST ANZ says ABPT accreditations remain valid for 18 months from the date of completion.
    What to check, answer or record
    The date the issuer names (closing date, contract date or each day of the testing window), and the date you checked each status.
    What it does not settle, and who decides
    Status after the day you checked. Check again close to the date that matters.
    Limits of this row
    Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
  18. E8. Did the clause come from someone else?
    Wording, question or field
    Was the clause set by another party, such as a customer, a head contractor or a panel, and has that party been asked about equivalence?
    Where the answer comes from
    The contract, policy or panel rule the clause came from.
    What to check, answer or record
    Who set the clause, whether they were asked, their answer in writing and its date.
    What it does not settle, and who decides
    What your contract requires of you. Ask your own adviser.
    Limits of this row
    Record-only row: the issuer gives the answer and you write it down; no test request goes to any system.
  19. S1. The requirement, who asked and by when
    Wording, question or field
    The CREST clause copied exactly, and the people and dates around it.
    Where the answer comes from
    Your tender, contract or customer policy, read with rows D1 to D10, and any answers from E1 to E8.
    What to check, answer or record
    Document name and clause number; the exact words; the body named; the discipline; the people clause; the evidence due and when; the issuer or customer and their contact; the date the report or evidence is due; and any equivalence answers with their dates.
    What it does not settle, and who decides
    Whether a provider meets the clause. The issuer decides, from the provider's evidence.
    Limits of this row
    Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
  20. S2. What is to be tested, and where
    Wording, question or field
    Targets and environment.
    Where the answer comes from
    Your own list of systems and your hosting setup.
    What to check, answer or record
    Every domain, subdomain and API address that is in scope; what the application does and who signs in to it; the build or version; anything at those addresses that must be left alone; and whether a staging copy that matches production exists, with its address. If production is the target, the agreed testing windows and how test data is removed afterwards.
    What it does not settle, and who decides
    Systems not listed here. They are out of scope, and the report should say so.
    Limits of this row
    Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
  21. S3. Ownership and written permission
    Wording, question or field
    Who owns each target, and the permission you hold to have it tested.
    Where the answer comes from
    Your contracts, and your hosting provider's testing policy.
    What to check, answer or record
    The owner of each target and who will sign the authorisation; for any target you do not own, the written permission you hold; and the hosting provider's testing policy as you read it, with the date.
    What it does not settle, and who decides
    Permission you do not hold. A target without it stays out of scope until the permission is in writing.
    Limits of this row
    Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
  22. S4. Services another business runs
    Wording, question or field
    Payment pages, booking engines, hosted forms, learning or practice management platforms and similar services the application uses.
    Where the answer comes from
    Each vendor's own terms, and its written reply where they are silent.
    What to check, answer or record
    For each service: what its terms say about testing, the question you sent the vendor where the terms are silent, the vendor's reply and its date, and anything listed as excluded.
    What it does not settle, and who decides
    What a vendor permits. Its own terms and its written reply decide; anything not permitted stays excluded.
    Limits of this row
    Record-only row: it reads vendor terms and replies, and no test request goes to the vendor's systems or yours.
  23. S5. Roles, test accounts and test records
    Wording, question or field
    The roles in scope and the accounts created for the test.
    Where the answer comes from
    Your application's roles, and the number of accounts the provider asks for.
    What to check, answer or record
    Each role in scope; the test accounts for each, with accounts in two customer organisations if the application serves more than one; the invented records each account holds; and the address or number any email or text from those accounts goes to, which your business controls. Keep passwords out of this sheet and send them to the provider separately.
    What it does not settle, and who decides
    Accounts the provider needs beyond these. It asks, and you add them here.
    Limits of this row
    Record-only row: it lists the accounts your business sets up for the test on your own application, on the staging copy in S2 where one exists. They hold invented records only, never a real customer's, patient's, client's, student's, tenant's or guest's. Passwords, keys, tokens and shareable links that open an account or a file for anyone who has them stay out of this sheet.
  24. S6. Depth and discipline
    Wording, question or field
    How far the test goes, and the discipline your document names.
    Where the answer comes from
    Your document and your own decision. The methodology guide in this library explains unauthenticated, authenticated and code-assisted testing.
    What to check, answer or record
    The depth (unauthenticated, authenticated or code-assisted), the roles each depth covers, and the CREST discipline the document names, such as Penetration Testing or Vulnerability Assessment.
    What it does not settle, and who decides
    Whether that depth is enough for whoever will rely on the report. They decide.
    Limits of this row
    Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
  25. S7. Conduct limits and exclusions
    Wording, question or field
    The rules the provider works to, written into your request.
    Where the answer comes from
    Your own rules for testing, agreed in writing before testing starts.
    What to check, answer or record
    Testing only against the targets in S2, on the staging copy listed there where one exists, with the permission in S3. No load testing, volumetric testing or denial-of-service attempts. Destructive actions off by default for real people's accounts and records that existed before the test; reset, lockout and deletion checks only on test accounts and test records where the rules of engagement allow them. Evidence and the report leave out passwords, keys, tokens and shareable links that open an account or a file for anyone who has them. If testing shows a real person's data, the provider stops, records the address and the time, opens nothing further and tells the contact in S8.
    What it does not settle, and who decides
    Anything the rules of engagement leave unstated. Settle it in writing before testing starts.
    Limits of this row
    Record-only row: it states limits for the provider, and no test request goes to any system.
  26. S8. Contacts, evidence handling and what comes back
    Wording, question or field
    Who the provider talks to, where evidence goes, and what you need at the end.
    Where the answer comes from
    Your own people, and your document's evidence clause. Under Penetration Testing and / or Red Teaming, CREST International's procurement guide says to request evidence of methodologies, reporting standards and retesting processes.
    What to check, answer or record
    The technical contact during testing who can pause it; the person responsible for privacy questions and incidents; where test evidence may be stored and who may read the report; and what you need back: the report, the retest result, the provider's accreditation evidence and its testers' certification evidence as your document asks, and a statement of whether the provider built, hosts or maintains the system.
    What it does not settle, and who decides
    Whether the report satisfies the issuer. The issuer decides.
    Limits of this row
    Record-only row: it writes down your own decisions and documents, and no test request goes to any system.
  27. S9. Provider status check
    Wording, question or field
    The provider's status, checked with the body your document names.
    Where the answer comes from
    CREST International's Marketplace or CREST ANZ's Approved Companies page, as row D6 decides.
    What to check, answer or record
    The provider's name, the body, the status and discipline shown, the date checked and who checked it; the evidence received for each tester; and, if you are a supplier rather than the issuer, the date you sent this record to the issuer.
    What it does not settle, and who decides
    Status after the day you checked. Each body keeps its own list.
    Limits of this row
    Read-only row: it reads a body's public list, and no test request goes to any system.

CREST penetration testing: what the word CREST in a tender can point to

A request for tender, a panel application or a customer contract can say that penetration testing has to be done by a CREST member company, by CREST-certified testers, or by an equivalent.

For the business that has to buy that test, those words decide which providers it can engage, what evidence goes in with a submission and what the provider has to hand over. This guide is written for whoever holds such a document, whether that is the owner, a manager or the technical lead.

It explains what CREST pen testing wording can refer to, using the pages of CREST International and CREST ANZ as read on 15 November 2026.

Start by telling the two bodies apart. CREST International's Australasia page says the formal relationship between it and CREST ANZ ended at the end of April 2019. Each body publishes its own names for what it grants to companies and to people. A document that says only "CREST" may not say which body it means, and row D6 of the decoder in this guide deals with that question.

Clever Ops is not CREST accredited. It does not hold any other security accreditation or certification either. When your documents require CREST, we point you to an accredited provider for that work, and the scope sheet on this page is written so you can brief that provider well.

Nothing on this page is a way to satisfy a CREST requirement without such a provider, and nothing here is legal or procurement advice: whether a provider meets your document is decided by whoever issued it.

CREST International and CREST ANZ: who each body is, in its own words

CREST International describes itself as an international not-for-profit, membership body representing the global cyber security industry.

Its pages call it CREST, CREST International or CREST (International), and the footer of its website, crest-approved.org, describes CREST (International) as a not for profit company registered in the UK with company number 09805375. It says it has a presence in all regions of the world, overseen by a geographically representative International Council and supported by regional councils in the Americas, Asia, Australasia, EMEA and the UK. Its Australasia page says CREST Australasia is represented and managed by the Australasia Council.

CREST ANZ is CREST Australia New Zealand Ltd, the company its website at crestaustralia.org names in its footer with ACN 155 713 447. Its history page describes CREST ANZ as Australia's sovereign, not-for-profit cyber security accreditation body.

The same page says CREST (Aust) Limited was registered as an Australian not-for-profit public company on 15 February 2012, and that on 18 January 2016 CREST (Aust) Limited changed its registered company name to CREST Australia New Zealand Ltd.

It also calls the organisation established in 2012 CREST Australia. A document that names "CREST Australia" therefore deserves a second look before anyone assumes which body it means.

CREST International's pages also speak about CREST ANZ. Its Australasia page says the formal relationship between CREST International and CREST ANZ ended at the end of April 2019, that CREST ANZ have no rights to the CREST International suite of company accreditations or individual certifications, and that CREST ANZ has not adopted CREST International's Accreditation Standards and therefore CREST ANZ membership alone is not recognised by CREST International as being equivalent.

Its procurement guide for Australia and New Zealand adds that CREST ANZ operates as a separate organisation and does not deliver CREST (International) accreditation or certification frameworks.

The CREST ANZ pages cited here describe CREST ANZ in its own terms and do not comment on those statements. This guide takes no view on the relationship beyond what each body says about itself and, in CREST International's case, about what it recognises.

What CREST ANZ approves and accredits

CREST ANZ uses its own names. Its Approved Companies page provides a list of organisations who have satisfied the CREST Australia New Zealand requirements to become CREST Approved, and says CREST ANZ Approved Member Companies have subjected themselves to audit and scrutiny by CREST ANZ and have signed up to the CREST ANZ Code of Conduct. Its Company Accreditation Standards page names the company scheme CREST ANZ Approved Company Member Accreditation.

Its membership application page says that to become a CREST ANZ Approved Company, an organisation must provide services and products to or in the cyber and information security industry in Australia or New Zealand, and meet the criteria determined by the Board of CREST ANZ Ltd from time to time.

Those criteria include ascribing to the CREST ANZ Ltd Constitution, completing a membership application form with supporting documentation, consenting to be bound by the CREST ANZ Code of Conduct, and a regular audit of policies and procedures relating to security testing.

For individual testers, CREST ANZ runs the Accredited Best of Breed Penetration Tester (ABPT) program. Its home page says the program accredits individual penetration testers, employees and contractors alike, against Technical Competency, Professional Competency and Trust Standards developed and defined by CREST ANZ members, and that it is open to individual penetration testers from both member and non-member companies. Its accreditation process page says ABPT accreditations remain valid for 18 months from the date of completion.

What CREST International accredits, and the Pathway stages that come before it

CREST International's accreditation is for organisations.

Its Accreditation page says CREST Accreditation is awarded to organisations that evidence compliance with CREST Accreditation Standards through an application, evidence submission and review, that CREST-accredited companies must undergo periodic reassessment to ensure continued compliance with best practices and CREST's Accreditation Standards, and that its accreditation disciplines include Penetration Testing and Vulnerability Assessment.

Its membership FAQs say companies can hold multiple CREST accreditations under a single membership, and that each accreditation remains subject to its own application and assessment process. So check which discipline a provider is accredited in, not only that its name appears on a list.

CREST International also lists organisations at stages before accreditation. Its Accreditation Pathway page says the pathway has three stages, which can be followed in order or combined depending on the organisation's maturity:

  • Pathway:a registration process and sign-up to the CREST Code of Conduct. The organisation is given a Pathway logo and listed on CREST's website with other Pathway companies, and the page says it is important that the organisation presents itself only as Pathway and not as a CREST-accredited Member.
  • Pathway+:a self-assessment against the CREST organisational standards and at least one cyber discipline standard, which the organisation attests to and submits. The page says CREST will not independently review the results at this stage, and that it remains important that a Pathway+ organisation presents itself only as Pathway+ and not as a CREST Accredited Member.
  • CREST Member:the formal application and awarding of CREST Accreditation and Membership. The organisation submits a detailed Accreditation application for independent review with supporting evidence, including the formal registration of the employees delivering services on its behalf to demonstrate they are suitably competent and qualified.

Status has a list and a date

A Pathway or Pathway+ listing is a different status from a CREST-accredited Member on CREST International's own terms, so match the provider's status to the exact words of your document. CREST International's procurement guide says its Marketplace enables buyers to search for accredited Member companies by service, capability and region. Use it to check a provider named in a submission against CREST International's own listing.

The membership FAQs say membership lasts for 12 months and is renewed annually, and that accreditations are included in the annual renewal, including periodic reassessment to ensure continued compliance with CREST's standards. A document that asks for a current member is asking about a particular date: the closing date, the contract date or the testing window, whichever the issuer sets. Record the date you checked.

The accreditation standards themselves

CREST International publishes accreditation standards: an organisational standard, CREST Accreditation Standard - Company General Requirements (including Responsible AI Use), and service-specific standards that include Penetration Testing and Vulnerability Assessment. Its standards page says that to download them you complete a short form, and the standards are then emailed to you.

This guide did not do that, so it says nothing about what the standards contain. If you need their text, obtain it from CREST International.

What "CREST certified penetration testing" can mean: certifications held by people

CREST International's recommended tender wording asks for "evidence of company accreditation and individual certifications".

In CREST International's usage, then, a company is accredited and a person holds a certification. CREST ANZ's pages use their own words: they name its company scheme CREST ANZ Approved Company Member Accreditation and its program for individual testers the Accredited Best of Breed Penetration Tester.

The word accredited can therefore point at a company or at a person, depending on the body. CREST International's exams page says its professional examinations are broken down into three levels: Practitioner, Registered and Certified. The examinations its certifications page lists under Penetration Testing are CREST Practitioner Security Analyst (CPSA), CREST Registered Penetration Tester (CRT), CREST Certified Tester - Infrastructure (CCT INF), CREST Certified Tester - Application (CCT APP), CREST Certified Red Team Specialist (CCRTS) and CREST Certified Red Team Manager (CCRTM).

The word certified does double duty. It is the ordinary word a document uses for any CREST certification, and Certified is also the name of the level that CREST's exams page says is designed to set the benchmark for senior professionals. A clause that asks for "CREST certified penetration testers" may mean any CREST certification or the Certified level in particular. Ask the issuer which, and record the answer.

CREST International's standards page says there is no mandatory requirement for individuals to be CREST qualified for a company to achieve accreditation, and that individuals are instead assessed based on their skills and experience or any qualifications they may hold.

So the people an accredited company sends may or may not hold CREST certifications. A document that asks for both an accredited company and certified people needs both checked, each against its own evidence.

CREST International also runs an equivalency programme of its own. Its Certification Equivalency Recognition Programme page says that, in partnership with OffSec, CREST recognises the OffSec OSCP and OSCP+ certification as meeting key requirements toward the CREST Registered Tester (CRT) qualification, under certain conditions, and that CRT equivalency will only be granted if the candidate has passed the OSCP or OSCP+ within the last three years of their application date and holds a valid pass in the CREST Practitioner Security Analyst (CPSA) qualification.

That is CREST's recognition inside its own certification framework. It does not decide what an "or equivalent" in your document accepts.

Reading a CREST clause line by line

CREST International's procurement guide for Australia and New Zealand, which carries a 2026 copyright notice, recommends wording for a request for tender (RFT) or request for proposal (RFP).

A document you hold may copy it, adapt it or use words of its own, so read yours against it rather than assuming. The recommended wording, sentence by sentence, is:

  • "The supplier must be a current CREST (International) Member company for the relevant services (red team testing, penetration testing, threat intelligence, incident response, or security operations centre)."
  • "All personnel engaged in delivering the services should hold appropriate CREST professional certifications or equivalent."
  • "Evidence of company accreditation and individual certifications must be provided with the tender submission."
  • "Submissions that do not meet these requirements may be deemed noncompliant."

What each sentence turns on

The first sentence is about the company. It names a body (CREST International, not CREST ANZ), a status (a current Member company) and a scope (the relevant services). It is answered by the provider's membership and by the accreditation it holds for the service you are buying, as at the date your document sets.

The second sentence is about people. It says should rather than must, it does not say which certification is appropriate, and it is the only sentence in the recommended wording that allows an equivalent. If your document keeps those words, the issuer decides what appropriate and equivalent mean for it.

The third sentence moves the check to the submission: the provider supplies evidence of its accreditation and of its people's certifications, and the issuer reads it. The fourth says that submissions that do not meet the requirements "may be deemed noncompliant". What happens to a submission with a gap is for the issuer to decide under its own evaluation process.

Among the questions the same guide's checklist says organisations should ask are whether the organisation is a current CREST (International) Member for the relevant service(s), and whether it can demonstrate that personnel hold current CREST (International) certifications or equivalent. Under Penetration Testing and / or Red Teaming, it also says to request evidence of methodologies, reporting standards and retesting processes.

The guide states CREST International's own recommendation as well: that, when procuring cyber security services, organisations should explicitly require providers to be CREST (International) Member companies and ensure that services are delivered by CREST (International) certified professionals.

That is the body's recommendation about its own scheme. Whether to require CREST at all, and which body, is the issuer's decision.

When your document allows an equivalent

A document may add "or equivalent" to a CREST clause.

Whether a provider, an approval or a certification is equivalent is the issuer's decision, made under its own procurement rules, and this guide does not say that anything is equivalent to anything else. The bodies' own statements bear on that decision, and none of them makes it for you.

CREST International says CREST ANZ membership alone is not recognised by CREST International as being equivalent; that is its position on what it recognises. CREST International also recognises the OffSec OSCP and OSCP+ certification as meeting key requirements toward its CRT qualification under the conditions its equivalency page sets; that is a recognition inside its own framework, not a ruling on your document.

If you issued the document, settle the question before you read any submission, and write the answer down. If you received it, for example as a supplier whose customer contract asks for testing by a CREST member company, put the question to the customer in writing before you engage anyone, and take your customer agreement to your own adviser.

Part E of the asset lists the questions in order. If the answer is no, or no answer comes, read the clause as it is written, and engage a provider that holds what the clause names.

What a CREST requirement settles, and what your scope still has to say

The wording CREST International recommends is about who does the work: the company and its people.

The pages cited in this guide describe how CREST International accredits organisations and examines people, and how CREST ANZ approves companies and accredits individual testers. None of them sets out what one particular test of your application will cover. That comes from your scope: which addresses, which roles and accounts, which environment, what is excluded, how evidence is handled and what you receive at the end.

So an accredited provider still needs a written brief, and Part S of the asset is that brief: your record of what you want tested, on systems you own or hold written permission to test, in a form you can send with a request for quotation.

The methodology guide in this library explains unauthenticated, authenticated and code-assisted testing, and the website security audit guide explains what a review from outside the login can and cannot see. Either helps you decide what to ask for before you write the scope.

The scope sheet also gives the provider its conduct limits in writing. The targets are systems you own or hold written permission to have tested, using the staging copy where you have one, and the test accounts hold only invented records, none of them a real customer's.

Destructive actions are off by default for real people's accounts and records that existed before the test, and reset, lockout and deletion checks run only on test accounts and test records where the rules of engagement allow them.

Email and text messages from the test accounts land in inboxes and phones your business runs. If testing shows a real person's data, the sheet asks the provider to stop, make a note of where and when it appeared, and tell your contact.

Passwords, keys, tokens and shareable links that open an account or a file for anyone who has them stay out of the sheet, the evidence and the report.

A payment page, booking engine, hosted form or other service another business runs for you can be included only to the extent its own terms permit. Read those terms, and where they say nothing about testing, ask the vendor in writing; anything the terms or the vendor's reply do not allow goes on the excluded list.

How to use the decoder, the equivalence questions and the scope sheet

The asset on this page is a single table with three parts.

Rows D1 to D10 decode wording you may find in a tender, panel document, contract or questionnaire. Rows E1 to E8 are equivalence questions for the issuer to answer. Rows S1 to S9 are the scope sheet: your own record of what you want tested, ready to send to a provider that holds what your document names.

  • Copy the table into a spreadsheet. Paste the exact clause from your document beside the D row it matches. Where no row matches, ask the issuer what the words mean before you go further.
  • Check a provider's status with the body your document names: CREST International's Marketplace for its accredited Member companies, or CREST ANZ's Approved Companies page. A logo on a proposal is the provider's own statement, and the body's list is the body's.
  • If your document allows an equivalent, take E1 to E8 to whoever issued it, and record each answer with who gave it and when.
  • Fill in S1 to S9 for systems you own or hold written permission to test, and send the sheet with your request for quotation. Keep passwords for the test accounts out of the sheet and send them to the provider separately.
  • Every row reads documents or records decisions, and no row tests anything: none sends a test request to a website or application, signs in to one or submits a form in one. The testing itself is for the provider you engage, under the scope and authorisation the sheet records.
  • Keep the completed sheet with the report. It shows what was asked for, by whom, and which provider status was checked on which day.

Who decides whether a provider meets the clause

Each decision has an owner, and none of them is the tester.

The issuer of the document decides what its words mean, whether an equivalent is acceptable and whether a submission complies, under its own procurement rules. Where a CREST clause reaches you through someone else's contract, such as a head contract or a customer's supplier policy, put the question of what it accepts to the party that set it, and take the agreement itself to your own adviser.

CREST International and CREST ANZ each award their own statuses, and each publishes a list of companies: CREST International's Marketplace and CREST ANZ's Approved Companies page.

A provider's statement of its status is where the check starts, and the body's list, read on a recorded date, is where it ends.

A document may name a different scheme beside CREST. IRAP is one: ASD calls it the Infosec Registered Assessors Program (IRAP), and describes IRAP Assessors as ASD-endorsed ICT professionals from across Australia who have the necessary experience and qualifications in ICT security assessment and risk management, and a detailed knowledge of ASD's Information Security Manual.

A CREST clause and an IRAP clause are separate requirements, and each is checked against its own body.

Where Clever Ops fits, and where the work goes elsewhere

Clever Ops tests what people reach in a browser or through an API.

A website security check reviews only what can be seen before anyone signs in. A WordPress security audit is for WordPress sites and WooCommerce stores. A web application and API penetration test goes inside a custom application, signed in under each role.

Apps made with AI builders get a vibe-coded app security check; chatbots and agents get an AI chatbot and agent security test. Whichever one fits, the report is evidence for the issuer or customer to weigh, not a certificate.

Clever Ops is not CREST accredited. It is not an IRAP assessor either, and no other scheme has certified or accredited it. When a tender, contract or customer requires a CREST-accredited provider, engage one: we refer that work on, and the scope sheet above is written for briefing the provider you choose.

A document that requires a CREST ANZ approved company or ABPT-accredited testers is handled the same way, with a referral to a provider holding exactly what the document names.

An "or equivalent" in your document does not change this, and nothing on this page presents Clever Ops as an equivalent of an accredited provider.

If a document asks for a penetration test and names no scheme, its exact words are where the scoping call starts, and the call confirms whether a Clever Ops service fits. Where the application was built or is hosted by Clever Ops, what we do is a security review, and its report says plainly which business built the application and which hosts it.

If your document asks for an independent test, give that work to a provider with no hand in building or running the system. Phishing, red teaming, physical testing and tests of internal networks, Active Directory or staff devices go to a specialist in network or red team work.

Load testing, volumetric testing and denial-of-service simulation fall outside every Clever Ops service, and none of those services tests a vendor's own product or platform.

Frequently asked questions

Not on CREST International's account. Its Australasia page says the formal relationship between CREST International and CREST ANZ ended at the end of April 2019, and its procurement guide for Australia and New Zealand says CREST ANZ operates as a separate organisation and does not deliver CREST (International) accreditation or certification frameworks. CREST ANZ is CREST Australia New Zealand Ltd, which describes itself on its own site as Australia's sovereign, not-for-profit cyber security accreditation body. If your document says only CREST, ask the issuer which body it means.

In CREST International's usage, accreditation is awarded to organisations that evidence compliance with CREST Accreditation Standards through an application, evidence submission and review. Certifications belong to individuals: its certifications page lists the examinations, and its exams page says its professional examinations are broken down into three levels: Practitioner, Registered and Certified. Its standards page says there is no mandatory requirement for individuals to be CREST qualified for a company to achieve accreditation. A document that asks for an accredited company and certified testers is asking separate questions, and each needs its own evidence.

CREST International's Accreditation Pathway page says its third stage, CREST Member, represents the formal application and awarding of CREST Accreditation and Membership. It says Pathway and Pathway+ organisations are given a Pathway or Pathway+ logo and listed on its website, and that it is important that each presents itself only as Pathway or Pathway+ and not as a CREST-accredited Member. It also says CREST will not independently review the Pathway+ self-assessment results at that stage. Check which list a provider is on against the exact words of your document.

The issuer of the tender, under its own procurement rules, and this guide does not say that any provider, approval or certification is equivalent. In CREST International's own recommended tender wording, "or equivalent" appears in the sentence about personnel certifications and not in the sentence about the company. CREST International also says CREST ANZ membership alone is not recognised by CREST International as being equivalent. Neither point decides what your tender accepts. Part E of the asset lists the questions to put to the issuer, and to record, before any submission is read.

No. Clever Ops is not CREST accredited. When a tender or contract requires CREST, we point you to an accredited provider, and this guide's scope sheet is there to brief them. If a document asks for a penetration test and names no scheme at all, the scoping call starts from its exact words and confirms whether a Clever Ops service fits.

CREST International's membership FAQs say membership lasts for 12 months and is renewed annually, and that accreditations are included in the annual renewal, including periodic reassessment to ensure continued compliance with its standards. CREST ANZ's accreditation process page says ABPT accreditations remain valid for 18 months from the date of completion. A document that asks for current status is asking about the date it sets, so check close to that date and record when you checked.

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.