New · Release 2026.04, Multi-tenant audit exports & SLA dashboards now liveSee changelog →
Cloud VAPT
Cloud penetration testing for AWS, Azure and GCP
Misconfiguration, not malware, is the leading cloud breach cause. We test IAM boundaries, storage exposure, network rules and workload vulnerabilities against your live cloud accounts.
Product illustration · sample data
Security & VAPT
A+ score
EngagementHTTP LabReport PDF
A+
Last scan · 2 hours ago
Critical vulnerabilities0
High severity2
Manual + imported4
Engagement reportReady
Product proof
Already live in the product
Infronest module
This engagement can align with shipped product capabilities in your tenant workspace.
Protected app route: /vapt
Platform
Included in the Infronest workspace
These capabilities ship in the product today—consulting adds human validation and attestation where required.
Automated web scanning
Scoped engagements
HTTP Lab
Manual & imported findings
Analyst workbench
Audit-ready reports
Capabilities
What you get
Delivered with AI-assisted engineering and human review on architecture, security, and production readiness.
IAM roles, trust policies and privilege-escalation paths
Publicly exposed storage, databases and endpoints
Security group and network ACL review
Secrets in code, environment variables and images
Container and workload vulnerability checks
Workflow
What teams can do here
Step 1
Scope accounts
Step 2
Audit configuration
Step 3
Test exploitability
Step 4
Report and retest
How it works
How it works
01
Scope accounts and access
Agree which AWS, Azure or GCP accounts are in scope and provide read-only credentials or a role for configuration review. Live-account testing runs under written authorisation.
02
Audit configuration automatically
The cloud scanner reviews IAM, storage exposure, security groups and network ACLs; credentialed CIS checks and a secrets scanner look for benchmark drift and leaked keys in code, environment variables and images. Container and workload checks run where relevant.
03
Analyse attack paths (human-led)
Misconfiguration, not malware, is the leading cloud breach cause. A reviewer traces IAM privilege-escalation and internet-to-data attack paths that automated checks flag but cannot judge in context.
04
Report against CIS and re-test
Findings are mapped to CIS Benchmarks and provider guidance with CVSS scoring, then re-tested after remediation to confirm the gaps are closed.
Example
A worked example
Say a 25-person startup faces its first enterprise security questionnaire with everything in one AWS account. Over a read-only role, the scanner surfaces a public-read S3 bucket, an IAM user with a wildcard policy and CloudTrail disabled in one region, while the secrets scanner catches an access key committed to a public repo. A reviewer chains the wildcard policy and the open bucket into a demonstrable internet-to-data path and puts it at the top of the report. The team scopes the policy down, rotates the key and enables CloudTrail — and a re-scan days later shows every CIS-mapped finding closed.
FAQ
Frequently asked questions
What level of access to our cloud account do you need?
For configuration and IAM review, a read-only role or credentials is enough and is the safest option. Anything beyond read-only is agreed in scope first and only used with your written authorisation.
Which cloud providers do you cover?
AWS, Azure and GCP. The scanner selects provider-appropriate checks for IAM, storage, network rules and workloads based on the account you connect.
How much does a cloud security review cost?
Cloud configuration reviews are usually quoted per account and often sit below full pentest pricing. For market context: a focused web application penetration test in India typically costs ₹1.5–4 lakh (USD 2,000–5,000), and combined network + web VAPT for a mid-size environment ₹5–15 lakh (USD 6,000–18,000). Infronest engagements start at ₹36,750 per application — see the VAPT hub.
How long does a cloud configuration review take?
A single-account, read-only review typically completes in about a week including the human attack-path analysis; multi-account estates trend to two or three weeks. These are typical industry ranges — a scoped web application test, by comparison, usually runs one to three weeks.
What do you mean by CIS Benchmark alignment?
The CIS Benchmarks are widely used hardening baselines for each cloud provider. We map findings to the specific benchmark controls they implicate so you can see where your configuration drifts from that baseline — it is a mapping, not a certification we grant.
Do you test IAM privilege-escalation paths?
Yes, as a reviewer-led step. Automated checks surface over-broad policies and trust relationships; a human then reasons about whether they chain into a real privilege-escalation or internet-to-data path, because that judgement needs context a scanner lacks.
Is cloud testing safe to run against live accounts?
Configuration review with read-only access is non-intrusive and safe against live accounts. Any active testing that could affect running workloads is scoped, scheduled and authorised in writing before it happens.