Managed services · Meraki Security

Firewall, VPN and threat policy under daily operation.

Managed security operations using Meraki MX and vMX, enterprise and advanced security capabilities, security monitoring, dashboards and reporting.

How the service runs Concept model
1 2 3
  1. 01 · Onboard Baseline the security posture Policy · licences · contacts
  2. 02 · Operate Monitor, triage and change Events · rules · escalation
  3. 03 · Review Report and re-check posture Reports · exceptions · QBR

A conceptual service lifecycle used to explain the model—not a customer deployment.

Overview

What it is

Managed security operations delivered through the Meraki dashboard and the CDS operations model. The service may include firewall, VPN, content filtering and threat protection capabilities, with security event monitoring, dashboards and recurring reporting.

  1. 01

    Security event monitoring and triage

  2. 02

    Firewall and VPN operated as a service

  3. 03

    Content filtering and threat protection policy

  4. 04

    Security dashboards, reporting and review

Service inclusions

What is included

Supported Meraki platforms: Meraki MX and vMX with enterprise and advanced security licensing. Specific capabilities depend on the licences held.

Service inclusions — Managed Meraki Security
Service inclusionManaged Meraki Security
Security event monitoring and triageIncluded
Cloud orchestration via Meraki dashboardIncluded
Firewall as a ServiceIncluded
VPN as a Service / Auto VPNIncluded
Content filteringIncluded
Threat protection / IDS-IPS policyIncluded
Network-based AMP enablementIncluded / License-dependent
Customer service portal / dashboardIncluded
Event log retentionAs per SLA
Availability reportingIncluded
Incident management reportsIncluded
Exception and threshold reportsIncluded
Security reports and reviewIncluded
Dual firewall / HA designOptional

Read the qualifiers. Rows marked optional, tiered, add-on, licence-dependent or “as per SLA” are not included by default — each is confirmed during scoping and written into the service agreement.

Right fit

Who it is for

Distributed perimeters

Every site has a security appliance and none of them should drift.

Teams without a SOC

Security events need triage by someone during the contracted hours.

Audit and review needs

Recurring posture reporting is expected by the business or a regulator.

Outcomes

What you get

Triage

Security events are looked at and escalated under a defined process.

Policy

Firewall, content and threat protection settings maintained under change control.

Reporting

Availability, incident, exception and security posture reports produced on a cycle.

Review

Policy and posture revisited rather than set once at deployment.

Questions, answered directly

What buyers usually need to establish

Is AMP included?

Network-based AMP enablement is listed as included but licence-dependent. Whether it applies to your estate follows the Meraki licences held.

How long are event logs retained?

Event log retention is set by the SLA rather than a fixed default. The retention period is confirmed in the service agreement.

Is a high-availability firewall design included?

No. Dual firewall and HA design is optional and scoped separately from the recurring managed security service.

Designing the security architecture Next-generation firewall — the build-side engagement

Start with who runs it today.

Describe the current estate, the operating gaps and the service level the business expects. Scope and packaging follow that conversation.