01 / Offensive security
Pentest findings your engineers can reproduce and fix.
Pentest, code audit and red team, in a scope you set.
Same finding. A long PDF: Nothing fixed. Steps to reproduce: Fixed and retested.
A long PDF: Nothing fixed. Steps to reproduce: Fixed and retested.
02 / Apps and APIs
We test web apps, APIs and mobile apps.
Login, access rights and business logic. Real attacks start there.
03 / Network
We test the perimeter and the internal network.
We start outside or from an agreed point inside. We look for a path to admin rights.
Between pentests, TrustFlare Surface watches what answers from the internet.
04 / Code
We audit source code and look for backdoors.
Critical code and dependencies, reviewed with the developers who will fix them.
For every merge request, see TrustFlare AI Security Agent.
05 / Red team
A red team tests people, process and tools together.
The campaign and any social engineering are agreed first. It shows if your defense works.
Web3 and smart-contract specialists when your stack needs them.
06 / The result
Every finding can be reproduced, and the retest is agreed.
A report is not the goal. The goal is a closed finding you can prove.
Finding
Steps to reproduce
Fix
Your engineers make the change
Retest
We confirm it is closed
Questions
A few things to know
Do you retest after the fix?
Yes, when the retest is agreed in the scope.
Can you test our mobile app?
Yes. Web, API and mobile apps are in scope.
Is a red team the same as a pentest?
No. A pentest checks systems. A red team checks how you defend.
Do you test people with phishing?
Only if the scope names it and you agree in writing.
Do we get a long PDF?
You get findings with steps to reproduce and a fix order.
Start a test
Tell us what to test.
We agree the scope and the retest before the work starts.