Server-side request forgery turns your own server into an attacker's proxy — reaching internal systems and, in the cloud, stealing credentials from the metadata service. This is dedicated SSRF testing of every place your application makes a server-side request, delivered as a focused part of a full web application penetration test.
SSRF has become critical in the cloud era: one forgeable request can hit the metadata endpoint and hand an attacker your cloud keys. We test every URL fetch, webhook, import and preview feature, and confirm blind SSRF with out-of-band callbacks.
SSRF is deceptively small on the surface and devastating underneath — a single feature that fetches a URL can chain into cloud takeover. Proving it, especially blind SSRF, takes controlled infrastructure and manual skill a scanner does not have.
What we test
Basic and blind server-side request forgery
Cloud metadata access (169.254.169.254)
Internal service and port discovery via SSRF
Protocol smuggling (gopher, file, dict)
DNS rebinding and redirect-based bypass
Filter and allow-list bypass techniques
Common vulnerabilities we uncover
Cloud credential theft via metadata SSRF
Internal-only service access from the internet
Blind SSRF confirmed via out-of-band callbacks
Port scanning of the internal network
RCE via SSRF-to-internal-service chains
Sensitive internal data exposure
Our methodology
Scoping & rules of engagement. We agree objectives, targets and boundaries for your ssrf testing, so testing is safe, authorized and focused on what matters to your business.
Reconnaissance & mapping. We enumerate the full attack surface in scope, building a complete picture before any exploitation begins.
Manual exploitation. Our senior testers chain vulnerabilities by hand — going far beyond automated scanners — to prove real, demonstrable impact.
Analysis & reporting. Every finding is triaged, risk-rated with CVSS and written up with a copy-paste reproduction and clear remediation.
Remediation support & free retest. We support your team through the fixes and retest the remediated issues to confirm they are genuinely closed.
Tools & techniques
We enumerate every server-initiated request and attempt to redirect it inward — to the cloud metadata service, to internal hosts, and across protocols — using out-of-band detection to catch blind cases. Any allow-list or filter is tested for bypass rather than trusted.
For the cloud side of the risk this pairs with our AWS penetration testing and cloud configuration review, and it sits within full web application penetration testing.
When you need this engagement
Your app fetches URLs, imports, webhooks or previews
You run in AWS, Azure or GCP with metadata endpoints
You proxy, render or process user-supplied resources
You want to know what an SSRF could reach internally
You need confirmed proof, including for blind SSRF
What you receive
Confirmed SSRF findings with proof
Out-of-band evidence for blind cases
Reachable internal targets documented
Allow-list and egress remediation guidance
Attestation letter where required
Complimentary retest after fixes
What’s included in your report
Every ssrf testing engagement concludes with a comprehensive, board-ready report and a working session to walk your team through it. Your report includes:
An executive summary with overall risk posture for non-technical stakeholders
Detailed technical findings, each with a step-by-step, copy-paste reproduction
CVSS v3.1 severity ratings and business-impact context for every issue
Prioritized, actionable remediation guidance your engineers can apply directly
A complimentary retest to confirm fixes and update finding status
A formal attestation letter for customers, auditors and compliance programs
Standards & frameworks
OWASP Top 10 A10: SSRFOWASP WSTGCWE-918NIST SP 800-115
Outcomes you can expect
After your ssrf testing, you will have clear, evidence-based visibility into your real security risk — not a scanner’s guesswork. You will know exactly which weaknesses an attacker could exploit, what the business impact would be, and the precise steps to fix them in priority order. Teams use our findings to close critical gaps, satisfy customer and regulator security requirements, and demonstrate due diligence to their board. With a complimentary retest included, you also get documented proof that the issues are genuinely resolved.
Engagement details & logistics
Every ssrf testing starts with a short, no-obligation scoping call to understand your goals, environment and constraints, followed by a fixed-price proposal and a clear statement of work. Most engagements are delivered fully remotely, with on-site work arranged where it genuinely adds value. Throughout testing we maintain an agreed communication cadence and escalate any critical, high-impact finding to you immediately rather than waiting for the final report. All work is performed under a signed NDA with strict data-handling controls, using safe, non-disruptive techniques and carefully coordinated rules of engagement to protect your production systems. On completion you receive your report and a walkthrough session, followed by a complimentary retest once your fixes are in place. Typical engagements are booked one to three weeks in advance, and urgent or pre-deadline testing can often be accommodated — just ask at hi@agentoffense.com.
Why organizations choose AgentOffense
Our ssrf testing is delivered by senior offensive-security engineers who test the way real attackers do — manually, creatively and with a relentless focus on proving genuine, demonstrable impact. Here is what sets our engagements apart:
Manual, exploit-driven testing that chains vulnerabilities the way a real attacker would, going far beyond what automated scanners can find.
Reproducible proof for every finding, with copy-paste reproduction steps your engineers can follow and independently verify.
Honest severity calibration so you invest in fixing what genuinely matters and avoid wasting effort on false positives and noise.
Clear, business-focused reporting that speaks to engineers and executives alike, tying every issue to real-world impact.
A complimentary retest included, so you get documented proof that your fixes actually close the attack path.
Responsible, collaborative delivery with a named point of contact and secure handling of all data throughout the engagement.
Explore related services
SSRF Testing is frequently scoped alongside our other offensive-security services for broader coverage. Explore related engagements that complement it:
Web Application Penetration Testing — Manual web application penetration testing against the OWASP Top 10 and business-logic flaws. Exploit-driven testing with…
AWS Penetration Testing — AWS penetration testing — IAM privilege escalation, S3 and storage exposure, SSRF-to-metadata, and misconfiguration review mapped…
API Penetration Testing — REST and GraphQL API penetration testing against the OWASP API Top 10 — BOLA, BFLA, mass…
How much does SSRF Testing cost?
Every ssrf testing is scoped and priced individually, so you pay for exactly the coverage you need — with no hidden extras. After a short, no-obligation scoping call we send a fixed-price quote, usually within one business day, with clear deliverables, a firm timeline and a complimentary retest included. The price of your ssrf testing depends on the size and complexity of the target and the depth of testing required, so you always know the cost up front before any work begins.
