For managed service providers

Your client needs compliance. You manage their IT.

Bring Sythe in for the compliance work and security testing. Your team coordinates the systems it manages; our operators request evidence, review technical controls, and report findings. We agree who handles the remaining work with you and the client before starting.

Discuss a client engagement Send a partner inquiry

Start with the requirement and deadline, without naming the client. Keep credentials and security reports out of this form.

Where we fit

A compliance program and a standalone test answer different client needs.

An ongoing compliance program

Use the platform to organize controls, evidence, policies, and review. Sythe operators handle technical validation and evidence review; the client retains its business decisions and policy approvals unless explicitly delegated.

Explore compliance support

A specific testing requirement

A client may only need a penetration test. We can scope that separately around the application or infrastructure, authorized access, report requirements, and retest. Vulnerability scanning is a separate activity, not a substitute for a penetration test.

Use the pentest scoping checklist

Who owns the work

Use this as a starting point for the scope, not a replacement for the signed agreement.

Business information and policy approval: The client supplies its business context and approves its policies. Any delegated approval needs an explicit agreement.
Access and technical evidence: Your MSP team coordinates the systems it manages. Sythe requests and reviews evidence for the agreed compliance scope.
Security testing and findings: Sythe tests the authorized assets and reports findings. The system owner approves the targets, access, and testing window.
Remediation and ongoing monitoring: Name the implementation owner before work starts. Hands-on fixes, ongoing monitoring, and advisory are separately scoped services.

Make the introduction

Referral, resale, and joint delivery are different arrangements. We discuss the terms before anyone makes a client commitment.

Have a client asking for help?

Tell us what they have been asked to produce and where your team's responsibility stops. Andrew will review the request with you before an introduction. If the work fits, we agree who speaks to the client and what we need to prepare a quote. Ask the client before sharing their details.

Referral fees, reseller pricing, branding rights, and support commitments require a separate written agreement. Sending an inquiry does not enroll you or your client in a partner program or newsletter.

Read our published client work

Scoping checklist

Use these questions with your team before making an introduction. No download or signup required.

Client request

What is the customer, insurer, or auditor asking for? Capture the actual requirement and deadline.

Systems in scope

List applications, environments, hosts, and the frameworks under consideration. Identify who can authorize access.

Existing work

Note current reports, evidence, providers, and open findings so the engagement does not repeat work unnecessarily.

Owners and handoff

Agree who communicates with the client, who approves work, who fixes findings, and how updates reach each team.

Partner inquiry

Andrew reviews these inquiries. Share your own contact information and a short, anonymized account of the client's need.