EXTDMZWS-07SRV-SQLSVCTARGET

$ whoami

I break in, so others can't.

Pentest/Red team/Offensive security/Vuln research

I'm Giulliano Amaral, a penetration tester and security researcher. I find the paths an attacker would take through your applications, networks and AI systems, then document them clearly enough for your team to close them.

Web · APIs · Active Directory · AI/LLM · OSS vulnerability research// authorized adversary

./why --pentest

Why hire a pentest?

Because someone is going to test your company's security. The only question is whether it's someone you hired, or an attacker.

The cost of finding out late

Most breaches don't need sophisticated tradecraft. They start with a known weakness nobody tested, in an exposed system or a supplier. The latest industry data shows how big the problem is:

US$4.99M

is the average cost of a data breach, a record high and 12% more than the year before.

IBM, Cost of a Data Breach 2026 ↗
31%

of breaches started with the exploitation of a vulnerability, now the most common way attackers get in.

Verizon, DBIR 2026 ↗
43 days

is the median time to fully fix a critical, actively exploited vulnerability. Only 26% of them were fully remediated.

Verizon, DBIR 2026 ↗
48%

of breaches involved ransomware, and another 48% involved a third party such as a supplier or partner.

Verizon, DBIR 2026 ↗

Where a pentest fits

01

Find the way in before an attacker does

If exploiting vulnerabilities is the top way in, the most direct defense is to look for them the way an attacker would, with manual testing of your applications, APIs and network.

02

Know what to fix first

Teams fix slowly because they have too many findings. The report ranks each one by real impact and exploitability, so effort goes to what actually opens the door.

03

Have evidence for customers and auditors

An independent report answers customers' security questionnaires and supports audits such as ISO 27001 and SOC 2, and shows due diligence under data-protection laws like GDPR and Brazil's LGPD.

cat services.txt

What I test

Every engagement is manual, scoped in writing, and ends with a report your developers can act on: reproducible steps, impact and fixes.

How engagements work
01

Web & API pentest

Manual testing of web applications and APIs, beyond what scanners report: access control, business logic and the way components chain together.

  • OWASP Top 10 / API Top 10
  • Authn, authz & IDOR
  • Business-logic abuse
02

Internal & Active Directory

Assume-breach assessments that start from a foothold and map the realistic path to domain compromise.

  • AD attack paths
  • Credential & Kerberos abuse
  • Lateral movement
03

AI / LLM red teaming

Adversarial testing of LLM apps and agents: prompt injection, tool abuse and trust boundaries between agents.

  • OWASP LLM Top 10
  • Agent & MCP tool abuse
  • Data-exfiltration paths

ls -t writeups/

Recent writeups

End-to-end attack chains from HackTheBox machines and AI red-team labs. Active machines stay sealed until they retire.

All writeups

ls articles/

Research & articles

All articles

ls ~/certs

Certifications

Hands-on, lab-based exams covering pentest, red team, Active Directory, web, API and AI security.

Details

./contact --scope yours

Have something in scope?

Tell me about the target, the environment and your timeline. I'll come back with questions and a proposed approach. Testing only starts with written authorization.