Skip to content
geekdevs
ESC
  • Pages

  • GeekApps

  • GeekSec

  • GeekForge

  • Company

  • Contact

GeekSec · Security

Think like an attacker. Fix like an engineer.

Penetration testing, red teaming and incident response from a team that builds software too. AI covers the breadth of your attack surface, and experienced testers find the bugs that matter.

geeksec — engagement

❯ geeksec engage --scope app.example.com --mode assisted

▸ mapping attack surface… 412 endpoints · 9 roles · 3 APIs

▸ ai triage: 38 candidates → queued for manual review

▸ analyst: chaining auth + IDOR on /api/v2/invoices

CRITBroken object-level auth → read any tenant's invoices

HIGHSSRF via PDF renderer reaches cloud metadata

MEDPrompt injection in support agent leaks system prompt

LOWVerbose stack traces on 500 responses

✓ report drafted · evidence attached · retest scheduled

❯

AI-augmented security

Machine speed. Human judgment.

We rebuilt our testing practice around AI tooling, but kept experts in charge. The result: wider coverage, faster turnaround, and testers who spend their time on the vulnerabilities that actually hurt.

Wider coverage

AI agents map every endpoint, parameter and role, so we test the parts of the attack surface that manual recon misses.

More time on the hard bugs

Automation handles the routine checks, so senior testers spend their hours on logic flaws and attack chains.

Faster, clearer reports

Evidence is captured as we test and drafted into findings immediately, then reviewed and signed off by a human.

Every finding is verified by a human before it reaches you.

How it works

A clear process with no surprises.

  1. 01

    Scope

    One call to agree on targets, goals and rules of engagement. A clear, fixed-scope proposal.

  2. 02

    Test

    AI handles the breadth, experts handle the depth. You get updates as we go, not just at the end.

  3. 03

    Report

    Clear findings with evidence and fixes, written for both engineers and executives.

  4. 04

    Retest

    Ship your fixes and we verify them, so the report reflects where you actually stand.

Deliverables

Reports your engineers will actually read.

No 200-page PDF of scanner output. You get prioritized findings with real proof and fixes your developers can ship.

  • Executive summary with business-risk framing
  • Every finding with evidence, reproduction steps and CVSS rating
  • Fix guidance written for your developers
  • Attestation letter for auditors and enterprise customers
  • Retest results once fixes ship

GS-2026-014 · Finding 01 of 12

CRITICAL

Broken object-level authorization on invoice API

Endpoint
GET /api/v2/invoices/:id
CVSS
9.1 · AV:N/AC:L/PR:L/UI:N
Impact
Any authenticated user can read invoices belonging to other tenants.
Fix
Enforce tenant ownership in the invoice repository layer, and add a regression test.
$ curl -H "Authorization: Bearer $USER_A" \
    https://app.example.com/api/v2/invoices/8812
{"tenant":"acme-b","total":48200,...}  # ← not user A's tenant

Sample finding. Illustrative only.

FAQ

Before you ask.

How does AI fit into your testing?

AI agents do the breadth work: mapping the attack surface, triaging scanner output and drafting evidence. Human testers do the depth work: business logic, attack chains and judgment. Every finding is verified and signed off by a person.

Is our data safe with your AI tooling?

We walk you through exactly how engagement data is handled during scoping, and we can work within your own data-handling and tooling requirements.

What do you need from us to get started?

A scoping call, a list of targets, and test accounts for each role. We handle the rest and keep you updated throughout.

Are you ready for a real attacker?

Tell us what you're worried about. We'll scope an engagement that answers the question.