Information security · Penetration testing

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

Four areas we test

External perimeter

We look for ways into the network from the internet: exposed services, remote access, email and the company’s public resources.

Internal network

We simulate an attack from inside — from a compromised computer or employee account — and find out how far an attacker can get.

Web applications and API

We test websites, customer portals and APIs for vulnerabilities that expose data or functions that should be closed.

Social engineering

Training phishing campaigns and other checks of employees: will they open the email, enter a password, report something suspicious?

Format

How much the tester knows at the start

We choose the format together with you, based on the goal of the test.

Black box

No information at all — like an outside attacker. The most realistic, but part of the time goes on reconnaissance.

Grey box

A regular user account, a list of addresses, a basic diagram. Lets us test deeper in the same time.

White box

Documentation, configurations, sometimes code. The deepest test, closer to an audit.

What to choose

A pentest is not the same as scanning

Vulnerability scanningPentestRed team
What it isAn automated check for known vulnerabilitiesManual testing by specialists within agreed limitsA simulated targeted attack on the whole organisation
ResultA list of possible vulnerabilitiesConfirmed vulnerabilities, attack chains, evidence, recommendationsAn assessment of whether monitoring and the team notice the attack
WhenRegularly, between pentestsAfter significant changes and on a scheduleOnce basic protection and monitoring are in place

Regular scanning is part of vulnerability management.

Result

What you get

Not just a list of findings, but a plan for what to do with them.

  • A report listing vulnerabilities with severity and evidence
  • Remediation recommendations for every finding
  • A retest after the fixes
  • A short summary for management — without the technical detail

How we work

Four stages of a pentest

  1. Scope and rulesWe agree what exactly is tested, the goals and the limits of the test, and put it in writing.
  2. TestingWe look for vulnerabilities and check whether they can really be exploited — within the agreed limits.
  3. Report and recommendationsWe describe every finding with evidence and severity, explain how to fix it and prepare a summary for management.
  4. RetestAfter the fixes we test again and confirm the vulnerabilities are closed.

Compliance

Pentest and PCI DSS preparation

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

What we need from you

  • The goal of the test: a client or standard requirement, a new service, a check of your monitoring
  • The scope: addresses, domains, applications — and what must not be touched
  • Written approval from the system owner; your cloud or hosting provider’s rules on testing
  • A contact person for the duration of the work and fresh backups of critical systems
  • A decision on whether to warn the IT team: if not, the pentest also checks whether they notice the attack

FAQ

Who carries out the pentest?

Bereg-IT’s own team.

Can you test just the website or a single application?

Yes. We agree the scope at the start — from a single web application to the whole infrastructure.

Will our systems stop working?

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.

How long does it take and how much does it cost?

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.

What about the confidentiality of the results?

Confidentiality terms are set out in the contract; only agreed people receive the report.

How often should we run a pentest?

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.

Is your pentest suitable for PCI DSS?

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

Related articles

All articles

Want to test your defences in practice?

Tell us what needs testing — we’ll agree the scope and format of the pentest. The first consultation is free.

Discuss a pentest