
Web application pentesting
Scanning is not the same as attacking.
We attack your web applications, portals and APIs the way an attacker would, with authorization and method, so that you are the first to find the vulnerabilities. Following OWASP, with findings classified by CVSS and retesting of the fixes.
- Building and running technology since 2008
- Microsoft Partner since 2010
- 200+ large organizations as clients
- ISO 27001 certified
- 60+ in-house professionals in Barcelona and Madrid
- Our own SaaS services and solutions
THE STARTING POINT
Applications are the entry point
Scanners find known flaws; attackers look for the logic flaws that no scanner sees.
Injection
Unvalidated forms
Every input field is a candidate for SQL injection, XSS or CSRF if it is not properly validated.
Authorization
Access that should not exist
Users who see other users' data (IDOR) or who reach functions of a higher role.
Sessions
Weak authentication
Unprotected cookies, poorly validated JWT tokens and sessions that never expire.
Configuration
Headers and encryption
Missing security headers, misconfigured TLS and exposed administration panels.
Without a pentest, the first to test your applications may be an attacker.
When does a pentest make sense?
If you identify with any of these scenarios, a pentest gives you the evidence you need.
New application or major release
Validate security before opening a portal, a private area or an API to the internet.
Clients, insurers or auditors
Security questionnaires, cyber-risk policies or due diligence that ask for a recent pentest.
ISO 27001, ENS or NIS2
Auditors expect periodic testing, classified findings and evidence of retesting.
Personal or business data
Applications with customer data, payments or critical information and several user roles.
Also as a periodic review: annually or after every relevant change in the application.
A scanner is not enough
A scanner detects the known; a pentest checks what an attacker can actually do.
Scanner only
A list of warnings
- Hundreds of unprioritized alerts
- False positives that nobody dismisses
- Invisible business logic flaws
- Unchecked permissions between roles
- No evidence that it has been fixed
Result: a feeling of security, not security
With Itequia
A controlled and documented attack
- Automated and manual tests combined
- Every role, tested against every function
- Controlled exploitation that confirms the risk
- Findings classified with CVSS
- Retest included to close each finding
Result: vulnerabilities confirmed and closed
What an attacker would do, with authorization
We combine the coverage of tools with the judgment of a specialist: neither is enough on its own.
The tools
Automated testing
Active scanning, path enumeration and analysis of the server and encryption, across the entire surface.
The specialist
Manual testing
Injection, sessions and business logic, role by role: what no scanner detects.
The result
Confirmed risk
Each vulnerability, exploited in a controlled manner, classified and with its fix.
Where we attack
Forms
SQL injection, XSS and CSRF in every input field
Roles
Authorization matrix: privilege escalation and IDOR
Sessions
Authentication, cookies and JWT tokens for each role
Server
HTTP headers, TLS configuration and administration panels
What we test
We follow the OWASP testing guide (WSTG) and cover the OWASP Top 10 risks.
Reconnaissance
- DNS and subdomains
- Exposed technologies
- HTTP headers
- Hidden paths and files
Data inputs
- SQL injection
- Cross-site scripting
- CSRF
- Input validation
Configuration
- Security headers
- TLS and certificates
- Web server
Authentication
- Login and passwords
- Session management
- Cookies and JWT tokens
- Expiration and logout
Authorization
- Role–function matrix
- Privilege escalation
- Other users' data (IDOR)
- Administration panel
Preferably in pre-production, or in production during agreed windows, with no impact on your users.
Our difference
A measured scope, not a rough estimate
The effort does not depend on the number of pages, but on the real attack surface.
01
We measure the surface
An OWASP ZAP crawl counts the pages (P) and forms (F) of the application.
02
We weigh the risk
Each form counts three times and each user role (R) multiplies: (P + 3F) × R.
03
Fixed price
The score places the application at a level with effort and price fixed in advance.
A 10-page portal with 4 roles may require more testing than an 80-page one without login.
Four steps, from authorization to retest
The duration is adjusted to each case: pages, forms and user roles in scope.
01
Signed scope
Authorization
Scope, environments, testing windows and emergency contact, in writing.
02
Measurement and preparation
Reconnaissance
Application crawl, confirmation of complexity and passive reconnaissance.
03
Automated and manual
Execution
Scans, manual role-by-role testing and controlled exploitation of findings.
04
Technical team and management
Report and retest
Reports with CVSS, remediation plan and verification of the fixes.
What you receive: evidence to act on
Executive report
The relevant risks and their potential impact, without technical jargon, for management.
Technical report
Each finding with its description, evidence and CVSS classification, from critical to informational.
Remediation plan
Prioritized by risk, with a specific recommendation per finding for the development team.
Retest
Verification that the fixed vulnerabilities have effectively been closed.
Evidence for the ISMS
Documentation ready for the ISO 27001 or ENS auditor.
The pentest confirms the risk and defines how to close it. Code fixes, infrastructure audits and periodic pentests are separate services.
How it works
Fixed price, no further commitments
Each step is decided based on the previous one: the pentest doesn’t commit you to anything else.
01
Initial assessment
One session to confirm the applications, environments and user roles in scope.
02
Pentest
At a fixed price, based on the complexity score of each application.
03
Remediation
As a project: code and configuration, according to the remediation plan.
04
Periodic review
Annual pentest or after each relevant release, using the same method.
The report and the remediation plan are yours, to carry out with whoever you choose. Tests are authorized in writing and data is handled under our ISO 27001 certification.
The difference from a scanner report
A team that also develops and operates applications.
Confirmed findings
Each vulnerability, exploited in a controlled way and verified by specialists.
Security we practice
Itequia is ISO 27001 certified and works in regulated environments: banking, pharma, industry and the public sector.
We know how to fix it
We have been developing applications since 2008: actionable fixes and, if you wish, we implement them.
What you get
Confirmed risk
What an attacker can really do in your applications.
Clear priorities
Findings classified by CVSS, from critical to informational.
Verified fixes
Retest of every closed vulnerability.
Evidence for third parties
Reports for customers, insurers and auditors.
Compliance
Technical vulnerability management for ISO 27001, ENS and NIS2.
Defined cost and scope
Fixed price calculated with an objective method.
Where the pentest fits
The pentest works on its own or alongside Itequia's other cybersecurity services.
Audit the network
Cybersecurity audit
Infrastructure vulnerabilities and policy maturity.
Test the applications
Web application pentesting
Controlled attacks, role by role, with retest of the fixes.
Assess the applications
Well-Architected assessment
Code, architecture and platform against the five pillars.
Comply
NIS2, ENS and ISO 27001 assessment
Applicability, gap by framework and prioritized action plan.
Each service is contracted separately. Infrastructure, applications and compliance with the same partner.
Why Itequia?
AI at the core of how we work. Our own AI-Driven method, applied across the entire lifecycle, to take solutions to production in weeks, not months.
We build it, we run it. Consulting, development, Microsoft and cybersecurity with a single partner, from assessment to operations, with the same point of contact throughout.
Security we practice. ISO 27001 certified, with automated code security analysis in every delivery and experience in regulated environments: banking, pharma, manufacturing and the public sector.
Your feedback, with its own channel. A Customer Experience team, independent from the people delivering your project, tracks your satisfaction so we can correct course in time.
Organizations that trust us
Frequently asked questions
The OWASP Web Security Testing Guide and the OWASP Top 10 risks. Reference tools such as OWASP ZAP, Nikto, Gobuster, sqlmap or sslyze and, above all, manual testing. Findings are classified with CVSS: critical, high, medium, low and informational.
By attack surface, not by number of pages: (P + 3F) × R, where P is pages, F is forms and R is user roles, counting the anonymous visitor. The score places the application in a tier with a fixed price, which you know before we start.
The audit scans the infrastructure (perimeter, internal network and servers) and reviews policies. The pentest attacks a specific application, manually and role by role. They are complementary and are contracted separately.
The assessment reviews the code, architecture and platform from the inside against the five pillars; the pentest tests the application from the outside, like an attacker. For critical applications, it makes sense to do both.
A written authorization signed by the application owner, with scope, environments, testing windows and emergency contact. We do not start without it. If the application is hosted by a third party (hosting or SaaS), their permission is also needed.
We preferably test in preproduction. If there is none, in production within agreed windows and with an emergency contact. Exploitation is always controlled.
Yes: it is evidence of technical vulnerability management (control A.8.8 of ISO 27001:2022) and of periodic security review. The report includes the classified risks, the remediation plan and the retest evidence.
The network and infrastructure (that is what the cybersecurity audit is for), native mobile applications, social engineering and the remediation of findings, which is quoted separately.
Sign the authorization, provide a test environment and users for each role, appoint a technical and emergency contact, and fix the findings before the retest.
When was the last pentest of your most exposed application?
Tell us which applications concern you and what customers, insurers or auditors are asking of you.