Learn pageAlso searched as 358 welded mesh / 358 weld mesh / 358 welded mesh fencing / 358 welded mesh security fencing
Tool layer + report layer in one canonical URL
Anti climb fence guide and 358 welded mesh security fencing fit checker.
If you are searching for 358 welded mesh or 358 weld mesh or 358 welded mesh fencing or 358 welded mesh security fencing or 358 mesh fencing panels, you are usually trying to decide whether an anti climb fence is worth the extra weight, cost, and specification detail. Start with the checker, then use the evidence, comparison, and risk sections to make a defensible buying decision.
Tool-first layer358 welded mesh fit checker
Check whether anti climb fence is justified before you quote it.
Use this quick screen to decide if 358 welded mesh, 358 weld mesh, or 358 mesh fencing panels match the perimeter, threat level, wind exposure, and budget pressure on your project. It is a procurement tool, not a structural design sign-off.
What this tool returns
Run the checker to get a fit band, starter panel count, recommended height range, and the main reasons to keep or reject 358 mesh panels.
Best for projects where anti-climb geometry, sightlines, and tamper delay matter more than the lightest install package.
Good boundary guardrail: if the project is low-risk, short, and cost-led, compare standard temporary fence before defaulting to 358.
Published and updated
Published:
Updated:
Source layer refreshed for this page update.
Public spec range
1.27 to 7.0 m
Permanent-system height band observed across current supplier pages.
Best fit
High-visibility security perimeters
Especially where camera sightlines and anti-climb delay both matter.
What makes the page different
The tool answers the immediate question first: should this site specify anti climb fence at all? The report layer then shows the public geometry, height, temporary use cases, and buying risks behind that recommendation.
Fast summary for alias intent
In most buyer conversations, “358 welded mesh”, “358 weld mesh”, “358 welded mesh fencing”, and “358 mesh fencing panels” all point to a small-aperture anti climb fence system rather than a generic welded panel. That is why this page uses one canonical URL instead of creating a separate alias page.
Key conclusions
The main decisions behind a 358 welded mesh purchase are visible before you ask for a quote.
These are the conclusions that matter most in early-stage screening. Each one is backed by the public source layer below, or explicitly marked as synthesis.
The geometry is the decision anchor.
Official Jacksons, Betafence, and Zaun product pages rechecked on April 6, 2026 still cluster around this small aperture, which is the core anti-climb feature.
76.2 x 12.7 mm
Public permanent systems share a broad height band.
Jacksons lists standard panels from 1270 mm to 5210 mm, Betafence markets one-piece panels up to 6.0 m, and Zaun advertises single panels up to 7.0 m on request.
1.27 to 7.0 m
Temporary 358 exists, but it is not the default answer.
Zaun temporary-system literature shows 358 used in short-term deployments with 455 kg or 910 kg bases and materially different design wind speeds, so engineering setup matters more than on standard temporary fence.
2.0 / 2.4 / 3.0 m
Sightlines are part of the value, not a side effect.
Manufacturers repeatedly position anti climb fence as a way to keep visibility for patrols and cameras while raising the climb barrier.
Open mesh
Certification target must be explicit.
LPS 1175 Issue 8.2 classifies intruder resistance by tool set and delay time. Product names like “358 welded mesh” or “358 weld mesh” do not encode a forced-entry rating by themselves.
A1 to H20
Rating band also changes attacker assumptions.
NPSA Forced Entry Standards Guide (Version 2, June 2024) maps lower LPS bands to one active adversary and higher bands to two active adversaries. Threat staffing assumptions should be explicit in the tender.
A1-E20: 1 | F1-H20: 2
Vehicle threat needs its own control layer.
NPSA hostile-vehicle guidance (updated March 17, 2026) reports over 140 vehicle-as-weapon attacks since 2014 and says nine out of ten locations lacked significant barriers, so fence-only logic is not enough where vehicle threat exists.
140+ attacks
Regulatory boundaries can block otherwise valid technical specs.
England permitted-development rules for fences and gates set height thresholds near highways and elsewhere. CDM 2015 also requires risk-based perimeter identification and/or fencing on construction sites.
1 m / 2 m
Stage1b gap audit
What this enhancement round fixed, and what is still open.
This table isolates evidence weakness from execution risk before adding new claims. Closed items are now source-backed below. Open items stay explicitly marked as pending.
| Gap detected | Risk if ignored | Stage1b fix | Status |
|---|---|---|---|
| Forced-entry claims lacked attacker-team context. | Procurement may select an inadequate rating for coordinated intruder scenarios. | Added explicit LPS band boundary (A1-E20 one adversary; F1-H20 two adversaries) in conclusions, spec table, and standards matrix. | Closed with public evidence (NPSA forced-entry guide + LPS 1175). |
| Vehicle-threat crossover was noted, but execution rules were thin. | Teams may buy fence upgrades while leaving vehicle pathways under-specified. | Added ISO 22343 transition marker and NPSA temporary VSB constraints (as-tested formation, delay + impact ratings, maximum gap reference). | Closed with public evidence (ISO + NPSA). |
| “All 358 quotes are equivalent” lacked concrete counterexamples. | Single-layer and reinforced systems may be priced or compared as if they were interchangeable. | Added variant reality table using archived NPSA CSE entries (single-layer 4 mm, double-skin DS2, and Super6 variant). | Closed with public evidence (NPSA CSE archive pages). |
| Open installed-cost benchmark remained weak. | Buyers may anchor on panel-only prices and miss gate/foundation/HVM scope costs. | Kept explicit uncertainty flag and retained RFQ-based comparison path. | Pending confirmation / no reliable public dataset. |
| Legal/permitting boundary for fence height was not explicit. | Teams can place orders before permits and trigger redesign, delay, or non-compliant installation. | Added GPDO Class A boundary markers (England: 1 m by vehicular highway, 2 m elsewhere with stated exceptions) into spec, standards, FAQ, and source layers. | Closed with primary legislation evidence (UK SI 2015/596, Schedule 2 Part 2 Class A). |
| Gate security and emergency-egress coupling was under-specified. | Security hardware choices can conflict with evacuation/access requirements and fail review. | Added NPSA and HSE boundary language into standards matrix, risk table, and FAQ to force gate-by-gate egress validation. | Closed with public guidance evidence (NPSA Fences and Gates + HSE CON1-2018). |
| Fence-only delay expectations lacked a quantified baseline. | Buyers may overestimate what fence geometry alone can deliver during an active intrusion. | Added UFC baseline markers (chain-link delay and clear-zone guidance) and framed them as context-specific, non-universal inputs. | Closed with public government reference (DoD UFC 4-022-03, October 1, 2013). |
Method and evidence
What the public data actually supports.
This page synthesizes current manufacturer data plus standards, guidance, and legislation sources (NPSA, LPCB, BSI, ISO, UK legislation, HSE, and UFC) rechecked on April 6, 2026. It is designed to support sourcing and scope definition, not to replace structural or security engineering.
Aperture logic
The decision signal behind “358 mesh fencing panels” is the small-aperture geometry, not the nickname alone.
The common public geometry reduces easy finger and toe purchase while keeping visibility. That is why 358 panels sit closer to security mesh than to ordinary welded fence panels in buying behavior.
Source quality note
The numbers below are a synthesis of current supplier pages, not a universal standard. Different markets can use different panel widths, post sizes, and coating stacks.
When the exact project spec matters, treat the public sources as a screening layer and move to supplier drawings before approval.
Public spec snapshot
Use this to spot whether a quote is aligned with current mainstream 358-style anti climb fence positioning.
| Metric | Observed range | How to use it |
|---|---|---|
| Common mesh opening | 76.2 x 12.7 mm | Confirmed on Jacksons, Betafence, and Zaun product pages rechecked April 6, 2026. |
| Common wire diameter | ~4 mm | Public product pages regularly describe the 358 format around a 4 mm wire. |
| Typical permanent panel width | 2.44 to 2.52 m | Jacksons and Zaun list widths around 2440 mm to 2515 mm. |
| Observed permanent height range | 1.27 to 7.0 m | Jacksons standard range runs to 5210 mm, Betafence offers one-piece panels up to 6.0 m, and Zaun advertises single panels up to 7.0 m on request. |
| Observed temporary height range | 2.0 to 3.0 m | From current temporary 358 literature; not every supplier offers this. |
| Observed temporary base reference | 455 / 910 kg | From the current Zaun RDS StrongHold S455-358 temporary-system PDF; larger bases support higher design wind speeds. |
| Observed temporary design wind speeds | 2.0 m: 80 / 110 mph, 2.4 m: 69 / 96 mph, 3.0 m: 55 / 77 mph | Zaun StrongHold S455/S910 public table: same panel type but different base mass gives materially different wind performance. |
| CNI standards transition marker | CSE removed from approved list from January 1, 2026 | NPSA states CSE is no longer on the approved standards list; avoid writing new security-critical tenders around legacy CSE shorthand. |
| NPSA security fence panel height guidance | >=2.4 m baseline; >=3.0 m for higher security | NPSA Security Fences and Gates guidance (last updated August 14, 2025). |
| NPSA anti-climb topping reference | 0.4/0.5 m BTC baseline or 0.6 m for higher security, with max 0.2 m loop spacing | Used where topping is selected and compatible with site health and safety constraints. |
| Coating standard scope boundary | ISO 1461 excludes continuously galvanized wire and welded mesh products | Do not assume one galvanizing standard covers all components in a 358 package. |
| Forced-entry scope limits (LPS 1175 Issue 8.2) | Excludes vehicle impact, explosion, ballistics, surreptitious entry, plus scaling/tunnelling resistance | Use separate controls when those attack paths are part of the threat model. |
| LPS 1175 attacker-team boundary | A1-E20: one active adversary; F1-H20: two active adversaries | From NPSA Forced Entry Standards Guide (Version 2, June 2024). |
| Vehicle-barrier standards transition marker | ISO 22343-1:2023 replaces withdrawn IWA 14-1:2013 (legacy references still appear) | Use version-explicit wording to keep legacy and current evidence auditable in one tender. |
| Temporary VSB line-layout control | NPSA temporary guidance advises air gaps no wider than 1.2 m between barriers | Barrier ratings apply to tested formations; changed spacing/layout requires revalidation. |
| Archived CSE 358 variant signal | Single-layer 4 mm, double-skin DS2 (four-panel layering), and Super6 6 mm vertical-wire variants all exist | Do not assume every quote using “358” language is architecturally equivalent. |
| NPSA hostile-vehicle signal | Since 2014: 140+ attacks; 9/10 locations lacked significant barriers | If vehicle-borne threat exists, add VSB/HVM requirements rather than relying on mesh choice alone. |
| Finish options seen publicly | HDG or HDG + polyester powder coat | Supplier options vary by environment, color, and project sector. |
| England planning threshold marker (GPDO Class A) | Adjacent to vehicular highway: typically <=1 m (schools have a specific 2 m clause with visibility condition); elsewhere: <=2 m | Use as an early legality check before RFQ freeze; listed buildings and Article 4/planning conditions can remove permitted-development rights. |
| Construction-site perimeter legal duty (CDM 2015 Reg 18) | Site perimeter must be identified by suitable signs and/or fenced off where necessary in the interests of health and safety | Treat temporary 358 selection as part of a risk-based site-security plan, not a standalone product swap. |
| Public anti-trespass control marker (HSE CON1-2018) | Perimeter fencing should be continuous/fixed; vulnerable access routes need extra local controls | Useful for residential/public-interface projects where child access risk is material. |
| UFC fence-only delay context (DoD reference) | Chain-link baseline is described as roughly seconds-level delay; clear zones are recommended at 20 ft each side where possible | Use as a caution against “fence alone” assumptions; pair perimeter hardware with detection, response, and layout controls. |
Where permanent anti climb fence usually makes sense
| Project signal | 358 call | Why |
|---|---|---|
| Utility, data, transport, or public-facing perimeter | Strong fit | These sites usually care about visibility, deterrence, and anti-climb geometry enough to justify the heavier panel system. |
| Warehouse boundary with frequent gate traffic | Strong fit if gates are specified early | The fence itself is suitable, but poor gate planning is a common failure point in otherwise good 358 projects. |
| Budget-led low-risk perimeter | Conditional fit | The system works, but it may be more fence than the site needs unless appearance or client policy demands it. |
Standards boundary
What each standard can and cannot answer for a 358 decision.
This matrix separates naming, construction quality, and forced-entry performance so the procurement brief remains auditable.
| Decision focus | What the source layer says | What to do in procurement |
|---|---|---|
| Base fence classification | BS 1722-14:2017 classifies open mesh fences from Category 1 (general purpose) to Category 4 (higher security). | Require category + statement of conformity in the tender pack, not only a “358” label. |
| Forced-entry language | LPS 1175 Issue 8.2 expresses performance as tool set (A to H) plus delay time (1 to 20 minutes), and warns there is no direct correlation to other standards. | For higher-threat procurement, set a target rating band and make sure gates are matched, not just panels. |
| Attacker-team boundary | NPSA forced-entry guidance maps LPS A1-E20 ratings to one active adversary and F1-H20 ratings to two active adversaries. | Write attacker-team assumptions into the threat brief so the selected rating band is defensible. |
| LPS scope exclusions | LPS 1175 Issue 8.2 excludes vehicle impact, explosion, ballistics, surreptitious entry, and scaling/tunnelling resistance from scope. | Do not use an LPS rating as proof for those threat paths. Add separate controls where relevant. |
| Perimeter design baseline | NPSA guidance recommends security fence panel heights of at least 2.4 m, with 3.0 m and stronger topping geometry for higher security. | Treat panel height and topping as first-order design inputs, not post-award extras. |
| CNI standards transition (2026) | NPSA states CSE was removed from the approved standards list from January 1, 2026, and that chain-link fabric is not recommended for CNI. | For new CNI/security-critical tenders, avoid legacy CSE shorthand and define a current standards path with explicit fence-type rationale. |
| Temporary deployment limits | NPSA flags temporary systems as foundation-free and sensitive to wind loading, ground bearing, burrowing, lift gaps, and PIDS compatibility. | Temporary 358 should be specified as a full engineering package (base, wind, terrain, inspection), not as a simple panel substitution. |
| Vehicle-borne threat boundary | NPSA separates perimeter fence decisions from hostile vehicle mitigation (VSB/HVM) where vehicle attack risk exists. | If VAW or VBIED threat is in scope, add VSB/HVM and stand-off requirements in the same procurement package. |
| Vehicle-barrier standards transition | ISO says ISO 22343-1:2023 replaces withdrawn IWA 14-1:2013; NPSA guidance still references both during transition. | Keep standard versions explicit in tender language and do not merge old/new claims without traceable mapping. |
| Temporary VSB formation dependency | NPSA temporary VSB guidance states ratings apply to tested conditions only and recommends barrier gaps no wider than 1.2 m. | Treat on-site layout control as part of compliance, not post-install housekeeping. |
| Coating scope boundary | ISO 1461:2022 does not apply to continuously hot dip galvanized wire/welded mesh products. | Validate per-component corrosion treatment standards before comparing service-life claims. |
| Planning/permitting boundary (England) | GPDO 2015 Class A sets explicit height limits for gates/fences/walls, with different limits near vehicular highways and specific listed-building constraints. | Treat legal-permission checks as a pre-order control gate for height, alignment, and boundary scope. |
| Construction site security duty | CDM 2015 Regulation 18 requires a construction site to be perimeter-identified and/or fenced off where necessary, in line with risk. | Specify temporary 358 with operational controls (fencing continuity, access-point control, inspections), not just panel SKU details. |
| Gate security versus emergency egress | NPSA gate guidance notes that gate security controls still need to satisfy legal emergency egress/access requirements. | Gate locking and access policy must be reviewed with fire and emergency procedures before acceptance. |
Regulatory and operating boundary checks
These controls are jurisdiction-specific and should be treated as decision gates before purchase orders are placed.
| Framework | Current signal | Applies when | Buyer action |
|---|---|---|---|
| UK SI 2015/596 GPDO Class A (gates, fences, walls etc.) | England permitted-development height limits are typically 1 m near a vehicular highway and 2 m elsewhere, with listed-building and school-specific clauses. | England projects where teams rely on permitted-development rights instead of full planning consent. | Run a permit screen at concept stage; if the project sits outside Class A limits/conditions, secure planning before procurement freeze. |
| UK CDM 2015 Regulation 18 (Good order and site security) | Construction sites must be perimeter-identified by suitable signs and/or fenced off where necessary in the interests of health and safety. | Construction projects with public interface, out-of-hours exposure, or elevated site-access risk. | Tie fence scope to the principal contractor site-security plan and define ongoing perimeter inspection responsibilities. |
| HSE Safety Alert CON1-2018 | Perimeter fencing should be continuous and fixed, with gaps minimised; vulnerable areas may need local fencing and controlled ladder access. | Scaffold and temporary works where children/public access risk is credible. | Specify continuity at fence interfaces, out-of-hours access controls, and escalation procedures after any trespass event. |
| NPSA Fences and Gates (updated November 10, 2020) | Security measures for gates should still satisfy legal emergency egress and access requirements, and gate effectiveness should be reviewed regularly. | Any perimeter using controlled gates as a key security control point. | Approve gate specification only after joint security + emergency-use validation, including operational testing and maintenance checks. |
| DoD UFC 4-022-03 (published October 1, 2013) | The guide frames fence delay as limited, seconds-level baseline performance and recommends clear zones (20 ft each side where possible) in the wider security system design. | DoD-style perimeter design context or when teams need a public baseline against fence-only assumptions. | Treat geometry as one layer in a detection-response architecture, and document where local policy supersedes UFC-era baseline assumptions. |
Evidence-layer assurance stack
Use this to stop scope confusion between geometry labels, forced-entry ratings, and vehicle-impact test claims.
| Evidence layer | What it confirms | What it does not confirm | Required procurement action |
|---|---|---|---|
| Geometry label ("358 welded mesh") | Small-aperture anti-climb intent and nominal mesh family characteristics. | Certified forced-entry delay rating, attacker-team assumptions, or vehicle-impact resistance. | Pair geometry with named performance standards and explicit gate/system scope. |
| LPS 1175 Issue 8.2 rating | Manual forced-entry resistance for the tested product assembly with defined tool category and delay time. | Vehicle impact, explosion, ballistics, surreptitious entry, or scaling/tunnelling resistance. | Keep LPS target for forced entry, then add separate controls for excluded attack pathways. |
| ISO 22343-1 / IWA 14 impact claim | Vehicle-impact behavior for the tested barrier format under the specified test conditions. | Manual attack delay unless separately tested, or equivalent performance when formation/site conditions change. | Request test-configuration evidence and pair impact rating with delay-rating requirement where vehicle threat exists. |
358 variant reality checks (counterexamples)
Public archived CSE records show that systems marketed around 358 language are not always structurally equivalent.
| Variant example | What changes in the system | Decision impact |
|---|---|---|
| Single-layer 358 baseline (NPSA CSE Securus listing) | 4 mm nominal wire panel, 76.2 x 12.7 mm mesh, with 2.520 m post centres and clamp-bar fixing on the listed build-up. | Useful as a baseline, but not a universal template for every “358” quote. |
| Double-skin DS2 358 (NPSA CSE Betafence listing) | Two pairs of double horizontal-wire panels (four panels thick total), mounted with 90-degree orientation to form a layered system. | Material and installation complexity differ materially from single-layer systems, so direct price equivalence is unsafe. |
| Super6 welded mesh (NPSA CSE listing) | Described as similar in concept to 358 but with 6 mm vertical wires and BS 1722-14 context in the listing notes. | Shows that anti-climb-style mesh families can change wire architecture and cut-resistance tradeoffs. |
2026 procurement hard-stop checks
Use this matrix to block common over-assumptions before a 358 tender is issued.
| When this is true | Do not assume | What fails if ignored | Minimum executable path |
|---|---|---|---|
| Threat model includes VAW/VBIED | 358 geometry alone controls vehicle-borne attack risk | The site can pass fence procurement but still fail vehicle-threat mitigation. | Add VSB/HVM line, stand-off logic, and vehicle-threat assumptions in the same brief. |
| Tender language still written around legacy CSE | CSE wording is still current for new CNI procurement | Spec ambiguity, delayed approvals, and hard-to-compare supplier responses. | Use current NPSA-aligned forced-entry/perimeter language and map each clause to an explicit threat. |
| Security rating copied without scope check | LPS 1175 rating covers covert entry, climb-over, and tunnelling | Uncovered attack paths remain outside the tested performance scope. | Pair rating target with anti-scale, anti-burrow, detection, and response requirements. |
| Vehicle-threat requirement uses mixed legacy/current barrier claims | IWA 14 and ISO 22343 claims are automatically equivalent without version mapping | Supplier responses become hard to compare and assurance can fail at review. | Request standard/version declarations and map impact + delay claims to one threat-based acceptance matrix. |
| Quote uses “358” wording but omits wire architecture | Single-layer 358 and reinforced variants are directly interchangeable | Panel, support, and cost assumptions drift between bidders. | Require layer count, wire diameter pattern, panel mass, and post/bracing schedule in the first submission. |
| Temporary deployment on open or sloped ground | Temporary 358 behaves like a standard panel-and-base swap | Lift gaps, wind instability, and redesign after mobilisation. | Define base mass, post centres, slope-gap treatment, and inspection criteria pre-award. |
| England project exceeds simple boundary-height limits | Fence and gate height can be fixed at design stage without planning-gate checks | Late permitting friction and possible forced redesign after supplier engagement. | Screen against GPDO Class A and listed-building constraints before locking the final perimeter height. |
| Gate package is upgraded for security only | Stronger locks and controls can be added without checking emergency-egress compatibility | Safety conflict at handover and avoidable operations risk. | Cross-check each gate control with emergency access/escape requirements and test operational procedures. |
| Public-facing temporary works rely on fence line alone | One perimeter line is sufficient even where local climb points remain | Residual trespass exposure through ladders, scaffold interfaces, or gap points. | Use layered controls: continuous perimeter fencing, local fencing at vulnerable interfaces, and out-of-hours access suppression. |
Evidence gaps to treat as open risks
These items were reviewed in this update and remain partially unresolved in reliable public data.
| Topic | Status | Why | Minimum action |
|---|---|---|---|
| Installed cost benchmark by region and threat class | Pending confirmation / no reliable public dataset | Public prices are usually incomplete and exclude gates, foundations, and local install constraints. | Build a scope-matched three-supplier RFQ set and compare total installed cost instead of panel-only rates. |
| Independent cut-delay data for specific 358 SKUs | Partially available | Public marketing sheets rarely publish full test attack logs or full-scope conditions. | Request certificate numbers, issuing lab, rating scope, and tested configuration for each quoted system. |
| Storm-event failure statistics for temporary 358 fleets | Publicly fragmented | No consolidated regulator dataset was found during this April 2026 review. | Use site-specific wind assessment, method statements, and post-event inspection criteria in contract terms. |
| Open benchmark combining fence + VSB/HVM package cost | Pending confirmation / no reliable public dataset | Public data usually separates fence product pricing from civil works and vehicle mitigation scope. | Split RFQ into fence scope and vehicle-mitigation scope, then compare total installed package cost. |
| Recent public benchmark for welded-mesh delay performance by threat class | Pending confirmation / limited open data | Public government references provide useful baseline context but not a modern, cross-jurisdiction, SKU-level delay dataset for direct procurement ranking. | Require project-specific certification/test evidence and keep open-source delay figures as screening context only. |
No-evidence-no-claim rule
Where public evidence is incomplete, this page marks the issue as pending instead of turning assumptions into facts.
Public standards and guidance are enough to define boundary conditions and specification logic, but not enough to publish a trustworthy universal installed-cost benchmark.
For final buying decisions, add supplier certificates, drawing sets, and site-specific engineering checks to this evidence layer.
Compare before you commit
Anti climb fence is a strong answer, but not the only answer.
Use this table when a buyer asks whether 358 mesh panels are better than standard temporary fence, chain link, or another welded mesh approach.
| Option | Best for | Why buyers choose it | Main tradeoff |
|---|---|---|---|
| 358 mesh panels / anti climb fence | Permanent or premium temporary security perimeters | Difficult to climb quickly, hard to cut fast, keeps camera sightlines | Heavier and usually pricier than standard temporary fence or basic chain link |
| Standard temporary fence panels | Fast, short-duration site separation | Quick to deploy and easier on budget | Lower anti-climb performance and a less defensive visual signal |
| Chain link security fence | Budget-sensitive permanent boundaries | Flexible, familiar, and cost-effective over long lines | More footholds and often a weaker anti-climb story without toppings or add-ons |
| Other welded mesh systems | Sites that want welded appearance without full 358 specification | Can balance looks, rigidity, and cost | May not provide the same climb-delay geometry as a true 358 format |
Warehouse perimeter upgrade
Existing chain link looks weak around a visible loading yard.
358 mesh panels are usually a strong fit because the site wants visibility, deterrence, and better climb delay without moving to solid hoarding.
Short-term construction project with theft pressure
The project needs a fast perimeter, but material theft has already happened nearby.
A temporary 358 deployment can make sense, but only if the team accepts heavier bases, more detailed gate planning, and a higher installed cost than normal temporary fence.
Budget-led low-risk boundary
The buyer wants visual separation first and anti-climb second.
This is where the fit checker often downgrades 358 and pushes the team to compare standard temporary fence or lighter welded mesh before overspending.
Risks and boundaries
The fence only works if the scope is bought correctly.
Most anti climb fence problems are scope-definition problems, not mesh problems. Use this matrix to keep the quote package honest.
| Risk | Trigger | Impact | Mitigation |
|---|---|---|---|
| Over-specifying a low-risk project | Tight budget, short timeline, low attack risk | Higher installed cost with little security upside | Compare 358 against standard temporary fence or lighter mesh before approval. |
| Treating a temporary 358 layout like a standard temp fence job | Windy site, long duration, or heavy gate traffic | Stability issues, redesign, or site rework | Review base mass, bracing, gate details, and engineering assumptions early. |
| Buying on panel price only | RFQ omits gates, posts, finish, or hardware scope | Quote drift and scope gaps after award | Request drawings, post sizes, fixings, finishes, and gate package in the first quote round. |
| Assuming every 358 panel is equivalent | Supplier naming is generic but the drawing is not | Mismatch on width, coating, hardware, or install method | Compare actual aperture, wire architecture, panel layering, post, and finish spec line by line. |
| Treating “358” as proof of certified intrusion delay | Specification uses product nickname without a forced-entry rating target | Security expectation gap between buyer and supplier | Specify the required forced-entry standard and rating band, then align fence and gate evidence to that target. |
| Using 358 mesh as a substitute for vehicle-threat mitigation | Threat model includes VAW or VBIED but procurement only specifies fence | Perimeter may remain vulnerable to vehicle-borne attack despite anti-climb mesh. | Add VSB/HVM controls and stand-off strategy instead of treating fence choice as a vehicle-security control. |
| Assuming impact-rated VSB data also proves vehicle delay resistance | Tender cites one barrier test claim without clarifying impact vs delay | The selected barrier may not hold the vehicle in place after initial contact. | Ask for both impact and delay evidence where vehicle threat is relevant, and map each rating to the exact threat scenario. |
| Treating tested temporary barrier ratings as valid after layout changes | On-site gaps, junctions, or line geometry differ from the tested configuration | Real-world protection can diverge from certification expectations. | Require tested-formation drawings and keep temporary barrier gaps within stated guidance constraints before acceptance. |
| Writing new CNI tenders around legacy CSE wording | Specification language was copied from older templates | Misaligned standards pathway and avoidable procurement/approval delays. | Update tender language to current NPSA-aligned standards and map each clause to a defined threat. |
| Assuming LPS rating includes covert or climb/tunnel pathways | Rating copied into tender without scope-exclusion review | Residual attack paths remain outside tested performance claims. | Pair forced-entry rating with anti-scale, anti-burrow, surveillance, and response requirements. |
| Applying the wrong coating standard across components | Quote says “galvanized” but does not identify per-component standard scope | Inconsistent durability assumptions and dispute risk at acceptance | Request coating standard references separately for posts, mesh wire, and hardware, then check exclusions and test method scope. |
| Assuming fence height is automatically permitted in every jurisdiction | Design freezes at 2.4 m+ without jurisdiction-specific planning review | Procurement delay, redesign, or forced scope change after ordering | Run an early permit-screening gate (for England, GPDO Class A thresholds and exceptions) before issuing the final RFQ. |
| Locking down access points in a way that conflicts with emergency egress | Security gate hardware is specified without cross-checking fire/evacuation routes | Safety non-compliance and operational failure during emergency conditions | Validate each gate against emergency-egress/access requirements and test operating procedures before handover. |
| Overestimating fence-only delay performance | Threat model assumes geometry change alone provides meaningful hold time | Residual intrusion risk because detection/response layers are under-specified | Treat fence hardware as one layer only and define integrated detection, response, clear-zone, and patrol controls. |
Buying checklist
Questions to send before the first RFQ round.
A serious 358 mesh fencing panels quote is more than a price per panel. Ask these questions up front and the quote comparison becomes much cleaner.
| Topic | Ask for | Why it matters |
|---|---|---|
| Geometry | Confirm aperture, wire diameter, and panel width in the drawing pack. | That is what tells you whether the quote is a true 358-style anti climb fence or only similar terminology. |
| Support package | List posts, base or foundation detail, bracing, and hardware separately. | Most scope drift happens outside the panel price. |
| Finishes | State galvanized-only or galvanized plus powder-coat, with color if needed. | Appearance and corrosion expectations change the real comparison between suppliers. |
| Gates | Quote pedestrian and vehicle gate widths with locking and hinge details. | Gate scope often decides whether the perimeter is actually deployable on site. |
| Proof | Request product sheets, project references, or test references tied to the exact system being quoted. | Generic marketing language is not enough when the site has real security consequences. |
What to do if the checker says “conditional fit”
Do not force 358 into the spec yet. Use that result as a prompt to compare standard temporary fence, chain link, and lighter welded mesh against the same site conditions.
Adjacent pages worth opening next
These links keep the anti climb fence page distinct while still connecting it to adjacent buying tasks.
Temporary fence panels
Use this when you need to compare 358 mesh panels against the faster, lower-security temporary default.
Fence gates
Gate package quality often determines whether an anti climb fence layout works in practice.
Fence clamps and couplers
Hardware scope matters when buyers compare temporary and fixed anti climb fence packages.
Sources
Public references used for the report layer.
The page uses current public manufacturer pages because this topic is product-driven and spec language changes over time. If your project depends on a compliance framework or a utility standard, verify the exact project document before ordering.
| Source | What it supports | Date |
|---|---|---|
| NPSA: Security Fences and Gates | Defines perimeter-design guidance, panel-height baselines (2.4 m and 3.0 m), temporary-system limitations, CSE removal from approved list (effective January 1, 2026), and CNI fence-type boundary language. | Accessed April 6, 2026 (last updated August 14, 2025) |
| NPSA: Protection from Forced Entry | Frames forced-entry procurement around threat, attacker profile, and required resistance time; stresses that no single standard is exhaustive. | Accessed April 6, 2026 (last updated January 2, 2026) |
| NPSA: Protection from Forced Entry Standards Guide (Version 2) | Adds an actionable LPS mapping: A1-E20 for one active adversary and F1-H20 for two active adversaries, with sector-specific standards context. | Accessed April 6, 2026 (Version 2, June 2024) |
| NPSA: Hostile Vehicle Mitigation (HVM) | Provides vehicle-borne threat context and states that vehicle attack risk needs dedicated mitigation; includes public attack trend markers (140+ incidents since 2014 and high no-barrier prevalence). | Accessed April 6, 2026 (last updated March 17, 2026) |
| NPSA: Considerations for Temporary Vehicle Security Barriers | States barrier ratings apply to tested conditions, recommends both impact and delay ratings for temporary barriers, and gives gap-control guidance (no wider than 1.2 m). | Accessed April 6, 2026 (last updated October 7, 2025) |
| LPCB RedBook Live: LPS 1175 Issue 8.2 | Defines security ratings as tool set A-H plus delay 1/3/5/10/15/20 minutes, warns there is no direct correlation to other standards, and lists scope exclusions including vehicle impact, explosion, ballistics, surreptitious entry, and scaling/tunnelling resistance. | Accessed April 6, 2026 (published September 2024) |
| BSI / ANSI preview: BS 1722-14:2017 | Defines four open-mesh fence categories (general purpose to higher security), wind-load annexes, and states no fence can stop a determined intruder given enough time and tools. | Accessed April 6, 2026 |
| ISO 1461:2022 | Covers hot dip galvanized coatings on fabricated steel articles and explicitly excludes continuously galvanized wire and welded mesh products. | Accessed April 6, 2026 (publication date August 2022) |
| ISO 22343-1:2023 | Specifies impact test methods for vehicle security barriers and records that it replaces withdrawn IWA 14-1:2013 in current standardization. | Accessed April 6, 2026 (published September 2023) |
| WBDG: UFC 4-022-03 Security Fences and Gates | Provides public government baseline context including limited fence-only delay expectations, clear-zone guidance, and the requirement to integrate fence design with wider threat/risk controls. | Accessed April 6, 2026 (publish date October 1, 2013) |
| NPSA: Fences and Gates | States that gate security controls should still satisfy legal emergency egress/access requirements and should be reviewed for effectiveness. | Accessed April 6, 2026 (last updated November 10, 2020) |
| UK Legislation: GPDO 2015 Class A (gates, fences, walls etc.) | Provides England permitted-development boundary conditions and explicit height limits/exceptions for gates, fences, walls, and other means of enclosure. | Accessed April 6, 2026 (UK SI 2015/596, Schedule 2 Part 2 Class A) |
| UK Legislation: CDM 2015 Regulation 18 | Defines legal duties for construction site perimeter identification and/or fencing based on health-and-safety risk. | Accessed April 6, 2026 (revised legislation view) |
| HSE Safety Alert CON1-2018 | Details practical anti-trespass controls for construction interfaces: continuous/fixed perimeter fencing, minimised gaps, and layered controls for vulnerable access points. | Accessed April 6, 2026 (issue date July 11, 2018) |
| Jacksons Security: 358 Securi-Mesh Fencing | Uses 76.2 x 12.7 mm mesh, 4 mm wire, 2519 mm panel width, and standard heights up to 5210 mm. | Accessed April 6, 2026 |
| Betafence: Securifor 358 | Lists 12.7 x 76.2 mm mesh, 4 mm wire, 2518.6 mm panel width, and one-piece panels up to 6 m high. | Accessed April 6, 2026 |
| Zaun: HiSec 358 | Lists 76.2 x 12.7 mm mesh, 4 mm wire, 2515 mm panel width, standard heights up to 5207 mm, and single panels up to 7 m on request. | Accessed April 6, 2026 |
| Zaun: RDS StrongHold S455-358 temporary-system PDF | Public temporary 358 reference showing 2.0 m, 2.4 m, and 3.0 m heights, 455 kg or 910 kg bases, and published design wind speeds by height/base combination. | Accessed April 6, 2026 |
| NPSA CSE archive: Betafence Securifor 358 DS2 | Illustrates a layered 358 variant with four-panel-thick orientation at 90 degrees, useful as a non-equivalence counterexample. | Accessed April 6, 2026 (archived CSE listing) |
| NPSA CSE archive: Cova Securus | Lists a single-layer 4 mm nominal wire 358-style system with explicit post-centre and fixing details for baseline comparison. | Accessed April 6, 2026 (archived CSE listing) |
| NPSA CSE archive: Cova Super6 welded mesh | Shows a related anti-climb family variant with 6 mm vertical wires and BS 1722-14 context, reinforcing that “358” naming is not one architecture. | Accessed April 6, 2026 (archived CSE listing) |
FAQ
High-frequency questions about anti climb fence, 358 welded mesh, 358 weld mesh, and 358 welded mesh fencing.
These answers are written for practical buying decisions rather than glossary-style definitions.
Final action layer
Use the checker output to request a cleaner quote package.
Send perimeter length, install type, target height, gate widths, and whether the project truly needs anti climb fence rather than a standard temporary boundary. That is the fastest way to avoid false “apples to apples” quote comparisons.
Inquiry email
Best for quotations, custom sizes, bulk orders, and delivery questions.