Garan Territoires, capability 04

Secured on day one, and every day after.

Most public sector sites are not breached through a sophisticated attack. They are breached because nobody applied a patch for eleven months. Security is an operating discipline, and it is included for the whole contract.

Threats

What actually happens to local authorities.

Not a generic threat catalogue. The four scenarios that put a town hall in the local press.

Ransomware

Local authorities are a favourite target, because services must keep running and backups are often untested. We keep encrypted backups in a separate location and test the restore every year, with the results sent to you.

Defacement

A political message on a town hall homepage is a communication crisis. Hardened administration access, integrity monitoring and rapid rollback keep the exposure window in minutes rather than days.

Denial of service

A flood of traffic during a sensitive news cycle or an election period. Mitigation runs at network level, before requests ever reach your site.

Data exposure

The real damage in the public sector is leaked resident data. Least privilege, encryption, minimal data collection and administrative logging limit both the odds and the blast radius.

Defence in depth

Four layers, none of them optional.

Our practices follow the general security framework and the ANSSI computer hygiene guidelines for public bodies.

01

Edge

  • DDoS mitigation at network level
  • Web application firewall with managed rulesets
  • Bot filtering and rate limiting on forms
  • TLS 1.3 enforced, HSTS, modern cipher suites only
02

Application

  • Hardened CMS with a minimal, audited extension surface
  • Strong authentication and role-based access for editors
  • Security patches applied within committed timeframes
  • Content security policy and standard security headers
03

Infrastructure

  • Isolated environments, no shared hosting for public bodies
  • Encrypted backups stored in a separate location
  • Least privilege access with full administrative logging
  • Hardened LTS operating systems, patched by our team
04

Operations

  • Automated availability and integrity monitoring, 24/7
  • Documented incident response and escalation path
  • Backups restored and verified, not just written
  • Annual restore test, results shared with you
Commitments

Response times, in the contract.

A security promise with no deadline attached is not a commitment. These are the ones we sign for.

Critical security patches

Applied within 24 hours

Other security updates

Applied within 7 days

Availability monitoring

Automated, every minute, 24/7

Incident acknowledgement

Under 1 hour during business hours

Extended support hours

Available as a priced option in the contract

Backup restore test

At least once a year, report shared

Security reporting

Monthly, with patches and incidents listed

Vulnerability disclosure

Documented contact and handling process

If it happens anyway

A plan, written before the incident.

No provider can promise nothing will ever happen. What we can promise is that the day it does, nobody improvises. The response plan is written, shared with your teams and tested, so the first hour is spent fixing rather than deciding who to call.

  1. 1

    Detect and contain

    Automated monitoring raises the alert, and the affected component is isolated.

  2. 2

    Notify you

    Your named contacts are called, with what we know, what we do not, and the next update time.

  3. 3

    Restore service

    Rollback or restore from a clean backup, with a documented recovery target.

  4. 4

    Support the legal side

    If personal data is involved, we give your DPO the technical facts needed for the notification deadline.

  5. 5

    Post-incident report

    A written account of the cause, the timeline and the corrections, delivered within five working days.