GIBP

Security

Understand the protections in place and those still being built.

Find the website controls we can describe today, the security principles guiding GIBP's development and the process for reporting vulnerabilities. Future product controls are not represented as independently certified.

Web application

HTTPS delivery, security headers, same-origin form handling, server-side input validation, rate limiting and reduced third-party browser exposure are part of the website baseline.

Data minimisation

Public sandbox and assistant interfaces are designed for synthetic or non-confidential data. Visitors are told not to submit credentials, identity documents or confidential customer data.

Deterministic financial control

The target financial architecture keeps money movement behind mandates, policy, limits and deterministic state rather than giving unrestricted authority to probabilistic models.

Resilience

Provider redundancy, degraded modes and recovery are design goals that require production testing and operational evidence before being represented as implemented controls.

Vulnerability disclosure policy

Report security issues through a dedicated channel.

Use the GIBP security reporting form for suspected vulnerabilities affecting GIBP systems owned or operated by The Raeburn Group. The form accepts anonymous reports and issues a reference number.

In scope

  • • Public GIBP web applications and APIs operated by The Raeburn Group.
  • • Authentication, authorisation, input-handling and data-exposure issues in those systems.
  • • Security-control weaknesses that can be demonstrated without harming other users.

Out of scope

  • • Denial-of-service, destructive testing, social engineering or physical attacks.
  • • High-volume automated scanning that degrades service.
  • • Third-party systems we do not own or operate.
  • • Accessing, modifying or retaining data beyond the minimum needed to demonstrate an issue.

Good-faith safe harbour

We will consider security research authorised when you make a good-faith effort to follow this policy. For accidental, good-faith violations while acting within this policy, The Raeburn Group will not initiate civil action or ask law enforcement to investigate on our behalf. We also waive, on a limited basis, contractual restrictions under our control that would otherwise prevent this permitted research.

This safe harbour applies only to claims and restrictions under our control; it does not bind independent third parties or excuse conduct prohibited by applicable law. If you are unsure whether a planned test is within scope, submit a report before proceeding.

We aim to acknowledge useful reports promptly, validate them in good faith and keep reporters reasonably informed while remediation is underway. This is a vulnerability disclosure programme, not a bug-bounty programme, and it does not promise financial rewards.

What we do not claim

  • • No certification badge appears without a current certificate and scope.
  • • No production availability percentage is published without an observed measurement window or contractual target label.
  • • No “mission-critical” claim is used as a substitute for disaster-recovery, load, security and incident evidence.
Ask