Home / Solutions / Pentest and Red Team
Offensive securityPentest 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).
When to put your security to the test
What the test can cover
Choose how much the test team knows about your environment
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.
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.
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.
Why run your pentest with Taura
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.
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.
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.
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.
What you get from Taura
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.