Home / Solutions / Pentest and Red Team

Offensive security

Pentest and Red Team

We test like an attacker. We prioritize like part of your team.

At Taura, pentests are manual and run by certified offensive security specialists. We test web applications, APIs, mobile apps, cloud and infrastructure in black box, gray box or white box mode, report any critical finding right away and follow the fixes through to the retest.

What is a pentest and how Taura runs yours

A pentest, or penetration test, is an authorized assessment in which specialists try to exploit vulnerabilities in the systems defined in scope. The result shows how each flaw could be used, what the business impact is and what to fix first. At Taura, tests are manual, supported by tools, follow PTES (Penetration Testing Execution Standard) and OWASP ASVS (Application Security Verification Standard), and the severity of each finding is calculated with CVSS (Common Vulnerability Scoring System).

PTESOWASP ASVSOWASP WSTGOWASP MASVSCVSSNIST SP 800-115MITRE ATT&CKBCB Res. 538
Context

When to put your security to the test

A customer or partner asked for security validationThe report and the attestation letter document what was tested and how findings were handled.
A new product or service is going liveBefore launch, you need to know it is secure. Testing first costs less than fixing later.
The environment or architecture changedNew features, migrations or architecture changes open paths worth a new round.
A standard requires testingCompliance with standards such as ISO/IEC 27001 and SOC 2, PCI DSS or Brazilian Central Bank (BCB) requirements. The scope is designed around what the standard or contract requires.
You want to know how your team reactsIn a Red Team engagement, the focus is on measuring prevention, detection and response.
Scope

What the test can cover

Web applications and APIsAuthentication, authorization, integrations, business rules and transactional flows, in REST or GraphQL.
Mobile appsLocal storage, communication, embedded credentials and backend interaction, on Android and iOS.
CloudIdentities, permissions and exposures in cloud environments.
InfrastructureInternal and external network, Active Directory, VPN and segmentation.
AI applications and chatbotsAuthorization, integrations, prompt manipulation and data exposure in systems that use language models.
Testing modes

Choose how much the test team knows about your environment

Option 1

Black box

The team starts with no credentials or internal information, as an external attacker would.

When to choose itFor mature, already validated environments, when you want an outside attacker's view.

Option 2Recommended for the first test

Gray box

The team receives credentials for the main access profiles, such as a regular user and an admin profile, and shows what a compromised account could do.

When to choose itFor first tests, when you want more coverage and to find as many gaps as possible.

Option 3

White box

The team has access to documentation, architecture and, when agreed, the source code.

When to choose itTo validate business rules, review code security and analyze the full architecture.

Taura

Why run your pentest with Taura

01

Certified offensive security specialists

Tests are run by Taura specialists holding OSCP (OffSec Certified Professional), OSEP (OffSec Experienced Penetration Tester) and OSWE (OffSec Web Expert), plus the Certified AI/ML Pentester for artificial intelligence systems.

02

Nothing critical waits for the report

If we find something critical at any stage of the project, we notify you right away through the channel agreed with your team.

03

A dedicated technical point of contact

The pentester is available throughout the project, with clear communication at each stage. If a test could affect the availability of the environment, we align with you before running it.

Method

How we run the pentest

No two pentests are the same. The plan changes with the testing mode, the type of system and what your company needs to prove. What does not change is how Taura handles each stage.

Scope designed with youIn the kickoff meeting, we define what the test covers, the testing mode, the windows and who follows the project on your side.
Understand before attackingWe map the attack surface and the system flows to find where an attacker would have the most to gain.
Manual exploitationThe team tries to exploit flaws as an attacker would, following references such as PTES, OWASP ASVS and OWASP WSTG (Web Security Testing Guide). For apps, OWASP MASVS (Mobile Application Security Verification Standard) also applies.
Business impact measuredWhen a flaw is confirmed, we follow it as far as it leads to show the business risk, not just the technical risk, always within the agreed limits.
Rating and prioritizationEach finding gets a CVSS severity and a remediation priority that takes the company's context into account.
Remediation follow-upWe answer the team's questions while they fix and agree on when to validate each change.
Deliverables

What you get from Taura

Full reportEach vulnerability with risk, business impact, evidence, CVSS severity, steps to reproduce and a remediation recommendation.
Technical meetingPresentation and discussion of the findings with the development and infrastructure teams.
Executive presentationThe main risks and priorities, in business language, for managers and C-levels.
Action plan supportTaura helps build the remediation plan, with priorities and owners.
Retest of each vulnerabilityValidation of the fixes applied, with the status recorded in the report.
Attestation letterA document that proves which tests were run and how the vulnerabilities found were handled.
FAQ

Frequently asked questions

How often should you run a pentest?

The most common approach is testing every six months or once a year, with extra rounds after launches, migrations and architecture changes. Rules such as those of the Brazilian Central Bank (BCB) and PCI DSS set their own frequencies.

Does a pentest replace a vulnerability scanner?

No, they complement each other. A scanner finds known issues at scale. A pentest investigates and validates exploitation paths, including business logic flaws and chained vulnerabilities that automated tools tend to miss.

Can the test affect production?

It can, which is why planning comes first. We agree on limits, windows, contact channels and how to stop the test if needed, and any test that puts availability at risk is aligned with you first. The choice between production and staging depends on how similar the environments are and on the goal of the test.

What is in the report?

An executive summary to support decisions and technical detail on each finding, with evidence, CVSS severity, business impact and a remediation recommendation. Results are presented in a technical meeting and an executive presentation. After the retest, we record the final status and issue the attestation letter.

Does the attestation letter prove the company is secure?

The attestation letter proves which tests were run in the period and how the vulnerabilities found were handled. It does not guarantee the absence of vulnerabilities, because the scope and the environment change and new flaws can appear.

Does the pentest meet Brazilian Central Bank requirements?

The Brazilian Central Bank (BCB) cybersecurity resolutions, updated by CMN Resolution 5,274 and BCB Resolution 538, require regulated institutions to run periodic penetration tests. Taura designs the scope around these requirements, and the report and the attestation letter document what was tested and how findings were handled.

How long does a pentest take?

It depends on the scope. For a web application tested in gray box mode with the main access profiles, Taura projects usually take three to four weeks from the kickoff meeting to the report delivery. Each project's schedule is presented in the kickoff meeting.

What is the difference between black box, gray box and white box pentests?

It is how much the test team knows about the environment. In black box, the test starts with no credentials, like an external attacker, and suits mature environments. In gray box, the team receives credentials for the agreed profiles, which is what Taura recommends for the first test. In white box, the team also has access to documentation and, when agreed, the code, with a focus on business rules and architecture.

What does Taura need to start the pentest?

A defined scope, a point of contact, the testing windows, the chosen testing mode and, when applicable, credentials for the agreed profiles. All of this is confirmed in the kickoff meeting, along with the schedule and how we will communicate.

Leave your details and a Taura expert will get in touch to talk about what your business needs.

How can we help?
How did you hear about Taura? optional
WhatsApp