Discover
Build an outside view from public internet records and confirm what belongs to you.
See yourself from the outside—before someone else does.
BrutClad keeps checking what an attacker can see and reach from the internet, every time your exposure changes.
Outside-in view / Authorised scopeExposure change detected
PATH / 04 Internet edge → Core serviceEvidence captured
Public reports reviewed63
1 Jan 2024–27 Aug 2026
Saudi ransomware victims named10 → 24 → 13
2024 / 2025 / 2026 YTD
Public-facing systemsCommon reported route
Where the way in was disclosed
The operating questionWhat is exposed today?
Not only at the annual check
A small external gap can become a route to the core.
6TBReported data loss in one public Saudi case reviewed
01Internet entry
A public-facing system provided the reported starting point.
02Credentials
Staff login credentials were reportedly taken from the network.
03Core access
The path reached machines supporting wider operations.
04Data removal
Ordinary transfer tools were reportedly used to copy data out.
Public reporting is incomplete and not every claim is independently confirmed. This example illustrates why connected attack paths matter; it does not imply BrutClad would have prevented a past incident.
Test what attackers actually find from the outside.
What goes wrong
Exposed websites and databases
Open admin and remote-access doors
Forgotten systems and drifting settings
Weak app-to-app permissions
Small gaps that link into a path
Connected devices, where authorised
What BrutClad tests
Website testing
Internet-facing infrastructure audit
Exposure discovery and monitoring
API testing
Attack-path analysis
Separately scoped device testing
What you get
Confirmed findings
Repeatable proof
What to fix first
How to fix it
Exposure-change monitoring
Rechecks after fixes
Leadership reporting
Clear scope boundaries
Outside-in testing covers only the internet-facing assets you authorise. Visibility depends on scope, timing, test accounts, rate limits and agreed quiet periods. It sits alongside internal monitoring, incident response and audit work; it does not replace them.
One cycle that repeats—
instead of one report a year.
Test
Perform authorised testing within agreed timing, rate limits and stop rules.
Chain
Join separate weaknesses into credible paths toward important systems.
Prioritise
Rank confirmed exposure by real risk, supported by reproducible proof.
Verify
Re-check completed fixes and preserve evidence of what changed.
Monitor
Review new sites, services and exposure changes in the next cycle.
Authorised
scope
scope
Proof for technical teams.
Clarity for leadership.
Visible asset inventory
A current view of the internet-facing systems discovered within agreed scope.
Confirmed technical evidence
Repeatable findings, practical fixes and context showing how gaps may connect.
Exposure alerts and rechecks
Visibility when new services appear and verification after priority fixes.
Leadership-ready reporting
A concise risk view plus a summary letter describing scope, dates, methods and limits.
Start with one baseline.
Then keep it current.
We map it.
Build the initial public view, then confirm with you which systems are yours.
You set the rules.
Agree what may be tested, how hard, quiet periods, stop rules and contacts.
First full check.
Onboarding begins in week one; the baseline is planned for weeks two to four.
Then it repeats.
Re-test changes, verify fixes and review newly visible systems first.
The first decision