Total Quality for Critical National Infrastructure: building resilience into digital transformation 

Challenge

A critical national infrastructure organisation’s systems were changing faster than its scheduled security testing, with lead times of two weeks to a month before a test could begin.

Approach

Building on a five-year penetration testing relationship, Resillion assessed how security testing, quality engineering and release assurance could connect directly to the client’s change management process.

Results

Phase one has given the client a structured roadmap towards risk-led assurance, with a proposed model that could cut test scheduling from up to 30 days to as little as three to four.

The client

The client is a critical national infrastructure (CNI) organisation responsible for managing safety-critical services in a highly regulated environment. Its work depends on complex sites, specialist systems and long-term operational programmes where service continuity, security, compliance evidence and public confidence all matter. 

As the organisation modernises its digital estate and moves towards cloud-first ways of working, its assurance processes need to keep pace with frequent system updates, approved changes and evolving operational demands. 

The client also needs to be confident that critical services remain stable as technology and delivery models change and be able to show clear evidence of robust risk management. 

energy substation

The challenge: assurance needed to keep pace with change

Penetration testing is often used to check whether an application, system or infrastructure component could be exploited by an attacker. But for this client, the issue was not whether testing happened. It was whether systems, devices and data were secure the day after the test was complete. And the day after that. 

The organisation had worked with Resillion on penetration testing for around five years, so the challenge was not a lack of security testing. The issue was that its established model was still largely based on scheduled, point-in-time assessments. 

A system might be tested and signed off on a given day. Then a legitimate operational change could follow – a workflow update, a configuration change, a move to cloud infrastructure or a change raised through the client’s own control board. Each change might be approved and necessary, but it could also affect the risk profile of something that had already been tested. 

That created a gap between the pace of change and the pace of assurance. The client needed a way to connect security testing more closely to real operational change, so testing activity could respond to what had changed, not just to the next scheduled assessment. 

In a regulated CNI environment, that gap also made evidence harder to maintain. The organisation needed to show that risks were being actively managed over time, not just assessed at isolated points. While the programme was not driven by an immediate regulatory mandate, stronger assurance evidence would help support internal governance, regulatory conversations and compliance expectations. 

When a system needed testing, the process still involved several manual steps, from scoping the work and gathering information to reviewing requirements, preparing a proposal, obtaining approval and scheduling the test. Depending on the circumstances, this could take between two weeks and a month before testing was ready to begin. 

It also needed greater confidence that releases would not disrupt critical functions. If a deployment introduced a functional regression or other issue, the organisation might need to roll back, creating disruption and operational risk. Security testing alone could not confirm that critical services continued to work as expected. 

The challenge was therefore broader than penetration testing. The client needed a more connected assurance model, bringing cyber security, quality engineering, change management and release processes together to support a more continuous, risk-led approach. 

The client’s ambition also went beyond making assurance more dynamic and continuous. They wanted a more end-to-end model that connected testing, reporting and remediation, so teams could receive practical support to address identified issues rather than simply being told what needed to change.

Our approach: connecting cyber security, quality and change processes

Resillion delivered a discovery and gap-analysis programme to assess how the client managed change, testing, release assurance and evidence of testing and risk management. The aim was to identify the gaps, dependencies and process changes that needed to be addressed before a more responsive approach to assurance could be introduced. 

Resillion had already been providing penetration testing support to the organisation for several years. That existing relationship gave the team a practical understanding of the client’s environment, the way assurance work was commissioned and the pressure on internal teams to keep critical services moving while maintaining strong evidence of security and control. 

Resillion brought cyber security and quality engineering expertise together from the outset. Rather than treating the engagement as a standalone penetration testing review, the team examined assurance across the delivery lifecycle, from change approval and release planning through to testing, remediation, reporting and stakeholder evidence. 

Expert identifying software security vulnerabilities

The completed phase-one assessment covered eight connected areas:

1

Change management: reviewing how changes were approved within the organisation and how assurance could be linked to the change process. 

2

System criticality and risk prioritisation: considering how the importance and risk of different systems should influence testing. 

3

Security testing and pre-scoping: reviewing test definitions, predefined test packages and statements of work. 

4

Quality engineering: assessing existing manual and automated testing capabilities. 

5

Findings contextualisation and remediation support:  assessing how findings are currently managed and identifying the processes, responsibilities and support needed to help teams address issues effectively. 

6

DevSecOps advisory: considering the processes and capabilities supporting delivery. 

7

Release assurance, improvements and sign-off: reviewing how changes were validated and approved for release. 

8

Metrics and governance reporting: identifying the information needed to demonstrate assurance to stakeholders. 

By considering these areas together, Resillion helped the client build a clearer picture of how risks, responsibilities and assurance activities connect across cyber security, quality engineering, release management and operations.

Results: Helping a critical national infrastructure organisation plan the move to continuous, risk-led assurance

Phase one is complete, giving the client a structured assessment of its existing assurance processes and a clearer direction for improvement. 

The work delivered three key outcomes: 

  • A clearer view of process gaps and dependencies: identifying where change management, testing, remediation and release processes need to evolve to support more continuous assurance. 
  • A more joined-up view of security and quality: bringing cyber security and quality engineering together to assess the client’s assurance needs across the delivery lifecycle. 
  • A foundation for future improvements: identifying where risk-based testing, predefined test packages and automation could help the client respond more effectively to change. 
  • A set of actionable recommendations: specific guidance on how the organisation should change their release processes to incorporate risk-based security testing in an effective and efficient manner. 

This gives the client a clearer understanding of what needs to change, which capabilities need further development and how it could move towards a more responsive assurance model. 

Phase two is under consideration. 

Enhance your applications and platforms with AI quality assurance advisory

Future phases: moving towards continuous, risk-led assurance

The proposed next phase would put the recommendations into practice, bringing assurance closer to the client’s day-to-day change and release processes. 

Linking testing to approved changes 

The proposed cyber security model would connect pen testing to the client’s change management process.  When an approved change is recorded, it could trigger a risk-based review to determine whether security assurance is needed and, if so, which type and level of testing is appropriate. Depending on the change and associated risk, this could range from targeted checks to a more comprehensive penetration test. 

This would allow testing to respond more directly to system changes and associated risks, rather than relying solely on scheduled assessments. Manual penetration testing would remain important where specialist assessment is needed, supported by repeatable processes and, where appropriate, mapping against recognised frameworks such as MITRE. 

Automating checks after deployment 

The proposed quality engineering model includes automated smoke and sanity testing to check that core application functions continue to work after deployment. 

Checks could cover whether an application starts correctly, users can log in and critical user journeys behave as expected. Over time, reusable automation packs could be developed for priority systems and run after future releases to provide repeatable evidence that key functions remain stable. 

Bringing assurance earlier into the lifecycle 

Future improvements would also aim to bring security and quality considerations into requirements, project planning, change management and release readiness, rather than relying heavily on checks close to go-live. 

This would give teams better visibility of potential issues and help integrate assurance into the way systems are designed, changed, tested and released. 

Expected benefits 

Once implemented, the proposed model could deliver several improvements: 

 

Person managing Synthesized test data platform in server room

Faster test scheduling

Potentially reducing the current lead time of 14-30 days down to 3 to 4 days, once the necessary processes and triggers are in place.

More reliable data flows across critical business systems

More responsive testing

Allowing relevant changes to trigger appropriate checks instead of waiting for the next scheduled assessment.

People discussing QC on Demand walking in office

Greater release confidence

Using automated checks to confirm that critical functions continue to work after deployment.

User testing software on laptops

Less manual effort

Reducing repeated scoping and commissioning through predefined test packages and automated triggers.

Group of professionals standing together reviewing laptop

Stronger assurance evidence

Giving the client's information security team clearer evidence to support internal stakeholders, regulators and compliance requirements.

Portrait of smiling data center specialists using 2026 01 11 10 56 09 utc scaled

Better use of specialist resources

Potentially reducing repeat manual testing effort by around 10% of an FTE annually, equivalent to approximately 20 working days for this project.

Data behind compliance decisions

Clearer remediation

Supporting more consistent reporting of findings and guidance on addressing identified issues.

These are anticipated benefits of the proposed future model. The scheduling and resource-saving figures are estimates that depend on successful implementation. 

Total Quality: connecting assurance across the lifecycle

Quality, security and delivery are closely connected, but they often come together only at key release points. Resillion’s approach brought these disciplines into a single assessment, helping the client understand how its processes and capabilities could work together to manage risk more effectively. 

That mattered because the client was not dealing with abstract systems in isolation. The work supported a real operating environment, where changes to applications, workflows and supporting infrastructure could have knock-on effects for service continuity, safety, regulatory evidence and public confidence. 

For critical national infrastructure organisations, assurance needs to keep pace with changing systems and risks. By connecting cyber security, quality engineering and change processes, Resillion helped the client establish a practical foundation for moving beyond periodic testing towards a more continuous, risk-led approach. 

Dedicated teams supporting your project

Build a more connected assurance model

Does your assurance approach keep pace with change? 

Resillion helps organisations connect cyber security, quality engineering and automation across the delivery lifecycle. From risk-led testing and release confidence to continuous assurance and compliance evidence, we help you strengthen assurance while supporting digital transformation. 

Talk to Resillion about building a more connected assurance model.