SECURITY & COMPLIANCE

OWASP-led audits, hardening and the operational controls that keep issues from returning.

Security & Compliance

Security that survives the week after the audit

A penetration test tells you where you stood on one afternoon. We work the other way round: find what is exploitable today, fix it properly, then put the controls and habits in place that keep the same class of problem from coming back.

  • OWASP-ledAudits mapped to the OWASP Top 10 for web, mobile and API
  • Fixes, not findingsWe remediate alongside your team rather than filing a PDF
  • Enterprise-readyThe evidence procurement and security questionnaires ask for

Defence in depth, layer by layer

Attackers do not respect your architecture diagram. Every layer assumes the one in front of it has already been bypassed.

Edge

DNS and WAF at Cloudflare, DoS and DDoS mitigation, rate limiting, bot filtering, TLS everywhere with automated certificate renewal.

Application

Injection, broken access control, XSS, CSRF, SSRF and insecure deserialisation — the OWASP Top 10 tested against your actual routes, plus dependency and secret scanning in CI.

Identity

MFA, SSO and session handling done properly. Least-privilege roles, service accounts scoped to one job, and a real off-boarding process.

Data

Encryption in transit and at rest, secrets in a managed vault, key rotation on a schedule, PII minimised and access to production data logged.

Operations

Tested backups and a defined recovery point, audit logging, alerting on suspicious activity, and an incident plan someone has actually rehearsed.

Where we look, and what with

Automated scanning finds the known problems cheaply. Everything interesting is found by hand, by someone who understands what your application is supposed to do.

Standards & frameworks

Default: OWASP ASVS as the checklist, because it turns "are we secure?" into a set of questions with verifiable answers.

  • OWASP Top 10
  • OWASP ASVS
  • OWASP MASVS (mobile)
  • PDPCI DSS readiness
  • GPGDPR practices

Edge & network

Default: Cloudflare in front of everything — DNS, WAF, TLS and DDoS absorption from one place, at a price that makes sense for a small team.

  • Cloudflare
  • WAF & rate limiting
  • DMDDoS mitigation
  • Let’s Encrypt
  • Nginx hardening

Application testing

Manual testing with Burp Suite against your real routes and roles, backed by automated dependency and static analysis running on every pull request.

  • Burp Suite
  • Snyk
  • SonarQube
  • Dependency scanning
  • Secret scanning

Identity & secrets

Default: MFA on every human account and a managed secret store for everything else. Shared credentials in a spreadsheet are still the most common finding we report.

  • MEMFA everywhere
  • Auth0 / SSO
  • HashiCorp Vault
  • 1Password
  • KRKey rotation

Mobile & API

Mobile apps ship your logic to a device you do not control. We test what an attacker can extract, replay or tamper with once they have the binary.

  • CPCertificate pinning
  • SSSecure storage
  • TRToken & refresh flows
  • RLRate limiting
  • IVInput validation

Resilience

Assume something will get through eventually. What matters then is how quickly you detect it, contain it, and prove afterwards what was and was not touched.

  • BPBackup policy
  • RDRestore drills
  • ALAudit logging
  • IRIncident response plan

Our bias. Fix the boring things first. Access control, MFA, patched dependencies, rotated keys and a restore you have actually tested will stop more real incidents than any exotic tooling — and they cost far less.

How we engage

  1. Assess

    Threat model your application, then test it — manually and with tooling — against OWASP.

  2. Prioritise

    Findings ranked by real exploitability and blast radius, not by scanner severity alone.

  3. Remediate

    We fix alongside your engineers, with a regression test for each issue closed.

  4. Sustain

    Scanning in CI, rotation schedules, alerting and a policy set your team can maintain.

The baseline we hold every product to

Whether or not you have engaged us for security, this is what we build into anything we ship.

  • TLS everywhere, with certificates renewed automatically
  • Secrets in a managed store, never in the repository
  • MFA on every account that can reach production
  • Dependency and secret scanning on every pull request
  • Least-privilege access, reviewed when people change roles
  • Encrypted backups with restores tested on a schedule