800+ IT
News
als RSS Feed abonnieren📚 Smogcloud - Find Cloud Assets That No One Wants Exposed
💡 Newskategorie: IT Security Nachrichten
🔗 Quelle: feedproxy.google.com
Find exposed AWS cloud assets that you did not know you had. A comprehensive asset inventory is step one to any capable security program. We made smogcloud to enable security engineers, penetration testers, and AWS administrators to monitor the collective changes that create dynamic and ephemeral internet-facing assets on a more frequent basis. May be useful to identify:
- Internet-facing FQDNs and IPs across one or hundreds of AWS accounts
- Misconfigurations or vulnerabilities
- Assets that are no longer in use
- Services not currently monitored
- Shadow IT
-
Install and setup golang
-
Install smogcloud using the following command
go get -u github.com/BishopFox/smogcloud -
Set up aws environment variable for the account you wish to query. We suggest utilizing a read-only Security Auditor role. The following commands can be used to set environment variables:
export AWS_ACCOUNT_ID='' # Describe account
export AWS_ACCESS_KEY_ID='' # Access key for aws account
export AWS_SECRET_ACCESS_KEY='' # Secret key for aws account -
Run the application
smogcloudor
go run main.go
Supported services for extracting internet exposures:
* API Gateway
* CloudFront
* EC2
* Elastic Kubernetes Service
* Elastic Beanstalk
* Elastic Search
* Elastic Load Balancing
* IoT
* Lightsail
* MediaStore
* Relational Database Service
* Redshift
* Route53
* S3AWS Patterns
From studying Open API documentation on RESTful AWS endpoints we determined these are the patterns of exposure URIs that you may find in AWS accounts. It is important to understand how to interact with these native services to test them for vulnerabilities and other misconfigurations. Security engineers may want to monitor Cloudtrail logs or build DNS monitoring for requests to these services.
- s3
- https://{user_provided}.s3.amazonaws.com
- cloudfront
- https://{random_id}.cloudfront.net
- ec2
- ec2-{ip-seperated}.compute-1.amazonaws.com
- es
- https://{user_provided}-{random_id}.{region}.es.amazonaws.com
- elb
- http://{user_provided}-{random_id}.{region}.elb.amazonaws.com:80
- https://{user_provided}-{random_id}.{region}.elb.amazonaws.com:443
- elbv2
- https://{user_provided}-{random_id}.{region}.elb.amazonaws.com
- rds
- mysql://{user_provided}.{random_id}.{region}.rds.amazonaws.com:3306
- postgres://{user_provided}.{random_id}.{region}.rds.amazonaws.com:5432
- route53
- {user_provided}
- execute-api
- https://{random_id}.execute-api.{region}.amazonaws.com/{user_provided}
- cloudsearch
- transfer
- sftp://s-{random_id}.server.transfer.{region}.amazonaws.com
- iot
- mqtt://{random_id}.iot.{region}.amazonaws.com:8883
- https://{random_id}.iot.{region}.amazonaws.com:8443
- https://{random_id}.iot.{region}.amazonaws.com:443
- mq
- https://b-{random_id}-{1,2}.mq.{region}.amazonaws.com:8162
- ssl://b-{random_id}-{1,2}.mq.{region}.amazonaws.com:61617
- kafka
- b-{1,2,3,4}.{user_provided}.{random_id}.c{1,2}.kafka.{region}.amazonaws.com
- {user_provided}.{random_id}.c{1,2}.kafka.{region}.amazonaws.com
- cloud9
- https://{random_id}.vfs.cloud9.{region}.amazonaws.com
- mediastore
- https://{random_id}.data.mediastore.{region}.amazonaws.com.
- kinesisvideo
- https://{random_id}.kinesisvideo.{region}.amazonaws.com
- mediaconvert
- https://{random_id}.mediaconvert.{region}.amazonaws.com
- mediapackage
- https://{random_id}.mediapackage.{region}.amazonaws.com/in/v1/{random_id}/channel
- elasticbeanstalk
- https://{random_id}.{user_provided}.elasticbeanstalk.com
- cognito
- https://{user_provided}.auth.{region}.amazoncognito.com
- Oscar Salazar - Initial work - Bishop Fox
- Rob Ragan - Initial work - Bishop Fox
@sweepthatleg - Brandon Gaudet - Initial work - Bishop Fox
We do our best to maintain our tools, but can't always keep them as up to date as we'd like. So, we always appreciate code contributions, feature requests, and bug reports.
Thank you for inspiration
