Edizione originale in inglese. La traduzione di questa nuova analisi è in preparazione.
Policy & leadership
China’s State Visits to Europe: Shared Venues, Separate Security Responsibilities
Using Xi Jinping’s May 2024 visit to France to examine delegation security, supplier access, meeting technology and the limits of public evidence.
In this analysis
- A documented visit with an important evidential boundary
- Hosting and visiting are different responsibilities
- Map the information before designing the room
- Interpretation and audiovisual systems are part of the boundary
- Define a protocol for unexpected equipment
- Keep delegation workspaces distinct
- Hospitality does not provide technical assurance
- Protect support personnel without stereotyping them
- Limit the usefulness of incidental observations
- Rehearse a translation-file incident
- Manage an incident across organisations
- A useful conclusion without invented tradecraft
A documented visit with an important evidential boundary
The Élysée documents Xi Jinping’s state visit to France in May 2024. Its record of the 6 May trilateral opening identifies the Chinese and French presidents and the President of the European Commission as participants. [1][2] These public records establish the diplomatic setting. They do not establish how Chinese protective personnel configured devices, examined rooms or operated communications. This article therefore uses the visit as context for an explicitly hypothetical security design. It does not attribute secret procedures to China, name an undocumented intelligence unit or infer a cyber incident from the presence of a delegation.
Hosting and visiting are different responsibilities
French police describe the Service de la protection, or SDLP, and include protection of visiting foreign heads of state or government among its responsibilities. [3][4] That public role should not be mistaken for complete visibility into a visiting delegation’s internal information systems. Our policy analysis distinguishes host protection, venue operation and delegation information assurance. Cooperation is essential, but each organisation should retain clear ownership of its own sensitive information and access decisions. A jointly attended event does not require every participant to share the same devices, administrators or confidential preparation materials.
Map the information before designing the room
Our recommended first step is a meeting information map. Separate what is intended for public release, what all participants may receive, what remains internal to one delegation and what is restricted to a smaller negotiating group. Identify who approves a document’s movement between those categories. This prevents an apparently harmless convenience, such as one shared folder for the whole event, from silently exposing draft positions. Apply the same discipline to agendas, seating plans and participant contact details: they may have different audiences even when they concern the same meeting.
Interpretation and audiovisual systems are part of the boundary
Microphones, interpretation channels, conferencing software and recording services process the substance of a meeting. Our proposed assurance checklist asks who operates them, who can connect remotely, whether recording is enabled and where recordings or transcripts would be stored. Agree these conditions before participants arrive. This is not evidence that any such system was misused during the 2024 visit. It is a practical consequence of including meeting technology in the information inventory. A physically restricted room does not, by itself, establish that its connected services have equally restricted administration.
Define a protocol for unexpected equipment
A supplier may need to replace a failed laptop, display adapter or conference unit at short notice. Our recommendation is an authorised change route with a technical owner, an inventory update and a decision about whether the replacement can handle the intended information. A familiar logo or helpful employee should not substitute for that process. Equally, the procedure must provide a usable fallback so that staff are not pressured into improvisation. For lower-sensitivity functions, a replacement may be acceptable; for a restricted discussion, postponing the technical feature may be the appropriate choice.
Keep delegation workspaces distinct
In our proposed model, shared event services carry only information approved for the shared audience. Internal deliberation uses each delegation’s own approved environment and access controls. Temporary collaboration accounts expire at the end of the agreed need, with no inherited access to unrelated corporate or government repositories. This is a recommendation about compartmentation, not a claim that a particular delegation uses a named platform. The same principle applies to international corporate negotiations: interoperability should be designed around the required exchange, not achieved by opening a broad internal workspace to everybody attending.
Hospitality does not provide technical assurance
A prestigious hotel can offer excellent service while remaining outside a visitor’s control. NPSA advises high-risk individuals to protect sensitive items and not rely on hotel safes for them. [5] Our recommendation is to establish an approved custody arrangement, minimise the material carried and identify where sensitive work can actually take place. Do not classify a hotel as safe or hostile based on branding, nationality or price. Evaluate the specific service and intended activity. A room suitable for sleeping may not be suitable for a restricted conversation or unattended official equipment.
Protect support personnel without stereotyping them
Interpreters, schedulers, technicians and liaison staff can encounter sensitive material because their jobs require it. Our recommended approach is role-based access, clear confidentiality instructions and a respectful reporting route. Avoid nationality as a substitute for evidence of misconduct. A person’s access, contractual responsibilities, training and observed actions are the relevant operational questions. Where host and visiting staff work together, agree who receives a concern and how it can be investigated without unnecessary disclosure of personal information. Treat people as contributors to assurance rather than as an undifferentiated insider threat.
Limit the usefulness of incidental observations
Our scenario assumes that some event information will be publicly visible or observable to service providers. The aim is to avoid adding unnecessary detail. Share schedules with the people who need them, use approved channels for late changes and avoid posting photographs that reveal documents or screens. This does not imply that every observation is an intelligence operation. It reflects the cumulative value of ordinary data. A policy that separates public communications from operational coordination reduces accidental exposure while allowing the diplomatic programme and legitimate press activity to proceed.
Rehearse a translation-file incident
Consider a hypothetical interpreter receiving a revised briefing file through a personal messaging account minutes before a meeting. The proposed response is to verify the sender through the established liaison, obtain the document through the approved exchange route and open it only in the designated environment. The organiser should provide a rapid alternative if that route fails. Record who can approve a change to the process. This exercise tests authenticity, document handling and time pressure together without requiring any speculation about the protective methods used by Chinese or European security services.
Manage an incident across organisations
Our recommended incident agreement identifies contacts, notification thresholds, evidence custody and the minimum information needed for cooperation. If a shared conference service is suspected of compromise, each organisation needs enough detail to protect its users without receiving another delegation’s confidential content. Preserve relevant logs and document the limitations of the available evidence. Avoid public attribution before a defensible assessment exists. The practical difficulty is that one party may need rapid continuity while another needs preservation for investigation; those priorities should have a negotiated decision route before the event.
A useful conclusion without invented tradecraft
The public record does not let an outside writer reconstruct the Chinese president’s protective communications or secret-service procedures. It does support a more useful policy discussion about a real diplomatic event involving multiple institutions. Our conclusion is that successful cooperation requires explicit boundaries: shared services have an agreed purpose, sensitive internal work retains separate authority, and exceptions have accountable owners. For a CISO, the transferable test is whether a team can explain who controls each service and what happens when that service changes. Ceremony and mutual respect are compatible with disciplined information assurance.
References
- Élysée · Xi Jinping’s state visit to France, May 2024
- Élysée · Opening of the trilateral meeting, 6 May 2024
- French National Police · The protection service, SDLP
- French National Police · SDLP protection responsibilities
- NPSA · Protect sensitive information
Original editorial analysis and paraphrases. Recommendations are distinguished from documented facts; references do not imply institutional endorsement.