Forgotten assets are the easiest way in
Every launch, trial or new provider leaves behind subdomains and services that nobody tracks. These assets usually sit outside patching and monitoring, and they are the first thing an attacker looks for.
An external security assessment covering your web apps, APIs and mobile apps, plus subdomains, public IP addresses and exposed services. Tested manually by Saudi researchers with a real attacker's mindset, and only within the scope you approve.
Attackers do not start with the one app you chose to test. They map everything you have on the internet, then go in through the weakest point: a forgotten subdomain, an exposed admin panel, a test environment nobody closed. A full external assessment shows you your organization the way they see it.
Every launch, trial or new provider leaves behind subdomains and services that nobody tracks. These assets usually sit outside patching and monitoring, and they are the first thing an attacker looks for.
An API key in a forgotten file on a subdomain can be enough to reach your main application's data. Testing each system on its own misses these chains; a full assessment finds them.
The NCA Essential Cybersecurity Controls (ECC) and the SAMA Cyber Security Framework (CSF) include penetration-testing requirements. Our reports are documented in line with both, to help you evidence that you meet them.
Your internet-facing systems are the first thing your customers and partners interact with. Finding and fixing a vulnerability before an attacker does protects their data and your reputation.
We test internet-facing systems only: those you own or are authorized to test, and that you list in scope. Reliant's services do not cover internal networks or on-premise infrastructure.
We enumerate the subdomains, public IP addresses and exposed services that belong to the agreed domains, within the approved scope only. Any new asset found during reconnaissance is not tested until you add it to the scope.
We look for admin panels exposed to the internet, weakly protected login portals, and staging and test environments left open. We test them for weak authentication such as default credentials and missing login rate limiting.
We check DNS records that still point to services or providers you no longer use, a flaw that lets an attacker publish content under your domain. We also review DNS misconfigurations that leak information about your systems.
We review TLS settings, certificates and allowed protocols, security headers, and ports and services left open without need. A single misconfiguration can be enough to expose data in transit or open an unexpected way in.
We look for configuration files, backups, .git repositories and open directory listings, as well as API keys and access tokens left in public files or in JavaScript code.
We identify the versions of servers, content management systems, plugins and components reachable from the internet, then manually verify whether known vulnerabilities in them are exploitable instead of relying on the version number alone.
We test business logic, sessions and authentication including JWT, OAuth and SSO, and REST and GraphQL APIs, looking for IDOR, SQLi, XSS, SSRF and privilege bypass between users and roles.
We test iOS and Android apps together with the backend APIs they talk to, using OWASP MASVS / MASTG as the checklist. For example, we look for sensitive data stored on the device and keys embedded in the app.
We chain findings the way a real attacker does: a secret exposed in a forgotten test environment can grant access to the production API. We document the full chain so its real business impact is clear.
Testing is manual, performed by Saudi researchers ranked among the top 10 on bugbounty.sa, the Saudi Federation's national vulnerability-discovery platform, and led by co-founders with 3,900+ combined documented findings. We do not hand you automated scanner output formatted as a report. We start with reconnaissance within the approved scope, test each asset, then chain vulnerabilities the way an attacker would. Every finding is manually reviewed, verified and reproduced before it reaches you.
Send us your main domains and the web apps, APIs and mobile apps you want tested, or book a 30-minute consultation with a lead penetration tester to define the right scope.
You create a program on the platform listing in-scope and out-of-scope assets, from domains and public IP addresses to app links. You set the rules of engagement: testing windows, forbidden techniques such as DoS, rate limits and the escalation channel, along with a suggested budget.
Reliant reviews the scope and agrees the budget with you. The program runs under Reliant's standard Engagement Agreement, or under your own contract once Reliant accepts it, and an NDA is signed before any testing.
The assigned researchers start with reconnaissance within the approved scope, then test each asset and chain vulnerabilities. Reliant triages every submission, and an approved Critical or High finding can be sent to you immediately, ahead of the report.
You receive the report with every approved finding in your dashboard. You discuss each finding with Reliant through comments, and you may be asked for your view through Company review.
After fixing, you request a free retest while the program is in its report or retest stage, and you get the result as soon as the check is done.
You pay only if Reliant confirms at least one Critical or High severity finding. The fee is then the program's agreed budget: one amount for the whole engagement, with the invoice issued automatically with the report. If no Critical or High is confirmed, the invoice is zero and the test and its report are delivered free. Price depends on scope size, testing depth and timeline.
Share your requirements or book a 30-minute consultation with a lead penetration tester. You pay only if we confirm a Critical or High.