Welcome to our

Cyber Security News Aggregator

.

Cyber Tzar

provide a

cyber security risk management

platform; including automated penetration tests and risk assesments culminating in a "cyber risk score" out of 1,000, just like a credit score.

Ending NPSA testing framework and its effect on security specifiers

published on 2025-10-02 11:51:05 UTC by Eve Goode
Content:

SJUK hears exclusively from Jacksons Fencing about the importance of prioritising proven and certified solutions ahead of the NPSA’s withdrawal of its testing framework.

The National Protective Security Authority (NPSA) announced last month that from 1 January 2026, fencing and gates will be removed from its Catalogue of Security Equipment (CSE).

The organisation also stated that it is no longer testing these products against the Manual Forced Entry Standard (MFES).

At first glance, this may seem like a procedural update, however, in practice, it marks a major shift for architects, security consultants and specifiers responsible for protecting the UK’s critical national infrastructure (CNI) and other high-risk sites.

For years, NPSA approved fencing was a trusted benchmark for high assurance projects, however, following on from its removal this will leave a gap and potential confusion about what ‘secure’ really means.

Why BS 1722 alone is not enough

In its announcement, NPSA referenced BS 1722, the long-standing British Standard for fencing, although it is important for basic compliance, BS 1722 has clear limitations.

Unlike robust third-party schemes, BS 1722 relies solely on self-certification where manufacturers can claim compliance by issuing their own statement of conformity with no independent testing or audits to verify performance.

For high security sites where hostile threats are a concern, this offers little real-world reassurance and as a result, very few serious security projects will rely on BS 1722 alone.

The role of LPS 1175

For true independent verification, specifiers often turn to the Loss Prevention Certification Board’s (LPCB) globally recognised LPS 1175 standard.

LPS 1175 classifies products from A1 (formerly SR1) through to H20, grading them according to how long they can withstand specific levels of forced entry.

The scheme ensures:

  • Independent, controlled testing of products
  • Annual audits to maintain consistent production quality
  • Clear communication of what threat level a product can resist

While highly effective, LPS 1175 doesn’t guarantee that a fence or gate will perform correctly once installed. Installation quality and ongoing maintenance also play vital roles, as well as areas not covered by product certification alone.

The rise of online sales of LPS 1175 certified fencing highlights this risk. Without direct oversight from product experts, customers may not receive essential drawings, guidance or support.

If installation doesn’t follow certified designs, the system can’t be guaranteed, which then creates a chain of liability between manufacturers, installers and clients, and in regulated sectors, the consequences of non-compliance can be severe.

“Avoid falling back on outdated specifications”

Cris Francis, Commercial Director, Jacksons Fencing stated: “The NPSA’s decision creates uncertainty for those tasked with protecting high risk sites.

“We must avoid falling back on outdated specifications.

“By working with experts who understand today’s threat landscape, specifiers can ensure the right solutions are matched to the right risks,” he concluded.

A holistic approach to security

True security assurance requires three interconnected elements:

  1. Proven attack resistance – verified through standards such as LPS 1175 or the now discontinued MFES
  2. Comprehensive manufacturer guarantees – covering durability, system longevity and maintenance requirement
  3. Expert advice and installation – ensuring systems perform as intended in real-world conditions

This full lifecycle approach is essential to bridge the gap between ‘certification on paper’ and effective site security.

Jacksons’ position and solutions

With decades of experience in perimeter security for CNI and other sensitive sectors, Jacksons Fencing has long been at the forefront of certified, independently tested solutions.

The company’s Trident range continues to offer resistance to climbing, burrowing and forced entry with many products successfully tested under the rigorous MFES regime.

Even as NPSA withdraws from product testing, these systems remain trusted for protecting critical infrastructure.

Jacksons also offers a wide selection of LPS 1175 certified fencing and gates with 16 systems rated from A1 (SR1) to E10 (SR5), as well as F1 and G1 ratings. This variety enables specifiers to balance security requirements with aesthetics and budget, matching systems precisely to identified risks.

What specifiers should do now

While the regulatory framework is changing, the fundamentals of good security design remain constant. Specifiers should focus on three key steps:

  1. Assess the threat level – Consider likely tools, attack methods and potential adversaries
  2. Choose independently certified systems – Prioritise products tested to robust third-party standards like LPS 1175
  3. Work with trusted experts – Engage manufacturers who provide guidance, installation oversight and support throughout the project lifecycle

“Compatible detection technologies and an effective response”

Richard Flint, BRE Global’s Technical and Commercial Lead for Physical Security, responded, saying:

NPSA’s decision reflects the pressures created by today’s complex threat landscape but their world-class guidance remains vital in helping organisations choose security solutions that align with real risks.

“Forced entry standards such as LPS 1175 are unique in covering fences, gates, turnstiles and more, supporting truly layered perimeter protection.

“It is critical that the performance of delay measures is underpinned by independent third-party assurance, rather than unsupported claims of being merely ‘designed to’ or ‘to the principles of’ and that these measures are paired with compatible detection technologies and an effective response to deliver robust, end-to-end protection,” Flint concluded.

The Risks of complacency

Removing independent testing altogether risks undermining years of progress in promoting rigorous specifications and high-quality installations. Without strong oversight, there’s a danger of substandard products entering the market under claims of ‘designed to’ or ‘built to the principles of’ recognised standards; terminology that lacks enforceable meaning.

This moment should serve as a catalyst for improvement across the security sector. Specifiers, manufacturers and contractors must work more closely than ever to maintain high standards through:

  • Enhanced training and education
  • Better guidance on product selection and installation
  • Stronger emphasis on whole-system performance rather than individual components

Looking ahead

As threats to national infrastructure become more sophisticated, so must the systems designed to defend against them.

Even without NPSA testing, the responsibility to ensure resilient, high performance perimeter security remains.

To ensure security, do not compromise on protection. Whether safeguarding a data centre, government facility, utilities site or other high-risk location, the stakes are too high to take shortcuts.

By basing specifications on real world threats, selecting proven, certified products and working with trusted partners, the industry can continue to deliver secure, reliable perimeters, even in a changing regulatory landscape.

To visit Jacksons Security website, please click this link: www.jacksons-security.co.uk.

Article: Ending NPSA testing framework and its effect on security specifiers - published 25 days ago.

https://securityjournaluk.com/jacksons-fencing-npsa-testing-framework/   
Published: 2025 10 02 11:51:05
Received: 2025 10 03 01:23:27
Feed: Security Journal UK
Source: Security Journal UK
Category: Security
Topic: Security
Views: 9

Custom HTML Block

Click to Open Code Editor