This repository holds the code for each Vulcan check's main binary.
Currently there's no vendoring provided for this project.
Current list of Checks
- vulcan-dkim - Checks if a domain (asset with a SOA record) have valid DNS configuration for DKIM
- vulcan-spf - Checks if a domain (asset with a SOA record) have valid DNS configuration for SPF
- vulcan-dmarc - Checks if a domain (asset with a SOA record) have valid DNS configuration for DMARC
- vulcan-ipv6 - Checks for IPv6 presence
- vulcan-exposed-amt - Checks if an asset has the Intel AMT port exposed and whether is it vulnerable or not
- vulcan-exposed-ssh - Checks SSH server configuration for compliance with Mozilla OpenSSH guidelines
- vulcan-exposed-ftp - Checks if an asset has open FTP well known ports and if they allow anonymous logins or vulnerable to bounce attack
- vulcan-smtp-open-relay - Checks for exposed SMTP, and if they are open relay
vulcan-csp-report-uri - Checks if an asset (site) has a proper defined CSP header and if violations are being reported to Argus- vulcan-exposed-varnish - Checks if an asset is a Web Cache, and also if it is a Varnish
- vulcan-exposed-http - Checks if an asset has open HTTP well known ports
- vulcan-exposed-db - Checks if an asset has open database well known ports
- vulcan-heartbleed - Checks if an asset is vulnerable to heartbleed vulnerability
- vulcan-lucky - Checks if an TLS asset is vulnerable to LuckyMinus20 attack
- vulcan-s3-takeover - Checks for a vulnerability related to domain names pointing to a S3 static website when the S3 bucket has been deleted
- vulcan-tls - Analyzes TLS health of an asset
- vulcan-wpscan - Checks Wordpress sites for vulnerabilities using the open source wpscan utility
- vulcan-exposed-bgp - Checks for exposed BGP port on Internet routers
- vulcan-exposed-router-ports - Checks if an asset has open router well known ports
- vulcan-mx - Looks for MX DNS Records on a given domain
- vulcan-certinfo - Extracts information about SSL/TLS certificates
- vulcan-nessus - Runs a Nessus scan
- vulcan-gozuul - Checks if a Zuul Gateway is vulnerable to Remote Code Execution as specified in nflx-2016-003
- vulcan-http-headers - Analyzes the security of a website based on its HTTP headers
- vulcan-exposed-files - Check asset for sensitive files exposed on HTTP server
- vulcan-exposed-memcached - Checks if an asset has exposed a memcached server
- vulcan-retirejs - Checks for vulnerabilities in JS frontend dependencies
- vulcan-drupal - Checks for vulnerabilities in Drupal CMS
- vulcan-zap - Checks for vulnerabilities in web applications using OWASP ZAP
- vulcan-aws-trusted-advisor - Checks AWS Trusted Advisor for security findings
- vulcan-exposed-services - Checks if a host has any port opened by scanning the 1000 most common TCP and UDP ports
- vulcan-host-discovery - Performs a quick Nmap ping scan that identifies which hosts are up
- vulcan-masscan - Checks if a host has any port opened by scanning the whole TCP port range using masscan
- vulcan-exposed-endpoint - Checks if well known or provided paths are present in a http url
- vulcan-exposed-hdfs - Checks if an EMR cluster is exposed to the Internet
- vulcan-exposed-rdp - Checks if an Microsoft Remote Desktop service is exposed to the Internet
- vulcan-seekret - Checks if a Git repository contains secrets like passwords, API tokens or private keys
- vulcan-trivy - Checks if a Docker image uses vulnerable packages or dependencies using Trivy
- vulcan-exposed-http-resources - Checks if a web address exposes sensitive resources
- vulcan-prowler - Checks compliance against CIS AWS Foundations Benchmark