01How is a pentest different from a vulnerability scan?
A scanner finds known vulnerabilities one by one. A pentest checks where they lead together: from which point an attacker reaches the data or admin rights. We use scanners, but we verify every finding by hand.
02Will you break production systems?
Scope, windows and forbidden actions are agreed in advance. Risky checks run on copies or at an agreed time, and we stay in contact with your on-call engineer throughout.
03How long does a pentest take?
It depends on scope: the number of addresses, applications and network segments. We give the timeline once the scope is agreed, before work starts.
04How often should it be done?
At least once a year and after major changes: a new application, a migration, a perimeter change. A retest after fixes is essential: per Verizon DBIR 2026, known exploited vulnerabilities take a median of 43 days to fix.
05What do you need from us?
A point of contact on your side, an agreed scope and, for an internal test, a network access point or an ordinary employee account.
06What do you test in LLM applications?
Direct and indirect prompt injection, leakage of system instructions and data, tool and agent permissions, handling of model output in the interface, and resource consumption. We follow the OWASP LLM Top 10.