SolutionsAWS, Google Cloud & Azure
Find the open doors in your cloud accounts.
One wrong setting can make a storage bucket public or give a forgotten key full access. BurstLayer reads your cloud settings, finds these mistakes and fixes them with your approval.
Most cloud leaks start with a setting nobody noticed.
Cloud providers give you thousands of switches. A bucket marked public, a test server left running or an access key that never expires is enough for an attacker, and they scan for exactly these mistakes.
What goes wrong in cloud accounts
These mistakes are easy to make, hard to spot by hand and easy for attackers to find.
Public storage buckets
Files meant for your team that anyone with the address can download. We find them and make them private.
Keys with too much access
Access keys that can do everything, often years old. We show where each key is used and help you replace it.
Forgotten servers
Test machines left running with old software. We list them so you can patch them or switch them off.
Firewall rules open to everyone
Rules that let the whole internet reach a database. We narrow them to the addresses that need access.
Admins without a second login step
Admin accounts protected by a password alone. We flag every one of them.
Unusual activity
Logins from new countries or sudden changes to permissions. We alert you within minutes.
From public to private, with one approval.
Every storage bucket is listed with who can read it. When a private file store turns out to be public, you can close it from the same screen.
- Who can read every bucket, in plain words
- Fixes applied only after you approve
- A record of who changed what
- acme-app-assetsAnyone (on purpose)
- acme-invoices-2021Anyone on the internet
- acme-backupsOnly your team
- acme-logsOnly your team
How BurstLayer protects your cloud
We connect with a read-only role. We ask for permission to change something only when you approve a specific fix.
Read-only by default
The connection can look at settings and nothing else, until you approve a fix.
Checked all the time
Settings are checked again whenever they change, not once a quarter.
One-click fixes
Close a bucket, narrow a firewall rule or disable an old key with one approval.
A history of changes
See who changed what and when, across every account you connect.
Alerts on risky changes
A rule opened to the world or a new admin created gets reported within minutes.
All three clouds in one place
AWS, Google Cloud and Azure appear in one list with the same rules.
Connect with a read-only role.
In AWS, one command creates the role BurstLayer uses. Google Cloud and Azure connect the same way: sign in and approve read-only access.
$ aws cloudformation create-stack \--stack-name burstlayer-readonly \--template-url https://get.burstlayer.com/aws/readonly.yaml \--capabilities CAPABILITY_IAM✓ Read-only role created✓ Account connected. First check running.
You can read the template before you run it. It only grants permission to look at settings.
- 01
Create the read-only role
One command in AWS, or a sign-in and approval for Google Cloud and Azure.
- 02
Get your first report
Public buckets, old keys and open firewall rules are listed within minutes.
- 03
Approve the fixes
Each fix asks for the smallest permission it needs, only when you say yes.
The products behind it
Each one works on its own. Together they cover AWS, Google Cloud & Azure, from the network edge to the last line of code.
Questions, answered.
Can BurstLayer change my cloud settings?+
Only after you approve a specific fix. The default connection can read settings and nothing else.
Can I connect more than one account?+
Yes. Connect as many AWS accounts, Google Cloud projects and Azure subscriptions as you like and see them in one list.
Where is my data stored?+
In the region you choose, in the EU or the US.
See what your cloud accounts are showing the world.
Free for your first account. Connect with read-only access and get a report within minutes.