Cisco & Meraki specialists. Across the UK.
+44 203 196 6566 · option 1sales@proxar.co.uk

Connect. Secure. Manage.

Meraki Air Marshal Configuration

Review Meraki wireless threat detection and Air Marshal settings, distinguishing alerting from active containment and checking authorisation before enforcement.

Cisco Partner since 2009 Projects & ongoing support

Illustrative Cisco and Meraki fibre network rack with structured cabling
Your network. Properly considered.Design · Implementation · Support
1,000+

Devices supported
across the UK

20+

Client locations
supported

Nearly 8 Tbps

Traffic handled
at peak time

3 min

Average
response time

Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.

Meraki Air Marshal configuration helps teams review wireless threats and unexpected access points. We plan supported detection and a clear response process for findings. Passive monitoring is kept separate from active containment. Any action that may affect radio traffic needs an authorised scope, with care for legitimate neighbouring networks and a named decision-maker.

01

Coverage and capacity

Design Wi-Fi around the spaces, devices and traffic that depend on it.

02

Secure access

Align authentication, segmentation and guest access with the wider network.

03

Measured performance

Validate roaming, interference and user experience instead of relying on signal bars.

Define the environment and the response authority

An office may see access points belonging to neighbouring businesses, personal hotspots and other legitimate systems outside its control. We establish the premises, authorised infrastructure and people responsible for investigating alerts. The customer should know who may classify a device, contact another tenant or authorise a response. A security feature does not itself establish permission to interfere with a third party’s service.

We check the site’s rules for personal hotspots and temporary wireless kit. A device may break an internal rule without being an attacker. Equally, a familiar network name may need investigation. The process distinguishes these cases and sets out the evidence needed before escalation, so each detection receives a proportionate response.

Illustrative Cisco Meraki wireless access point in a modern office
01Cloud-managed wireless for modern workplaces.
Cisco PartnerCisco Partner
Cisco MerakiCisco Meraki
ISO 9001Quality management
ISO 27001Information security
Cyber EssentialsCyber Essentials
Cyber Essentials PlusCyber Essentials Plus

MCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information

Check platform visibility and coverage

We review the access-point models, software and monitoring setup to establish what the deployed system can observe. Detection coverage depends on the physical setup and supported radio behaviour. We do not assume that a dashboard feature provides continuous, complete visibility of every channel and every device across an entire building under all operating conditions.

The assessment also considers the relationship between RF observations and the wired network. Where the platform provides information that helps classify a potential rogue, that evidence is interpreted within its limits. An unfamiliar radio detected outside a window should not be declared connected to the corporate LAN without supporting information. The report separates observed facts from the classification that still requires confirmation.

Illustrative Cisco and Meraki network rack in a modern office
02The office network: switching, uplinks and structured cabling.

A useful starting point

Not sure where to start?

Bring the requirement. We will help you define the engineering work.

Talk to a specialist

Establish a reliable authorised-device baseline

We reconcile known access points, site locations and approved wireless arrangements. The baseline should include legitimate temporary or specialist rollouts so they are not repeatedly treated as unexplained threats. It also needs a process for new equipment and decommissioning. A static allowlist becomes less useful as the estate changes.

Naming alone is not enough for trust. We assess the identifiers and supporting records available for the platform, and identify who maintains them. Where several suppliers operate wireless systems in the same premises, the baseline and escalation route are agreed across the relevant teams. This prevents a legitimate contractor installation from triggering an uncoordinated response by someone who was never told it existed.

Illustrative Cisco and Meraki network operations centre with monitoring displays
03Visibility, monitoring and operational control.

Separate detection from containment decisions

Active containment can disrupt radio traffic. It requires a clear right to act, an agreed scope and review of applicable rules and effects on others. Our default assessment does not turn on broad automatic containment. Any proposed enforcement must first be approved through the customer’s security and legal process.

Where an authorised containment use case is considered, we check the exact supported behaviour and limitations before rollout. The plan defines when the action may be taken, who can stop it and how legitimate services will be checked. We do not provide a guarantee that containment defeats every threat or substitute it for stronger authentication, wired access controls and ordinary incident-response procedures.

Illustrative Cisco and Meraki equipment in organised data-centre racks
04Data-centre connectivity with clear physical and logical boundaries.

Make alerts actionable and investigate safely

Alert routing should identify the people who can review the evidence and the urgency associated with different events. We agree the information to retain and how it will be handled, taking account of the sensitivity of wireless identifiers and captures. The aim is enough context to investigate, not indiscriminate collection without a defined operational purpose.

A typical investigation compares the observed device with the authorised inventory, physical location and relevant network evidence. Where uncertainty remains, we use approved passive observations or coordinate an on-site check. Disruptive testing is not the first response to an unfamiliar identifier. The incident record explains the conclusion and any policy or change to the settings that follows.

Illustrative Cisco and Meraki fibre network rack with structured cabling
05Fibre, switching and the physical path behind the service.

Validate the configuration and review it over time

Testing uses controlled, authorised scenarios to confirm visibility and alert delivery. We check that the response team can distinguish a test event from a real incident and knows the escalation process. Any enforcement testing requires its own approved scope and safeguards. Results describe the conditions tested rather than claiming complete wireless threat coverage from a single demonstration.

MCI can review Air Marshal alongside Meraki dashboard access control and broader wireless security. The handover includes the baseline, monitoring policy, duties and limitations. It leaves the customer with a considered detection and response process, while keeping active interference decisions separate from routine network administration.

Illustrative Cisco Meraki wireless access point in a modern office
06Cloud-managed wireless for modern workplaces.

Technical references

Illustrative Cisco and Meraki network rack in a modern office
07The office network: switching, uplinks and structured cabling.

Talk to a specialist

What does your network need next?

Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.

+44 203 196 6566

Choose option 1

sales@proxar.co.uk

UK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.

Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.

Tell us what you need.

A short outline is enough. Please do not include passwords or sensitive network details.

Thank you. Your enquiry has been submitted.

We’ll use these details to respond to your enquiry. Please leave out passwords and sensitive network information. Read our privacy notice.