Connectivity, support, hosting and security have different constraints. Start with critical services, data and acceptable recovery time.
| Need | Questions to examine |
|---|---|
| Support | Covered equipment, support hours and authorised access. |
| Cloud and telecoms | Capacity, contractual location, dependencies and exit terms. |
| Cybersecurity | Assessment scope, confidentiality, deliverables and remediation follow-up. |
| Incidents and responsibility | Describe a fictional incident and ask who receives it, assesses urgency and restores service. Separate acknowledgement time from resolution time. Record dependencies and escalation procedures rather than comparing the word “support” alone. |
Availability commitments need a period, measurement method and exclusions. An untested backup does not demonstrate recovery capability.
No. Support restores or maintains a service; an audit examines risks within an agreed scope. Ask about methodology, relevant qualifications and how findings will be addressed.
Read the related practical guide · Explore all directory resources
FRENCH DIGITAL SOCIETY only publishes identifiable organisations and official resources. Inclusion is not a certification or ranking; check references, availability, legal information and contractual terms before appointing a provider.
1 resources shown
Select resources in the list to compare their role and scope. Compare your shortlist on screen with your team. Selection stays on this page, with no account or browser storage; filtering does not clear it.
Inclusion does not establish quality or availability. Check identity, scope, source and relevant evidence before using a resource.
Official online assistance service for guidance when facing a cybermalicious situation. Describe the situation on the official site; the service and its diagnosis do not replace your internal incident procedure.
Use it for: Obtain diagnosis and guidance from the official public service when cybercrime is suspected.
Read uses, limits and checks →
Source: 17cyber.gouv.fr · Link checked
Open the official site
National cybersecurity resources covering prevention, good practice and incident response.
Use it for: Use the guidance to build checks for access, updates, backups and incidents.
Read uses, limits and checks →
Source: cyber.gouv.fr · Link checked
Open the official site
Guidance and tools from France’s data-protection authority for organisations.
Use it for: Consult when a project collects personal data; compare its purpose, notices and safeguards with CNIL guidance.
Read uses, limits and checks →
Source: www.cnil.fr · Link checked
Open the official siteFirst steps, checklists and practical answers on data protection for small businesses.
Use it for: Structure an initial processing inventory for a small organisation.
Read uses, limits and checks →
Source: www.cnil.fr · Link checked
Open the official site
Independent guidance for understanding and comparing fibre, ADSL, 4G/5G, satellite, mobile plans and telecoms services in France.
Use it for: Prepare a connectivity comparison based on use and actual eligibility.
Source: www.connexion-internet-france.fr · Link checked
Open the official site
Prevention, victim support and links to local professionals following a cyber incident.
Use it for: Use it for team awareness and the first steps when a cyber incident is suspected.
Source: www.cybermalveillance.gouv.fr · Link checked
Open the official sitePrevention guidance for organising copies, protecting storage and verifying data recovery.
Use it for: Prepare a checklist for a restoration exercise.
Read uses, limits and checks →
Source: www.cybermalveillance.gouv.fr · Link checked
Open the official siteFree cyber-awareness learning for individuals, small-business staff and public-sector workers.
Use it for: Prepare basic awareness of threats and useful security habits.
Read uses, limits and checks →
Source: www.cybermalveillance.gouv.fr · Link checked
Open the official site
Standards and resources from the French interministerial digital directorate, including quality public services.
Use it for: Find public reference frameworks relevant to quality digital services.
Read uses, limits and checks →
Source: www.numerique.gouv.fr · Link checked
Open the official site
Methods and examples for selecting useful automations in small-business processes.
Use it for: Identify a repetitive process and its exceptions before choosing a tool.
Read uses, limits and checks →
Source: www.francenum.gouv.fr · Link checked
Open the official site
Government Digital Service guidance for examining technical dependencies, cloud service value and exit preparedness. UK public procurement requirements are not French obligations.
Read uses, limits and checks →
Source: www.gov.uk · Link checked
Open the official site
Local computer support, maintenance and practical IT assistance.
Use it for: Describe a device or software incident before requesting support.
Source: hardware-software-intervention.fr · Link checked
Open the official site
Private digital intelligence based on open sources, including OSINT, cyber monitoring, due diligence, online reputation and risk analysis.
Use it for: Define an open-source investigation with a question, scope and expected deliverable.
Source: internet-intelligence-service.com · Link checked
Open the official site
Public diagnostic and support services helping companies strengthen cybersecurity.
Use it for: Find a public service suited to an initial security assessment.
Read uses, limits and checks →
Source: messervices.cyber.gouv.fr · Link checked
Open the official site
ANSSI programme offering an initial cybersecurity diagnostic and access to listed cyber advisers.
Use it for: A starting point for proportionate cybersecurity priorities and follow-up actions.
Source: monaide.cyber.gouv.fr · Link checked
Open the official site
B2B guide to tools, APIs, standards and technology partners for tourism and travel professionals.
Use it for: Compare booking, distribution and API tools within a tourism workflow.
Source: www.performance-voyage.com · Link checked
Open the official siteNo resource matches these filters.
A directory entry is a starting point. Match the resource to a defined need, check the original source and compare approaches before committing a budget.
Write down the audience, the problem, the expected result and the deadline. A website redesign, a security review and a data project call for different evidence and skills.
Open the organisation’s own site. Check its legal identity, the scope of its services, the date of its guidance and how to contact it. For public data, review the publisher, licence and update frequency.
Ask providers about relevant work, delivery method, responsibilities, accessibility, handover and support. Compare proposals against the same brief and note what is excluded.
A public resource may help you learn or benchmark; a provider may carry out a mission. Inclusion here does not imply endorsement, affiliation or current availability. Read the expert selection guide for a fuller checklist.
The filters group different types of resources. These notes explain the intended use and the checks to make before acting.
Choose this category when the need concerns a website, application, integration or long-term technical maintenance. Distinguish a delivery provider from a public guide explaining how to prepare the project.
Before you decide: Ask about ownership of the domain and code, accessibility checks, security updates, documentation and the support plan.
Scope the workUse this category for brand messages, visual identity, editorial production and channels. A communication plan should name its audience and the action it is meant to support.
Before you decide: Compare examples of published work, approval steps, usage rights and how consistency will be maintained across formats.
Plan contentExplore this category for infrastructure, connectivity, cybersecurity and operational support. Start with an inventory of essential services and who can access them.
Before you decide: Confirm response arrangements, backups, recovery responsibilities, subcontractors and the boundary between support and security advice.
Review security basicsFind public datasets, APIs and guidance for analysis or a controlled AI experiment. A catalogue entry describes a source; it does not automatically make the data suitable for a decision.
Before you decide: Check licence, update frequency, coverage, missing values, access conditions and whether a human can review consequential outputs.
Choose indicatorsLook here for search visibility, campaigns, email and measurement guidance. Begin with a target audience and a meaningful outcome before selecting a channel.
Before you decide: Ask which baseline will be used, how consent and tracking work, and who will maintain content after a campaign.
Build a content planUse networks to discover organisations, training or support. An entry in a network is a lead for further checking, not proof of availability or quality.
Before you decide: Verify membership criteria where relevant, the person who will carry out the work and the terms of any proposed introduction.
Compare specialistsThe date records an automated availability check, not a guarantee of data freshness, service quality or eligibility. Some publishers block automated requests. For each dataset or API, check the actual licence, update date, coverage and access terms before reuse.
Define the expected outcome and constraints before choosing a service or provider.
Scroll horizontally to read all columns.
| Criterion | What to check | Practical implication |
|---|---|---|
| Need | Specify users, task, data processed and expected result. | A well-known tool can still be unsuitable for your team or data. |
| Evidence | Request a representative demonstration with the access rights future users will have. | An administrator demonstration does not establish usability for everyone. |
| Acceptance criteria | Describe a complete task, its inputs, expected outcome and the person who will validate it. | A delivered screen does not prove the journey works; agree on error handling and support requests as well. |
| Data scope | List essential fields and connect each to a service purpose. | Broader collection complicates management without necessarily improving outcomes. |
Fictional case: a charity needs a booking tool. It tests a scenario with one user, a cancellation and an export, then checks who can see the data and retrieve the calendar. This exposes terms to settle before wider use.
Describe a real task, required data, who will access them and the expected result. A limited trial against that scenario reveals more than a context-free feature list.
Data minimisation limits personal data to what is necessary for the purpose. CNIL — Minimisation Source consulted on .
