Build managed Layer 7 security services on infrastructure you control.
Deploy VxSure as a compact software-defined appliance in your own environment, operate it for many customers from one console, and define the service, the SLA and the price yourself.
Foundation tier: no fee, six Advanced evaluation instances.
Who it is for
Provider type
Problem today
How VxSure fits
MSSPs
Web security is resold, not operated, so it adds little to the managed service
Run inspection on your own infrastructure and feed every web decision into your SOC
System integrators
Client designs need a Layer 7 control that fits custom networks and identity
Deploy on the client's platform of choice, with JWT-based SaaS integration in Advanced
Telcos and ISPs
Connectivity is sold without a security layer
Inline inspection for subscriber traffic, with traffic mirroring to your monitoring
Cloud operators
Customers ask for security that stays in your region and your data centre
Run VxSure alongside your existing services, with logs kept in-region
Security specialists
Advisory work ends at a report, with no recurring service behind it
Turn policy and compliance work into an operated service
ProblemA platform is only useful to a provider if it maps to services customers buy.
Eight services, each mapped to an edition.
Managed secure web gateway (SWG)
Basic
Problem: DNS and category filtering cannot see inside HTTPS or files hosted on trusted domains.
Controls: TLS inspection with the customer's own CA, inline file inspection, DNS filtering and tunnelling detection, command-and-control blocking, content disarm.
Typical buyer: small and mid-sized organisations.
AI and SaaS governance
Power
Problem: staff paste and upload company data into AI tools and personal SaaS accounts.
Controls: identifies AI and SaaS destinations, separates company and personal accounts, applies allow, limit or block per app.
Typical buyer: any organisation where staff use AI tools at work.
Data loss prevention (DLP)
Power
Problem: sensitive data leaves through browser uploads, including inside archives and images.
Controls: detects PII, financial and health records in text, files, archives and images (OCR); blocks uploads to unapproved destinations.
Typical buyer: finance, healthcare, IT and outsourcing firms.
Compliance evidence
All editions
Problem: auditors need long-term decision logs kept in a specific jurisdiction.
Controls: every decision logged with user, rule and action; versioned policy changes; logs stored on your in-region infrastructure.
Typical buyer: regulated organisations.
Remote browser isolation (RBI)
Power
Problem: unknown sites are either blocked, which stops work, or allowed, which exposes the endpoint.
Controls: risky pages render in a remote browser on your infrastructure; active code never reaches the device.
Problem: SOCs lack application-layer evidence from web sessions.
Controls: structured logs of every web decision forwarded to the SIEM, ticketing and automation tools.
Typical buyer: customers of MSSPs with a security operations centre.
ProblemUnclear responsibility between vendor and provider is where outages and disputes start.
Who does what.
Area
Partner
VxSure
Infrastructure (compute, storage, bandwidth, including RBI)
✓Included
–Not included
Deployment and configuration
✓Included
Guidance and reference material
Customer contract, service scope, SLA and price
✓Included
–Not included
First-line operations and customer support
✓Included
–Not included
Platform software, updates and threat intelligence
–Not included
✓Included
Second-line partner support
–Not included
✓Included
Product defects and fixes
–Not included
✓Included
Enablement: workshops, reviews, documentation
–Not included
✓Included
ProblemRunning one stack per customer does not scale for a provider team.
Many customers, one console.
Per-customer policy: each tenant has its own rules, users and logs.
Policy consistency: policies, threat feeds and directory integration stay in sync across nodes and sites.
High availability: active-active behind a load balancer, or active-passive failover.
Change control: policy changes are versioned and backed up; a replacement node restores its configuration.
Evidence per tenant: structured logs per customer to your SIEM, ticketing and automation tools.
Console · TenantsIllustration
Customer ABasicpolicy v14
Customer BPowerpolicy v9
Customer CAdvancedpolicy v22
Customer DBasicpolicy v3
Customer EPowerpolicy v11
ProblemSecurity layers that need network redesign or endpoint rollout stall in delivery.
One appliance. Your platform.
Form factor: one compact software-defined appliance with a built-in console.
Platforms: public cloud, private cloud, KVM-based hypervisors, virtualised data centres, or the customer's own environment.
Network position: beside the existing firewall, adding Layer 7 inspection.
Traffic onboarding: the organisation's VPN for remote users; firewall and router tunnels from offices. No endpoint agent.
Identity: the organisation's existing identity provider.
Scaling: add CPU and memory to a node first, then add nodes.
ProblemA demo tenant shows the vendor's environment, not yours.
Test the Advanced edition before you sell it.
Join as a Foundation partner
No fee. Onboard up to two technicians and receive six Advanced non-production instances for proof of concept, evaluation and training.
Build the proof of concept
Deploy in your lab or a prospect's environment. Validate TLS inspection, DLP, RBI and logging against your own test cases, with fortnightly workshops and included assistance sessions.
Move to production
Deploy Basic without instance limits. Add Power and Advanced as customers need them.
Evaluation instances are non-production and subject to published usage rules.