Security and compliance

We ensure your website is secure and compliant with the latest standards, providing regular updates and security patches. Download our free security whitepaper for the same hardening checklist we publish on geonovation.it.

Start a Drupal project

Security is how the platform is operated

A Drupal site used by a public institution is judged on more than the week it launches. Core and contributed updates have to land. Permissions have to match the roles that were agreed. Configuration has to be the configuration that was reviewed, not a setting changed on production and never written down.

GeoNovation treats that as part of the build. We keep the site on a supported release, apply security releases on a schedule you can explain to a reviewer, and separate what an editor may change from what only a deployment may change. The same hardening checklist is the one we publish: you can read it before you share a system with us.

What a reviewer can actually see

Compliance work fails when it is a slide. The useful artefact is the platform itself: accounts with the least access that still lets people work, administrative paths that are not the public front door, dependencies you can list, and an update history. We align the site with that evidence.

We do not sell a certificate we cannot stand behind. Where a programme needs an independent test, we will say so and leave the platform in a state that test can examine. Our own published starting point is the security whitepaper.

  • Core, contributed, and custom code kept on versions that still receive security releases.
  • Roles and permissions written as policy, then checked against the people who hold them.
  • Configuration exported, so production is not a place where security settings drift.
  • A hardening checklist you can read in the security whitepaper before the engagement starts.

Who this is for

This is the security work inside a Drupal platform for EU institutions, UN agencies, and public-sector programmes: the kind of site that will be asked how it is updated, who can publish, and what happens when a dependency warns. An NDA is available before you share the detail. We reply within 24 hours.

Download the security whitepaper

This work sits inside Drupal Development. Start a Drupal project — tell us the organisation, the platform, and the constraint.

More under Drupal Development