Penetration testing: what it is, types and stages
What a penetration test is and how it differs from vulnerability scanning and red teaming. Types, stages, report contents and how to prepare a company.
Read the articleInformation security · Penetration testing
We test your defences the way an attacker would — but with your permission and within agreed limits. We find vulnerabilities in the perimeter, the internal network, web applications and processes before someone else uses them.
Types of testing
We look for ways into the network from the internet: exposed services, remote access, email and the company’s public resources.
We simulate an attack from inside — from a compromised computer or employee account — and find out how far an attacker can get.
We test websites, customer portals and APIs for vulnerabilities that expose data or functions that should be closed.
Training phishing campaigns and other checks of employees: will they open the email, enter a password, report something suspicious?
Format
We choose the format together with you, based on the goal of the test.
No information at all — like an outside attacker. The most realistic, but part of the time goes on reconnaissance.
A regular user account, a list of addresses, a basic diagram. Lets us test deeper in the same time.
Documentation, configurations, sometimes code. The deepest test, closer to an audit.
What to choose
| Vulnerability scanning | Pentest | Red team | |
|---|---|---|---|
| What it is | An automated check for known vulnerabilities | Manual testing by specialists within agreed limits | A simulated targeted attack on the whole organisation |
| Result | A list of possible vulnerabilities | Confirmed vulnerabilities, attack chains, evidence, recommendations | An assessment of whether monitoring and the team notice the attack |
| When | Regularly, between pentests | After significant changes and on a schedule | Once basic protection and monitoring are in place |
Regular scanning is part of vulnerability management.
Result
Not just a list of findings, but a plan for what to do with them.
How we work
Compliance
For companies that accept card payments, PCI DSS v4.0 (requirements 11.4.2 and 11.4.3) requires internal and external penetration testing at least once every 12 months and after any significant change to the infrastructure or applications. The tester must be qualified and organisationally independent.
We prepare you for the PCI DSS audit together with our partner, a Qualified Security Assessor (QSA) listed by the PCI SSC: the documentation and policies, and the technical controls the standard requires. The partner then carries out the compliance audit (often called certification), and we stay with you through it and help close any findings. Bereg-IT does not certify on its own — that is done by the QSA.
External vulnerability scanning for PCI DSS is a separate requirement: it is performed by a PCI SSC Approved Scanning Vendor (ASV).
More in the article “PCI DSS: what it is and what it requires of IT”.
Preparation
Bereg-IT’s own team.
Yes. We agree the scope at the start — from a single web application to the whole infrastructure.
We agree the timing and the permitted methods in advance. Methods that could affect availability (for example, denial-of-service attacks) are not used without separate consent.
It depends on the scope and format of the test. We give timelines and cost once the scope is agreed; the first consultation is free.
Confidentiality terms are set out in the contract; only agreed people receive the report.
After significant changes — a new application, a migration, a network redesign — and on a schedule set by your risks and industry requirements. Between pentests — regular vulnerability scanning and monitoring.
Yes: we carry out internal and external penetration testing with our own team. We prepare you for the PCI DSS audit together with our partner, a QSA listed by the PCI SSC, and the partner carries out the compliance audit; Bereg-IT does not certify on its own. External ASV scanning is done by an approved vendor, and your acquirer decides how compliance is confirmed.
Blog
What a penetration test is and how it differs from vulnerability scanning and red teaming. Types, stages, report contents and how to prepare a company.
Read the articlePCI DSS is the payment card data security standard. Who it applies to, the 12 requirements and what they mean for IT: scanning, pentests, MFA, logs.
Read the articleA vulnerability is a weak spot attackers use. How to find and close vulnerabilities: inventory, scanning, priorities by CVSS, EPSS and KEV, updates.
Read the articleWhat phishing is, which kinds target Ukrainian companies now, how to spot a fake and which measures protect a business. What to do if someone already clicked.
Read the articleRelated services
Tell us what needs testing — we’ll agree the scope and format of the pentest. The first consultation is free.