Provider responsibilities
- Operate the client environment and technology stack
- Implement approved changes and provide relevant completion evidence
- Maintain existing support, escalation, and incident processes
For MSPs & IT providers
Add security leadership without becoming a different kind of provider.
Praeven works alongside managed service providers and internal IT teams that want a clear security-program layer for clients: priorities, reviewed exposure, evidence, and leadership reporting.
Operating model
Complement the technical relationship you already own.
Praeven is not a replacement help desk, RMM, SOC, endpoint-management platform, or incident-response team. The partnership gives clients an accountable security-program layer around the technology services you provide.
Praeven responsibilities
- Maintain the agreed risk register and security-priority plan
- Review approved internet-facing assets and agreed business-platform evidence
- Translate findings into practical decisions and leadership reporting
Client responsibilities
- Approve scope, remediation priorities, and accepted business risk
- Provide authorized contacts, assets, and business context
- Own the systems, data, decisions, and remediation approvals
When to bring Praeven in
The client has technology support but no one carrying the security program.
The best fit is a small or midsize organization that already relies on an MSP or internal IT lead but needs help with security priorities, policy ownership, customer questions, public exposure, and regular leadership discussion.
Contractors and field services, professional firms, and multi-location hospitality groups are useful starting points. The same model can fit other businesses with a clear IT relationship and a need for practical security leadership.
Signals a client may be ready
- They are receiving security questionnaires or insurance questions
- Policies, AI use, personal devices, or access ownership are unclear
- Leadership wants a recurring view of risks and remediation progress
- The MSP can implement work but does not sell security leadership
- Public domains, email, cloud access, or vendor fraud are causing concern
A clear service ladder
Introduce the right operating depth.
These are Praeven’s client-facing program prices. Scope, delivery responsibilities, and client communication are agreed before work begins.
| Service | What the provider brings | What Praeven adds | Client price |
|---|---|---|---|
| External Exposure Review | Approved asset list and technical contact | Monthly reviewed external findings and results discussion | $895per month |
| Managed Security Program | Relevant Microsoft 365 or business-platform evidence; remediation support | Risk register, monthly security review, and up to 2 advisory hours | $1,895per month |
| Standard | Regular implementation coordination and evidence | Up to 25 approved internet-facing assets, working sessions, and up to 6 advisory hours | $3,000per month |
| Expanded / Embedded | Defined technical and client-communication collaboration | Leadership reporting, policy/vendor work, or substantial program ownership | $5,000 / custom scope |
Partner commercial terms are agreed separately and are not implied by the client-facing service price.
Co-delivery flow
Keep the client, provider, and security program aligned.
Use a visible sequence so nobody is surprised by scope, access, or remediation ownership.
Qualify together
Confirm the client’s business goal, current provider relationship, likely scope, and whether a fixed foundation project or monthly program fits.
Set the scope
Identify authorized internet-facing assets, evidence sources, client contacts, implementation roles, scan windows, escalation paths, and reporting audience.
Run the cadence
Praeven maintains priorities and reviewed reporting; the provider implements agreed work; the client approves decisions and receives a useful progress view.
Start a conversation
Bring one client situation, not credentials.
A useful first discussion covers the client’s business, their IT relationship, the systems that matter, and the decision they are trying to make.
Do not send credentials, network diagrams, security logs, or incident details through the website contact form. Praeven will arrange an appropriate channel if technical detail is needed.
What to bring
- Client industry, size, and current IT arrangement
- The business concern or customer requirement driving the conversation
- Whether they have a Microsoft 365 or similar business tenant; any endpoint work can be scoped separately
- Known public domains, VPNs, portals, or cloud assets
- The client stakeholders who need to approve scope and remediation
Prepare. Anticipate. Protect.