Monitor your AWS environments' security via Slack


Automatically scan your AWS environment to prevent vulnerabilities



Beacon. We help you keep your environment secure, so you can focus on your business.






Scan your AWS infrastructure for security vulnerabilities

Beacon demo screen 1





Get detailed information with actionable recommendations for securing your environment

Beacon scans for security vulnerabilities across various AWS services, including:

  • EC2
  • IAM
  • RDS
  • Route53
  • S3

We run scans for a variety of security and infrastructure vulnerabilities, including:

  • Security groups open to unrestricted access
  • Misconfigured S3 buckets
  • Un-encrypted data storage
  • Improperly backed up data storage
  • Infrastructure that is nearing account service limits
  • and more...

How do I run an on-demand security scan?

It's as simple as typing `perform security scan` in a command that @-mentions the Beacon bot, or a DM.

How do I start using Beacon?

It's easy to get started using the Beacon bot. Once you add the Beacon slack extension, a bot with an @beacon username will be added to your workspace. We'll create a channel where the Beacon bot will post its automated scan results and have you point us at the AWS infrastructure you'd like us to scan. Within 5 minutes, you'll be ready to scan for vulnerabilities on-demand and automatically.

How does Beacon get access to my AWS ecosystem to scan for vulnerabilities?

The Beacon bot scans our AWS infrastructure for security vulnerabilities by leveraging read-only audit access to your AWS account. When you add Beacon Bot, we'll guide you through the creation of a CloudFormation stack. This is a straightforward process that you only takes a few clicks. This stack creates an IAM Role that gives the bot read-only permissions to your AWS account. Beacon can't configure, create, or delete things in your account. You can remove the access you have granted at any time by deleting the stack that is created.

Will you create any resources (EC2 instances, S3 buckets, etc.) in order to scan for vulnerabilities?

Nope. We won't make any changes to your existing infrastructure, nor add nor remove any components.

Where does the Beacon bot post the results from its automated scans?

By default, the Beacon bot will create a new channel, #beacon_scans, and post its results there. You can change the channel where it posts the scans results from its automated scans at any time using the `configure` command.

Want to know more?


Questions about Beacon?





Privacy     Contact