Run AD and Entra ID audit services across clients without rebuilding the workflow each time
EtcSec’s partner model is built for MSSPs, security consultancies, and channel operators that need recurring identity reviews across multiple customer environments. The core scope is the live product scope today: Active Directory and Microsoft Entra ID, backed by the ETC Collector evidence engine.
The goal is operational leverage, not a generic reseller badge. Multi-tenant management, white-label exports, client-facing reporting, revenue alignment, and dedicated onboarding matter because partner delivery breaks when every audit has to be repackaged manually.
Operate multiple customer environments from one partner workflow without flattening everything into a single local project folder or a pile of one-off reports.
Deliver identity audit output under your service wrapper when the client relationship depends on your brand, methodology, and remediation language.
Share the reporting layer with clients that want visibility while keeping collection, scheduling, and delivery under partner control.
The partner tier is designed for repeatable service delivery economics rather than isolated one-off engagements.
The MSSP workflow should stay repeatable from onboarding to recurring review
The value of the partner plan is not a bigger logo on a pricing card. It is the ability to onboard a customer, deploy the collector in the right operating mode, produce a branded review, and come back later with the same evidence model and remediation trail.
Dedicated CSM and onboarding path
Partner delivery usually fails in the first rollout, not the twentieth. A dedicated success contact matters when the service template, packaging, and client rollout need to be aligned early.
Recurring reviews instead of static snapshots
The partner value proposition improves when audits can be rerun after privilege changes, Conditional Access updates, M&A events, or remediation waves without rebuilding the process.
Local-first collection with central follow-up
The ETC Collector remains local to the customer environment while the partner workflow can still centralise visibility, reporting, and follow-up where appropriate.
Commercially usable packaging
White-label reporting, volume terms, and a clear partnership route help MSSPs sell a service, not just hand over a raw tool output.
What a partner-ready identity audit offer needs beyond a standard customer plan
MSSPs do not need another generic “contact us for volume” paragraph. They need a model that supports service packaging, repeated delivery, and customer-facing reporting without diluting the underlying audit evidence.
Multi-tenant delivery is the baseline, not an add-on
The partner plan is meant for operators managing multiple customer environments. That changes the requirements immediately: tenant separation, environment grouping, repeatable naming, and a workflow that does not assume one internal security team operating one domain.
On the commercial side, this is what allows an MSSP to build recurring AD and Entra ID review services instead of reselling access on a per-login basis.
White-label exports and client portal access solve different problems
White-label reports matter when the MSSP owns the customer relationship and wants the deliverable to look like part of its own service catalogue. Client portal access matters when customers want to review posture and remediation status directly without taking over collection operations.
A serious partner workflow needs both options because some customers want managed service delivery, while others want shared visibility with clear audit ownership.
Keep the partner promise aligned with the live product scope
| Area | Current position | Why it matters |
|---|---|---|
| Live audit scope | Active Directory and Microsoft Entra ID | Avoids selling providers that are not live today |
| Collection model | ETC Collector in standalone API or SaaS daemon mode | Matches client locality and managed-service needs |
| Deliverables | White-label exports, client portal, recurring review workflow | Explains what the partner actually delivers |
| Commercial path | Volume pricing and partnership contact | Makes the buying route explicit |
Where the partner plan fits best
- MSSPs packaging recurring AD and Entra ID posture reviews
- Identity consultancies that need a reusable assessment workflow instead of bespoke spreadsheets
- Channel partners building a managed identity hardening offer around reporting and remediation follow-up
- Teams that need commercial terms, white-label output, and a dedicated success contact
Partner FAQ
Who is the partner plan for?
It is for MSSPs, consultancies, and channel operators managing multiple customer environments and packaging identity audits as a service.
What does the partner tier add over a standard plan?
The partner positioning is built around multi-tenant management, white-label reporting, client portal access, revenue alignment, volume pricing, and a dedicated CSM path.
What audit scope is live today for partner delivery?
The live scope today is Active Directory and Microsoft Entra ID. The partner page intentionally avoids claiming live provider coverage beyond those two areas.
How should we start the conversation?
Use the partnership contact route so the team can discuss client count, white-label requirements, managed users, and the operating model you want to package.
Related pages
Review the partner tier positioning alongside Premium, Elite, and Enterprise.
See how the evidence engine works in standalone API and SaaS daemon mode.
Review the 275-detection Active Directory scope used in partner-led audits.
Review the 144-detection Entra ID scope used in partner-led audits.
Build an MSSP identity audit offer on top of a repeatable AD and Entra workflow
If you need multi-tenant delivery, branded exports, and a partner-ready commercial path, open the partnership conversation rather than forcing the model through a standard self-serve signup.