Frequently asked questions
What to expect from an SPG engagement
Every scope is tailored, but these answers explain the typical working arrangements, inputs and delivery decisions.
- Can SPG help us choose between an internal SOC and an MSSP/MDR model?
- Yes. The current-state assessment compares internal capability, coverage requirements, telemetry, response responsibilities and resource constraints. SPG then sets out internal, outsourced or hybrid options with dependencies and governance implications rather than assuming full outsourcing is always best.
- Does managed security always mean 24/7 monitoring?
- No. Coverage should reflect your risk and operating requirements. SPG can help define business-hours, extended-hours or 24/7 models, including what happens to alerts and incidents outside covered periods. Agreed hours and escalation expectations are documented in the SLA.
- Can you work with our existing SIEM and EDR tools?
- Yes. The tooling and telemetry assessment begins with your current platforms and identifies integration, data-quality and visibility gaps. SPG provides vendor-neutral recommendations, so existing investments are retained where they meet service requirements.
- What should the SLA measure?
- Useful measures can include coverage, data-source health, triage and escalation times, response activities, reporting and service availability. Definitions must account for client dependencies and approval requirements so performance reporting remains meaningful and auditable.
- How is managed service pricing determined?
- Pricing typically depends on coverage hours, assets and data sources, telemetry volume, response responsibilities, technology requirements, integration complexity and transition effort. SPG documents these scope drivers so commercial comparisons use equivalent assumptions.
- How do you transition without creating a monitoring gap?
- The phase-in plan sequences telemetry, access, workflows, rehearsals and acceptance checkpoints. Parallel-run and rollback arrangements are included where needed, and service activation occurs only after agreed operational readiness criteria have been satisfied.