Solutions

Production data without copies. With proof for every ticket.

GLEJT replaces costly database copies, standing access and guesswork in the audit.

For CISOs, DPOs, development and operations, and vendor management.

Lifecycle of a ticket
  1. 01Ticket openedINC-4821 · Jira
  2. 02Access grantedbilling-core · PROD · until 16:40
  3. 03Work on productionSELECT only · personal data masked
  4. 04Window expiredaccess ended by itself
  5. 05Audit reportexactly what was seen · signed Ed25519
  6. 06Written to the Jira ticketaudit report attached to the ticket

01 · No copies

Fast, secure insight into production data

Problem

Copying a large production database takes days, costs money and creates one more place for data to leak.

Solution

GLEJT lets authorized people query production directly, read-only and with personal data masked before it is shown.

  • No copies, refresh jobs or anonymization scripts
  • Current data as soon as access is granted
  • No slowdown for the source database

Nothing is installed on the database. It runs the user's SELECT as fast as from a SQL client, so a badly written query weighs on it the same as over a direct connection. On PostgreSQL and MySQL, GLEJT also stops a query that runs longer than 15 seconds (the limit is configurable).

02 · Ticket and time

Access only on a Jira ticket and for a set time

Problem

Standing access and shared passwords: a month later nobody knows who was in production, or why.

Solution

Without an open ticket, nobody gets access. When the ticket closes or the time runs out, access ends by itself and an audit report of exactly what the person saw is written to the ticket.

  • No standing access
  • Audit report right in the Jira ticket

03 · ISO 27001

GLEJT enforces the processes ISO 27001 requires

Problem

Access rules live in ISMS documents, and in practice they get bypassed.

Solution

GLEJT turns them into a technical rule: no ticket, no access. The only exception is emergency break-glass access, with an escalated audit and a mandatory review. Evidence for the auditor builds up continuously.

  • A process that cannot be bypassed
  • Audit evidence without last-minute preparation

ISO 27001:2022 controls GLEJT enforces and evidences

  • A.5.15 · Access control Access only via ticket and time window
  • A.5.18 · Access rights Rights expire by themselves
  • A.8.2 · Privileged access Production read-only, time-boxed
  • A.5.19–A.5.22 · Suppliers Every row a vendor saw is audited
  • A.8.11 · Data masking Personal data masked before display
  • A.8.15 · Logging Tamper-evident WORM audit
  • A.8.16 · Monitoring Sentinel, anomalies, SIEM
  • A.5.28 · Collection of evidence Signed evidence pack for every session

GLEJT does not replace an ISMS or certification.

Before and after

What changes with GLEJT

AreaTodayWith GLEJT
Production dataA copy, days of waitingDirect, read-only, masked
AccessStanding accountsTicket + time window
What was seenA query log and a guessEvery row, signed
AI on productionBanned or riskyPseudonyms over MCP
AuditAn admin can rewrite itWORM with a hash chain
Breach or GDPR requestWeeks of forensicsIndex lookup + report

Try it on a real ticket.

Self-hosted, nothing installed on your databases, running against a UAT database in days.