A public tender mentions "SecNumCloud cloud mandatory" to rebuild the town hall site — three WordPress pages. The integrator proposes Cloud Temple at enterprise price. Legal review asks: what sensitive data justifies qualification? Embarrassing answer: none. Over-qualifying costs; under-qualifying exposes.
SecNumCloud is a filter — not a universal public sector badge. Cloud Temple offers qualified offers on precise scopes; brand name alone does not answer a poorly drafted tender.
SecNumCloud: what it is for
ANSSI qualification for cloud limiting extraterritorial access risk — Cloud Act, etc. Relevant for sensitive State workloads, vital operators, defense, certain classified or critical data per doctrine.
Further frame: SecNumCloud criteria, GDPR HDS SecNumCloud.
| Public project | SecNumCloud often required? |
|---|---|
| Town hall brochure site | Rarely |
| Sensitive business IS | Yes if doctrine |
| Patient health data | HDS — sometimes SecNumCloud too |
| Vital operator / OIV | Often yes |
| Public open data | No |
Qualification protects a risk — not a marketing budget.
Cloud Temple and public tenders
Strengths: French sovereignty, infrastructure pricing transparency, possible dual HDS/SecNumCloud qualification per products. Limits: cost, onboarding, no two-euro brochure shared hosting.
Tender checklist: data classification; ANS / RGS framework if applicable; qualification scope required by specs — not competitor mimicry; segregated qualified / non-qualified architecture; documented reversibility and DR.
SecNumCloud versus public alternatives
OVHcloud SecNumCloud, Outscale, 3DS — compare qualification scope, network egress price, support. Cloud Temple if trusted cloud at IS core; OVHcloud if shared plus qualified cloud mix.
The peak: qualification sold, sensitivity unclassified
Decide and move forward without blind spots
Classify data with project owner and CISO, open Cloud Temple attestations for target product, then compare qualified actors on the compare tool. See guides and directory public sector to avoid over-qualification and contractual blind spots.
Frequently asked questions
SecNumCloud mandatory for every local authority?
No — per real sensitivity; tender specs and ANS decide, not buzzwords.
Cloud Temple only SecNumCloud?
No — several qualified; compare scope and price on identical scenario.
Covers whole architecture?
No — per zone and service; analyze backups and administration.
Replaces health HDS?
No — possible complement, not substitution.
Cloud Temple and SecNumCloud matter when sensitivity is proven — not when the tender repeats a buzzword.