ScanTitan checks what the internet can reach in your cloud. Test whether an S3, Google Cloud Storage or Azure Blob container allows anonymous listing, and assess cloud-hosted websites and servers as public assets. It does not connect to your cloud accounts, and object contents are never downloaded.
Cloud vulnerability scanning is the automated search for weaknesses in a cloud environment: exposed storage, misconfigured services, vulnerable software and unpatched workloads. Scanners reach the environment in three ways, and each one sees something different.
ScanTitan works from the outside and shows what the internet can reach, the way an attacker enumerates your cloud. It needs nothing from you except an address to check. For everything inside the account, use a connected posture tool, an open-source auditor, or your provider's own scanner. For other assets, see the ScanTitan website vulnerability scanner.
Each provider names the same mistake differently. The check tests anonymous listing on all three and never downloads object contents.
Check: anonymous listing of the bucket.
Fix: turn on S3 Block Public Access and review the bucket policy and ACLs for public grants.
Check: anonymous listing of the container.
Fix: set the container access level to private and disable anonymous blob access on the storage account.
Check: anonymous listing of the bucket.
Fix: remove allUsers and allAuthenticatedUsers and enforce public access prevention.
These get marketed as one thing and they are not. An external scan needs nothing from you and sees what an attacker sees. A connected assessment reads your account through a role you grant and sees what is configured inside it. ScanTitan offers the external scan.
Access needed: none. You enter a storage container or website address. It sees public storage, cloud-hosted websites and servers with a public address. It cannot see account configuration, identities or anything without a public address.
Access needed: a role in your cloud account. It would see configuration, identities and workloads inside the account. ScanTitan does not offer this, so use a connected posture tool or an open-source auditor for it.
The damaging cloud incidents are rarely exotic: storage left open, an identity with more power than anyone realised, a management port exposed to the internet. Some of these can be seen from outside, others only from inside the account.
| Vulnerability | What it looks like in practice | Visible from outside? |
|---|---|---|
| Public storage containers | Anonymous listing or reading exposes object names and sometimes data. ScanTitan tests listing on S3, Google Cloud Storage and Azure Blob. | Yes |
| Management ports open to the internet | SSH, RDP and database ports reachable from the internet. Assessed on a public IP or server asset (Business plan). | Yes |
| Unpatched cloud servers | Public servers running software with published CVEs, ranked by CVSS, EPSS and CISA KEV status. | Yes |
| Over-permissive identity roles | A role with more power than needed lets one stolen key reach much more. It needs account access, which ScanTitan does not use. | No |
| Missing encryption or logging | Settings inside the account decide whether data is encrypted and whether attacks leave a trail. | No |
| Leaked credentials | Keys committed to code or left in configuration. This needs a secrets-scanning tool, which ScanTitan does not provide. | No |
Visible from outside means a scan with no cloud account access can find it.
Yes. Each major provider has a scanner that runs inside your account. They see your workloads and configuration, but not what an outsider sees.
Scans workloads such as EC2 instances and container images inside an AWS account.
Assesses security posture and workloads across Azure resources from inside your subscription.
Surfaces vulnerabilities and misconfigurations across Google Cloud resources from inside your organization.
An external scan fills what native tools cannot see. Native tools see inside your account. ScanTitan sees what an outsider sees: public storage, websites and servers, with no access to your account.
Open-source auditors are excellent and free, and native tools are already in your account. The table records how each one reaches your cloud and what it is best for. ScanTitan is the outside-in option.
| Feature | ScanTitan | Prowler | ScoutSuite | Cloud-native tools |
|---|---|---|---|---|
| Access needed | None, public targets only | Credentials you provide | Credentials you provide | Runs inside your account |
| Checks account configuration and identities | Not covered | Yes | Yes | Yes, per provider |
| Tests public storage from the outside | Yes, anonymous listing | Reads configuration | Reads configuration | Reads configuration |
| Price | Free check, paid plans for assets | Open source | Open source | Varies by provider |
| Best for | What the internet can reach | Auditing AWS, Azure and Google Cloud configuration | Multi-cloud configuration audits | Workloads and posture inside one provider |
Based on each tool's public documentation. ScanTitan does not check account configuration, so it complements these tools rather than replacing them.
Start from the question you need answered, then check the access each tool needs and how it ranks findings.
Seeing inside the account needs a connected or agent-based tool. Seeing what the internet can reach needs an external scan.
A tool that needs a role in your account adds to your own risk surface. An external scan needs none.
Prefer ranking by CVSS, EPSS and CISA KEV status over raw severity, so the first fix is the one most likely to be used.
The check runs from outside and needs no cloud account and no ScanTitan account.
We would rather tell you now than after you sign up.
The external check needs nothing from you, and it never downloads object contents.
Reviewed by Obaida Al-Sulaiman, Information Security Manager