Home / Services / Pentest / Penetration Testing

Offensive Pillar - Penetration Testing

Penetration Testing: find out
what an attacker could
exploit in your applications

Pentesting for web applications and APIs, with controlled exploitation, business impact explained and a prioritized remediation plan

Scanners point out possible flaws. A penetration test answers what really matters: can this flaw be exploited? What could an attacker access? Do your current controls block the attacks you worry about most? ASER's Penetration Testing simulates real attacks against your applications and APIs, within a scope authorized in writing, to show in practice the risk of each vulnerability and what to fix first.

Teste de intrusão em aplicação web e API: falha de autorização expondo dados de outro cliente
What is

What is a Penetration
Testing?

A penetration test, or pentest, is an assessment in which specialists take an attacker's perspective and try to exploit, in a controlled way, the vulnerabilities of a system.

The goal is not to hand over a list of alerts, but to prove what is exploitable, how far exploitation goes and what the impact is on operations, data and customers.

The test can be performed without credentials (black box), with test users of different profiles (gray box) or with access to documentation and code (white box), depending on the agreed objective.

For specific environments, ASER also offers Network Pentest, Mobile Pentest and E-commerce Pentest.

The assessment may include:

What questions does a Penetration Test answer?

A good test starts with the questions the company needs to answer — for the board, for auditors or for its own customers.

An isolated vulnerability may seem low-impact. Combined with an authorization flaw or a weak credential, it can expose your entire customer base.

At the end of the test, you will know:

Why Aser

Why choose the Penetration
Testing
at ASER?

Offensive security specialists

Tests are carried out by professionals who analyze the application from an attacker's perspective, combining specialized tools with manual exploitation. Team certified in OSCP, CEH and eWPT.

Business-oriented assessment

We don't just deliver a technical score. We explain how each flaw would affect customers, data, revenue, reputation and business continuity.

Recognized methodologies

Testing follows references such as the OWASP Web Security Testing Guide, OWASP Top 10, OWASP API Security Top 10 and PTES, with techniques mapped to MITRE ATT&CK where applicable.

Authorization and logic testing

We test what scanners can't see: access to other users' data, privilege escalation between profiles, and abuse of workflows and business rules.

Custom scope

Each project is planned around the architecture, technologies, integrations and access profiles of the application under test.

Integrated with ASER operations

Findings can flow into our Vulnerability Management and SOC services, which track remediation and tune detection.

Each finding is analyzed considering ease of exploitation, the access obtained and the technical and operational impact on the organization.

How does
Penetration Testing?

01

Scope and authorization

We define objectives, applications, APIs, access profiles, time windows and exclusions. Nothing is tested without written authorization.

02

Reconnaissance and mapping

We identify technologies, endpoints, exposed surfaces, authentication flows, integrations and possible entry points.

03

Automated analysis

We use specialized tools to support the initial discovery of vulnerabilities, misconfigurations and exposed components.

04

Manual testing

Specialists validate the findings and perform manual testing of exploitation, authorization, authentication, sessions, APIs and business logic.

05

Impact analysis

Each vulnerability is analyzed considering how exploitable it is and its technical and business impact on the company.

06

Report and presentation

We deliver an executive overview, technical details, evidence and a prioritized remediation plan, and present the results to the teams involved.

Test governance

How we run
every test

Written authorization

No test starts without formal authorization from the environment owner. Out-of-scope systems are never touched.

Documented scope and exclusions

Assets, techniques, time windows and what is excluded are recorded before we start, so there are no surprises.

Immediate stop

If there is unexpected impact or any sign of a real incident in progress, testing stops and you are notified right away.

Named contacts on both sides

One person in charge at ASER and one at the customer, with a direct escalation channel throughout the engagement.

Evidence handled under the LGPD

We collect only what is needed to prove each finding, with agreed retention and disposal periods.

Remediation validation

After fixes are applied, a retest confirms that each flaw has really been eliminated, when included in the scope.

Which test to choose

Which test answers
your question?

Where are my weaknesses and which should I fix first? Continuous scanning, risk-based prioritization and remediation governance.

Is this flaw exploitable, and what is the impact? Controlled exploitation of applications and APIs, with evidence and a remediation plan.

How far can an intruder get in my network? Internal and external infrastructure testing, segmentation and lateral movement.

Does my team detect and respond to a real attack? Adversary simulation with defined objectives, measuring detection and response.

What do I have exposed on the internet without knowing? Continuous discovery of exposed assets, services and domains.

Do my employees fall for scams? Phishing, SMS and phone-call simulations, with training at the moment of failure.

Aser Specialists - Since 2004

Offensive security with a certified team
OSCP, CEH and eWPT

FAQ

Frequently Asked Questions
about Penetration Testing

A scan uses automated tools to point out possible vulnerabilities, outdated components and misconfigurations.

A penetration test validates those findings manually, exploits them in a controlled way and shows the real impact — including when small flaws combined open an attack path.

Black box: the specialist starts with no credentials or internal information, like an external attacker.

Gray box: the specialist receives test users with different profiles, to assess authorization and what a malicious customer or employee could do.

White box: the specialist has access to documentation, architecture and, if agreed, source code, which increases the depth of the analysis.

Tests are planned to preserve availability.

Before we start, we define rules of engagement, time windows, critical assets and an immediate stop channel. Techniques that could cause downtime are only used with specific authorization.

A penetration test is important evidence for these requirements. PCI DSS requires periodic penetration testing (requirement 11.4), Brazil's LGPD calls for technical security measures appropriate to the risk, and CMN Resolution 4,893 provides for tests and scans to detect vulnerabilities.

On its own, however, a test does not guarantee compliance: it proves the security posture on the assessment date and guides remediation.

At least once a year and always after relevant changes, such as new features, integrations, a platform change or an infrastructure migration.

Just tell us:

  • the applications and APIs in scope (approximate addresses and number of access profiles);
  • the goal of the test (customer requirement, audit, launch or routine);
  • the desired timeline.

Do not send passwords or credentials at this stage. They are exchanged securely after formal authorization.

Offensive Pillar

Other offensive solutions

ASER
Next step

Discover what an
attacker would find

Talk to a specialist to define the scope of your test and receive a proposal.