RU Contact us
Cases / 04 typical scenarios

How a pentest turns into fixes

The four scenarios we see most often: the perimeter, Active Directory, a web application and an AI assistant. The attack path step by step, findings by severity and what changed after the retest.

Typical scenarios: assembled from common findings, not describing specific clients. Figures are illustrative.

+An archive cabinet with case folders
04 / case files
+
Case 01 / EXT+INTDistribution, about 1,200 employeesExternal and internal network pentest10 working days2 days to domain admin

An old VPN gateway opened the way to the domain

Attack path
  1. EXT

    Found an unpatched VPN gateway on the perimeter with a publicly known vulnerability.

  2. INT

    Gained access to the internal network as an ordinary user.

  3. AD

    Requested service account tickets and cracked a weak password (Kerberoasting).

  4. DA

    The service account was a member of Domain Admins.

  5. DATA

    Reached the accounting system and finance file shares.

Findings by severity · 31
Critical3
High7
Medium12
Low9
What changed
  • Patched the gateway and enabled MFA
  • Moved services to managed service accounts (gMSA)
  • Rebuilt privileged groups
  • Set up Kerberoasting detection

RETEST Retest after 3 weeks: no critical findings, one high.

Case 02 / APPOnline financial serviceWeb application and API15 working daysOther customers' statements on day two

One API parameter exposed other customers' statements

Attack path
  1. RECON

    Collected every API method from the mobile app and documentation.

  2. IDOR

    By changing the ID in a statement request we received other customers' statements.

  3. RACE

    Bypassed the daily transfer limit with parallel requests.

  4. AUTH

    A legacy method accepted tokens without signature verification.

Findings by severity · 22
Critical2
High5
Medium9
Low6
What changed
  • Server-side object ownership checks in every method
  • Locking and idempotency for transfers
  • One token validation library, legacy method removed
  • CI tests for access to other users' objects

RETEST Retest: all critical and high closed; IDOR tests run on every build.

Case 03 / INTManufacturing companyInternal pentest and Active Directory8 working days1 day to domain admin

A flat network and a certificate template: the domain in a day

Attack path
  1. NET

    Servers and the production control system were reachable from the office segment.

  2. RELAY

    SMB signing was off: we captured and relayed authentication (NTLM relay).

  3. ADCS

    A certificate services misconfiguration let us issue an admin certificate (ESC8).

  4. BKP

    The backup server was domain-joined, so the backups could be deleted.

Findings by severity · 27
Critical4
High6
Medium10
Low7
What changed
  • Segmented the network: office, servers, production, management
  • Enabled SMB and LDAP signing
  • Fixed certificate templates and web enrollment
  • Took backups out of the domain and added an immutable copy

RETEST Retest: the path to domain admin no longer works.

Case 04 / LLMCustomer support with an AI assistantLLM application and its tools7 working daysOther users' tickets within 3 hours

A document with a hidden prompt made the assistant leak other users' tickets

Attack path
  1. INJ

    Uploaded a document carrying a hidden instruction for the model (indirect prompt injection).

  2. LEAK

    The assistant revealed its system instructions and tool list.

  3. AGENCY

    Used the ticket search tool to fetch other customers' tickets.

  4. EXFIL

    The answer embedded a link with data in its parameters, leaking it on render.

Findings by severity · 11
Critical2
High3
Medium4
Low2
What changed
  • Tools run with the user's permissions, not the service's
  • Output filtering and no external links in answers
  • Human confirmation for actions on other users' data
  • An adversarial prompt suite runs on every update

RETEST Retest: a 300-prompt adversarial suite finds no leaks.

+
Client projects

Projects our clients allowed us to show

+
Contact

Describe your task

Tell us what is happening and what has been tried. The engineer who will handle it replies.