On this pageWhat White Label Testing MeansDelivery Models for PartnersWho Does WhatWhat the Client SeesScope and Authorization Per ClientRecords for Each ClientPackaging Testing With MonitoringTesting in the Service CatalogPreparing the Partner's TeamIntroducing Testing to an Existing ClientA Finding in the Service DeskPresenting Findings in a Client ReviewWhere an Independent Test FitsChoosing a White Label ProviderWhite Label Testing With ThreatDefenceFrequently Asked Questions An MSP or MSSP holds the client relationship, and a specialist provider supplies the testing behind it. The brand changes hands, while the authorization to test still comes from each client whose systems are tested. This guide covers the delivery models open to a partner, who does what between partner and provider, what the client sees, and scope and authorization for each client. It then follows the service into the partner’s practice, from the catalog entry and the team behind it to the first client conversation, a finding in the service desk and the client review. What White Label Testing MeansWhite label testing means a partner sells and presents a penetration test that a provider performs. The same arrangement is called white label pentesting. A pentest reseller is a related role: a partner that sells a testing firm’s engagements, with or without its own brand on them. The label describes how the service is branded and delivered, and the test itself follows the same method as any other penetration test. Client: The organization that owns the systems and authorizes the test. Partner: The MSP or MSSP that holds the client relationship, presents the service under its own name and usually helps with the fix. Provider: The company that runs the tests, confirms the findings and keeps the evidence. The testing behind the label may be led by human testers working to a schedule, or by software agents working continuously. The guide to AI penetration testing explains how the agentic form works and where a person still leads. Delivery Models for PartnersA partner can add testing to its catalog by referring clients to a testing firm, by reselling that firm’s project tests, or by delivering a continuous service under its own brand. The models differ in who the client deals with and in how much of the work passes through the partner. Area Refer Resell project tests Deliver a continuous service Who the client deals with The testing firm, after an introduction The partner, with the testing firm behind it The partner Brand on the findings The testing firm’s The partner’s, or both names The partner’s When tests run When the client commissions one On dates agreed for each project Through the year, as the client’s systems change Partner’s part The introduction, and help with fixes afterwards Scheduling, scope, presenting the report and fixes Onboarding, scope for each client, reviewing findings and fixes Typically suits A client that needs an occasional independent test A client with a periodic testing requirement A client whose exposed systems change through the year Referral keeps the partner outside the test, and a resold project typically reaches the partner as a finished report. A continuous service makes testing part of what the partner delivers every month, with findings arriving as they are confirmed. What starts a test in the continuous model, and how often standards expect one, is set out under continuous penetration testing. In most practices the models run together, with referral kept for the work a continuous service leaves to a human tester. Who Does WhatThe partner owns the client relationship and the route to a fix, and the provider owns the test and its evidence. The split is worth writing down, since a second company works behind the first. Joint guidance from CISA, the NSA, the FBI and partner agencies in the United Kingdom, Australia, Canada and New Zealand, Protecting Against Cyber Threats to Managed Service Providers and their Customers, recommends that an MSP clearly explains the services a customer is purchasing, and that customers thoroughly understand the security services their MSP provides. Activity Partner Provider Scope and authorization Collects each client’s confirmed targets and signed authorization. Checks the targets, loads them into that client’s test policy and tests nothing else. Running the tests Tells its own monitoring team where test traffic will come from. Runs the tests inside the agreed limits and keeps the record. Confirming findings Reads each significant finding before it reaches the client. Confirms each weakness with proof before reporting it. Fixing Fixes the systems it manages and coordinates with the client’s own IT team for the rest. Supplies fix steps and answers technical questions. Retesting Reports that the fix is in place. Repeats the original test and records the outcome. Decisions on what to fix stay with the client. The NCSC’s guidance on penetration testing states that risk assessment and decisions on applying fixes are the commissioning organization’s responsibility, and that this work should not be wholly outsourced to the test team. What the Client SeesThe client sees the partner’s brand on every surface of the service. Portal: Findings, their status and their history sit in a portal that carries the partner’s name and sign-in address. Findings: Each finding names the affected system, shows the proof, gives a severity and sets out the fix. Notifications: Messages about new findings arrive from the partner, by email or through the partner’s ticketing system. Reports: Periodic summaries carry the partner’s branding and suit a service review meeting. Retest results: The client can see that a reported fix was tested again and whether the finding closed. The agreement behind these surfaces, with its scope, retests and reporting, is described in the guide to penetration testing as a service. White label covers the brand, and the provider’s involvement is typically disclosed. NIST SP 800-115 says an assessment plan should answer who is authorized to conduct the assessment, and its rules of engagement template identifies the organization engaged to conduct the testing. Scope and Authorization Per ClientEach client authorizes testing of its own systems in writing, and the provider holds each client’s scope separately. The general practice, including rules of engagement and consent from third parties that host a system, is covered in the penetration testing guide. The steps below are the ones a partner adds. Confirm ownership. The client confirms the domains and addresses that belong to it. Authority to approve a test sits with the system owner, including for systems the partner manages day to day. Separate the partner’s own platforms. A hosting platform or remote access gateway that serves several clients usually belongs to the partner, and NIST treats a system shared by several organizations as a case where all parties sign. Set exclusions and limits. The client names the systems to leave alone, the permitted methods, the request rates and any time windows. Name the testing party. The signed authorization identifies the provider as well as the partner, so the client approves the company that will send the traffic. Enforce the scope technically. The provider loads the scope into a test policy for that client alone, so a test for one client cannot reach another client’s hosts. Review on change. A new domain, an acquisition or a move to a new host reopens the scope, and the client confirms the addition before it is tested. Records for Each ClientA partner should be able to produce, for each client, the records showing that a test was authorized, stayed in scope and led to a fix. Client record What it proves Where it is kept Signed authorization Who approved which targets, methods and hours, and which company runs the test. Copies with the client, the partner and the provider. Ownership of each target That every domain and address in scope belongs to the client, or that its host has consented. The client’s domain registration and DNS records, the cloud or hosting account behind each address, and any written consent from a host. Client test policy The scope, exclusions, rate cap and time windows as configured for that client. The provider’s console, under that client’s tenant. Test traffic That requests seen in the client’s logs came from the provider. The provider’s list of source addresses, set against the client’s firewall and web server logs. Finding record The request and response that prove the weakness, the severity and the fix steps. The branded portal, and the matching ticket in the partner’s service desk. Retest result That the fix held when the same test ran again. The history of the finding in the portal. Data handling What test data was collected, where it is stored and when it is destroyed. The provider’s data handling statement, which NIST SP 800-115 section 7.4 gives a structure for. Where the partner also monitors the client, its SOC should find the test traffic in the client’s own logs. That comparison checks the provider’s record against an independent one. Packaging Testing With MonitoringTesting fits most naturally beside the monitoring a partner already delivers, because each service gives the other something to act on. Outside view first: Attack surface discovery and external testing start from a client’s domains, so they can begin before any log source is connected. Findings into monitoring: A confirmed weakness tells the SOC where to look. Logs can be searched for earlier use, and monitoring can be tightened around the system until the fix is in place. Monitoring into testing: A new host, a leaked credential or a newly published flaw in a product the client exposes is a reason to test now, ahead of the schedule. Scanning and testing together: A scanner lists possible weaknesses and a test confirms which can be used, as the guide to penetration testing vs vulnerability scanning sets out. Testing in the Service CatalogIn a service catalog, testing typically appears inside a managed security package or as an addition to one. The entry reads best in the terms the partner already uses for monitoring and patching: what is covered, what starts the work and what the client is asked to provide. What is tested: The entry names the kinds of system covered, such as internet-facing hosts, remote access services, web applications and sign-in pages, and ties them to the client’s confirmed domains. What starts a test: The entry says whether tests run on a schedule, on change or both, and how a client asks for one ahead of a release. What the client receives: The entry lists findings with proof and fix steps, a retest after each fix and a summary for each service review. What the client provides: The entry asks for a signed authorization, a confirmed list of targets and a named contact who can approve a change of scope. Referred work: The entry states which testing the partner refers to an independent firm, so the client reads the boundary before it asks. The joint advisory on MSPs asks a provider to explain the services a customer is not purchasing as well as the ones it is. A catalog entry that names its boundary does that in writing. The same entry is delivered differently depending on who runs the client’s IT. Client with no IT staff: The partner manages every system, so it collects the authorization from an owner or director, fixes each finding itself and reports in plain language. Client with an internal IT team: Findings are routed by system owner, with the client’s team fixing what it runs and the partner fixing what it manages, both working from the same record. Client under a formal testing requirement: The branded service runs between the independent tests the requirement calls for, and the client’s assessor decides what weight its records carry. Preparing the Partner's TeamThe partner’s team needs to know how the service behaves, since the testing skill itself sits with the provider. NIST SP 800-115 notes that an assessment team benefits from a member with strong technical writing skills who can convey results to less technical readers, and in a white label service that part falls to the partner. Role at the partner What the role needs to know Where it is used Account manager What is tested, what starts a test and which testing is referred elsewhere. Client conversations and service reviews. Service desk How a finding arrives as a ticket, which queue takes it and who owns the affected system. Triage of each new finding. Engineers How to read the proof in a finding, apply the fix through the normal change process and report it for retest. Remediation. SOC or NOC analysts The provider’s source addresses, each client’s test windows and how to tell test traffic from other activity. Alert handling while tests run. Service manager Which clients hold a current authorization and when a scope is due for review. Onboarding and periodic scope checks. An alert raised during a test window is handled as any other alert until its source address and time match the provider’s record. NIST advises that when a real adversary is found during an assessment, assessors stop assessing the systems involved while the organization carries out its response, so the partner’s analysts should know how to ask the provider for that pause. Most partners learn the service by running it on their own estate first. The joint advisory on MSPs gives a second reason: its authoring agencies expect malicious actors to step up their targeting of MSPs in order to exploit the trust relationships between providers and their customers. Scope the partner’s own domains. Remote management tools, client portals, support sites and remote access gateways go in first, since they connect to every client. Sign the authorization as a client would. An owner or director approves the targets, limits and hours on the same form later asked of each client. Route findings through the service desk. The team sees how a finding arrives, who picks it up and how its status stays current. Fix and request the retest. Engineers practice the full cycle on systems they know well. Check the SOC’s view. Analysts confirm that test traffic appears in the partner’s own logs and matches the provider’s source addresses. Keep the record. The partner’s own findings and retests, with sensitive detail removed, become a worked sample for client conversations. Introducing Testing to an Existing ClientTesting is easiest to introduce at a moment when the client already has a reason to ask how exposed it is. The conversation starts from the client’s own systems, and the service is presented as an extension of work the partner already does. A service review: The regular review is a natural place to raise testing, alongside patching and monitoring results. A change project: A new website, a cloud migration or a change to remote access puts new systems on the internet. A security questionnaire: A cyber insurance form or a customer’s supplier questionnaire may ask whether the client’s systems are tested and how often. From there the partner brings the client into the service in stages. Show the outside view. The partner lists the client’s internet-facing domains, hosts and services, which may include systems set up by a past supplier or a former member of staff. Place testing beside existing reports. The client already receives patching and scan reports, and the partner explains that testing adds proof of what an outsider can do today. Agree a first scope. A small, clearly owned scope, such as the main website, mail and remote access, keeps the first authorization simple. Present the first findings in person. The first results are walked through in a call or meeting, so the client sees a finding, its proof and its fix before notifications begin to arrive on their own. Agree how findings will flow. The client names who receives notifications, which fixes the partner may apply without asking and which need the client’s decision. Widen the scope. Further domains and applications are added once a first cycle of finding, fix and retest has run. A client that already commissions an annual test keeps it, and the branded service is presented as the testing that happens between those tests. A Finding in the Service DeskA confirmed finding becomes a ticket in the partner’s service desk and follows the partner’s normal change process to a fix. The example below follows one finding for a client whose website is maintained by an outside web developer, while the partner manages the client’s network and devices. The provider confirms that a staging copy of the client’s website serves a backup file containing database credentials. The finding arrives. A ticket opens under the client’s name with the affected hostname, the severity, the proof and the fix steps. NIST advises that critical, high-impact vulnerabilities are reported to the responsible people as soon as they are discovered, so a significant finding arrives ahead of any periodic report. An engineer reads the proof. The engineer confirms from the recorded request and response that the file is reachable, and identifies who runs the host. The client is told. The account manager explains in plain terms what was exposed and what the fix involves, and the client decides to remove the staging site and change the credentials. The owner approves the change. NIST says the system owner should be contacted and should approve planned mitigation actions before they are implemented, so the client and the developer both agree the change. The fix is applied. The developer removes the file and the staging site, and the database password is changed. Earlier use is checked. Because the partner also monitors this client, its SOC searches the web server logs for earlier requests for the file. The retest runs. The partner marks the ticket as fixed and the provider repeats the original request. NIST notes that a retest verifies a fix only when it mirrors the original test. The cause is recorded. The ticket closes with a note on the cause, which is that test copies of the site were being published without review. NIST observes that a root cause can often be traced to a weakness at the level of a program, and it notes that recommendations may be nontechnical as well as technical, such as a change to a process. Here the partner and client agree that new sites are reported to the partner before they go live, which turns one finding into a standing change. Presenting Findings in a Client ReviewA client review presents findings as decisions and progress, for readers who run the business. NIST notes that a report may have several audiences and may need several formats, and the review version is the one written for management, with the items that need a decision first. Decisions needed. Open findings that need the client’s approval, budget or a third party’s action come first, each with an owner and a date. Closed since the last review. Each fixed finding is shown with its retest result, so the client sees that the fix was checked. Changes to the surface. New domains, hosts and services found since the last review are confirmed as the client’s and added to scope, or retired. Recurring causes. Findings that share a cause are grouped, and the partner proposes one change to the underlying process. Accepted risks. A finding the client chooses to leave open is recorded with the name of the person who accepted it and a date to revisit it. Work ahead. Planned releases, migrations and scope changes are noted, so tests can be requested ahead of them. Each finding is described by what an outsider could do and what that would reach, with the technical proof available on request. A count of findings says little on its own, since a higher number may reflect a growing surface as much as weaker systems. The NCSC advises giving special attention to vulnerabilities the organization did not previously know about, with the aim of identifying how such issues could be spotted in future. For a partner, a finding that its own patching or scanning service should have caught is a prompt to review that service as well as to fix the system. The NCSC also points out that the solutions testers propose may not be the only ones possible, and the review is where partner and client choose between them. Where an Independent Test FitsAn independent, human-led test keeps its place beside a white label service, particularly where the partner manages the systems being tested. NIST observes that engaging third parties offers an independent view that internal assessors may not be able to provide, and it advises organizations to be mindful of conflicts of interest, such as one individual conducting a formal assessment and being responsible for addressing its findings. A partner that built and runs a client’s environment is close to that position. Testing through a separate provider adds distance, and a fully independent firm adds more. Formal assurance: A client whose standard, regulator or customer asks for an independent test is referred to a firm with no part in running its systems. Human-led work: Business logic, social engineering, physical access and internal networks sit outside a service built on the external view. Choosing a White Label ProviderBefore the service is offered to a client, the partner needs the provider’s answers on the points below. Branding: Ask which surfaces carry the partner’s brand, including the portal, the sign-in address, reports and notifications, and whether the provider’s name appears on any of them. Client separation: Ask how one client’s scope, findings and data are kept apart from another’s, and whether the partner’s staff can work across all clients in one view. Who tests: Ask whether tests are run by people, by software agents or by both, and who reviews a finding before it reaches the client. Authorization: Ask how authorization is collected for each client and what happens to a target whose ownership cannot be confirmed. Partner tooling: Ask whether findings arrive in the partner’s own service desk and how status stays current in both places. Trial on the partner’s estate: Ask whether the partner can run the service against its own environment before offering it to clients. Client contact: Ask whether the provider ever contacts a client directly, and under what circumstances. White Label Testing With ThreatDefenceMSPs and MSSPs can deliver ThreatDefence agentic penetration testing under their own brand, beside the managed SOC for MSPs and MSSPs. Both belong to one platform: an AI SOC with a 24x7 SOC team behind it and automation across security monitoring, compliance and cyber risk management. Branding in the license: White-label branding is included, so the client portal, reports and notifications carry the partner’s brand. Partner email domain: Alerts can be sent from the partner’s own email domain. Scope per client: Scope and limits are set separately for each client. Shared cases: The partner works each finding with the ThreatDefence SOC in the same case. PSA integration: Integrations cover ConnectWise, Autotask, HaloPSA and ServiceNow. NFR license: An NFR license covers the partner’s own environment. Tests cover each client’s confirmed and authorized scope, higher-impact tests wait for approval, and SOC analysts review significant findings. Internal network testing, social engineering and formal attestation are work for an independent human-led firm, which the partner can refer. Frequently Asked QuestionsWhat is white label penetration testing?White label penetration testing is testing that a specialist provider performs and an MSP or MSSP delivers to its clients under its own brand. The partner holds the client relationship and presents the findings, while the provider runs the tests and keeps the evidence. Each client still authorizes the testing of its own systems.Is a pentest reseller the same as a white label partner?No. A pentest reseller typically sells a testing firm’s project engagements, sometimes with both names on the report. A white label partner presents the service as its own, with its brand on the portal, the reports and the notifications. The roles overlap, and a partner may resell project tests for some clients while delivering a continuous branded service to others.Does the client know another company runs the test?Yes, in most arrangements. The portal and reports carry the partner’s brand, but the authorization the client signs typically names the organization that conducts the testing. NIST’s rules of engagement template identifies the organization engaged to conduct the test, and a client may ask the same question as part of its supplier checks.Who authorizes a white label penetration test?The client authorizes it, as the owner of the systems. The partner collects the signed authorization and the confirmed list of targets, and the provider tests only what that document covers. A platform the partner hosts for several clients needs the partner’s own authorization as well.Can an MSP test systems it manages for a client?Yes, with the client’s written authorization. Management access to a system does not replace the owner’s approval to test it. Because the MSP also maintains those systems, NIST’s caution about conflicts of interest applies, and a client with a formal assurance requirement may still want a test from a fully independent party.Does an MSP need its own penetration testers to offer testing?No. In a white label arrangement the provider supplies the testing, whether through human testers or software agents. The partner needs people who can explain the service, collect scope and authorization from each client, read a finding and see the fix through, which a managed service team typically already does for its other services.Can white label testing start before a client is onboarded for monitoring?Yes. External testing starts from a client’s domains and a signed authorization, so it can begin before any log source is connected. A partner can use the outside view as a first engagement with a new client, then add monitoring so that confirmed weaknesses can be checked against the client’s logs.How should an MSP introduce penetration testing to an existing client?An MSP typically raises testing at a service review or alongside a change project, starting from a list of the client’s own internet-facing systems. A small first scope, such as the main website, mail and remote access, keeps the authorization simple. The first findings are presented in person, and the scope widens once a full cycle of finding, fix and retest has run.Should an MSP test its own environment before offering testing to clients?Yes, in most cases. Remote management tools, client portals and remote access gateways connect the MSP to every client, and joint guidance from CISA and partner agencies expects attackers to step up their targeting of MSPs to reach their customers. Running the service on its own estate first also shows the team how findings arrive, how fixes are retested and what test traffic looks like in its own logs.How are findings kept separate between an MSP's clients?Each client typically has its own scope, test policy and portal view, so a test for one client reaches only that client’s hosts, and its findings are visible only to that client and the partner. The partner’s staff usually work across all clients in one view. A provider should be able to show how the separation is enforced for reports, notifications and stored test data.