Ask what has actually been demonstrated
An airport technology proposal may combine approved equipment, new software, revised staff roles and a different passenger layout. These elements do not automatically inherit assurance from one another. Evidence should identify the tested configuration, the intended use and any conditions attached to the result. A claim without those boundaries is difficult to interpret.
Assurance is not a single certificate or a marketing adjective. It is an organised explanation of why a particular deployment is acceptable for its purpose, supported by relevant evidence and accountable decisions. The scope may include aviation security requirements, data protection, accessibility, cybersecurity and continued operational support.
Describe the data before defending its use
Different checkpoint systems handle different information. Equipment status logs, queue observations, baggage images and identity records should not be treated as one undifferentiated category. Some information may be personal data because it identifies a person directly or can reasonably be linked to them. The assessment depends on the actual design and context.
A useful starting point is a clear data map: what is collected, for what purpose, where it goes, who can access it and how long it remains. Avoid assuming that all screening uses facial recognition or that every image is retained. Equally, do not assume that a system is anonymous simply because names are absent from its main display.
Assess necessity and proportionality
Where personal data is involved, the organisation needs an appropriate legal basis and a clear purpose. Data protection impact assessments are required in specified high-risk circumstances; they are not merely a procurement checklist. An assessment should consider risks to people and identify measures that address those risks before deployment.
Useful questions include whether the same operational need can be met with less data, whether access is limited by role and whether retention is justified. A policy should describe what happens in practice, including support access and deletion. Consent should not be casually presented as a universal answer in a setting where passengers may have limited practical choice.
Demonstrate accessibility in use
Accessibility needs evidence from real tasks, not just a statement that a system is easy to use. Consider passengers with mobility, sensory or cognitive disabilities, people travelling with assistance and people who need more time to process instructions. Staff-facing interfaces also need to be usable by the people expected to operate them.
Digital guidance can draw on the World Wide Web Consortium’s Web Content Accessibility Guidelines. Physical services require additional assessment; compliance of a webpage does not prove that a checkpoint layout is accessible. Involve affected users, review the assistance journey and check whether changes move a difficulty elsewhere rather than removing it.
Protect the connected operational environment
Networked equipment introduces questions about access, updates, supplier support and incident response. These are organisational responsibilities as well as technical ones. A supplier should be able to explain how the system is maintained and how changes are controlled without exposing sensitive operational details publicly.
General frameworks such as ISO/IEC 27001 and the NIST Cybersecurity Framework can help structure information security work. They do not, by themselves, establish that a particular screening device meets aviation requirements. Assurance should connect each claim to the relevant evidence and make clear who owns the residual risk.
Use an evidence register
| Area | Evidence question | Accountability question |
|---|---|---|
| Approved use | Which configuration and purpose were assessed? | Who authorises changes? |
| Personal data | What is collected, retained and shared? | Who owns the processing decision? |
| Accessibility | Who tested the actual tasks? | Who resolves identified barriers? |
| Support | How are updates and incidents managed? | Who coordinates suppliers and operations? |
Keep assurance alive after launch
Deployment is not the end of the evidence process. Software changes, supplier changes, new uses for data and altered passenger workflows can all affect the original assessment. Change control should identify when evidence needs to be refreshed and when further approval or consultation is necessary.
Monitoring should include complaints, accessibility feedback and staff experience alongside technical indicators. Public information should remain accurate and understandable, with a route for questions and correction. The aim is justified confidence: a system that can explain its purpose and limitations, demonstrate responsible operation and respond when the evidence changes.
Return to human oversight for the role of trained staff, or read our website privacy notice for the separate question of how this publication handles information.
Sources and further reading
- ICO UK GDPR guidance — accountability, lawful processing and impact assessment.
- European Data Protection Board — European data protection guidance.
- W3C Web Content Accessibility Guidelines 2.2 — digital accessibility.
- ISO/IEC 27001 — information security management.
- NIST Cybersecurity Framework — cybersecurity risk management.
- European Union Agency for Cybersecurity, ENISA — cybersecurity resources.
- UK National Cyber Security Centre — organisational cybersecurity guidance.