SecureOps InTandem™

Poor flexibility, high overhead

You get bodies you need to train and micromanage

Usually not 24/7, no SLA

No structure around consultants

Frequent turnover

Uneven quality and expertise

Bodies do not equal output

Availability limited for extra hours/nights/weekends

Fully managed Staff Aug or Collaborative/Open Managed Services

Dedicated team, but MANAGED by the SecureOps process (QA/Seniors/PMs)

24/7 with customer-driven SLA's

We agree on an objective and deliverables quarterly, SecureOps manages and executes

Nimble/Flexible: No contractual change required for changing priorities as long as LoE and expertise doesn't change.

Can use any pricing driver but usually the most flexible is used

SLAs/KPIs can be enforced as with MSSPs

FTE model can be used if preferred

Low overhead, low flexibility

No direct control, no nimbleness

Any change requires changing process and SLA as they are agreed upon upstream

You don't control people, process or infrastructure

Almost impossible to calculate actual ROI

Natural drift between needs and service given typical contract duration

Customer does not own documentation or process, transition to internal team or another provider exceedingly difficult

Pricing is usually based on input/SLA (number of firewalls, events, IPs, etc). Very difficult to predict future pricing