Delivered under CHECK
Testing for public sector and CNI systems is carried out as an NCSC CHECK company, within the scheme rules.

IT Health Checks and penetration testing under the NCSC CHECK scheme, for UK public sector bodies, their suppliers and operators of critical national infrastructure.
Government departments, local authorities, NHS bodies and their suppliers are often asked to show that a system has been independently tested before it goes live, connects to a shared network or handles official information. An IT Health Check (ITHC) is the usual way to provide that evidence.
GIFGIF is an NCSC CHECK company. CHECK is the National Cyber Security Centre scheme that approves companies to carry out authorised penetration testing of public sector and critical national infrastructure systems. We are also CREST accredited and certified to ISO/IEC 27001, so the way we handle your data and findings meets the standard public sector buyers expect.
An ITHC is scoped with the system owner and, where relevant, the accreditor or senior risk owner. The report sets out what was tested, each finding with its significance and a practical remediation route, giving you a basis for a remediation action plan and the conversation with your assurance team.
No permission. No test.
Authorisation. Testing requires written authority from the system owner, agreed targets and rules of engagement. An ITHC is a point-in-time assessment, not a guarantee of security or of accreditation. Remediation remains with the system owner; any retesting must be separately confirmed.
Assurance your accreditor will recognise. Public sector assurance teams need testing carried out under the right scheme and reported in a form they can use. We deliver CHECK work within the NCSC framework and explain the results for technical owners and risk owners alike.
Testing for public sector and CNI systems is carried out as an NCSC CHECK company, within the scheme rules.
Coverage is agreed with the system owner and, where relevant, the accreditor or senior risk owner before testing begins.
Each finding comes with its context and a practical remediation route, structured to feed a remediation action plan.
The work is defined by the systems and applications agreed for this assessment. These descriptions do not expand that scope.
Agree the systems, interfaces and connections the assurance need actually covers.
A typical ITHC may cover internet-facing services, the internal network, end-user devices, servers, directory services and the applications that sit on them. Where a system connects to a shared government network, such as the Public Services Network where that still applies, the connection points and controls around them are included in scope.
Coverage is agreed in writing before testing starts. Where an accreditor or customer has set specific requirements, the scope reflects them so the report answers the question they will ask.
Work for public sector and CNI customers is carried out as a CHECK company, within the scheme rules.
Many public sector buyers specify CHECK for systems that handle official information or support essential services. Commissioning a CHECK company means the testing is carried out within the NCSC framework, with the handling and reporting standards that come with it.
Where a customer requires CREST rather than CHECK, or both, the same engagement can be framed to meet either requirement. We confirm which scheme applies during scoping.
Give technical owners and risk owners a report each can use.
Each finding describes the issue, where it was observed, its potential significance and a recommended remediation route. A summary sets out the overall picture for senior risk owners, without the technical detail they do not need.
The report is structured so it can feed directly into a remediation action plan. Any retest of fixed issues is agreed separately once remediation is complete.

Written authorisation, identified targets and agreed rules of engagement are prerequisites. Activity stays within that scope.
From the brief to useful security findings. We agree the objective, written authority and rules of engagement before assessing the named systems and explaining the results.
We clarify the decision, parties or systems in scope, intended use and lawful purpose of the work.
Written permission, identified targets, exclusions and rules of engagement are established before testing.
Information is considered for source, date, relevance and corroboration; uncertainty is not converted into a conclusion.
The account explains what was observed, what it may mean, what remains unresolved and the limits of the work.
When an IT Health Check is usually needed. Examples to help frame an enquiry; these are not case histories.
A department or supplier may need independent testing before a service handling official information is accepted into use.
An organisation connecting to a shared public sector network may be asked for an ITHC as part of its compliance evidence.
A public body may commission a yearly ITHC to support ongoing accreditation and show progress on earlier findings.