← All research

Offensive Security

Inside a penetration test: what happens, what you receive, and how to prepare

Drocol Research · 28 Jan 2026 · 8 min read

A penetration test is a controlled, authorized attempt to break into your own systems — by the same routes an attacker would use — so you learn what's actually reachable before someone with bad intentions does. It is not a vulnerability scan, and it is not a guarantee of security. It is a point-in-time assessment with defined scope, rules, and deliverables. For organizations in Nigeria and across Africa — where attackers increasingly target fintech rails, mobile money, and government platforms — a well-run engagement is one of the fastest ways to understand what is genuinely exposed. Here is what happens before, during, and after a professional engagement, and how to get the most value out of your first one.

Before the engagement: scoping is everything

The quality of a penetration test is decided before the first packet is sent. Scoping defines what is in bounds, what is out, and how the test may run:

  • In-scope assets: the exact domains, IP ranges, applications, APIs, and devices the test covers.
  • Rules of engagement: approved hours, tested user accounts, whether destructive or denial-of-service techniques are permitted.
  • Access: credentials for authenticated testing — testing without them only finds what an anonymous attacker sees.
  • Contacts: who the testers call if something goes wrong, and who authorizes emergency actions.
  • Legal authority: a signed statement of authorization covering every in-scope asset, including third-party infrastructure.

What actually happens during the test

A professional test moves through the same phases an attacker would, but disciplined and documented:

PhaseWhat happensWhat it produces
ReconnaissanceMapping the external attack surface — domains, certificates, exposed servicesAn asset and exposure inventory
EnumerationExtracting detail from reachable services — versions, users, endpoints, misconfigurationsA list of candidate weaknesses
ExploitationProving that weaknesses are reachable with working proof-of-conceptsConfirmed, reproducible findings
PivotingUsing one foothold to reach deeper systems and dataAn internal attack-path map
ReportingValidating, de-duplicating, prioritizing, and explaining every findingThe final report and remediation guide

What you receive

The report is the deliverable that matters, and a good one is written for two readers. An executive summary in plain language — what was tested, what was found, what it means for the business — followed by technical detail for your engineering team:

  • An executive summary with a risk profile and the findings that matter most.
  • Every confirmed finding with severity, evidence (screenshots, requests, logs), and reproducible steps.
  • Attack paths that connect individual findings into the business impact they create.
  • Clear, prioritized remediation guidance — the fix, the owner, and the effort involved.
  • A re-test procedure so you can verify fixes actually landed.

How to prepare for your first test

  • Reconcile your asset inventory with the scoping document before kickoff.
  • Provide authenticated access and realistic test accounts — surface-level testing wastes the budget.
  • Brief your engineering and operations teams so an unexpected alert does not turn into an incident response.
  • Plan how findings will be triaged and fixed before the report lands, not after.
  • Book the re-test into the calendar at the same time as the initial engagement.

Ready to build confidence

Whether you're preparing for compliance, strengthening your security posture, or building the next generation of digital services — we're here to help.