05Practice
Cybersecurity & Compliance
Security work that changes the system, not just the policy binder. We threat model your architecture, fix what the model exposes, and build the evidence pipeline that turns SOC 2, ISO 27001 or HIPAA readiness into a continuous state rather than an annual scramble. Findings arrive with patches attached, not just severities.
- Typical duration
- 1 week to start · 1–2 weeks
- Engagement models
- Assessment · Readiness programme · Security retainer
- Practice lead
- Named at proposal stage

01The problem
Most breaches are not clever
They are a long-lived access key in a public repository, an administrative interface reachable from the internet, a dependency three years behind, or a former contractor whose account was never disabled. The interesting attacks make the conference talks; the ordinary ones make the incident reports. Almost all of them were visible in an asset inventory nobody maintained.
Compliance has a parallel failure. A team writes policies in the month before the audit, screenshots a dozen settings, passes, and then drifts for eleven months until the next scramble. The certificate is real and the security posture it describes is not. Both problems have the same fix: make the control enforce itself in the pipeline, and make the evidence a by-product of normal operation.
02What GatiQ delivers
The work itself
Every item below is something you can inspect, run or read at the end of the engagement.
- 01
A threat model tied to your actual architecture
We work through data flows with your engineers, apply STRIDE at each trust boundary, and produce a ranked list where every item has an owner, an estimate and a verification step. It is a working document your team updates, not a PDF filed after delivery.
- 02
Testing that ends in merged pull requests
Authenticated application testing, cloud configuration review and, where in scope and authorised in writing, social engineering. Every finding arrives with reproduction steps, a suggested patch, and a retest once you have shipped the fix.
- 03
Identity tightened without stopping the work
Single sign-on, hardware-backed multi-factor for privileged roles, short-lived credentials in place of static keys, and just-in-time elevation with an audit trail. We stage the rollout so your support desk does not spend a week resetting locked-out accounts.
- 04
Controls enforced by the pipeline
Dependency and container scanning, static analysis, secret detection, infrastructure policy checks and signed provenance on every build. A failing control blocks the merge, which means the evidence for the auditor is simply the pipeline history.
- 05
Readiness that stays ready
Control mapping, gap remediation, automated evidence collection and a dry-run audit before the real one. We work alongside your assessor — we do not issue the report, and any firm offering to both advise and certify deserves a hard question.
03Engagement model
Three ways to buy it
- Assessment
- Three to five weeks: threat model, technical testing, and a prioritised remediation plan with effort estimates your engineering lead can drop straight into a sprint.
- Readiness programme
- Twelve to twenty weeks to SOC 2 Type I or ISO 27001 certification readiness, including the policy set, control automation, staff training and the dry-run audit.
- Security retainer
- A standing block of hours each month for design reviews, dependency triage, incident support and the quarterly re-test. Priced so that asking us a question is never a change request.
04Typical timeline
What the calendar looks like
- 01
Scoping
1 weekAsset inventory, data classification, authorisation and rules of engagement.
- 02
Assess
2–4 weeksThreat model, technical testing, access review, written findings report.
- 03
Remediate
4–12 weeksFixes shipped with your team, controls automated in CI, policies written.
- 04
Verify
1–2 weeksRetest, dry-run audit, tabletop exercise, evidence handover.
Ranges, not dates. We narrow them at the end of discovery and tell you the same week if they move.
05Technologies
What we reach for
Defaults, not rules. If your team already runs something else competently, that is usually the better choice.
- Application security
- Semgrep, CodeQL, OWASP ZAP, Burp Suite
- Supply chain
- Trivy, Syft, Grype, Sigstore, Dependabot
- Identity and secrets
- Okta, Entra ID, HashiCorp Vault, IAM Identity Center
- Detection
- Falco, GuardDuty, Wazuh, OpenTelemetry
- Governance
- OPA, Kyverno, Vanta, Drata